What should a quick quote or proposal deck actually include?

This page may contain affiliate links from which Blur Studio earns commissions.

Most proposal decks fail for the same reason: they're either too long because someone tried to cover everything, or too generic because it's a copy-pasted template with the client's name swapped in. A good quick proposal deck does neither. It's short, specific to this client, and ends with one clear action. Here's the actual slide-by-slide structure.

The 8-slide structure, copy this directly

1. Title slide: the client's company name, your company name, and the date. Nothing else. This slide exists to confirm you got the name right and this is specifically for them, not a template.
2. The problem, in their words: one sentence restating what they told you they need, ideally close to their own phrasing from your first conversation. This is the single highest-leverage slide in the deck, since it proves you listened before you start selling.
3. What you're proposing: 2-4 bullet points, plain language, no jargon. This is the "what" before the "how," kept short on purpose.
4. Scope and timeline: what's included, what's explicitly not included (this prevents scope disputes later), and a realistic timeline with 2-3 milestones, not just a start and end date.
5. Pricing: the number, clearly, with what it includes. Don't bury the price on a later slide or in an appendix; clients notice when pricing feels hidden, and it reads as a trust problem, not a sales tactic. Keeping that figure current across decks is covered in keeping your pricing slide up to date.
6. Proof: one result, case study or testimonial relevant to this specific client's situation. One strong, relevant proof point beats three generic ones.
7. Why us, briefly: 2-3 bullet points on what makes you the right fit for this specific job, not a generic "about us" slide copied across every proposal.
8. Next step: one clear action with a date, "sign by Friday to start Monday," not a vague "let's discuss further."

That's it. Eight slides, most of them with under 30 words on screen. If you're regularly padding past 10-12 slides for a quick proposal, you're likely restating the same point more than once or adding content that belongs in a follow-up conversation instead.

A worked example: an $18,000 landscaping proposal

Say you run a landscaping company and a property manager asked for a proposal to redo the common-area irrigation and planting across a 40-unit complex. Here's how the 8 slides actually fill in for that specific job:

1. Title: "Westbrook Gardens Common Area Renewal, prepared for [Property Manager], [Management Company]."
2. Problem: "Three dead irrigation zones and patchy turf are driving resident complaints and hurting curb appeal ahead of lease renewals."
3. Proposal: replace zones 4 through 6, regrade and reseed 1,200 sq ft of turf, add drought-tolerant beds at the main entrance.
4. Scope and timeline: irrigation work (week 1), regrading and seeding (week 2), planting (week 3, weather permitting). Explicitly excluded: the pool deck landscaping, which is a separate quote.
5. Pricing: $18,400, itemized across irrigation ($7,200), turf ($5,600) and planting ($5,600), net 15 days.
6. Proof: a before/after photo and one line from a similar job at a 60-unit complex two miles away, named with permission.
7. Why us: licensed and insured for irrigation work specifically, same crew lead for the past 3 years, local supplier relationships that keep plant costs down.
8. Next step: "Approve by the 15th to start irrigation work the following Monday, ahead of the spring planting window."

Notice what's absent: no slide listing every tool or truck the company owns, no generic "about our company" history. Everything on the slide either answers a question this specific property manager actually has, or it's cut.

Building it fast without design skills

The structure above works in any slide tool. The difference between them is how much of the formatting you handle yourself: If you are starting from scattered notes, see turning a pile of notes into a deck.

• Google Slides: free, and fine if you already have a clean template. You're responsible for keeping spacing and alignment consistent slide to slide.
• Canva: free to start, with a large template library that makes the design decisions for you, though locking your own branding into a template costs extra on a paid plan.
• Beautiful.ai: $45/month (or $14.50/month billed annually), no free plan, 14-day trial that requires a card. Its Smart Slide layouts auto-handle spacing and alignment as you type, so building this 8-slide structure is mostly just filling in content rather than also designing each slide.

If you only build a proposal deck occasionally, Canva or Google Slides is the more sensible choice, since you won't offset a monthly subscription with occasional use. If you're sending 3 or more proposals a week, the time saved on formatting in Beautiful.ai adds up fast enough to justify the cost.

Worth knowing before you commit to a paid tool: Beautiful.ai's Pro plan also gives you basic viewer analytics, so you can see whether a client actually opened the deck before you follow up, rather than guessing. That alone changes how a follow-up call starts; "did you get a chance to look at it" lands very differently when you already know the answer. Canva and Google Slides don't offer this out of the box, you'd need a separate link-tracking tool layered on top.

Following up without sounding pushy

Most proposals that get a "yes" get it within 3 to 5 business days, and most that don't get a reply at all rarely come back on their own, so a planned follow-up matters more than a perfect deck. A simple approach: follow up on day 3 if there's been no reply, reference something specific from the proposal (not "just checking in"), and set a soft deadline tied to your own timeline, not an artificial urgency tactic. "I want to make sure we can still hit the week-1 start date we discussed" does real work; "let me know if you have any questions!" does none.

If a client goes quiet after an initial positive conversation, it's worth a direct question rather than another gentle nudge: has something changed, is the timing wrong, or is the price the sticking point. Clients often won't volunteer a real objection unless asked plainly, and chasing with soft check-ins for weeks wastes time you could spend on a proposal that's actually moving.

What I'd actually tell you about this structure

The slide most people skip, and shouldn't, is slide 2, the problem restated in the client's own words. It's tempting to jump straight to your solution because that's the part you're proud of, but a client reads that second slide and decides in about five seconds whether you actually understood them or whether this is a generic pitch with their logo pasted on. Spend the extra two minutes getting that one sentence right; it does more selling than the rest of the deck combined.

I'd also push back on the instinct to add more slides to feel thorough. A longer deck doesn't read as more professional, it reads as less decisive. If you're worried about leaving something out, put the extra detail in a one-page appendix the client can read if they want it, not in the main flow they have to sit through. If someone has to sign off first, getting a manager to approve a client deck helps.

Common mistakes that make a fast deck look slow

• Reusing the exact same "why us" slide verbatim across every proposal. Property managers and procurement people talk to each other more than businesses expect; a generic slide that reads the same for every prospect undercuts the personalization the rest of the deck is doing.
• Burying the exclusions. Leaving out what's not included feels like it makes the scope look bigger, but it's the single most common source of a dispute later. State it as plainly as what is included.
• Sending the deck as an email attachment with no cover note. A one-line email ("here's the proposal we discussed, happy to walk through it on a call") gets opened faster than a cold attachment.
• Using a stock photo on the title slide instead of a photo of the actual job site or product. It's a small thing, but a client notices the difference between a generic landscaping photo and a photo of their own property. Sourcing better images is covered in finding good photos that fit your brand.

When a deck is the wrong format entirely

For a genuinely simple, one-line quote (a fixed-price repair, a single service with no variables), a plain PDF or a one-page document is faster to produce and faster for the client to read than any slide deck, however short. Clients in that situation often prefer it, since it reads as "here's your answer" rather than "here's a presentation about your answer." Reach for the 8-slide structure when there's a real decision to walk someone through, not for every quote you send.

How I'd approach this

If you're sending the same style of proposal to a steady stream of similar clients, the next real improvement isn't a better template, it's pulling your actual pricing, scope and client details automatically into the deck from whatever system already holds that data, instead of retyping it every time. That's a small custom build, not a bigger slide tool, and it's the kind of thing worth doing once your proposal volume makes manual rebuilding the real bottleneck.