Earn the next conversation

The end of a project is a chance to learn whether the work helped, where the process failed and whether a future conversation would be useful. It is not automatic permission to start selling again. A customer may be satisfied and have no further need; another may need help but be reluctant to raise a problem.

Fieldnote has delivered Harbour Services’ approved documents. The files exist, but that alone does not establish that staff use them or that misunderstandings have decreased. A proportionate review should examine those questions without claiming more evidence than is available.

Review use as well as delivery

Agree a suitable review point based on when the customer can use the output. Asking for an outcome immediately after handover may be premature. Waiting indefinitely loses useful detail. For this example, the internal training session creates a sensible opportunity to ask what happened in practice.

If a customer declines a review conversation, accept that and record it. The absence of feedback is still information about the relationship, and pressing for a review the customer does not want undermines the goodwill the review was meant to build.

Fieldnote asks which document staff used, where they still needed clarification and whether anything important was missing. It does not begin with “How much time did we save you?” because no dependable baseline has been established. If the customer reports an improvement, record the observation and its context rather than converting it into a general performance claim.

Compare what you can actually observe with the original purpose. The service rules may now be consistent, while the customer-facing summary is rarely used because staff cannot find it. That is a different problem from poor wording. A useful review distinguishes the quality of the output, its implementation and external influences.

It also helps to agree what a useful outcome would look like before asking. Fieldnote decides in advance that it would count the review as successful if it learned where staff still needed clarification and whether the summary was being found. That keeps the conversation from drifting into general satisfaction scores, which are pleasant to hear but rarely change what the business does next. A short list of specific questions, agreed internally beforehand, also makes reviews across different customers comparable, so that patterns can be noticed rather than remembered.

Figure 1Closing the learning loop

1. 1What was promisedthe accepted offer
2. 2What was deliveredversions, changes, handover
3. 3How it was usedobserved after a suitable interval
4. 4What we learnedeffort, input quality, usefulness
5. 5Next decisionselection, pricing, delivery, follow-up

Compare the estimate with what happened

The review with the customer looks outward. The team also needs an internal review, and the most useful starting point is the comparison between estimated and actual effort. This is an illustration for the Harbour Services package:

Figure 2Where the six extra hours went

Input review2 hours over estimate

Drafting2 hours over estimate

Customer discussion and reviews1 hours over estimate

Checking and corrections1 hours over estimate

Handover0 hours over estimate

The pattern matters more than the total. Four of the six extra hours came from the condition of the inputs, not from the writing itself. That points to a change in the offer, such as an input check before the price is fixed, rather than a general increase in the drafting allowance.

Hold a short team review

The customer review asks whether the work helped. A separate team review, held soon after the job closes and while details are fresh, asks how the work went. For a two-person business it can take twenty minutes and needs only three questions: what went well and should be kept, what took more effort than it should have, and what one or two changes would make the next job better.

Bring the evidence rather than impressions: the estimate and actual hours, the change and incident records, and the customer’s comments. Evidence keeps the discussion on the process rather than on who was at fault. A late edit error, for example, is more usefully discussed as a missing final check than as one person’s carelessness, because the check prevents the next error and the blame does not.

Keep the review short and regular. A brief review after every job builds a steady habit of improvement; a long review held only after a difficult job tends to become a search for someone to blame and is avoided after the first attempt.

Turn lessons into specific changes

A review that ends with “communicate better next time” changes nothing. Each lesson should become a specific change to a document, a checklist or a step, with an owner and a date. From the Harbour Services job, Fieldnote takes three:

1. Offer: add a short paid input review before the full package price is confirmed, for customers whose source documents disagree.
2. Delivery: add a final consistency check of every package name after the last edit, because the late edit introduced the error.
3. Kick-off: confirm all reviewers by name at the kick-off, because a reviewer joining late added a review cycle.

Make the change in the relevant template the same week, while the reason is fresh. Note the date and the job that prompted it, so that a later review can see whether the change helped.

Treat problems as decisions with consequences

When a customer reports a problem, first establish what happened, what is affected and whether an immediate action is needed to limit harm. Acknowledge the report without making unsupported conclusions about cause or liability. Give a clear response time and keep the customer informed if investigation takes longer.

In the fictional case, Harbour Services finds an old package name in a final document. Fieldnote checks the accepted inputs and discovers it introduced the error during a late edit. The team acknowledges the mistake, supplies a checked correction, identifies the affected version and confirms where it was distributed. It also improves its final consistency check.

Contrast that with a new package introduced by the customer after handover. The document may now need updating even though the original work met the approved requirement. Explain the difference with reference to the agreed scope and chronology. Avoid treating every complaint as extra work or every new requirement as a supplier failure.

Figure 3Two reported problems, two different responses

	Old package name in a final document	New package added after handover
Source	Within the agreed scope	Customer change after completion
Response	Correct it promptly	Offer an update as new work
Record	Factual note of the issue and fix	Change or new offer

Separate obligations from discretionary goodwill

Australian consumer guarantees can apply to qualifying purchases, including some business purchases. The ACCC’s consumer rights and guarantees guidance explains that these rights arise automatically where applicable. A remedy owed under law is not merely a goodwill favour. Check the circumstances and obtain advice when necessary rather than relying on a blanket “business customers are excluded” assumption.

After addressing applicable obligations and the agreed scope, the business may choose additional assistance. Record what it is offering and why. A modest help session might be worthwhile to clarify use; an open-ended promise to fix any future change is a different commitment. Generosity is easier to sustain when its boundaries are understood.

For an unresolved disagreement, maintain a factual record of the issue, relevant documents, proposed resolution and next step. Avoid using the prospect of a negative review as the sole reason to act. The decision should be defensible for a customer who never posts publicly.

Ask for feedback without scripting the answer

A useful feedback request permits criticism. Ask what worked, what required too much effort and what the customer would change about the process. An invitation that only welcomes praise will produce a flattering but incomplete picture.

Do not turn private feedback into a public testimonial without permission for that use. Confirm the wording and context, and do not add outcomes the customer did not describe. If you request public reviews, use a consistent process that does not pressure customers to give a favourable rating or conceal dissatisfied experiences.

Fieldnote can learn from one customer’s comments without treating them as representative of every buyer. If three customers mention confusing review instructions, that pattern justifies investigating the instructions. It still does not establish a precise percentage of the market that experiences the problem.

Measure repeat work with a meaningful denominator

Repeat purchasing depends on the service and observation period. A one-off document package may not need to be bought again soon. Counting every completed customer as a failed repeat sale after thirty days would misrepresent the business.

Suppose ten fictional customers completed work in a period. Six have subsequently reached a defined annual update window, and four of those six commission an update. The observed repeat-purchase proportion among that eligible group is 4 ÷ 6, or about 66.7%. The other four customers are outside this particular observation window. State the rule and the small count alongside the percentage.

Figure 4Repeat purchases with an honest denominator

Completed customers10

Reached the annual update window6 eligible

Commissioned an update4 66.7% of eligible

Do not quietly redefine eligibility to exclude customers who chose not to return. Establish the rule before examining outcomes, and separately record cancellations, uncontactable customers and known changes in need. A measure that improves only because inconvenient cases disappear is not useful learning.

Make follow-up serve a current need

A follow-up can be tied to an agreed review date, a known service change or a requested update. State that reason. Ask whether the conversation remains useful, and respect the customer’s response. Permission to complete a project does not establish blanket permission for unrelated marketing.

For Harbour Services, the next useful conversation may be before its planned annual package review. Record that timing if the customer wants it. If no continuing need exists, close the engagement clearly and make it easy to return later. A respectful ending is a valid commercial outcome.

Decide whether to seek more work with this customer

Not every customer is one the business should pursue further, and the end of a job is a good time to decide deliberately. Look at the evidence from the engagement: whether the customer supplied inputs on time, kept to the agreed review process, paid as agreed and treated the team respectfully, and whether their likely future needs match what the business does well.

A customer who fits on all counts is worth a follow-up at the agreed time. A customer whose needs have moved outside the business’s scope can be thanked and, where helpful, pointed elsewhere. A customer whose engagement was consistently difficult may still be served if they return, but on terms that address the difficulty, such as a fixed input deadline or a smaller first stage. Recording this decision in the pipeline means it is applied consistently, rather than rediscovered painfully the next time the customer calls.

Ask for introductions with care

A customer who valued the work may be willing to introduce the business to others with a similar need. Ask directly, at a natural point such as the review, and make it easy to say no. A useful request describes the kind of business that tends to benefit, so the customer can think of a specific person, rather than asking vaguely whether they know anyone who needs help.

Leave the introduction to the customer. Do not ask for a list of contacts to approach yourself, and do not treat an introduction as permission to add the new contact to a marketing list. If the introduced business becomes a customer, thank the person who introduced them. Any reward for referrals should be disclosed to everyone involved, as Chapter 3 described for referral partners.

Keep the job records in good order

Once the engagement is closed, decide what to keep, where and for how long. Keep what the business needs for its obligations, its tax records and future work: the accepted offer, the final deliverables, invoices, and the change and incident records. Remove working drafts and personal details that no longer serve a purpose, following the retention approach chosen in Chapter 4.

Store the records so that someone else in the business can find them. A future update for the same customer, a question about what was agreed, or a review of how a type of job usually runs all depend on records that are complete and findable. A closed job filed carefully is also the best starting point for the next offer to the same customer.

Exercise: close the learning loop

Review one completed engagement using four questions: What was promised? What was delivered? What happened when the customer used it? What should change in the next offer or delivery process? Assign one improvement to a person and date. Keep observations separate from explanations you have not tested.

The customer relationship now feeds evidence back into selection, pricing and delivery. The final chapter assembles these practices into a manageable thirty-day implementation.