Half the quotes you send won’t be approved by the person reading them. Your contact loops in their boss, their CFO, or the founder, who then makes the actual call. A quote written for the contact but read by the decision maker often dies in translation. Writing it for the decision maker from the start changes the win rate.
Here’s what gets me about most freelance quotes: they’re written for the person on the call, not the stranger who actually approves them. The fix isn’t to write longer quotes. It’s to write quotes that make sense to a stranger in 90 seconds.
The 90-second test
Imagine the decision maker opens the email, glances at the attached quote, and gives it 90 seconds before approving, rejecting, or asking for more info. They didn’t attend your discovery call. They don’t know your background. They have 14 other emails to deal with.
In 90 seconds, the quote needs to answer:
- What is this project?
- What does it cost?
- What do we get?
- When does it ship?
- Why this freelancer?
If any of those answers requires the reader to scroll past page 1, the quote probably gets bounced back to your contact with “can you explain this?” That’s the delay that kills deals.
What goes on page 1
The first page of a quote for decision maker should be a clean executive summary, formatted so the eye can scan it in seconds.
Structure:
Project: [Clear name] Prepared for [Company], based on conversations with [Contact name] Date: [Date] / Valid through: [Date]
Overview One paragraph (3-4 sentences) describing the project, why it exists, and what success looks like.
Deliverables
- [Deliverable 1]
- [Deliverable 2]
- [Deliverable 3]
Timeline [Start date] to [End date], with milestones at [key dates]
Total investment: [Price]
Payment terms [Brief, e.g., 40% deposit, 40% at design approval, 20% on delivery]
That entire page fits on one screen. The decision maker reads it without scrolling and knows enough to approve or escalate.
What goes on pages 2 to 4
Pages 2 to 4 are the detail for anyone who wants it. Most decision makers don’t read this; they trust the executive summary if it makes sense.
Page 2: Detailed deliverable breakdown. Each deliverable gets a paragraph describing what’s included, what’s not, and the format of delivery.
Page 3: Scope assumptions, what triggers a change order, and dependencies (e.g., “Timeline assumes content is provided by [date]”).
Page 4: About you. Brief, relevant experience, 1-2 case studies or testimonials, contact info. Don’t pad this. The decision maker is checking that you exist and have done this before, not reading your life story.
The cover email that gets forwarded
The cover email needs to work standalone, because most contacts forward it as-is rather than rewriting it.
Template:
Subject: Proposal: [Project name], [Your name]
Hi [Contact name],
Proposal attached for [project name], total comes in at [price], with delivery in [timeframe]. Page 1 has the summary, full detail in the rest of the document.
A few highlights:
- [Key deliverable]
- [Key timeline detail]
- [One thing the project will accomplish for them]
Happy to jump on a call if it’s useful for the decision team. Quote is valid through [date].
[Your name]
Why that email works when forwarded: the subject line names the project so the decision maker recognizes it, the opening sentence gives the price and timeline immediately, the highlights summarize what they’re buying, the “happy to jump on a call” line opens a door without requiring one, and the expiration date creates a soft deadline.
When the contact forwards this with “thoughts?”, the decision maker has enough context to respond without asking questions.
What to leave out
A quote for decision maker should be ruthless about cutting things that don’t move the decision. Common bloat to delete:
- Your bio or “about” section longer than one paragraph
- Process diagrams or methodology pages
- Lists of generic services you offer beyond this project
- Vague mission statements about “your commitment to quality”
- Long FAQ sections
- Testimonials that don’t relate to this specific project type
- Pricing comparisons with other vendors
Every page that doesn’t answer one of the five 90-second questions slows the decision down.
How to frame the price
The price needs to feel reasonable in context, which means putting it next to the value it produces, not buried alone.
Weak:
Total: 22,400
Stronger:
Total investment: 22,400
Includes full brand identity, 8-page website design and build, content strategy, and 30 days of post-launch support.
The expanded version gives the decision maker something to mentally compare the number to. They see “22,400 for these specific things” rather than “22,400 for an unclear bundle.”
Confident framing without arrogance
Tone matters as much as content here. Apologetic framing (“I know this is more than you might have expected, but…”) signals that you’re not sure your price is fair. Direct framing, without apology, signals you’ve thought through the number and stand behind it.
Confident framing examples:
- “Total investment: 18,400” (not “Estimated cost: around 18,400”)
- “Delivery in 6 weeks” (not “Hopefully by week 6”)
- “Includes 2 revision rounds” (not “Comes with 2 revision rounds if needed”)
None of these is arrogant. They’re just direct. Decision makers approve direct numbers faster than they approve hedged ones.
What to do when the decision maker asks questions
If the decision maker asks a question through your contact (“can you explain why this is X?”), respond fast and through the same channel. The contact will forward your response.
A few rules for the response: answer the question in the first sentence, add one sentence of context if useful, and offer a 15-minute call for the detail.
Example:
“Quick answer: the price reflects the full scope including content strategy, which the other quotes you mentioned probably don’t include. Happy to jump on a 15-minute call with the decision team if it would help, Tuesday afternoon works for me.”
Don’t write a paragraph defending your price. Don’t itemize the entire quote again. Answer the question, offer the call, move on.
The follow-up timing for decision-maker quotes
Decision-maker approvals take longer than contact approvals. The contact had context; the decision maker has 90 seconds and 14 other things to do. Adjust your follow-up timing:
- Day 1: send the quote
- Day 4: short check-in to the contact (“any questions from the team?”)
- Day 8: second check-in with an offer to clarify
- Day 12: heads-up about the expiration date
- Day 14: expiration reminder
Faster follow-up than this feels pushy for decision-maker approvals. Slower feels like you don’t care.
The structure that builds trust before the decision
Decision makers approve quotes from freelancers who look organized. The structure of the quote itself does most of that work, clean formatting, clear headers, consistent fonts, no typos, real page numbers if longer than 2 pages.
A quote for decision maker that looks like a typed-up email loses to one that looks like a real document, even if the email contains more useful information. Spend the 10 minutes on formatting. It pays back consistently.
The shortest version
Decision makers want to know: what is it, what does it cost, what do we get, when does it ship, why you. Answer those five questions on page 1. Put the detail on pages 2 to 4. Write the cover email so it can be forwarded as-is. Strip out everything that requires context the decision maker doesn’t have. That’s the whole framework, and it consistently raises approval rates on forwarded quotes.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
