Before you write a proposal, ask your prospect three things: what a win would look like on this project, what the decision-making process is, and what happens if they do nothing. The answers tell you what belongs in the document, how fast to move, how long the deal will realistically take, and whether it is worth writing at all.
Most proposals fail before they are even written.
Pricing, formatting, a weak close: those are real problems too. But they are not the problem we are talking about here. Sometimes a proposal fails simply because the wrong information went into it.
Why proposals fail before they are written
A proposal is a translation. You take what you learned about someone's business and turn it into a scope, a price, and a recommendation.
Which means the quality of the document is capped by the quality of what you learned. If discovery was thin, no amount of design saves it. You end up writing your standard pitch, in your usual language, with your usual packages, and hoping it happens to land on the thing this particular client actually cares about.
Three questions fix most of that. None of them are clever. That is the point: they are easy to ask and easy to skip.
1. "What would a win look like for you on this project?"
It sounds obvious. Almost too simple to say out loud.
But most of us skip it, because we assume we already know what the client cares about.
Your customer is not hiring you because you did a good job explaining your process. They are hiring you because your solution fixes their actual problem. If you do not know what success looks like to them, you are aiming at a target you invented.
Ask it early, then listen for the specific thing they name. The answer usually rewrites the top of your proposal:
- "We keep losing leads from the website." Lead capture and tracking move to the front of the scope, and the summary states the outcome instead of the deliverables.
- "My team is drowning in manual work." Time saved becomes the headline, and phasing matters more than launching everything at once.
- "I have to show my board a number by Q4." The number and the date go in the summary, because that is the slide they are building.
Same services, three different proposals. Build the document around their answer, not yours.
2. "What's the decision-making process like?"
This one is not about the pitch. It is about preparation.
Is the person you are talking to actually the decision maker? Or are you about to write a beautiful proposal for someone who has to forward it to three other people? Is there a formal procurement process? Multiple departments that need to sign off?
Knowing this changes how you write, and how you set your own expectations:
- One decision maker, on the call. Write for them and keep it tight. You can lean on the conversation you just had.
- It gets forwarded. The proposal has to stand on its own, because you will not be in the room to explain it. Cut every "as we discussed" and make the summary readable cold.
- Procurement or multiple departments. Get the requirements now rather than discovering them in round three, and plan for months of back-and-forth instead of a quick close.
And sometimes this question reveals something more valuable than any of that: you do not want the deal. A low-probability project with a long, painful approval chain can eat months of your time for nothing.
3. "What happens if you do nothing?"
This is the urgency question, and it is the one that tells you how committed the buyer really is.
Is there real pain if they do not act? A cost to standing still? Or is this a nice-to-have that could just as easily happen in six months, or never?
If the stakes are high, you are talking to a serious buyer, someone who is going to make a decision. Move fast, stay focused, and give the proposal your best effort, because it is likely to convert.
If the answer is closer to "not much," something important just changed:
That means the proposal has to work harder to create urgency instead of laying out options and waiting. Name the cost of delay in their words. Put a reason to start now in the document, whether that is a scheduling window, a price that holds for 30 days, or a smaller first phase that lowers the risk of saying yes.
The natural follow-up here is asking what is driving the timeline. "We want to start next month" means nothing on its own. What sits behind that date is what tells you whether the deadline is real.
What the answers change in your proposal
| Question | What you learn | What changes in the proposal |
|---|---|---|
| What would a win look like? | Their definition of success, in their words | Scope order, the summary, and which outcome you lead with |
| What's the decision-making process? | Who decides, how many approvals, how long | How self-contained the document is, and your own timeline expectations |
| What happens if you do nothing? | Whether there is real urgency or none | How hard the proposal has to work to create a reason to act now |
When to ask them
On the discovery call, before you open a blank document. Not as a script you read off, just as three things you make sure you leave the call knowing.
If you have already sent a proposal without the answers, you get one more shot: walk them through it live instead of emailing it and hoping. A proposal review meeting is where the questions you skipped tend to surface anyway, and you can adjust scope on the spot.
Put it together
None of these questions are complicated. That is the point.
Which leaves the mechanics, and the mechanics should be the fast part. Smart Pricing Table is interactive proposal software with live pricing tables for agencies, IT companies, and consultants, so once you know what the client needs, you are assembling from templates and a reusable line-item library instead of rebuilding a document from scratch. The thinking is the work. The formatting should not be.
or start a free trial and try it yourself.
Explore more
What's really driving the date
Present it, don't email it
Proposal software for agencies
Frequently Asked Questions
What questions should I ask before writing a proposal?
Three cover most of it: what a win would look like for the client on this project, what their decision-making process is, and what happens if they do nothing. The first tells you what to put in the proposal, the second tells you who you are writing for and how long approval will take, and the third tells you how much urgency the document needs to create.
What should I ask a client on a discovery call?
Beyond scope and budget, ask about their definition of success, their approval process, and the consequences of inaction. Those three answers change what you write far more than a longer list of requirements does, because they tell you what the client is actually trying to accomplish and how a decision will get made.
How do I know if I'm talking to the decision maker?
Ask directly what the decision-making process looks like, including who else needs to sign off and whether there is a formal procurement step. If the proposal will be forwarded to other people, write it so it stands on its own without you there to explain it.
What if the client says there's no urgency?
Then you are competing against inertia rather than another vendor, and the proposal has to create a reason to act. Name the cost of waiting in the client's own terms, and consider a smaller first phase or a price that holds for a set window so saying yes feels lower risk.
Should I write a proposal for every prospect who asks?
No. A low-probability project with a long, painful approval chain can consume months for nothing. If the decision-making process is heavy and the urgency is low, finding that out before you invest hours in a proposal is itself a win.
How long should discovery take before writing a proposal?
Long enough to answer these three questions, which is usually part of a single call rather than a separate process. The goal is not a longer discovery phase, it is leaving the conversation knowing what success means to them, how the decision gets made, and what happens if nothing changes.
You might also like:
👉 What's Driving the Timeline? The Question That Changes Everything
👉 How to Close More Deals: 7 Proposal Strategies That Work
👉 How to Build Trust Before They Even Read Your Proposal
