The pitch and the proposal

Once you understand the problem, the pitch is short: here is what I would build, here is what it costs, here is when it is done. You are not convincing. You are prescribing. The proposal exists to let them say yes without another meeting.

Anchor on value, then state the price

Before the number, restate what this is worth using their own figures from discovery: "You told me what a new customer is worth, and the site is dropping calls. This pays for itself with a single job." Then say the price plainly and stop talking. Value first makes the number feel small; silence after makes it feel firm.

The proposal that closes itself

• Their problem, in their own words from the call. This is the most persuasive section and the one everyone skips.
• The package: exactly what is included, straight from your service menu. Scope text should be identical every time; consistency is what makes promises keepable.
• The price: build fee and monthly care plan, clearly separated, one option or at most two. Five options is a homework assignment, not a proposal.
• The timeline: kickoff, first look, launch. Dates, not durations, when you can.
• Proof: one or two relevant links or screenshots. The demo site, if you built one.
• One clear next step: "Reply yes and I will send the deposit link and book your build week."

The quote-to-proposal flow

Mechanically, this should take you fifteen minutes, not an evening: your service menu already contains the scope and the price, the call notes contain their words, and the platform turns the quote into the proposal and the proposal into the invoice when they accept. Your agent can draft the personalized sections from your call notes while you drive home. Review, humanize, send.

One page beats ten

Long proposals are where deals go to die. Nobody reads page seven; they skim for the price and stall. One page (two with proof) says: this is simple, I have done it many times, you are in good hands. The confidence of brevity is part of the pitch.