A proposal written before you fully understand a client's situation is a gamble — and usually a losing one. It either misses the mark entirely, or it is so generic it could apply to any client. Clients can tell the difference between a proposal written for them and one recycled from a template.
The information gathering happens before you write a single word. Here is everything you need to know.
Their Situation and Background
- What does the client do, and who are their customers?
- What is the context for this project — what has driven the need for it now?
- What has changed recently that makes this urgent or important?
- What have they already tried, and what happened?
- Who are the key stakeholders involved in or affected by this project?
The Problem They Are Trying to Solve
- What specifically is the problem or opportunity they want to address?
- How significant is it — in financial terms, in operational impact, or in strategic importance?
- Is the problem clearly defined, or are they still figuring out exactly what they need?
- What happens if this problem is not solved — what is the cost of doing nothing?
- Are there constraints on how the problem can be approached (technology, regulation, internal politics)?
What Success Looks Like
- What does the client expect to be different once this project is complete?
- How will they measure success — what is the metric that will tell them it worked?
- What would a really good outcome look like?
- Are there any specific deliverables they need, or are they open to your recommendation?
This is the most important section to get right. If you can describe what success looks like in the client's own terms — better than they can — your proposal will resonate far more strongly than one that stays vague.
Budget and Investment
- Does the client have a budget for this work?
- If yes, is it flexible, or is there a firm ceiling?
- Is the budget pre-approved or does it need sign-off?
- Are they comparing your proposal against others — is cost the main driver, or is fit and quality more important?
Many clients are reluctant to share budgets. If they will not, try a different approach: offer three price points ranging from minimal to comprehensive, and ask which range feels appropriate. Most clients will give you useful directional guidance rather than committing to a specific number.
Timeline and Key Dates
- When does the client need this delivered by?
- Is there a hard deadline (a product launch, a financial year end, a regulatory deadline)?
- When would they ideally like to start?
- Are there any dates that are unavailable (holidays, board meetings, existing commitments)?
- What happens to the project if there is a delay?
The Decision-Making Process
- Who will make the final decision about whether to proceed?
- Who else is involved — is there a committee, a procurement team, a board?
- What is the approval process and how long does it typically take?
- Is the person you are speaking to the decision maker, or do they need to get approval?
- Are there any internal politics or stakeholder sensitivities you should be aware of?
If you can understand who needs to say yes — and what they need to see to say it — you can shape your proposal to speak directly to them, not just the person you met.
Their Concerns and Objections
- What are their main worries about this kind of project?
- Have they had bad experiences with suppliers before — what went wrong?
- What would make them hesitate to sign off?
- Is there anything about your company or approach that they would want you to address?
Most clients will not volunteer their objections — you have to ask. A proposal that anticipates and directly addresses the client's main concerns converts significantly better than one that ignores them.
Their Evaluation Criteria
- How will they compare your proposal against alternatives?
- What matters most to them — price, speed, quality, credentials, relationship, something else?
- Is there a formal scoring process, or is it a more instinctive decision?
What to Do If You Cannot Get Answers
Sometimes clients are vague, in a hurry, or simply have not thought through the details yet. In those cases:
- State your assumptions clearly in the proposal: "This proposal is based on the following assumptions..." — it shows professionalism and invites the client to correct any misunderstanding
- Offer a discovery phase: A short paid scoping exercise to properly define the brief before committing to the full project — standard practice for complex or ambiguous work
- Ask one more time in a different way: sometimes "what does success look like?" gets a better answer than "what do you need?"
Turning Your Answers Into a Proposal
With solid answers to the questions above, writing a proposal becomes much more straightforward. You are not guessing at what the client needs — you know. Your executive summary can open with their specific problem. Your approach can address their specific constraints. Your pricing can connect to the specific value you are creating.
If you want to turn your answers into a professional proposal in under two minutes, try the AI Guide. Answer the questions above and it generates a complete, polished proposal ready to send. Or download a free proposal template if you prefer to write your own.
Write better proposals, faster
DraftYourBid learns from your winning proposals and generates tailored bids in minutes — in your voice, not a template.
Try free for 7 days →