Discovery call questions to ask before a proposal

The best discovery call questions are the ones whose answers you can paste into a proposal. Ask about the problem, the outcome, what is in and out of scope, the deadline, who signs and the budget range, and close by agreeing when your proposal will arrive. Below, each question is mapped to the proposal section it fills, followed by a call script to copy and sample call notes turned into a proposal.

Why a discovery call decides the proposal

For a freelancer or a small agency, the discovery call has one job: to collect what you need for a proposal the client can say yes to without calling you back.

Generic lists of sales discovery questions are written for software teams qualifying a lead for a demo. You are about to commit to a scope, a price and a date in writing. So every question below is tied to a section of the proposal; if a question feeds no section, it can wait.

The questions, mapped to the proposal

The table is the short version; the sections after it give the wording and what to listen for. Treat the full list as a menu, not a questionnaire: follow the client's answers, and tick questions off as they come up.

The problem and the outcome

I open a proposal with the client's problem, not with a presentation of my company, so I need these answers in the client's own words.

• "What made you look for help now?" Listen for the trigger: a launch, a new hire, a complaint, a deadline.
• "What happens if you do nothing this year?" This tells you the cost of the problem, in their terms.
• "If this goes well, what is different in six months?" Write the answer down word for word; it is the outcome line in your summary.
• "How will you know it worked?" A number they already track is better than one you invent.

Scope: what is in and what is out

These decide whether you can count the deliverables. The guide to writing a scope of work turns the answers into a list a third party could check.

• "What must be in the first version, and what can wait for later?"
• "Which existing material do we reuse: text, images, accounts, code?"
• "Who writes the content, and who provides it by when?"
• "How many people give feedback, and how many rounds do you expect?"
• "Is there anything you assume is included that we have not talked about?"

That last question earns its place. A client should feel the proposal covers everything they asked for, and that only works if it says clearly what is in and what is out.

Timeline and decision

• "Is there a date this has to be live by? What happens if it slips?" A real deadline has a reason; a vague one can move.
• "When do you want to decide?" This is the date your proposal has to beat.
• "Who else needs to agree before this goes ahead?" Then: "Will they read the proposal, or hear about it from you?"
• "Who signs?" If that person was not on the call, write the summary for them.

Budget and price

Ask directly, after the scope questions, so the client has just heard how big the work is: "Projects like this vary a lot depending on scope. Have you set a range for it?" If they hesitate, offer the range you would expect for what you heard and ask where they sit within it. Ask who signs before this question: a range means little if the person who sets it is not on the call.

Don't decide for the client that they can only afford the basic version. Use the range to set your first option, then add a premium option they can opt into; the guide on three-tier pricing with a premium option shows how. If you price by the day, start from a day rate that covers your costs.

After launch and extra work

• "Who looks after this once it is live: you, us or someone else?"
• "Are there licences, hosting or subscriptions you expect us to manage?"
• "How do you usually handle small requests that come up during a project?"

Costs that continue after go-live belong in the proposal, not in a later email. So does your hourly rate for work outside the proposal: extra requests will come, and the proposal should already say what they cost. If the client wants you to look after it, write the recurring side as a retainer proposal.

Proof and fit

• "Have you worked with someone on this before? What went well, and what did not?"
• "Which of our past work made you get in touch?"

The answers tell you which cases to include. Pick the ones that match this client's problem, rather than adding the same cases to every proposal.

A call script and notes page to copy

Use this as your notes page during the call. Each heading is a section of the proposal, so after the call the notes are already in proposal order.

Template

Client: [Company], [name, role]. Date of call: [date]. Also deciding: [names, roles].

Opening (say this): "Thanks for the time. I'd like to understand the problem well enough to send you a proposal with a scope and a price. I'll ask some questions and take notes, and at the end I'll tell you when you'll have it. Does that work?"

The challenge: Trigger: [why now]. In their words: "[quote]". Cost of doing nothing: [answer].

Outcome: In six months: "[quote]". How they will measure it: [metric they already track].

Scope: Must have: [item, with a number], [item, with a number]. Later: [item]. Reuse: [text, images, accounts]. Content from: [who, by when]. Feedback: [people], [rounds]. Assumed included but not discussed: [answer].

Timeline: Live by: [date], because [reason]. Decision by: [date].

Decision: Signs: [name]. Reads the proposal: [names]. Was the signer on this call? [yes or no].

Budget: Range: [answer, or "not shared"]. My range given: [range]. Their reaction: [answer].

After launch: Looked after by: [who]. Ongoing costs to include: [hosting, licences, care plan]. Small requests handled by: [answer].

Fit: Past supplier experience: [answer]. Work of ours they mentioned: [case].

Close (say this): "Let me check I have this right: [problem], [outcome], [scope in one sentence], by [date]. What did I miss? I'll send the proposal on [day], and could we book a short call on [day] to go through it together?"

Worked example: from call notes to proposal

Below are sample notes from a fictional discovery call and the proposal sections they produce. The bakery, the people and all amounts are made up for this guide: replace them with your own.

Example

The call. A freelance web developer speaks with Tom Reyes, co-owner of Harbour Lane Bakery, which has two shops. His business partner, Anna, signs anything over €5,000 and was not on the call.

The notes, as written during the call.

• Trigger: "We lose Saturday cake orders because people can't get through on the phone." Christmas pre-orders start on 1 December.
• Outcome: "Half of the cake orders come in online, and the shops stop taking orders by phone on Saturdays."
• Must have: online shop for cakes with pre-order and collection at either shop. Later: delivery.
• Reuse: logo and product photos. Tom can write the product texts within a week of kick-off.
• Feedback: Tom and Anna, two rounds.
• Assumed included: "We thought you'd set up the payment provider too." (Not discussed before; added to scope.)
• Budget: "We were thinking €5,000 to €7,000." Developer: similar shops run €6,000 to €10,000, depending on stock updates.
• After launch: nobody in-house; wants someone to call.
• Decision by: 7 November, so the shop is live before December.

What the notes became in the proposal.

Challenge: "We lose Saturday cake orders because people can't get through on the phone."

Summary (written for Anna): An online cake shop with pre-orders and collection at both shops, live by 28 November. Two options, from €6,400 excluding VAT.

Scope: Included: homepage and four page templates; cake shop with pre-orders and a collection slot per shop; payment provider set-up; two feedback rounds. Not included: delivery, product texts, new photography.

Price:

Item	Essential	Complete
Design: homepage and four templates	€2,400	€2,400
Shop with pre-orders and collection slots	€4,000	€4,000
Stock updates from the till system	€0	€2,000
Total one-off (excl. VAT)	€6,400	€8,400

Optional care plan for both options: €95 a month, with updates, backups and one hour of small changes. Extra work outside the proposal at €85 an hour.

Timeline: Kick-off 10 November, design approved 14 November, product texts from Tom by 17 November, live 28 November.

Next step: Proposal sent the day after the call; a call with Tom and Anna booked for two days later.

Almost nothing in the proposal is invented after the call: the challenge is a quote, the scope follows the "must have" and "assumed included" lines, the budget range sets the first option, and the care plan comes from "nobody in-house". The guide on turning days into a website price shows how to get from days to prices like these.

When to stop and not write the proposal yet

Some answers mean another conversation will do more than a document:

If the scope is still unclear, a range may be the honest answer: send an estimate instead of a proposal.

After the call: send it fast

Don't wait: a good proposal sent quickly beats a perfect one sent late, and the fastest proposal often wins. That is why the script closes by naming the day you will send it. Write it while the call is fresh, in the order the guide to writing a business proposal sets out: scope and price first, then the approach, the challenge and the summary last.

Booking the walk-through before you hang up means the follow-up is already arranged; if you still hear nothing, following up on a proposal has wording for each day.

FAQ

How many discovery call questions should I ask?

Fewer than you think. Gong's analysis of 519,000 recorded B2B discovery calls found that asking 11 to 14 targeted questions correlated with the most successful calls. That is a correlation, not proof. Pick the questions for the proposal sections you cannot fill yet.

How long should a discovery call be?

Long enough to fill the notes page. For a small project, half an hour is often enough to fill the page; for a larger one, book a second call with the person who signs rather than stretching the first.

This is general information, not legal or tax advice. For your situation, ask a lawyer or accountant.

How Propozit helps

Propozit asks for your notes in steps, on your laptop or on your phone straight after the call: the type of work, the client, the scope, the people, the options and the payment plan. The deck builds itself from your own price list and standards; see your first proposal in eight steps. The options you shaped around the budget become pricing the client can adjust, with live totals as they tick options and pick a plan.

You can also paste a description from your notes: the proposal AI drafts the deck from your own prices, cases and template, and lists what it could not find for you to check (describe a proposal and get a draft). Before you send, Propozit flags a missing project price, or a team or length that does not match the prices and the timeline. Then ask the AI for changes in plain words and apply them in one step (ask the AI for changes).

Propozit is in early access and free to start.