23 June 2026 · 6 min read
Discovery call to proposal in one afternoon
A repeatable workflow for turning a messy sixty-minute call into a priced, sendable document before you lose the thread — without writing from a blank page.

Most proposals are not late because they are hard. They are late because the work happens twice: once during the call, when everything is clear, and again three days later, when you sit down with cold notes and try to remember what the client actually meant by modernise. The fix is to compress the gap. Here is a workflow that gets from a discovery call to a document you can send in a single afternoon.
Take notes in the shape of a proposal
During the call, do not write chronologically. Keep four running headings on the page: Goals, Constraints, Scope signals, Numbers. Everything the client says drops into one of them. When they mention a launch tied to a conference, that is a constraint. When they say the team will handle their own copy, that is a scope signal. When they name a range, even vaguely, that is a number. You will finish the call with the skeleton of a proposal instead of two pages of prose to re-read later.
Ask the three questions that unblock pricing
Before hanging up, get answers to: what does success look like in six months, who else has to approve this, and what budget range are you working within. The last one is uncomfortable exactly once. Without it you are guessing, and a guess costs you either the project or your margin. If they will not name a figure, offer brackets — under ten thousand, ten to twenty-five, more than that — and let them point.
Draft within two hours
Memory of a conversation decays fast. Block two hours the same day and produce a full draft, deliberately imperfect. Do not chase phrasing; chase completeness. Every section present, every number filled in, placeholders marked clearly. A complete rough draft is easier to finish tomorrow than a beautiful half-document.
Use the structure, not a blank page
The document does not need to be invented each time. Cover note, client goals, scope, phased timeline, pricing with rationale, exclusions, next steps. That order works for a website build, a brand system, a data project or a retainer. If you paste your four-heading notes into Pitchscribe, you get exactly that skeleton back, filled with your own facts, in under a minute. What used to be the first two hours becomes the first two minutes, and your afternoon goes into judgement instead of typing.
Price before you polish
Set the numbers while the constraints are fresh. Pricing decisions made a week later drift, because by then the awkward parts of the project have faded and the optimism has not. Write the phase prices, then write the rationale sentence for each one immediately — if you cannot explain a line in a sentence, the line is wrong.
Edit as a reader, not as the writer
Take a fifteen-minute break, then read the draft as if you were the client's finance director. You are looking for three things: a number without a reason, a promise without a date, and a paragraph about you rather than them. Cut all three. Most drafts lose about a fifth of their length in this pass and get noticeably stronger.
Send the same day, with a short message
The email matters more than people think. Three sentences: thanks for the call, here is the proposal, here is the one decision I need from you. Attach the PDF rather than linking to a portal that asks the client to log in. Friction at the moment of reading is the last place you want to be clever.
Keep a follow-up rhythm
Agree the next contact point before you send: I will follow up Thursday if I have not heard back. Then actually do it. Two follow-ups, spaced four and ten days, are normal and expected; silence after sending reads as indifference. If the answer is no, ask one question — what tipped it? The pattern in those answers is the most useful pricing research you will ever collect.
Why the afternoon matters
Speed-to-proposal is not about looking eager. It is about arriving while the client still remembers why they called. A document that lands the same day is compared against the conversation you just had; a document that lands next week is compared against whatever the competition sent in the meantime. Same content, different context, very different odds.
Get the next article by email
One letter a month on pricing, scoping and closing better work. No spam, unsubscribe in a click.