How to Write Emails and Proposals That Actually Get a Yes

A product manager needs approval for one new hire. Version A opens with two paragraphs of team history before finally asking for headcount in paragraph four. Version B opens with a single line: “Requesting approval to hire one QA engineer by August 1st - this cuts our release delays by an estimated 30%.” The VP replies to Version B in nine minutes. Version A sits unread for four days.

Same request. Same facts. Same person asking. The only difference is where the point was placed - and that difference decided whether the hire happened this quarter or not at all.

Why this matters

Nobody owes you their attention. Every email, proposal, or Slack message you send competes with dozens of others for a few seconds of someone’s focus. Studies of reading behavior find that a large share of people decide whether to even open a message based on the subject line alone, and once it’s open, many readers give it well under fifteen seconds before deciding whether to act, forward, ignore, or delete.

If your actual ask isn’t visible in that window, it might as well not exist - no matter how good the idea behind it is.

The fix isn’t fancier vocabulary or a clever hook. It’s structure. A handful of specific, learnable moves - in your subject line, your opening sentence, and your call to action - determine whether your message gets a decision or gets buried. This post walks through all of them, with templates you can copy today.

Persuasion at work isn’t manipulation

Before the tactics, one honest reframe: persuading a colleague or a client isn’t about tricking them into a decision they wouldn’t otherwise make. It’s clarity plus credibility plus ease. You’re removing the friction - confusion, extra effort, unclear risk - that stops a reasonable person from agreeing with a reasonable idea.

That distinction matters, because the line between persuasion and manipulation is exactly whether you’re making the truth easier to see or harder. Every technique below should do the former.

Think “vending machine,” not “treasure hunt”

Here’s an image worth keeping in your head every time you draft a request: a treasure hunt makes the reader dig through clues - background, history, context - before they find the prize (your actual ask) at the end. A vending machine shows the exact item and the price up front. Press one button, get the result.

Busy readers want vending machines. Almost every professional writing mistake - the four-paragraph windup, the ask buried in the last line, the “thoughts?” with no clear next step - is really just building a treasure hunt for someone who only has time for a vending machine.

Win the subject line, or nothing else matters

The subject line is a gate, not a decoration. Research on email behavior consistently finds that close to half of recipients decide whether to open a message from the subject line alone, before reading a single word of the body. A vague subject like “Quick question” or “Update” means your carefully written message may never get opened at all.

What actually works:

• Be specific, not clever. “Budget approval needed by Friday - $4,200” beats “Question about spending” every time. Specificity lets the reader triage instantly.
• Front-load the action or deadline. Mobile inboxes often cut subject lines off after 30-40 characters, so put the important word first: “Approve: Q3 hire (decision needed Thu).”
• Aim for six to ten words. Long enough to be specific, short enough to scan in one glance.
• Name the action, not just the event. “Server outage last night” is a fact. “Need your sign-off: outage fix, 15 min” is a request. The second gets replies.
• Never overpromise. A subject line that misleads trains the reader to distrust your next one - and plenty of people admit they tune out senders whose subject lines don’t match the content.

A simple formula covers most cases: [Action needed] + [Topic] + [Deadline]. For example: “Decide: vendor contract - renews Oct 1.”

Once it’s open, don’t waste the momentum on pleasantries. Skip “I hope this email finds you well” and get to something useful in your very first sentence. Compare “I wanted to reach out because I’ve been thinking about our onboarding process…” with “Our onboarding process loses 20% of new hires’ first-week productivity - here’s a two-step fix.” The second sentence has already earned the third.

Lead with your point: BLUF and the Pyramid Principle

BLUF (Bottom Line Up Front) is a writing habit born in the U.S. military: state your main point and required action in the first sentence or two, before any background.

The Pyramid Principle, developed by Barbara Minto - the first woman to graduate from Harvard Business School’s MBA program, later a McKinsey consultant - says essentially the same thing in structural terms: state your conclusion first, support it with a small number of grouped arguments, then back each argument with evidence. Picture an upside-down triangle, wide point at the top.

Both fight the same natural habit: building up to the point. We tell stories the way we lived them - first this happened, then that, then I realized, so here’s my idea. That’s how humans think. It is the opposite of how busy readers want to receive information.

The real test: if your reader stops after your first sentence, do they know what you want? If they stop after the first paragraph, do they know why? A pyramid-structured message passes that test at every level. A chronological one only makes sense once you’ve read the whole thing.

Before: “Hi team, over the last quarter we’ve noticed support tickets climbing, and after digging into the data with the CS team, we found most relate to the new billing flow. We also looked at churn data and saw a correlation. Given all this, I think we should consider pausing the rollout.”

After (BLUF): “Recommend pausing the new billing rollout by Friday. Reason: it’s driving a 40% spike in support tickets and is correlated with rising churn. Details below.”

Same information. One version a reader can act on from the first sentence; the other requires four sentences of patience they don’t have.

To apply this yourself: write your conclusion first, literally draft the ask and then move it to the top. Answer who needs to do what, by when, and why, in your opening lines. Group your supporting reasons into three buckets or fewer. Push background to the bottom, or an appendix - most readers won’t need it, and the ones who do can scroll down.

One caveat: BLUF works best with people who already trust you or share context with you - your manager, your team, a regular collaborator. For a cold email to a stranger, add one warm, credibility-building sentence before the ask. Just keep it to one sentence, not one paragraph.

Give them exactly one thing to do

Here’s a mistake that quietly kills more good ideas than bad writing does: asking for too many things at once, or asking so vaguely the reader isn’t sure what “yes” even looks like. “Let me know your thoughts” is not a call to action - it’s an invitation to do nothing, since doing nothing technically satisfies the request.

A real call to action (CTA) names the exact behavior you want, ideally with a deadline:

Weak ask	Strong ask
”Let me know your thoughts on this."	"Reply ‘approved’ or flag concerns by Wednesday 5pm."
"We should probably discuss the budget at some point."	"Can we do 20 minutes Thursday at 2pm to finalize the budget?"
"I’ve attached the proposal for review."	"Please review pages 1-2 only and confirm the pricing works by Friday."
"Happy to help however is useful."	"I can take the client call Tuesday - want me to send the invite?”

To make it even easier to say yes, remove steps between “I agree” and the reader’s action:

• Pre-fill the decision. Instead of “What time works for you?” try “Does Tuesday 2pm or Wednesday 10am work? I’ll send the invite either way.” A small, bounded choice beats an open-ended one.
• Do their homework for them. Attach the document already formatted the way they need it. Draft the reply they could send.
• Name a default, sparingly. “If I don’t hear back by Friday, I’ll proceed with Option B” respects everyone’s time - but only use it for low-stakes calls, never anything sensitive where silence shouldn’t be read as agreement.
• One ask per message. Three decisions crammed into one email usually get one reply, if any.

This is the same logic behind the “foot-in-the-door” finding in persuasion research: people say yes far more readily to a small, specific, low-effort request than a large, vague one. A bounded CTA is the small step. A vague “thoughts?” is the unbounded one.

Three templates you can copy today

The right structure shifts with the format, but the underlying logic - point first, then support, then action - never changes.

The persuasive email

Subject: [Action] + [Topic] + [Deadline]

1. Greeting (one line)
2. BLUF: the ask or recommendation, in 1-2 sentences
3. Why it matters (1-3 short reasons)
4. Evidence or context (short - link/attach the rest)
5. Clear CTA with deadline
6. Warm, brief close

For example: Subject: Approve: switch to new invoicing tool (saves ~6 hrs/week). “Hi Dana, requesting approval to switch our invoicing from Sheets to Invoicely by August 1st. It’ll save the finance team roughly six hours a week and cut billing errors, based on a two-week trial we ran last month. Why now: our current process caused two late invoices this quarter, and the trial showed zero errors across 40 test invoices. Cost is $40/month, already within budget. Could you reply ‘approved’ by Thursday so I can set it up before month-end billing?”

The one-page proposal - N-O-S-E

Proposal expert Tom Sant built a structure that works whether you’re pitching a client or your own leadership:

• Needs: show you understand the problem from the reader’s point of view, not just yours.
• Outcomes: describe the specific result they want, ideally with a number.
• Solution: present your proposal, tied directly back to the needs and outcomes above.
• Evidence: back it with a case study, data point, or comparable result - proof, not just promises.

The executive summary

This is the short, standalone section at the top of a longer proposal or report that lets a decision-maker act without reading the rest of the document. It matters more than most people realize: senior readers often spend well under a minute deciding whether a document is worth deeper attention, so the summary is frequently the only part that gets read. Keep it to one page, following Opener → Need → Solution → Evidence → Call to Action.

Write the executive summary or the persuasive email last, after you’ve done the full analysis - but put it first in the document. You can only compress well once you already know everything worth cutting.

Tone decides whether structure gets welcomed

Structure gets your message understood. Tone gets it welcomed. A perfectly structured email written in a cold or entitled tone can still get a “no,” because people help people they like and trust - not just people who happen to be logically correct.

Stay warm but efficient: a single friendly line (“Hope the launch went well!”) costs nothing, as long as it doesn’t delay the point past your first two sentences. Stay confident, not demanding: “Please approve by Friday” reads as more collaborative than “I need this by Friday.” And own your ask instead of hedging it - overusing “just,” “sort of,” or “I was wondering if maybe” quietly undercuts your credibility. State the ask plainly, then be polite around it, not inside it.

Asking up the chain - your manager, a skip-level leader, an executive - needs an extra layer of care, because you’re also asking them to spend political or budgetary capital on your behalf. Three adjustments help most:

1. Lead with business impact, not personal need. “I’d like a new laptop” is personal. “My current laptop’s slow builds are costing the team ~3 hours/week” is a business case that happens to help you too.
2. Show you’ve already done the thinking. Add a short “options considered” line for anything nontrivial - senior readers approve faster when they can see you’ve weighed the obvious objections already.
3. Make the decision small. Frame the ask as approve/reject on something you’ve already scoped, rather than open-ended homework. Executives say yes far more readily to a ready-made decision than to “figure out what to do about X.”

One thing to avoid: CC-ing an executive’s boss, or a wide group, to add pressure for a decision. It can read as an attempt to force a public yes rather than let the person genuinely evaluate the request, and it often backfires into defensiveness.

Follow-ups that get answers, not annoyance

Most requests don’t get a “no” - they get silence. Your message simply slipped down the inbox. A good follow-up isn’t nagging; it’s a service to a reader who probably still intends to respond but needs a nudge.

• Wait two to three business days for routine requests, longer for anything that needs input from other people on their side.
• Reply in the same thread. Don’t start fresh - that forces the reader to reconstruct what you asked.
• Restate the ask in one line, don’t retell the whole story: “Circling back on this - still hoping to get your sign-off on the invoicing switch by Thursday.”
• Make replying take five seconds. Offer a yes/no or a one-word reply option: “A quick ‘approved’ works great if you’re good with it.”
• Never write “as I mentioned before” or “per my last email.” Both read as passive-aggressive and put the reader on the defensive right when you’re trying to move them toward yes.

If you’ve followed up twice with no response and the deadline is real, it’s fair and professional to say so plainly: “Since I haven’t heard back and the offer expires Friday, I’ll plan to proceed with Option B unless you’d like to weigh in before then.” That’s not rude. It respects both your deadline and their right to object.

Common misconceptions

• “A longer, more thorough email is more persuasive.” The opposite is usually true. Length reads as friction. The reader’s trust in your judgment goes up when you can compress a complex situation into a clear ask - not down.
• “If I just explain the background clearly enough, they’ll see why I need this.” Background convinces people who already have time to be convinced. Busy readers decide from the first line; background belongs at the bottom, for the minority who ask for it.
• “Ending with ‘thoughts?’ is polite.” It throws away all the clarity you built. If you’ve made a case, ask for the specific decision that follows from it - not an open invitation to debate from scratch.
• “Following up makes me look pushy.” Silence usually means “busy,” not “no.” A brief, blame-free nudge in the same thread is a courtesy, not an imposition.
• “Being direct means being cold.” Structure and warmth aren’t in tension. You can state your ask in the first sentence and still open with one genuine, brief friendly line.

How to use this

1. Draft your last sentence first. Write the ask or recommendation as if it were the conclusion, then physically move it to the top of the message.
2. Rewrite the subject line last, using the formula. [Action needed] + [Topic] + [Deadline] - and keep it to six to ten words.
3. Cut your opener to one line. One warm sentence, maximum, before you get to something useful.
4. Turn your final line into one specific CTA with a deadline. If it could be satisfied by the reader doing nothing, rewrite it.
5. Read it once for tone, out loud if you can. If it would sound rude said to their face, soften it. If it would sound weak or apologetic, tighten it.
6. Set a follow-up reminder for two to three days out, before you send. Don’t rely on remembering to circle back.
7. For anything nontrivial going up the chain, add one “options considered” line. It turns an open problem into a ready decision.

Conclusion

Every technique here reduces to one idea: make saying yes the path of least resistance. Put your point where a skimming reader can find it, ask for exactly one thing, and remove every unnecessary step between agreement and action. That’s not a trick - it’s respect for someone else’s limited time, and it’s why the same idea, written two different ways, can get approved in nine minutes or ignored for four days.

Structure and a clear ask will get your message read and understood. But understanding isn’t the same as being moved - and the deeper reasons a reader leans toward “yes” or “no” often have nothing to do with your wording at all. They come down to the mental shortcuts everyone’s brain uses to decide, whether they notice it or not - and that’s worth looking at next.