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.

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.

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.

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.

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.

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.