What a contractor proposal actually is (and isn't)
A contractor proposal is a written offer to perform specific work for a specific price, under specific terms, by a specific date. When the customer signs it — physically or electronically — it becomes a binding contract.
It's not the same as an estimate. An estimate is a ballpark, often informal, that the contractor can revise without penalty. A proposal is a commitment: here's exactly what we'll do, exactly what you'll pay, and exactly when. The difference matters because customers behave differently with each. They negotiate estimates. They sign proposals.
Most contractors lose deals not because of price but because their document feels like an estimate even when they meant it to be a proposal. Three things separate a winning proposal from a wobbly one: scope clarity, line-item math, and a clean signature flow.
What every contractor proposal must include
Customers are more likely to sign a proposal that anticipates their questions. The strongest contractor proposals include these seven sections — every time.
- Letterhead with your business name, license number, and contact info
- A unique proposal number and issue date
- Customer name and job-site address
- Scope of work broken into line items — quantity, unit, unit price, subtotal
- Totals (subtotal, tax, discount if any, deposit amount, total contract price)
- Schedule (start window, expected duration, completion target)
- Payment terms (deposit, milestone payments if any, final payment trigger)
- Acceptance language and signature line
How to structure line items so customers say yes
Line items are where contractors usually leave money on the table. Too few, and the customer feels like they're signing a blank check. Too many, and they feel nickel-and-dimed. The right number is 5–15 for residential, more for commercial.
Each line item should answer three questions: what is it, how much of it, and what does it cost? 'Architectural shingles, 24 squares, $145/sq, subtotal $3,480' is a line item. '$3,480 for materials' is not.
Group related work into descriptive lines. 'Tear-off + disposal' is one line, not three. 'Underlayment + ice & water shield' is one line, not two. Customers don't want to count nails — they want to know what they're buying.
- Use quantities + units consistently (sq ft, linear ft, hour, day, each)
- Show unit prices so customers see the math
- Mark which items are taxable separately from non-taxable
- Group materials and labor where it makes sense, separate where it doesn't
- Reserve a 'Premium upgrades' section for optional add-ons
Deposit and payment schedule basics
Most states cap residential contractor deposits at 10–33% of the contract value, with hard rules around when remaining payments can be collected. Check your state's contractor licensing board. Florida, for example, caps deposits at 10% for residential work over $2,500.
Beyond the legal floor, a clear payment schedule reduces friction. The two most common structures: a deposit at signing followed by final payment on completion, or a deposit at signing plus a progress payment when materials are delivered or a major milestone hits.
State the trigger for each payment, not just the amount. 'Final payment due upon completion' is vague. 'Final payment due within 5 business days of customer's walkthrough sign-off' is enforceable.
ESIGN, UETA, and why phone signatures count
The federal Electronic Signatures in Global and National Commerce Act (ESIGN) and the Uniform Electronic Transactions Act (UETA, adopted by every state except New York) make electronic signatures legally equivalent to handwritten ones — including signatures drawn with a finger on a phone.
For an e-signature to be binding, four things must be true: the signer intended to sign, they consented to electronic transaction, the signature is associated with the document, and the signed record is retained and accessible.
The simplest way to satisfy all four: send the proposal as a link the customer opens on their phone or computer. They review, draw their signature, tap accept. Your system captures the signature image, the timestamp, the IP address, and a hash of the exact document version they saw. That audit trail is what makes the signature enforceable in court.
Five proposal mistakes that lose deals
Some of these we've made ourselves. Most contractors make at least three of them.
- Sending a Word doc as an email attachment — customer prints, signs in pen, scans, emails back. Three steps where one would do.
- Burying the total in dense text — the customer should see the number in the first 5 seconds.
- No deposit schedule — leaves both sides confused about when money moves.
- Vague scope ('install new kitchen') — every dispute starts with a vague scope.
- No expiration date — proposals from six months ago come back to bite you when material costs have risen 12%.
When to send an estimate vs a proposal
Send an estimate during the early conversation when you don't have enough information to commit. Send a proposal when you've measured the job and you're ready to sign.
Most contractors send too many estimates and not enough proposals. If a customer is qualified, ready to buy, and the scope is clear, skip the estimate. A proposal forces the conversation toward a decision.
Next steps: write your first proposal in 10 minutes
Pick one upcoming job. Open BuildEasyPro (or your tool of choice). Build the proposal with the seven sections above. Send the link by text or email. Watch what happens.
Most contractors are surprised by how much faster customers sign when the proposal is clean, structured, and signable from a phone. If you want to try it on a real job, start a free 14-day trial — every feature in this guide ships out of the box.