Before You Write the Proposal, Run the Discovery Call

A proposal you write without a discovery call is a guess dressed up as a quote. You're estimating the work based on a brief that probably leaves out the most important details — the client's real deadline, who else is making decisions, what failure actually looks like to them. Without those answers, your proposal can only reflect what you think the project is. Not what it is.

The discovery call fixes that. It's a 20-to-30-minute conversation before any formal document changes hands, focused on understanding the project well enough to price it confidently and decide whether to take it. Most freelancers who skip it pay in one of two ways: they undercharge because they misread the stakes, or they take a bad-fit project because they didn't ask the questions that would have revealed the warning signs.

What you're actually listening for

The surface purpose of discovery is information gathering. The deeper purpose is calibration. You're reading the client's situation, understanding what the project is worth to them, assessing who has authority to approve your work, and making a preliminary judgment about whether this is someone you want to spend the next several weeks working with. A good discovery call answers all of those questions naturally, without an interrogation. Most clients are happy to talk about their project. Your job is to listen carefully and ask the follow-up that gets under the initial answer.

The six questions worth asking

1. What is this project meant to accomplish? Get past the deliverable and into the outcome. A landing page isn't a landing page — it's a campaign launch, a product test, or an investor pitch. The answer reframes the scope and often the stakes.
2. What happens if this doesn't get done? Not every project is urgent. But clients who have a real cost to inaction — a launch delayed, a team blocked, a contract at risk — carry that urgency into how they work with you. The project's stakes reveal its value and tell you something about how this client will behave under pressure.
3. What does success look like six months from now? This reveals whether the client is measuring outputs or outcomes. Someone focused on outcomes will be a better partner, give cleaner feedback, and more willingly absorb scope conversations when something changes.
4. Who needs to sign off on this work? Design by committee doesn't announce itself. Ask early. If three people carry equal weight and none has final authority, factor the revision overhead into your price — or find out who does have final say before you quote.
5. What's your timeline, and is it fixed or flexible? Arbitrary deadlines respond to a conversation. Real deadlines don't. The answer also signals how thoroughly the client has thought through the project before reaching out to you.
6. Have you worked with freelancers on something like this before? What did that look like? This is a budget question that doesn't feel like one. You learn what they've paid before, what went wrong last time, and whether their expectations are grounded in reality.

What to do with what you learn

After the call, you should be able to answer two questions: what is this project worth to this client, and do I want to do it? If you can't answer both, the call didn't go deep enough. Price from the first answer, not from your hourly rate times an estimated hour count. Scope from the second — if the flags you noticed during the call persist in your gut, they'll probably materialize in the project.

The proposal you write after a thorough discovery call is shorter and more direct. You're not hedging to cover scenarios you don't understand — you understand the project. You're describing the work in terms the client already used, quoting a number that reflects what the outcome is worth to them, and presenting a timeline built on their actual constraints. Clients recognize a proposal that understands them. That's the one they accept.

The discovery call takes half an hour. What it saves — in misaligned proposals, underpriced projects, and work you shouldn't have taken — compounds far beyond that.