Skill Tracer
Skills › Knowledge Work Plugins › proposal-builder › proposal_structure.md

proposal_structure.md

120 lines · small-business/skills/proposal-builder/reference/proposal_structure.md at 2574e29

Open on GitHub
1# Proposal Structure
2
3Use the owner's own template when one exists. This structure is the fallback, and it is also what to offer to save as their template if they have never had one.
4
5---
6

Proposal Structure

Use the owner's own template when one exists. This structure is the fallback, and it is also what to offer to save as their template if they have never had one.


Raw lines 1 to 6
7## Sections, in order
8
9**1. Header**
11Owner's business name and contact, customer name and contact, date, proposal number, and a validity date. The validity date protects the owner when material prices move.
13**2. What you asked for**
15Two or three sentences restating the customer's need in their own words, pulled from the discovery. This is not filler — customers scan for whether the vendor actually understood the job, and most proposals fail that test in the first paragraph.
17**3. What we'll do**
19The scope, in specifics. Quantities, equipment, locations, and sequence where it matters.
21Write it so a stranger could tell whether the work was completed. "Upgrade the HVAC system" is not scope. "Replace five rooftop units with Carrier 48TC, reconnect existing ductwork and electrical, haul away old units" is.
23**4. What's not included**
25The most valuable section in the document. Scope disputes are where service businesses lose money, and they begin with what nobody wrote down.
27Include anything a reasonable customer might assume is covered:
29```
30Not included:
31 - Ductwork replacement or modification beyond reconnection
32 - Electrical service upgrades, if required by inspection
33 - Roof repair or patching beyond the curb penetrations
34 - Crane or lift, if roof access proves inadequate (see assumptions)
35 - After-hours or weekend labor
36```
38Every line is a conversation that happens now instead of an argument later.
40**5. Assumptions**
42The conditions the price depends on, in customer-visible language, each with what happens if it turns out otherwise:
44```
45This price assumes:
46 - Roof access by the existing ladder. If a crane or lift is required, add USD 1,800.
47 - Existing electrical service is adequate. If an upgrade is needed, quoted separately.
48 - Work performed during normal business hours.
49```
51Naming the consequence converts a dispute into a pre-agreed change order.
53**6. Investment**
55The price, broken into lines the customer recognizes as decisions. Options presented as clearly labeled tiers if used, with the recommended one named.
57**7. Timeline**
59Start window, duration, and what it depends on. Say what would move it — permit approval, equipment lead time, customer access. A timeline with no dependencies listed is a promise the owner cannot keep.
61**8. Terms**
63Deposit, payment schedule, change-order process, warranty, validity window.
65**9. Next step**
67One sentence. Not "we look forward to hearing from you" — an actual instruction:
69```
70Sign below and I'll order the units. Lead time is 3 weeks from deposit.
71```
73**10. Signature block**
75Both parties, with dates. When DocuSign routes it, the fields go here.
77---

Sections, in order

1. Header

Owner's business name and contact, customer name and contact, date, proposal number, and a validity date. The validity date protects the owner when material prices move.

2. What you asked for

Two or three sentences restating the customer's need in their own words, pulled from the discovery. This is not filler — customers scan for whether the vendor actually understood the job, and most proposals fail that test in the first paragraph.

3. What we'll do

The scope, in specifics. Quantities, equipment, locations, and sequence where it matters.

Write it so a stranger could tell whether the work was completed. "Upgrade the HVAC system" is not scope. "Replace five rooftop units with Carrier 48TC, reconnect existing ductwork and electrical, haul away old units" is.

4. What's not included

The most valuable section in the document. Scope disputes are where service businesses lose money, and they begin with what nobody wrote down.

Include anything a reasonable customer might assume is covered:

Not included:
  - Ductwork replacement or modification beyond reconnection
  - Electrical service upgrades, if required by inspection
  - Roof repair or patching beyond the curb penetrations
  - Crane or lift, if roof access proves inadequate (see assumptions)
  - After-hours or weekend labor

Every line is a conversation that happens now instead of an argument later.

5. Assumptions

The conditions the price depends on, in customer-visible language, each with what happens if it turns out otherwise:

This price assumes:
  - Roof access by the existing ladder. If a crane or lift is required, add USD 1,800.
  - Existing electrical service is adequate. If an upgrade is needed, quoted separately.
  - Work performed during normal business hours.

Naming the consequence converts a dispute into a pre-agreed change order.

6. Investment

The price, broken into lines the customer recognizes as decisions. Options presented as clearly labeled tiers if used, with the recommended one named.

7. Timeline

Start window, duration, and what it depends on. Say what would move it — permit approval, equipment lead time, customer access. A timeline with no dependencies listed is a promise the owner cannot keep.

8. Terms

Deposit, payment schedule, change-order process, warranty, validity window.

9. Next step

One sentence. Not "we look forward to hearing from you" — an actual instruction:

Sign below and I'll order the units. Lead time is 3 weeks from deposit.

10. Signature block

Both parties, with dates. When DocuSign routes it, the fields go here.


Raw lines 7 to 78
79## Length
81Most SMB proposals should run two to four pages.
83An RFP response goes as long as the RFP requires — compliance beats brevity there, and page limits are usually mandated anyway.
85A repeat customer for routine work can take one page. Do not make a customer who has bought this six times read a full proposal.
87---

Length

Most SMB proposals should run two to four pages.

An RFP response goes as long as the RFP requires — compliance beats brevity there, and page limits are usually mandated anyway.

A repeat customer for routine work can take one page. Do not make a customer who has bought this six times read a full proposal.


Raw lines 79 to 88
89## Tone
91Match [the shared voice profile](../../../shared/voice-profile.md). A proposal that reads nothing like the owner's emails is jarring, and the customer has usually already exchanged mail with them.
93**If that file has no profile yet**, follow its "When there is no sample" instruction — ask for three emails the owner was happy with. If they decline, write plain and neutral and say the proposal is un-voiced. Never invent a personality.
95Plain language throughout. This audience sells to people reading on a phone between jobs.
97Avoid the standard proposal padding: no mission statement, no "why choose us" section, no stock photos of handshakes. Owners in this segment win on being clear and being responsive, and a padded document undercuts both.
99---

Tone

Match the shared voice profile. A proposal that reads nothing like the owner's emails is jarring, and the customer has usually already exchanged mail with them.

If that file has no profile yet, follow its "When there is no sample" instruction — ask for three emails the owner was happy with. If they decline, write plain and neutral and say the proposal is un-voiced. Never invent a personality.

Plain language throughout. This audience sells to people reading on a phone between jobs.

Avoid the standard proposal padding: no mission statement, no "why choose us" section, no stock photos of handshakes. Owners in this segment win on being clear and being responsive, and a padded document undercuts both.


Raw lines 89 to 100
101## Formatting
103- DOCX and PDF, both, every time. The customer wants the PDF; the owner sometimes needs to edit.
104- Owner's logo and colors when available from the template or brand assets
105- Price table right-aligned on numbers, currency formatted as currency
106- Page numbers and the proposal number in the footer, so pages don't get separated
107- Signature block on its own page if the document runs past two pages
109---

Formatting

  • DOCX and PDF, both, every time. The customer wants the PDF; the owner sometimes needs to edit.
  • Owner's logo and colors when available from the template or brand assets
  • Price table right-aligned on numbers, currency formatted as currency
  • Page numbers and the proposal number in the footer, so pages don't get separated
  • Signature block on its own page if the document runs past two pages

Raw lines 101 to 110
111## Offering to save it as a template
113If the owner had no template and the proposal comes out well, offer once:
115```
116Want me to save this layout as your standard proposal template? Next one would
117start from it instead of from scratch.
118```
120If yes, store it so later runs match. That is the difference between a skill that saves an evening once and one that saves an evening every week.

Offering to save it as a template

If the owner had no template and the proposal comes out well, offer once:

Want me to save this layout as your standard proposal template? Next one would
start from it instead of from scratch.

If yes, store it so later runs match. That is the difference between a skill that saves an evening once and one that saves an evening every week.

Raw lines 111 to 120