Outline for Proposal Writing: The Framework That Closes

Why Most Proposals Get Ignored

I've reviewed thousands of proposals from agency owners and freelancers over the years. The majority of them have the same problem: they're built around the seller's ego, not the buyer's decision-making process. They lead with company history, a long list of services, and vague outcome language. The prospect reads three paragraphs, gets bored, and files it away forever.

A good proposal is not a brochure. It's a persuasion document that walks a skeptical buyer from "I'm not sure" to "let's do this." Every section has a job. If a section doesn't move the prospect closer to signing, cut it.

This article gives you a clear outline for proposal writing - one you can adapt whether you're closing a $3,000 SEO retainer or a $150,000 enterprise software engagement.

Before we get into structure, one number worth knowing: the average B2B proposal win rate across industries sits around 30%. That means roughly 7 out of 10 proposals you send right now are going nowhere. The agencies and consultants who consistently outperform that benchmark share one thing in common - they follow a deliberate, repeatable structure. That's what this article gives you.

What Is a Proposal Outline (and What It's Not)

A proposal outline is the skeleton of your persuasion document. It determines what goes in, what order it appears in, and what each section needs to accomplish. Done right, it guides a skeptical prospect through a logical sequence that ends with them wanting to sign.

Here's what often gets confused with a proposal:

• A proposal is not a quote. A quote lists prices. A proposal makes the case for why those prices are worth paying.
• A proposal is not a business plan. A business plan describes your company's goals. A proposal describes what you'll do for a specific client's specific problem.
• A proposal is not a brochure. Brochures are generic. Every good proposal should be so specific to one client that it would be useless to send to anyone else.
• A proposal is not a contract. A proposal presents your offer. A contract formalizes the agreement once that offer is accepted. If you want both working together, pair your proposal with a clean contract - my one-page contract template is built exactly for this.

The goal of a proposal outline is simple: remove every reason for the client to hesitate. By the time they reach the signature line, every question should already be answered.

Types of Proposals: Which One Are You Writing?

Not every proposal is the same situation. Knowing which type you're writing changes how you approach the outline - specifically how much explaining you need to do upfront.

Formally Solicited Proposals (RFP Responses)

The client publishes a Request for Proposal, Request for Quotation, or Invitation for Bid. They know what they need and they're comparing multiple vendors side-by-side. This is a competitive situation. The RFP typically comes with formatting guidelines and evaluation criteria - follow them exactly. Deviation signals that you either didn't read the brief or that you can't follow instructions.

For formally solicited proposals, your differentiator isn't creativity in structure - it's depth of understanding and specificity of solution. The client has a checklist. Your job is to check every box while making it undeniably obvious that you understand their situation better than your competitors do.

Informally Solicited Proposals (Post-Discovery Call)

This is the most common situation for agencies and independent consultants. The prospect asked for a proposal after a conversation - there's no official RFP, no formal process, and in many cases no competing bids. This is the best possible situation to be in, and most sellers blow it by sending a generic document that ignores everything discussed in the call.

The outline I give you in this article is built primarily for this scenario. You've had the discovery call, you know the client's problem, and now you need to turn that knowledge into a persuasive document that makes signing feel like the obvious next step.

Unsolicited Proposals

You send a proposal to someone who didn't ask for one. This is essentially a cold pitch in document form. These are harder to land because you're not responding to a stated need - you're creating one. If you go this route, your problem statement section needs to work twice as hard, because the prospect may not even agree that they have a problem yet. You need to prove the problem exists before you can pitch the solution.

Renewal and Revision Proposals

You're already working with the client and either renewing the engagement or adjusting scope. These are among the easiest proposals to close because you have credibility built in - but sellers still lose them by treating them as a formality. A renewal proposal is your chance to reframe the relationship, demonstrate the results you've delivered, and often expand scope. Treat it like a fresh pitch, not a copy-paste of the original.

The Core Outline for Proposal Writing

There are six sections every strong proposal needs. Here's each one, what it does, and what to put in it.

1. The Problem Statement

This is the single most important section of your proposal, and it comes first. Before you pitch anything, you need to demonstrate that you understand the client's situation better than they do. When a prospect reads this section and thinks "how did they know that?" - you've already won half the battle.

What goes here:

• The specific business problem the client is facing (not a generic version - their version)
• The cost of that problem in revenue, time, or opportunity
• What they've likely tried before and why it hasn't worked

Write this section using the exact language from your discovery call. If the CMO said "we're generating leads but they're not converting," use that phrase. Mirror their words back to them. This builds instant credibility and shows you were actually listening.

The relevance factor here is not a soft concept - it's the number one driver of whether proposals win or lose. A relevant proposal is one that strikes a personal chord with the individual people you're selling to. You achieve that best through careful attention during discovery conversations, then reflecting what you heard directly back in the proposal.

Common mistake: Writing a problem statement that applies to every client in the industry. If your problem statement could be copy-pasted onto a competitor's proposal with zero edits, it's not good enough.

2. Your Proposed Solution

Now that you've established you understand the problem, you explain how you solve it. Keep this focused. You're not listing every service you offer - you're describing the specific approach you'll take for this client.

Structure it like this:

• The strategic approach (the why behind your method)
• The tactical execution (what you'll actually do, in plain language)
• The timeline (when things happen)

Avoid jargon unless your client uses that jargon themselves. A B2B SaaS founder may love hearing about "intent-based outbound sequences." A local roofing company owner does not. Speak their language.

This section should be specific enough that the client thinks "these people have done this before" - but not so granular that you're handing over your entire methodology for free. Save the deep process detail for after they sign.

3. Deliverables and Scope

This is where you get surgical about what is - and isn't - included. Scope creep kills agency profitability. A clearly defined deliverables section protects both parties and removes ambiguity before it becomes a dispute.

Format this as a clean bulleted list or table. Include:

• Specific deliverables with quantities (e.g., "8 cold email sequences per month, each with 5-step follow-up")
• Explicit exclusions (e.g., "paid ad management is not included in this engagement")
• Communication cadence and reporting format

If you want a solid legal baseline to go alongside this, grab my one-page contract template - it pairs well with a proposal and handles the terms that proposals typically skip.

4. Investment

Stop calling it "pricing." Calling it "investment" isn't a trick - it's a framing shift that reminds the client this is money working toward an outcome, not money being spent. Small thing, but it matters.

How to present it:

• One primary recommendation (not three confusing tiers)
• The monthly or project fee, clearly stated
• Payment terms (net 15, 50% upfront, etc.)
• Optional: a one-line ROI framing - e.g., "If this adds two new clients at your average deal size, the engagement pays for itself in the first month"

Avoid itemized line-item breakdowns that invite the client to start negotiating individual pieces. You're selling outcomes, not hours.

If you want to offer options, do a maximum of two: a core package and an expanded version. Three tiers creates decision fatigue. One option can feel take-it-or-leave-it. Two is the sweet spot.

5. Social Proof and Case Studies

Don't put this section first. A lot of agencies lead with testimonials and awards - that's a mistake. Social proof lands harder after you've already described the client's problem and your solution. By now they're already leaning in, and the case study confirms they're not taking a risk.

What to include:

• One or two relevant case studies (same industry or same problem type as this prospect)
• Specific results: numbers, percentages, timeframes
• A one-line client quote if you have one

If you're early-stage and don't have polished case studies yet, use a project summary: "We worked with a 12-person digital agency on their outbound process. In 90 days, they booked 31 qualified calls from cold email alone." Specificity beats polish every time.

6. The Call to Action and Next Steps

Every proposal needs to end with a clear, frictionless next step. Don't end with "let us know if you have any questions." That's passive and invites delay.

Instead, end with something like:

• "To move forward, sign below and I'll send the onboarding questionnaire within 24 hours."
• "If you're ready to start, reply to this email and I'll send the contract over today."

If you're using a digital tool to send proposals, add an e-signature block right on the document. Remove every reason to delay. The easier you make it to say yes, the faster deals close.

For the contract itself, don't leave it as an afterthought. A clean, professional contract protects you and signals to the client that you run a real operation. My agency contract template covers the terms most agencies forget to include.

Optional Sections Worth Adding

The six sections above are the core. Depending on deal size and complexity, you may also want:

• About Us (brief): Two to three sentences max. Who you are, how long you've been doing this, relevant credentials. This is not your origin story - keep it tight.
• Team Bios: For larger engagements where the client needs to know who's actually doing the work. One paragraph per key person, focused on relevant experience.
• FAQ Section: Pre-empt the objections you know are coming. "What if we want to pause?" "Who will we be communicating with?" Answer them proactively and you remove friction before it surfaces in a follow-up email.
• Guarantee or Risk Reversal: If you offer any kind of performance guarantee or satisfaction clause, include it here. This is especially powerful in competitive bids.
• Executive Summary: For longer, more complex proposals - particularly formal RFP responses - a one-page executive summary at the top lets busy decision-makers understand the core offer without reading the whole document first. Many senior stakeholders will only read this section thoroughly, so make it tight and client-focused.

How to Write Each Section: Step-by-Step

Having the outline is one thing. Knowing how to execute each section under pressure - when you're cranking out three proposals a week - is another. Here's how I approach each section from scratch.

Step 1: Start With Your Discovery Call Notes

Before you write a single word, pull up your notes from the discovery call. If you don't take notes, start. Every phrase the prospect used to describe their problem is gold. Their exact language - not your rephrasing - is what makes the problem statement feel uncannily accurate.

Look for:

• The primary business pain (in their words)
• What they've already tried
• What they said when you asked "what does success look like?"
• Any concerns or hesitations they raised
• Specific numbers they mentioned (revenue, team size, current results)

Feed all of this into the problem statement section before anything else. The rest of the proposal flows from there.

Step 2: Write the Problem Statement Before the Solution

Most people write the solution first because they know their services better than they know the client's problem. That's backwards. Start with the problem statement. Force yourself to articulate the client's situation in full before you start describing your services.

This discipline does two things: first, it builds empathy into the document from the opening paragraph. Second, it prevents you from defaulting to a generic services pitch when the problem gets complex.

Step 3: Make the Solution Section Specific to This Client

After you've nailed the problem, write a solution that is visibly tailored. This doesn't mean starting from zero every time - you can have templated language for your approach. But the framing should reference the specific client situation. If the discovery call revealed that they've tried cold outreach before with no success, your solution section should acknowledge that and explain what you'll do differently.

The test: could you send this solution section to a different client with zero edits? If yes, it's not specific enough.

Step 4: Build the Deliverables List From the Solution

Once the solution section is written, your deliverables list should practically write itself - it's just the concrete, measurable outputs of everything you described in the solution. Each deliverable should have a quantity, a format, and ideally a frequency.

If you find yourself writing vague deliverables like "ongoing strategy support" or "regular check-ins," stop. Vague deliverables create disputes. Get specific: "Two 30-minute strategy calls per month" or "One written competitive analysis per quarter."

Step 5: Price It, Then Anchor It to Outcome

Write the investment section last, not first. Build the full value case first - problem, solution, deliverables, proof - and then put the investment number at the end of that logic chain. The price feels small when it follows a compelling articulation of the problem it solves.

The one-line ROI anchor is underused. Something like: "Two new retainer clients at your average $4,500/month deal size covers this engagement in full" reframes the cost entirely. You're not asking them to spend money - you're showing them how to make more of it.

Step 6: Choose the Most Relevant Case Study

Don't default to your biggest or most impressive case study. Default to the most relevant one. A prospect in the SaaS vertical cares more about a case study from a similar SaaS company with modest results than a flashy case study from an industry they don't relate to.

Same-problem relevance beats prestige every time. If you helped a 15-person agency fix their lead generation and this prospect is a 20-person agency with the same problem, that story is worth more than a headline client in an unrelated space.

Proposal Format: Keep It Simple

Long proposals don't win more deals. I've seen six-page proposals close $50,000 contracts and 40-page decks lose to someone who sent a clean two-pager. Clarity beats volume.

For most agency engagements and consulting projects, 8 to 12 pages is the optimal range. Simple projects can work in 4 to 6 pages. Complex enterprise engagements might warrant more - but more only helps if each page is earning its place.

Formatting guidelines:

• Use white space liberally - walls of text get skimmed or skipped
• Bold the most important phrases so scanners catch the key points
• Use a consistent header structure so the document feels organized
• One font, two weights (regular and bold) is all you need
• Tables for deliverables and pricing - they're easier to scan than paragraphs
• If you include a cover page, make the headline about the client's outcome, not your company name

If you want a head start on the writing itself, my Proposal AI Templates give you plug-and-play language for the sections above - useful when you're cranking out multiple proposals a week and need to move fast without sacrificing quality.

The Proposal Sequence That Actually Gets Read

Even a perfect proposal won't close if it's sent at the wrong time or to the wrong person. Here's the process that works:

1. Send within 24 hours of the discovery call. The prospect is most engaged immediately after the conversation. Every day you wait, momentum bleeds out.
2. Send it to the decision-maker, not the gatekeeper. If you've only been talking to a manager, ask them to loop in whoever signs contracts before you send the proposal. Otherwise you're writing for someone who can't say yes.
3. Follow up twice if you don't hear back. First follow-up at 48 hours: "Just checking in - any questions on the proposal?" Second follow-up at 5 days: "Still interested in moving forward?" After that, let it go and focus your energy on the next prospect.

Common Proposal Mistakes That Kill Deals

I've seen the same errors show up repeatedly across the proposals I've reviewed. Here are the ones most likely to cost you a deal.

Leading With Your Company Story

Nobody cares about your founding year or your mission statement before they know you understand their problem. Leading with "About Us" is a reflex that comes from insecurity - you're trying to establish credibility before you've earned the right to ask for it. Credibility comes from demonstrating understanding, not from talking about yourself. Bury the "About Us" section at the end, or cut it entirely for smaller engagements.

Copying and Pasting From a Previous Proposal

The fastest way to get a "no" is to send a document the client can tell was written for someone else. Small tells include: a different company name appearing somewhere in the document, a case study from an industry wildly different from theirs, or problem language so generic it could apply to any business. Clients notice. Even if they don't say it out loud, they feel that you didn't put in the effort - and if you're not putting in effort for the proposal, why would they trust you with the work?

Listing Services Instead of Outcomes

"We will provide monthly SEO reports" is a service. "We will drive a 40% increase in organic traffic within six months" is an outcome. Clients buy outcomes. They don't care what the service is called; they care what it produces. Wherever you've written what you'll do, rewrite it as what the client will get.

Over-Explaining Your Process

There's a tendency, especially from technically skilled practitioners, to document every step of the methodology in the proposal. Resist this. You're not writing a user manual - you're writing a persuasion document. Give the client enough detail to feel confident you know what you're doing, but save the deep process breakdown for the kickoff call after they sign. Over-explaining process does two things: it bores the client, and it hands over your methodology before they've paid for it.

Sending It With No Follow-Up Plan

Sending a proposal and then waiting silently is one of the most common mistakes I see. Have your follow-up cadence ready before you hit send. Know exactly what you're going to say and when. The clients who don't respond aren't always saying no - they're often just busy, and a timely, confident follow-up is all it takes to get the deal back on track.

Making It Hard to Say Yes

Every step between "I want to sign" and "contract signed" is an opportunity for a deal to die. If you're sending a PDF and asking the client to print it, sign it, scan it, and email it back - you're introducing friction. Use a digital proposal tool where possible. Include an e-signature block directly in the document. The goal is a one-click path from decision to commitment.

Proposal Tools Worth Knowing

You don't need expensive software to send a great proposal. But the right tool can speed up your process, track engagement, and remove friction from the close. Here's the honest breakdown:

Google Docs or Notion

Free, flexible, and good enough for most engagements under $20,000. The downside: no tracking, no e-signature, and the formatting can look unprofessional if you're not careful with design. Best used when you have a clean template and you're moving fast.

PandaDoc

Purpose-built proposal software with templates, e-signatures, and engagement tracking. You can see when the prospect opened the proposal, how long they spent on each section, and whether they've shared it internally. That intelligence is worth a lot in follow-up timing.

Proposify

Similar to PandaDoc with a stronger emphasis on design. Good for agencies where the visual quality of the proposal is itself a signal of your creative capability. Pricing scales up with team size.

Close CRM

If you're managing a pipeline of proposals, you want them tracked in a CRM, not scattered across your inbox. Close is built for outbound sales teams and handles pipeline management well - you can see where each proposal is, schedule follow-ups, and track your overall win rate over time.

Canva

If you need your proposal to look like a polished deck rather than a Word doc, Canva is the fastest way to build a visually impressive document without needing a designer. Use one of the business proposal templates and customize it to match your brand. The output is a PDF - no e-signature, but the visual quality is high.

How to Adapt This Outline for Different Proposal Types

The core six-section outline works across most B2B scenarios, but here's how to adjust it for specific situations.

The Short-Form Proposal (Under $10K Engagements)

For smaller deals, a full-length proposal is often overkill. A well-structured one or two-pager that covers the problem, solution, deliverables, and investment - in that order - is enough. The case study section can be a single sentence: "We've run this exact process for four other agencies in the SaaS space and the average result was X." The shorter the engagement, the shorter the proposal should be. Respect your prospect's time.

The Enterprise Proposal (Six-Figure Engagements)

Larger engagements require more structure because more stakeholders are involved in the decision. Add an executive summary at the front - a one-page overview that the VP can share with the CFO without forwarding a 25-page document. Include team bios, a risk section, and more detailed case studies. These proposals often take longer to write, but they also have more direct revenue impact. Budget the time accordingly.

The Competitive RFP Response

Follow the client's format exactly, even if you disagree with it. Deviation from the requested format signals either that you didn't read the brief carefully or that you think your way is better than theirs - neither is a good look. Within the format they've prescribed, front-load every section with client-focused language rather than company-focused language. And if you have any relationship with the buyer before the RFP drops, use it - teams that engage with clients before the formal solicitation process consistently win more often.

The Renewal Proposal

Open with results, not a pitch. The first thing the client should see is what you've delivered. Quantify everything: leads generated, revenue attributed, time saved, whatever metrics matter to that client. Then present the next phase as a natural extension of that progress. A renewal is the easiest proposal to close if you've done the work - let the results make the case, then ask for the continuation.

Tracking Your Proposal Win Rate

If you're not tracking your win rate, you're flying blind. You might be sending 20 proposals a month and winning 4, but unless you know that, you can't improve it. Here's how to think about it.

Calculate your win rate by dividing the number of proposals won by the total number sent. If you sent 20 and closed 6, your win rate is 30%. Industry benchmarks suggest an average of around 42% across industries, but that number varies significantly based on whether you're responding to cold RFPs, warm inbound requests, or post-discovery follow-ups. Your win rate on proposals after a discovery call should be substantially higher than your rate on cold RFP responses - if it's not, your proposal is losing ground that your sales process already won.

Track these additional metrics alongside win rate:

• Time to send: How long after the discovery call before the proposal lands? The faster you send, the higher your close rate on that proposal.
• Proposal open rate: If you're using a tool with tracking, are prospects even opening it? An unopened proposal tells you the problem is in delivery or timing, not in the document itself.
• Response rate by proposal length: Are your shorter proposals getting faster responses? This tells you something about the ideal length for your specific client base.
• Win rate by proposal type: Are you winning more on inbound than outbound? More on smaller engagements than larger ones? Break down the data and you'll find patterns to exploit.

For tracking all of this in one place, a CRM like Close makes proposal pipeline visibility simple. You'll know exactly what's open, what's stalled, and what's closed at any given moment.

Building a Pipeline That Needs Proposals

A great proposal outline only matters if you have prospects to send it to. The bottleneck for most agencies isn't proposal quality - it's pipeline volume. They're not sending enough proposals because they're not having enough conversations.

The fix is systematic outbound: a clean list, a tight cold email sequence, and consistent volume. For the list-building side, ScraperCity's B2B lead database lets you filter by job title, industry, company size, and location so you're only prospecting people who are a genuine fit - the ones who'll actually read that proposal when it lands.

For finding individual contact emails when you know who you want to reach, an email finding tool like ScraperCity's Email Finder is faster than manual searching through LinkedIn. Build your list, find the emails, and get them into a sequence.

For the outreach itself, tools like Smartlead and Instantly handle the sequencing and deliverability side so your emails actually reach inboxes instead of spam folders.

Get the outbound engine running and your proposal becomes the final step of a well-oiled process - not a Hail Mary you're scrambling to send after a lucky referral.

What to Do After You Send the Proposal

Most salespeople treat the proposal as the finish line. It's not - it's the start of the closing process.

• Schedule a proposal review call when you send it. Don't just email it and wait. Say: "I'll send this over now. Can we get 20 minutes Thursday to walk through it together?" This gives you a live opportunity to handle objections in real time.
• Track opens if your tool allows it. Knowing the proposal was opened three times tells you the prospect is interested but hasn't committed yet - that's your cue to follow up.
• Don't negotiate on price before they ask. A lot of sellers preemptively discount to "make it easier to say yes." All that does is train buyers to hold out for discounts. Stand behind your number until they specifically push back.

The proposal is a tool. Like any tool, how you use it matters as much as the design. Follow this outline, keep the language sharp and client-focused, and make saying yes as frictionless as possible. That's what closes deals.

Proposal Outline: A Complete Template You Can Use Today

Let me put the full outline in one place so you can use it as a checklist every time. Copy this structure into your preferred document tool and fill it in from your discovery call notes.

Cover Page

• Client company name and logo (if you have it)
• Proposal title: frame it around their outcome, not your service (e.g., "A Plan to Double SQLs for [Company Name]" not "SEO Proposal")
• Your company name, contact info, and date

Executive Summary (optional for larger deals)

• One paragraph: the problem, the solution, the primary outcome expected
• Written for someone who won't read the full document

Section 1: The Problem Statement

• Their specific situation in their language
• Quantified cost of the problem where possible
• What they've tried before and why it hasn't worked

Section 2: The Proposed Solution

• Strategic approach - the why
• Tactical execution - the what, in plain language
• Timeline - when milestones happen

Section 3: Deliverables and Scope

• Specific deliverables with quantities
• Clear exclusions
• Communication format and reporting

Section 4: Investment

• One primary option (two max)
• Monthly or project fee
• Payment terms
• One-line ROI anchor

Section 5: Social Proof and Case Studies

• One or two relevant case studies
• Specific numbers: results, timeframes
• Client quote if available

Section 6: Next Steps and Call to Action

• Clear, specific action for the client to take
• E-signature block if sending digitally
• Your contact info for questions

Optional Add-Ons (based on deal size)

• About Us (2-3 sentences max)
• Team bios for key personnel
• FAQ section pre-empting common objections
• Guarantee or risk reversal clause

For the legal side of things, once the proposal is accepted, you need a contract that covers the terms. My guide on how to write a contract walks through exactly what needs to be in there - scope, payment, ownership rights, termination, and the clauses most agencies forget until they're in a dispute.

How to Write Proposals Faster Without Sacrificing Quality

If you're running a growing agency, speed matters. The proposal that lands in the prospect's inbox at 7pm the night of the discovery call closes at a higher rate than the one that shows up three days later. Here's how to compress the time without producing a generic document.

Build a Modular Proposal Library

Create pre-written blocks for every section of your proposal. Write five strong problem statement templates across your most common client types. Write three solution sections for your core service offerings. Write four case study summaries for your best results. Then, for each new proposal, you're assembling and customizing - not building from a blank page. The customization happens in the specifics: you're swapping in the client's language, their problem, their numbers.

Teams that do this cut proposal creation time dramatically while actually improving quality, because they've refined each block through iteration instead of writing everything fresh under time pressure.

Send a Voice Memo or Loom With the Proposal

This is underused and disproportionately effective. Record a 3-5 minute video or voice memo walking through the proposal before you send it. Narrate the key points, tell them what to pay attention to, and give them a sense of your thinking. When the prospect opens the document, they're not reading cold text - they have your voice in their head explaining it.

This works especially well for larger deals where multiple stakeholders will review the proposal. Your video doesn't replace the document - it pre-sells it, and it travels with it when the recipient forwards it internally.

Use AI for First Drafts, Not Final Copies

AI tools are useful for getting words on a page quickly, but they produce generic output by default. Use AI to generate a first draft skeleton, then go in and replace every generic line with specifics from the discovery call. The problem statement especially needs to be rewritten from scratch using the client's actual language. AI doesn't know what the prospect said - you do. That's where the value comes from.

My Proposal AI Templates are built to bridge this gap - pre-structured prompts that output proposal-ready language you can edit rather than blank-page generation you have to clean up from scratch.

The Discovery Call Is Half the Proposal

I want to come back to this because it's the leverage point that most people overlook. The quality of your proposal is almost entirely determined by the quality of your discovery call. A mediocre proposal built on excellent discovery notes will almost always beat a polished template built on nothing.

Here's what to extract from every discovery call specifically to serve the proposal:

• The primary pain in their exact words. Quote it back. Don't paraphrase.
• The business impact of the pain. How much revenue are they leaving on the table? How much time is it wasting? What's the cost of inaction?
• Previous attempts and why they failed. This lets you position your approach as different - not just better in the abstract, but specifically designed to avoid the failure mode they already experienced.
• What success looks like to them. Their definition of success should be the language you use when describing expected outcomes.
• Who else is involved in the decision. This tells you whether to ask to loop in other stakeholders before sending the proposal.
• Their timeline. If they need results in 60 days, your proposal timeline should directly address that. If they're flexible, you can structure the engagement differently.

Run through this checklist at the end of every discovery call. If you don't have answers to all of these, ask before you hang up. The 10 minutes you spend getting specific answers at the end of the call will save you an hour of guessing during proposal writing - and dramatically improve your close rate.

Scaling Your Proposal Process Across a Team

When it's just you, the proposal process lives in your head. When you have account executives or client services people sending proposals, you need the process to live in documentation - otherwise quality varies wildly and your win rate becomes unpredictable.

Here's how to systematize it:

• Build a proposal playbook. Document the outline, the rules for each section, and the quality standards. Include examples of strong and weak problem statements side by side. Make it concrete enough that a new hire can follow it without supervision.
• Create a discovery call template. The proposal is only as good as the inputs. Standardize the discovery call questions so you're consistently capturing what you need.
• Review proposals before they go out. For deals above a certain threshold, have a second set of eyes on the proposal before it's sent. This catches lazy problem statements and generic language that slipped through.
• Track win rates by rep. If one person on your team has a 55% win rate and another has a 25% win rate, that's not random. Find out what the high performer is doing differently and systematize it.

If you want help building out systems like this across your sales process, I work through this kind of infrastructure in depth inside Galadon Gold - my live coaching program for agency owners and sales professionals.

What Great Proposals Have in Common

After reviewing thousands of proposals across industries and deal sizes, here's what the ones that consistently close share:

1. They make the client feel understood before they make a pitch. The problem statement is so accurate that the client thinks "they get it" before they've read a word about services.
2. They're specific about outcomes, not activities. Every deliverable is framed in terms of what the client gets, not what the seller does.
3. They make saying yes easy. One clear next step, minimal friction, ideally a direct path to signature.
4. They don't try to impress - they try to persuade. No buzzwords, no jargon the client doesn't use themselves, no corporate chest-puffing. Just a clear argument for why this engagement makes sense.
5. They respect the prospect's time. They're as short as they can be while still answering every likely question. Every sentence earns its place.

The proposal is a document, but it's also a demonstration. The care you put into writing it is a preview of the care you'll put into doing the work. When a prospect reads a great proposal, they're not just evaluating the offer - they're evaluating you. Make it count.