How to write a proposal that gets approved

A proposal that does not get approved has usually failed for one of a small number of reasons, and almost none of them are "the trip wasn't good enough." More often, it is too long, too vague on price, structured around too many choices, or simply hard to act on: the client reads it, feels vaguely positive, and then does nothing, because nothing in the document told them what to do next.

One option beats three, most of the time

The instinct to offer three tiers, such as good, better, best, feels like it gives the client control. In practice, for most trips, it does the opposite: it hands the client a comparison problem instead of a decision. Faced with three similar-looking itineraries at three price points, many clients disengage rather than choose, because evaluating trade-offs across three options is genuinely more cognitive work than saying yes or no to one.

A single, well-built option based on what you already learned in the discovery conversation converts better for most trip types, because it puts the burden of thinking back on you, where it belongs: you are the one with the expertise, and a confident single recommendation reads as expertise, while three options can read as uncertainty about what the client actually wants. Reserve genuine multi-option proposals for situations where the client explicitly wants to compare, a real fork, like two different regions or two meaningfully different trip styles, not as a default structure.

Front-load the parts that answer "is this the trip I asked for"

Open with what the client actually cares about first: the overall shape of the trip, the headline experiences, why this specific itinerary answers what they told you they wanted. Do not open with logistics, hotel chain history, or a lengthy scene-setting introduction. Those belong later, if at all. A client scanning the first screen of a proposal should immediately recognise their own trip in it, not have to read three paragraphs to find out whether you understood the brief.

Pace it so nothing feels front-loaded or backloaded

A proposal that spends most of its length on the first two days and thins out toward the end reads as unfinished, even if the later days are just as well planned. Clients notice when detail drops off. Match the level of detail across the trip: each day or major segment gets enough specificity that the client can picture it, without some days reading like an afterthought.

Make the price impossible to miss and simple to parse

Pricing buried at the bottom of a long document, presented as a wall of line items, or split across multiple currencies without a clear total is one of the most common reasons a client stalls. State the total clearly, close to where the client will be making the decision, broken down only as much as is genuinely useful: what is included, what is not, any planning fee, and the payment schedule (deposit amount and date, balance amount and date). Do not make the client do arithmetic to find out what they are actually committing to.

If per-person and total figures both matter (common for group and family trips), show both, clearly labelled, rather than making the client guess which number applies to their whole party.

End with a specific, low-friction next step

A proposal should not end on the itinerary. It should end on an instruction. "Let me know your thoughts" is not a call to action; it invites a delay. "Approve below to confirm your deposit and lock in these rates" gives the client one clear action and a reason to take it now rather than later, particularly if rates or availability are genuinely time-sensitive (which is often true and worth stating honestly, not as manufactured urgency).

Keep unresolved items visibly unresolved

If part of the itinerary is still pending, such as a specific excursion not yet confirmed or a room category still being checked, mark it clearly as pending rather than presenting it as settled. A client who later discovers something in their "confirmed" proposal was actually still tentative loses trust in the rest of the document, even the parts that were genuinely locked in.

Set an expiry, and mean it

A proposal with no expiry implicitly tells the client there is no cost to waiting, which is rarely true: rates, room availability and exchange rates all move, sometimes quickly. If the proposal is genuinely time-sensitive, say so with a specific date, not a vague "subject to availability" that reads as boilerplate. And if a proposal does expire without a response, follow up once with a direct question rather than silently resending the same document: a client who has gone quiet usually has a specific reason, and a short, direct check-in is more likely to surface it than another copy of the same proposal landing in their inbox.

What this looks like put together

1. Open with the trip's shape and how it answers the brief
2. One well-built option, paced evenly across the whole trip
3. A clear, unmissable price with a simple payment schedule
4. Pending items marked as pending, not glossed over
5. A specific next action, with a reason to take it now

WaypointsX proposals are built from the trip itself and shared as a live link the client can approve directly: no separate document to keep in sync, and pricing, payment schedule and pending items stay accurate because they are pulled from the actual trip record. See how the itinerary looks to a client on the itineraries page.