21 Days of AI
Back to course overview
Day 8Free~15 minNo account required

Day 8: Write Proposals That Win Business, Not Just Describe It

By 21 Days of AI · Last updated: July 4, 2026

EmailLinkedIn

The Point Of Today

Most proposals describe the seller's work. Strong proposals help the buyer make a decision.

That difference is not cosmetic. A proposal that lists deliverables, timeline, and price may be accurate, but it leaves the buyer to do the harder mental work: why this, why now, why this vendor, and why this investment is worth defending internally. If the proposal does not help answer those questions, the buyer may still like you and still delay.

Today you will use AI to draft a proposal that does more than summarize a meeting. It will mirror the buyer's situation, make the stakes clear, connect your approach to their priorities, and create a decision path that feels practical.

AI is useful here because proposals are structured documents. Once you provide the right inputs, AI can organize the argument quickly. But the quality depends on the specificity of what you give it. If you feed it vague notes, it will write a polished but generic proposal. If you feed it the buyer's actual language, it can help you produce something that feels considered and precise.

The Proposal Is Not About You

Buyers do not read proposals to learn how impressive your company is. They read them to decide whether moving forward is safe, sensible, and worth the effort.

That means the opening should not begin with your company story. It should begin with their world.

The best first page answers:

  • Do they understand our situation?
  • Do they understand what is at stake?
  • Is the proposed approach clearly connected to what we said matters?
  • Can I explain this internally without doing extra work?

If a buyer has to translate your proposal into an internal business case, you have made the proposal too seller-centered.

Start With The Mirror

The Mirror section is where you prove that you listened. It should reflect the buyer's problem using their language, not your preferred category terms.

If the buyer said, "Our managers spend Friday afternoons chasing updates before the Monday forecast call," do not translate that into "inefficient sales operations." Say what they said. Their language carries emotional and operational truth.

A strong Mirror section might sound like:

"Your team is not short on pipeline activity. The issue is that managers are spending too much time reconstructing what happened after the fact, which leaves less time for coaching and deal support. The proposal below focuses on reducing that management drag while giving leadership a cleaner view of deal movement."

That kind of opening tells the buyer, "This is about us."

Make The Stakes Practical

Stakes are not scare tactics. Stakes are the business cost of inaction.

Weak stakes sound generic:

"If this is not addressed, the company may face inefficiencies and missed opportunities."

Strong stakes are grounded:

"If managers continue spending several hours each week collecting status updates manually, the cost is not only time. Coaching gets pushed later, deal risks surface too late, and forecast conversations become less useful because the data is stale before leadership sees it."

This section matters because buyers often underestimate the cost of staying the same. Your job is not to exaggerate. It is to make the current cost visible.

Connect The Approach To Priorities

Do not describe your solution in isolation. Connect each part of it to something the buyer said.

Use this pattern:

  • "Because you said [buyer priority], the proposal includes [solution element]."
  • "To address [specific friction], we will [approach]."
  • "This matters because [business consequence]."

This is where the proposal moves from "here is what we do" to "here is why this is the right response to your situation."

AI can help create this mapping, but only if your input includes real priorities. Before you run the prompt, scan your notes for the buyer's stated goals, concerns, language, objections, and success measures.

Proof Should Be Honest

Proof does not have to be perfect. It does have to be honest.

If you have a direct case study from the same industry, use it. If you do not, use the closest relevant example and explain why it matters. If you have no proof yet, write a placeholder and fill it later. Do not let AI invent proof.

Good proof is specific:

  • A comparable company.
  • A measurable result.
  • A before-and-after situation.
  • A risk reduced.
  • A time saved.
  • A revenue or margin outcome.

Avoid vague proof like "we have helped many companies improve performance." Buyers cannot use that internally.

Present Investment Without Apology

Price should be clear. Do not bury it, soften it excessively, or over-explain it.

The investment section should state:

  • What the buyer pays.
  • What is included.
  • What outcome the investment supports.
  • Any assumptions or boundaries.

Confidence matters. If you sound nervous about your own price, the buyer will become nervous too. Your proposal should not be defensive. It should make the price feel like part of a considered plan.

Create A Decision Path

Many proposals end with vague language:

"Let us know if you have any questions."

That is not a next step. It is a delay invitation.

Instead, create a clear decision path:

  • Who should review the proposal.
  • What decision needs to be made.
  • What happens next if they approve.
  • When you suggest reconnecting.

Example:

"If this matches the direction you want to take, the next step is a 30-minute working session with you and the operations lead to confirm scope and implementation timing. If we can do that by Friday, we can begin onboarding the following week."

That gives the buyer something practical to respond to.

Today's Practice

Choose one real proposal. Run the prompt. Then do not send the first output.

Improve it in this order:

  1. Rewrite the Mirror section with the buyer's actual language.
  2. Strengthen the Stakes section with specific cost of inaction.
  3. Remove anything that sounds like a brochure.
  4. Check that every solution element maps to a buyer priority.
  5. Make the next step unmistakable.

The proposal should feel like a decision document, not a document about your services. When you get that right, the buyer has less work to do internally, and deals move with less friction.

Prompt of the day

Copy this into your AI tool and replace any bracketed placeholders.

Prompt

You are a senior B2B sales strategist helping me write a proposal that sells the decision, not just the deliverables.
Deal context: - Client's stated problem: [WHAT THEY SAID IS NOT WORKING] - Desired outcome: [WHAT THEY SAID SUCCESS WOULD LOOK LIKE] - Current cost of the problem: [TIME, MONEY, RISK, DELAY, MISSED REVENUE, OR WRITE 'UNKNOWN'] - Key stakeholders: [WHO WILL READ OR INFLUENCE THE PROPOSAL] - My proposed approach: [WHAT I AM OFFERING] - Timeline: [DELIVERY OR IMPLEMENTATION TIMELINE] - Investment: [PRICE OR PRICING STRUCTURE] - Relevant proof: [CASE STUDY, RESULT, CUSTOMER EXAMPLE, OR WRITE 'NEED PLACEHOLDER']
Write a proposal draft using this structure: 1. Mirror: reflect their situation in their language. 2. Stakes: explain the cost of leaving the problem unresolved. 3. Approach: connect each part of my solution to a specific buyer priority. 4. Proof: include the strongest relevant proof or a clearly marked placeholder. 5. Investment: state the price clearly and explain what is included. 6. Decision path: show the next step, owner, and timing.
Rules: - Use confident, plain language. - Do not sound like a generic agency proposal. - Do not invent proof. - Keep the opening strong enough that a busy executive would keep reading. - Make the proposal feel specific to this client.

Your 15-minute task

Use a real active or recent opportunity. Fill in the client language from your discovery notes, not from memory if you can avoid it. Run the prompt, then manually improve the Mirror and Stakes sections until they sound like they could only have been written for that client.

Expected win

A client-specific proposal draft that frames the business decision, shows the cost of inaction, connects your approach to their stated priorities, and gives the buyer a clear path forward.

Power user tip

Ask AI to review the draft as the economic buyer: 'What would make me hesitate, what feels generic, and what evidence would make this proposal easier to approve internally?' Use that critique before sending.

Finished today?

Mark this lesson done on this device. No account is required, and you can continue straight to the next day.

Continue to Day 9

Want Day 9 in your inbox tomorrow morning?

Email delivery is optional. You can keep reading for free now, or use the starter sprint to get a short daily reminder.

Set up daily delivery
EmailLinkedIn