21 Discovery Questions to Ask Before You Send a Freelance Proposal

Discovery is not a sales performance. It is structured listening so your proposal writes itself. These 21 questions are what experienced freelancers ask before they quote, grouped by theme, with notes on how answers change your scope and price.

Goals and success criteria

1. What business result would make you recommend this project internally?
2. How will you measure success in 90 days?
3. What metric is embarrassing today that you want fixed first?
4. If this goes well, what do you personally gain (time, credibility, promotion)?

If they name a metric, anchor proof and options to it. If they cannot, add a paid discovery milestone before build pricing.

Scope and boundaries

1. What is in scope for phase one versus nice-to-have later?
2. What existing assets must we reuse (brand, code, copy, data)?
3. How many revision rounds does your team typically need?
4. What integrations are mandatory on day one?

Answers here become your deliverable table. "Unlimited iterations" from them means you need a capped revision clause in writing.

Timeline and urgency

1. What is the fixed external date, if any, and who set it?
2. What happens if we miss that date?
3. Are there blackout weeks where your team cannot review work?

Real urgency gets rush fees or reduced scope. Fake urgency with flexible reviewers gets a standard timeline and pushback on rush discounts.

Decision process and stakeholders

1. Who signs the contract and who can say no after yes?
2. Who else must approve copy, design, or technical changes?
3. Have you bought similar work before? What went wrong?

More approvers means more meeting time in your price. A past bad agency experience means emphasize communication rhythm and checkpoints.

Budget and commercial fit

1. Do you have a budget band for this phase?
2. Is spend coming from marketing, product, or central IT?
3. Do you need three vendor quotes for procurement?

No budget answer is not an automatic disqualify, but it changes your proposal to tiered options with a recommended middle path.

Current pain and root cause

1. What triggered this project now?
2. What have you already tried, and why was it not enough?
3. What is the cost of doing nothing for another quarter?

Strong pain answers let you open the proposal with their words. Weak pain means they may be shopping for ideas; protect your time with a smaller paid first step.

Tools, assets, and access

1. What systems do we need access to on day one?
2. Who owns admin rights for those systems?
3. Where does content live today (CMS, drive, Notion, paper)?

Access delays are a top reason projects slip. Price assumes client-side access within a stated number of business days or timeline shifts.

Risks and constraints

1. Any legal, security, or compliance rules we must follow?
2. Third parties we depend on (dev agency, ad partner, hosting)?
3. What would make you cancel the project mid-way?

Compliance and multi-vendor setups belong in assumptions and fees, not footnotes.

How answers change the proposal (quick examples)

SaaS lead gen: success metric is demo volume, budget band $12 to $18k, three stakeholders. You propose a fixed test landing package plus analytics readout, not a full site rebuild.

CRM cleanup: pain is duplicate leads breaking routing, access to Salesforce in two weeks. You propose audit week one, implementation weeks two to four, training session included.

Agency-of-record pitch: vague goals, no metric, rush timeline. You propose a paid workshop deliverable instead of a build quote.

Read a client brief before you book discovery.

Handle objections after the proposal lands.

ClientWin OS keeps discovery notes attached to the lead so pricing and proposal sections pull from the same answers. You decide what the client sees.

ClientWin OS for discovery-to-proposal workflow.