How to Write a Proposal That Gets Accepted (Not Ignored)

Most proposals lose before the client finishes reading. Here's how to write one they actually want to say yes to.

Why most proposals get ignored

Clients don't ignore proposals because they're too busy. They ignore them because:

It reads like a resume

All about you, nothing about their problem.

It's too long

They wanted a clear answer, not a 12-page document.

The pricing is confusing

Too many options, hidden costs, or no clear total.

There's no urgency

Nothing telling them why now is better than later.

The 6-part proposal structure that wins

1. Start with their problem

Critical

Open with a 2-3 sentence summary of what they told you. This proves you listened.

Example:

“You mentioned your current website isn't converting visitors into leads, and you need a redesign before your product launch in March. Here's how I'd approach it.”

2. Propose your solution (not a feature list)

Describe what you'll do in terms of outcomes, not deliverables. “A website that converts at 3%+” beats “5-page responsive website with CMS integration.”

3. Break the scope into phases

Clients get overwhelmed by one big number. Break it into clear phases so they can see progress.

Phase 1: Research & strategyWeek 1-2

Phase 2: Design & prototypingWeek 3-4

Phase 3: Build & launchWeek 5-7

4. Make pricing dead simple

One clear price. Or two options at most (a “good” and a “better”). Don't make them do math. Don't bury the number at the bottom.

5. Add a timeline with a start date

Don't say “4-6 weeks.” Say “If we kick off Monday March 3, you'll have the final version by April 14.” Concrete dates create urgency.

6. End with a clear next step

Most skip this

Tell them exactly what to do next. Don't end with “Let me know what you think.”

Instead say:

“If this looks good, reply and I'll send the contract today. I have availability starting March 3.”

Mistakes that kill proposals silently

Sending a PDF attachment

Use a link they can open instantly. PDFs feel heavy and get lost in downloads.

Writing more than 2 pages

If it takes more than 5 minutes to read, it's too long. Summarize, then offer to elaborate on a call.

Using jargon they don't understand

Write like you're explaining it to a smart friend, not a technical colleague.

No social proof

One sentence about a similar project you've done is enough. You don't need a case study section.

Waiting days to send it

Send the proposal within 24 hours of the conversation. Speed signals competence.

A great proposal still needs a follow-up

Even the best proposals don't always get an immediate yes. Clients get busy, distracted, or need internal approval.

The difference between winning and losing the deal is often just a well-timed follow-up 3-5 days later.

The proposal gets you considered. The follow-up gets you hired.

Send better proposals. Follow up automatically.

SecondPing tracks when your proposal is opened and sends follow-ups at the perfect time — from a SecondPing address.