You turn a discovery call into a better proposal by writing down what the client said in their own words, sorting it into goal, problem, scope, and constraints, and building the proposal around those points instead of a generic template. A proposal that mirrors the call shows you listened, and it gives the client something they can forward to whoever approves the spend.
This article covers the hour after the call, a confirmation email, how call details map to proposal content, and how to offer options. The questions to ask during the call are in what to ask on a freelance discovery call, and the document’s format is covered in how to write a proposal without overcomplicating it.
Capture the call while it is fresh
Details fade quickly, so spend about 15 minutes organizing notes soon after the call rather than the next day. Sort what you heard into buckets:
| Bucket | What to record |
|---|---|
| Goal | What the client wants to achieve and why now |
| Problem | What is going wrong today and what has been tried |
| Deliverables | What they expect to receive |
| Constraints | Budget, deadline, tools, brand rules, technical or legal limits |
| People | Who approves, who gives feedback, who supplies materials |
| Risks | Unclear points, bad past experiences, many stakeholders |
| Quotes | Exact phrases the client used about priorities or worries |
The last bucket matters most for writing. When a client says “we cannot afford another failed launch,” that wording belongs in the proposal.
If you want a recording, ask permission first. Rules on recording calls differ by place, and some require everyone’s consent.
Send a confirmation email first
A short email the same day catches misunderstandings before you invest hours writing. Something like:
“Thanks for the call today. To make sure I have it right: the goal is [goal], the main deliverables are [list], the target date is [date], and the budget is around [range]. [Name] approves the final work. I am still unsure about [question 1] and [question 2]. If I have anything wrong, tell me and I will build the proposal around the corrected version.”
A client who replies with corrections is engaged. A client who never answers may be a lower-priority lead, which is useful to know before you write a long document. How to chase one politely is covered in following up without sounding desperate.
Map what you heard to proposal content
This is where a proposal gains value. Each concern from the call should show up as something concrete.
| What you heard | What to put in the proposal |
|---|---|
| “We need more leads from the website.” | A goal statement tying deliverables to lead generation |
| “Our last freelancer disappeared.” | A communication plan with fixed check-in dates |
| “Several people need to approve.” | A named approver and a feedback process |
| “We need it before our event on the 15th.” | A timeline built backward from that date, with client deadlines |
| “Budget is tight.” | A tiered option or a phased approach |
| “We do not have photos or text yet.” | An assumption that materials arrive by a set date, or an optional add-on to create them |
Then follow the client’s order of thinking: summary of the goal, your approach, deliverables, timeline, price, terms, next step. Length should match the project; the checklist in what a proposal should include covers what must be present.
Offer options at different price points
Rather than one number, many freelancers present two or three choices. Options let the client choose a level instead of deciding yes or no, and they can reveal the real budget.
| Option | Includes | Best for |
|---|---|---|
| Essentials | Core deliverables, one revision round | Tight budget or a first project |
| Standard | Core deliverables, two revision rounds, one extra component | Most clients |
| Complete | Standard plus extra deliverables and a short support period | Clients who want more coverage |
Make the options meaningfully different, and only include versions you would be happy to deliver. If the call showed ongoing needs, a retainer can follow the first project; retainer vs project pricing compares the two. The price itself should rest on your floor and a realistic estimate, as in how to price freelance work without undercharging.
A short worked example
Suppose a prospect says: “We run a small landscaping company. People call us, but our website looks old and nobody fills out the contact form. We want to launch before spring, and the budget is around $3,000. My business partner signs off.” (An invented call, with illustrative numbers.)
A matching opening might read:
"Goal. Increase the number of quote requests that come through your website before spring, with a refreshed site that works well on a phone.
What I heard. The current site looks dated, the contact form is rarely used, and you want to launch by [date]. You and your partner approve the work.
Approach. I will redesign the five core pages, cut the contact form to four fields, and add a clear call to action on each page, using your existing photos.
Timeline. Kickoff [date], first draft [date], launch [date], provided I receive photos and feedback by the dates listed."
It names the goal, reflects the details, and states what the client must supply. It also avoids promising results, such as a number of leads, that the freelancer cannot control.
Check for gaps before sending
Read it the way a cautious stranger would, someone who might forward it to a colleague. Does it answer the stated goal? Are deliverables countable? Are assumptions about materials and approvals written down? Are revisions and changes to scope addressed? If you find an “it depends” you have not resolved, fix it first, and consider a short note on what is not included.
For large projects or unusual terms, have a qualified professional review the contract. Contract rules vary by state and country.
When possible, walk through the proposal on a short call rather than sending it cold. It lets you answer questions and notice reactions, and if you do send it by email, state the next step and a follow-up date.
When the client wants a number on the call
Some prospects ask for a price before you have finished asking questions. A quote given on the spot is usually a guess, and it is hard to walk back. A calmer answer is to explain that the number depends on scope, offer a range only if you can stand behind it, and promise a written proposal by a specific date. Something like: “I would rather give you a figure I can stand behind. Once I have written up what we discussed, I will send a proposal with a price by Thursday.”
If the client insists on a ballpark, say clearly what it assumes: “For something like this, projects often land between $X and $Y depending on how many pages and revisions are involved.” Then follow it with the confirmation email, so the assumptions behind the range are in writing.
Where this comes from
This article is based on commonly published freelance proposal and discovery practice, including guides that describe proposals as an overview, scope of work, deliverables, timeline, and price. It also rests on general project-scoping logic. No regulator sets a format for proposals. Examples and dollar figures are invented, and contract rules, prices, and market norms change, so check them with a qualified professional for your situation.
General information, not legal, tax, or financial advice.