Turn a conversation into a decision record

A productive customer conversation should leave both sides better able to decide. It should establish what matters, what is possible and what remains unknown. Its value is not measured by how many questions the seller asks or how enthusiastically the customer responds.

Fieldnote receives an enquiry from Harbour Services, a fictional maintenance business. The manager says, “We need a better brochure by the end of next month.” That sentence contains a proposed output and a date, but little evidence about the underlying problem. Quoting immediately would turn several assumptions into a promise.

Agree the purpose of the conversation

Begin with a short explanation of what you hope to establish and ask whether the customer wants to add anything. For example: “Let us understand where the current information causes difficulty, what needs to be ready and who would approve it. Then we can decide whether a document package is suitable.”

This is also a chance to set a time boundary. A focused initial discussion can identify the need for a separate paid diagnostic exercise. If answering the enquiry requires reviewing hundreds of documents or resolving complex technical questions, name that work instead of absorbing it into an unlimited sales call.

Avoid making the customer repeat information already supplied. Read the enquiry beforehand, bring the relevant questions and explain any uncertainty in your understanding. Preparation shows up in the usefulness of the conversation, not in an elaborate introductory speech.

Figure 1Shape of a productive first conversation

1. 1Agree the purposewhat to establish, and a time boundary
2. 2Find a recent event"What prompted the request?"
3. 3Clarify constraints and rolesresult, deadline, inputs, approvals, money
4. 4Summarise and invite correctionexpose misunderstandings early
5. 5Write the decision recordowner and date for the next action

Prepare in fifteen minutes

A short, consistent preparation routine makes most first conversations better. Before the call with Harbour Services, Fieldnote spends about fifteen minutes on four things:

Figure 2Fifteen minutes before a first conversation

• Avoid: Re-read the enquiry and any earlier messages
• Avoid: Look at the customer's public service information
• Avoid: Write the three questions that would most change the next step
• Do: x Note what you will not offer, so the boundary is ready if needed

The public information often shows the problem before the customer describes it: two pages that describe the same package differently, or a service list that has outgrown its layout. Noticing that in advance lets the conversation start from something concrete. The note of what will not be offered matters because boundaries are easier to state calmly when they were decided before the call than when they are improvised in response to an enthusiastic request.

Keep the preparation proportionate. Fifteen minutes suits a first conversation about a modest package; a complex or high-value enquiry may justify more, and a quick question from an existing customer may need none. The test is whether the preparation would change what you ask or say. If an extra half hour of research would not alter a single question, it is better spent on delivery work already promised to someone else.

Move from the request to a recent event

Fieldnote asks what prompted the brochure request. The manager describes two staff members giving different answers about whether an inspection is included in a maintenance package. The problem is now more specific: inconsistent explanations of an inclusion.

A useful next question is how the organisation currently decides what is included. If the approved rule is clear but scattered across documents, consolidation may help. If managers disagree about the rule, writing should wait for a business decision. The same customer complaint can lead to quite different work.

Ask about the consequences without supplying dramatic figures. “What did the team have to do to put that right?” invites evidence. “How much revenue are you losing every month?” presumes a measurable loss that the customer may not know. An uncertain answer should remain uncertain in the record.

Clarify constraints and decision roles

Explore the desired result, the reason for the deadline, the inputs available and the people needed to make a decision. A requested date may be linked to a launch, a meeting or simply an initial preference. Knowing the reason helps determine whether a smaller first release or a later complete package is useful.

Authority is often distributed. One person may manage the work, another approve wording and a third approve expenditure. Ask how those responsibilities work here. Do not assume a job title establishes the full decision process, and do not treat a useful contact as an obstacle because someone else signs the order.

Figure 3Who decides at Harbour Services

• The purchase decision
  • Manages the workday-to-day contact; consolidates feedback
  • Approves wordingconfirms service rules and inclusions
  • Approves expendituresigns the order

Money can be discussed directly and respectfully. Explain which scope variables affect the price and ask about the customer’s approval process or constraints. A customer may have no fixed budget because they are still learning what the work involves. That is different from being unwilling to pay. You still need enough information to decide whether preparing an offer is worthwhile.

Answer the price question honestly and early

Customers often ask about price in the first conversation, and avoiding the question tends to reduce trust. Where the price depends on scope, explain what it depends on and, if you can, give a range for typical work, making clear that a firm figure follows once the scope is agreed.

This is an illustration with fictional figures. Fieldnote might say: “A pack covering up to five services, with two rounds of review, has typically been in the range of A$2,000 to A$3,000. The main things that move it are the number of services, how settled the service rules are, and how many people review the draft.” That statement gives the customer enough to judge whether to continue, and it names the variables that the decision record will need to pin down.

Avoid a single number given before the scope is understood. It tends to become the customer’s reference point, and any later increase feels like a broken promise even when the scope has grown. A range with its reasons is more honest and more useful.

When the customer wants a proposal straight away

Some customers ask for a proposal at the end of the first call, before the important uncertainties are resolved. Writing one immediately can feel responsive, but a proposal based on guesses either overprices the work to cover the unknowns or underprices it and creates problems later.

A practical alternative is to send the decision record first, with the open questions clearly marked, and propose the proposal once they are answered. For Harbour Services, Fieldnote replies that it will send a fixed-scope offer within two working days of receiving the current documents and the owner’s confirmation of the inclusion rule. The customer gets a definite date, and the offer, when it comes, rests on evidence rather than assumption.

When the customer wants to start before details are settled

Sometimes a customer is ready to begin before the important questions are answered: the documents have not arrived, the approver has not been confirmed, but the deadline is close and they want work to start. Beginning on that basis can feel helpful, yet it usually means drafting from guesses and redoing the work once the real inputs arrive.

A better response is to offer a start that does not depend on the missing information. For Harbour Services, Fieldnote could begin by reviewing the documents already supplied and listing every place where they disagree, which is useful whatever the final scope. The writing itself starts when the owner confirms the inclusion rule. Stating this plainly, with the date by which the confirmation is needed to keep the training deadline, gives the customer momentum without committing Fieldnote to work it may have to discard.

Record any such agreement in the recap. “Work starts on the document review on Monday; drafting starts when the inclusion rule is confirmed” is a commitment both sides can check. “We’ll get going and sort out the details” is not.

Listen for corrections, not just confirmation

Periodically summarise your understanding and invite correction: “I have heard that the service rules are agreed, but staff use three different documents. Is that accurate?” A useful summary can expose a misunderstanding before it enters a proposal.

Silence, tone and body language can have many explanations. Do not diagnose a person’s motives from them or use unsupported percentages about how communication works. Ask a neutral clarifying question when something is unclear. Give the customer time to explain and allow them to decline a question that is not necessary.

Fieldnote initially writes that the deadline is a service launch. The manager corrects this: it is an internal training session. That changes the immediate deliverable. A concise approved reference for staff may matter more than a polished public brochure. Listening has altered the scope rather than merely built rapport.

Figure 4One correction changes the scope

	Before the correction	After the correction
Reason for the date	Public service launch	Internal training session
Main reader	Customers	Staff
Likely first deliverable	Polished public brochure	Concise approved staff reference

Include the people who decide

When more than one person shapes the decision, a conversation with only one of them can produce an agreement that the others later reverse. Where the approver of the wording or the expenditure is not on the call, ask whether they could join a short second conversation, or whether the contact would like a brief summary to share with them.

Make that summary easy to forward: a few lines stating the problem as the customer described it, what the work would and would not include, the inputs needed and the next step. Written for the absent decision-maker, it is often more useful than a full proposal, because it lets them correct a misunderstanding before anyone has invested in detailed pricing.

Recognise when the conversation should end

Sometimes the most useful outcome of a first conversation is a clear finding that the work is not a fit. The underlying problem may be a management disagreement no document can resolve, the timing may be impossible, or the customer may need a service you do not offer. Continuing the conversation in the hope that something will change usually costs both sides time.

Say so directly and kindly, summarise what you learned that might help them, and, where you can, suggest the kind of help that would suit. For Harbour Services, if the manager and owner turned out to disagree about the inclusion rule, Fieldnote would say that the writing should wait until that decision is made, and offer to return to the work afterwards. That is an honest conclusion, and it often brings the customer back once they are ready.

Create a record that can be corrected

The useful output is a short decision record, not a transcript of everything said.

Send a concise recap through the agreed channel and invite corrections. Distinguish what was agreed from what was proposed. “We discussed a possible start in November” does not mean “November is booked.” Identify an owner and date for the next action so the conversation does not end in an indefinite promise to stay in touch.

Send the recap the same day

The recap described above is most useful when it arrives while the conversation is fresh in both minds. Sending it the same day, or the next morning at the latest, gives the customer the best chance to correct anything misheard, and it shows that the business is organised. Keep it short enough to read on a phone, with the decision record attached or included, and end with the single next action and its date.

Keep only information the work needs

Customer records should help deliver the service. Avoid collecting personal details merely because they might be useful someday. Restrict access, avoid copying sensitive material into casual notes and decide how records will be retained and removed.

Australian privacy obligations depend on the business and its activities. The OAIC’s small business guidance explains that small-business status does not establish a universal exemption. Check applicability rather than assuming size settles the issue. Regardless of the legal position, explain why information is requested and use a proportionate collection process.

Exercise: repair a vague next step

Take the phrase “We will send something through soon.” Rewrite it to state the document or information, the responsible person, the intended date and the decision it enables. Then identify one fact you have inferred but the customer has not confirmed. Mark it as an assumption and decide whether it matters enough to clarify now.

A conversation is ready to become an offer when the important uncertainties are visible and manageable. The next chapter tests whether the proposed promise can support its price, its workload and its cash timing.