Make the offer easy to assess

An offer should let a customer understand what they would be buying and what must happen for it to work. Attractive language helps little if the reader cannot distinguish an included output from an aspiration, a target date from a reserved slot or a fixed price from an estimate.

Fieldnote now has enough information to offer Harbour Services a defined document package. Its proposal should connect the customer’s problem to a specific piece of work. It should not imply that clearer documents will automatically increase revenue or eliminate every misunderstanding.

Start with the decision the customer faces

Use a short account of the situation and the intended result. For example: the current staff references describe package inclusions inconsistently; the proposed work will produce one approved reference and an agreed customer-facing summary from customer-approved service rules.

The statement should be recognisable to the customer. If it introduces a new problem or a promised result that was never discussed, revisit the conversation. A proposal is a poor place to conceal an unresolved diagnosis beneath confident writing.

Separate a deliverable from its hoped-for effect. A revised reference is a deliverable you can inspect. Fewer clarification calls is an outcome influenced by use, training, service complexity and other factors. You can explain how the deliverable is intended to help without guaranteeing the outcome.

Write for the reader who was not in the meeting

The person who decides is often not the person who had the conversation. Harbour Services’ owner, who approves the expenditure, may read the offer without having heard any of the discussion that shaped it. An offer that relies on shared context, such as “as discussed, the usual approach”, gives that reader nothing to assess.

Write each section so that it makes sense on its own. State the problem as the customer described it, the work proposed, what the customer must provide and what it costs, in plain sentences. Avoid internal labels and abbreviations. A useful test is to hand the draft to someone outside the business and ask them to explain back what is being bought and what the customer must do. Any hesitation marks a passage to rewrite.

Keep the offer short enough to be read

A long offer is not more convincing; it is more likely to be skimmed, and the parts that matter most, such as exclusions and dependencies, are the parts most likely to be missed. For a package of this size, two pages are usually enough.

Figure 1A two-page offer for a small package

1. 1The situationthe problem as the customer described it
2. 2The workoutputs, inputs, reviews and handover
3. 3What is not includedand what would need a separate decision
4. 4Timingthe dependencies and the slot
5. 5Price and termsfee, GST, payment schedule, changes
6. 6How to proceedthe single next step

Supporting material, such as an example of past work shown with permission or a longer explanation of the review process, can go in an attachment for readers who want it. The main offer should be complete without it.

Define the boundaries of the work

A useful scope identifies the outputs, their formats, the inputs required, the review process and the limits. Specificity prevents two reasonable people from interpreting the same phrase differently.

These entries illustrate a scope discussion; they are not a contract template. The precise terms need to suit the service, customer and applicable law. An exclusion should never be used to conceal a task that is necessary to deliver what the headline promises.

Figure 2The parts of an assessable scope

• Fieldnote document package
  • Outputsstaff reference and customer summary, within length limits
  • Inputscurrent documents, approved inclusions, one set of corrections
  • Reviewstwo rounds through one nominated contact
  • Handoverfinal files and a short discussion
  • Exclusionsservice design, legal review, website build
  • Changesassessed and agreed before extra work begins

Explain timing as a set of dependencies

A delivery date usually depends on more than the supplier’s speed. List the important inputs and approval points. Explain what happens if they arrive late. This is more useful than placing a broad disclaimer after an unconditional date.

Figure 3A delivery date is a chain of dependencies

1. 1Acceptance and initial paymentconditions agreed in the offer
2. 2Production slot reservedfor a stated period
3. 3Inputs suppliedapproved rules and current documents
4. 4Drafting and two review roundsvia one contact
5. 5Handoverfinal files and discussion

Fieldnote proposes to reserve a production slot once the agreed acceptance and payment conditions are satisfied. The customer supplies approved inputs before drafting begins and consolidates feedback within the agreed review windows. If a dependency slips, both sides review the schedule rather than assuming the team will absorb the delay through unpaid overtime.

Do not invent urgency. If a slot has a real hold expiry, say so accurately and explain the next available option. A false countdown can pressure a decision while damaging the credibility of the entire offer.

Say who will do the work

Customers buying a service are partly buying the people who will deliver it. An offer should say who will do the work, who the customer will deal with day to day, and how to reach them. For Fieldnote, that might be a sentence naming which of the two partners will lead the drafting and which will handle the final check and handover.

If any part of the work will be done by someone outside the business, such as the external reviewer budgeted in Chapter 5, say so, and say what that person will see. A customer who later discovers that their internal service documents were shared with a third party they were not told about has a legitimate complaint, however competent the reviewer. Naming the arrangement in advance turns a potential breach of trust into an ordinary, accepted part of the service.

Present the commercial terms together

Place the fee, tax treatment, payment schedule and any variable charges where the customer can readily assess them. If an item is estimated, label it as such. Explain the basis on which it may change. A small initial price followed by unavoidable undisclosed charges is not a clear offer.

The Australian Government’s guidance on preparing quotes explains the importance of clear quotation details and notes that an accepted quote can become a binding contract. Have appropriate terms reviewed when the work warrants it. Do not assume the word “proposal” makes commitments legally inconsequential.

Fieldnote’s educational example uses a A$3,600 fee with a proposed 40% initial payment and 60% later payment. A real offer must specify the actual payment triggers and due dates, along with relevant cancellation, change and other terms. The arithmetic alone does not establish a suitable contract.

Figure 4Proposed payment schedule

1. Initial payment, 40%A$1,440 · 40%
2. Later payment, 60%A$2,160 · 60%

Say how long the offer stands

An offer based on a capacity check and current costs cannot stay valid indefinitely. State a validity period, such as thirty days, and explain what happens after it: the price may be reviewed and the delivery slot may no longer be available. This is not a pressure tactic if it reflects a real constraint, and it should be stated as plainly as any other term.

Distinguish the validity of the price from the reservation of a slot. Fieldnote’s offer might say that the price stands for thirty days, while the delivery slot is held only until the end of next week, because another enquiry may need it. Both statements are true and useful; combining them into a single vague deadline would be neither.

Offer alternatives only when they solve different needs

Three price columns are not automatically helpful. Alternatives should reflect meaningful differences in scope, risk or timing. For Harbour Services, an assessment-only engagement may be useful if service rules remain unsettled. The full package becomes suitable once the rules and reviewers are clear. Website implementation would be a separate service, not an unexplained premium tier.

Explain what each option leaves unresolved. A cheaper diagnostic exercise may identify inconsistencies without producing final documents. The customer should not discover that limitation after purchase. Sometimes the right alternative is to defer the work until the necessary internal decisions have been made.

Handle requests to change the offer

Customers often respond to an offer with requests: a lower price, a shorter timeline, an extra output. Each is a reasonable thing to ask, and each should be answered by going back to the same evidence that built the offer.

A request for a lower price is best met by asking which part of the scope could change, as Chapter 5 described. A request for an earlier date goes to the capacity check: is there a slot, and what would it displace? A request for an additional output goes to the estimate: how many hours does it add, and does the price change? Answering in those terms keeps the conversation about the work rather than about who will give way.

Issue a revised offer as a new version, clearly dated and marked as replacing the earlier one, rather than agreeing changes piecemeal in email. Two versions of an offer circulating at once, each accepted by a different person, is a common and avoidable cause of disputes. The version number also lets the decision record show which offer the customer finally accepted.

Support claims with evidence

The ACCC’s guidance on false or misleading claims stresses accurate claims and reasonable grounds for what a business represents. Review the overall impression of the offer, including qualifications and omissions. Evidence about one past project does not establish a guaranteed result for every customer.

For this fictional business, that means describing the actual service and process rather than inventing testimonials, client logos or performance statistics. A sample document should be labelled as a sample. If a forecast is included, identify its assumptions and uncertainty. Relevant evidence builds understanding; exaggerated certainty creates a delivery obligation the work may never meet.

Trace every promise back to the record

Before sending the offer, check each statement against the decision record from Chapter 4 and the pricing work from Chapter 5. Every output should match something the customer said they needed. Every input the customer must provide should have been discussed. Every date should rest on the capacity check, and every amount on the estimate.

Items that cannot be traced are a warning. They may be helpful additions the customer never asked for, which add cost and dilute the offer. Or they may be assumptions that slipped in during drafting, such as a review round nobody agreed. Either way, remove them or raise them with the customer before the offer goes out. This check takes a few minutes and catches the most common source of later disputes: a promise one side remembers making and the other does not.

It also helps to read the offer once from the customer’s side, asking at each paragraph what they would have to do, decide or provide. Offers drafted from the supplier’s point of view tend to list what the supplier will do and leave the customer’s obligations implicit. Making them explicit, with dates where possible, is what turns a description of a service into a plan both sides can follow.

Make the response path explicit

End with a clear way to ask questions, request a change, decline or accept. State the period for which the offer remains valid if that limit is real. Record which version was accepted and ensure the delivery team can find it. A verbal discussion after the document was issued may have changed the agreement; resolve that difference before work starts.

Follow up once, at an agreed time

Agree in the conversation when the customer expects to decide, and follow up then, not before. One clear follow-up message, asking whether they have the information they need and whether anything in the offer needs clarifying, is courteous and useful. Repeated reminders that add nothing new tend to turn a considered decision into an irritation.

If the customer needs more time, ask what the decision is waiting for and agree a new date. If they decline, thank them, ask whether they are willing to say why, and record the answer without arguing. Declined offers are a valuable source of evidence: a pattern of price objections, misunderstood scope or poor timing tells the business something no successful offer can.

Exercise: read the offer as a newcomer

Ask someone unfamiliar with the project to identify the outputs, customer responsibilities, total price, payment timing and next decision. Any answer that requires your spoken explanation points to a gap. Revise the offer, then check that every significant promise appears in your cost and capacity assumptions.

A clear offer makes the decision easier without manufacturing pressure. The next chapter shows how to track that decision alongside other opportunities without confusing hopeful conversations with committed work.