A homeowner calls and asks for a "quote" on a kitchen remodel. You send a polite Word document with a number and call it a "proposal." Six months later you are in small-claims court because the homeowner thought your number was binding and you thought it was informational. The legal and commercial differences between proposal, estimate, and bid are not academic. They determine whether your number is binding, whether the customer can hold you to it, and whether either party has a contract. This guide is the working contractor's framework.
BuildCrux is contractor management software with AI estimating that produces estimates, proposals, and bids from the same line-item data. The framework below is what every contractor should run through before sending a price to a customer, regardless of what they call the document.
Why the words matter
A signed proposal is often a contract
Most jurisdictions treat a signed proposal as the contract itself when the proposal contains scope, price, and the parties involved. If your proposal does not include the terms you actually want to govern the project (payment schedule, retainage, change order procedure, dispute resolution), the customer's signature still binds you anyway. Either upgrade your proposals to full contract terms, or call them estimates and follow with a contract.
A bid is firm; an estimate is not
When you submit a hard bid in response to an ITB, your number is firm; if the owner accepts, the contract price is locked. Estimates are informational and can be revised. Customers do not always understand the difference. If you send a friendly "estimate" that is actually a bid, the customer may treat your number as their contract price even after scope grows.
The customer remembers what you called it
You said "estimate" verbally. The customer heard "quote." You sent a document titled "proposal." The customer signed it expecting that price to hold. Two months later you are explaining why the actuals came in 20% over because of unforeseen conditions. The naming on the document drove the customer's expectation; the legal reality does not always match.
Different audiences expect different documents
Commercial owners expect bids in response to ITBs. Tenant reps expect proposals on TI work. Residential homeowners expect either estimates (for early conversations) or proposals (when they are ready to commit). Picking the wrong document type for the audience signals inexperience. Picking the right one signals professionalism.
The BuildCrux Method for Pricing Documents
Accurate Estimating
AI takeoff produces line-item data once. From the same data you generate an internal estimate (full detail), a customer-facing proposal (line items + scope + terms), or a hard bid (firm price + alternates + exclusions). Same source, different formats, different legal weight.
- Single source of line-item data
- Multiple output formats from same data
- Document type chosen for audience
Structured Planning
Proposal includes scope of work, price, schedule, payment terms, exclusions, alternates, insurance certificates, signature block. Estimate is internal-only with full takeoff detail. Bid is firm price plus all of the above formatted to the ITB requirements.
- Proposal includes scope + terms + signature block
- Estimate is internal-only with full detail
- Bid formatted to ITB requirements
Controlled Execution
Document type tracked in the project record. If the customer signed a proposal, the proposal is the contract. If the customer signed a separate contract after the proposal, the contract is the contract. Single source of truth on what document governs.
- Document type tracked in project record
- Signed-document hierarchy clear
- Audit trail for any pricing dispute
Change Order Management
Whatever document originated the contract value sets the baseline for change orders. CO unit costs inherit from the original document. The CO modifies the original; it does not replace it. If the original was an estimate (not a contract), the CO chain is murky and disputes follow.
- CO unit costs inherit from original document
- Document chain tracked from original to current
- Disputes resolved against the controlling document
Financial Visibility
Pipeline value tracked separately for estimates (informational), proposals (commitment-stage), and bids (in active competition). Win rate tracked per document type. Helps you understand which conversion stages you actually close at.
- Pipeline value by document type
- Win rate by document type
- Conversion analytics for sales process
Side-by-side: estimate vs proposal vs bid
| Dimension | Estimate | Proposal | Bid |
|---|---|---|---|
| Legal weight | Informational; non-binding | Often becomes contract on signing | Firm; binding if accepted |
| Typical audience | Early-stage homeowner conversation | Customer ready to commit | Owner running ITB process |
| Format | Line items, often informal | Full scope + terms + signature block | Firm price + alternates + exclusions |
| Revisable? | Yes, freely | Yes, before signing; no after | No once accepted |
| Includes contract terms? | Usually no | Usually yes | Reference to ITB-supplied contract |
| Customer expectation | "Ballpark" | "This is what I will sign" | "This is the contract price" |
| Competitive context | One-on-one | One-on-one or short list | Competitive vs other bidders |
Generate the right document for the right audience
BuildCrux outputs estimate, proposal, or bid format from the same line-item data. 30-day money-back guarantee.
Get StartedWhen to use each one
| Situation | Use | Why |
|---|---|---|
| Homeowner asking "ballpark" by phone | Estimate | Non-binding; sets expectations early |
| Customer ready to sign after a walkthrough | Proposal | Becomes the contract on signing |
| Commercial ITB on a 50-sheet drawing set | Bid | Firm price required; competitive context |
| Tenant rep evaluating 3 GCs on a TI | Proposal | Commitment-stage but not ITB-style |
| Repair work after damage with insurance involved | Estimate first, then bid for the insurer | Insurer needs firm bid; homeowner conversation starts as estimate |
| Friend asking what their kitchen would cost | Estimate (verbal or rough written) | Pre-commitment; do not box yourself in |
| Custom home from a long-term repeat client | Proposal | Trust + commitment context |
Case study: a $52K courtroom misunderstanding
A residential remodeler in San Antonio sent a Word document titled "Proposal for Kitchen Remodel" to a homeowner. The document listed scope and a price of $84,000. The homeowner signed it. Three months into the project, unforeseen pipe corrosion drove the actual cost to $136,000. The contractor billed for the overage. The homeowner refused to pay anything above $84,000, citing the "Proposal" they had signed.
In small-claims court, the judge ruled that the signed proposal constituted a contract for $84,000. The contractor's argument that the proposal was an "estimate" failed because the document was titled "Proposal" and the homeowner had signed below a price line that read "Total Project Cost: $84,000." Unforeseen conditions, the contractor argued, should have generated change orders. The judge agreed in principle but noted that no change orders had been issued. Final ruling: contractor recovers $84,000; the additional $52,000 of incurred cost was the contractor's loss. Had the original document been clearly labeled "Estimate" with a follow-up contract issued separately for the agreed scope, the change-order conversation would have been routine.
Why pricing documents originate in BuildCrux
BuildCrux outputs estimate, proposal, or bid format from the same line-item data. Document type is selected per use case; each format includes the right scope, terms, and signature blocks for its legal weight. Customer-facing documents are sent through the customer portal with e-signature. Document chain (estimate → proposal → contract → COs) tracked in the project record so you always know which document governs.
BuildCrux Feature
AI Blueprint Estimates
AI-powered estimates from your blueprints
Learn moreFrequently asked questions
What is the difference between a construction estimate and a proposal?+
An estimate is informational and revisable; you can update the number as scope clarifies. A proposal is a customer-facing offer that often becomes the contract when the customer signs. Estimates are early-stage; proposals are commitment-stage.
What is the difference between a proposal and a bid?+
A proposal is a one-on-one offer to a specific customer, typically prepared after a walkthrough or design conversation. A bid is a firm price submitted in response to a competitive ITB with multiple contractors bidding the same project. Both are binding on acceptance; the competitive context differs.
Is a signed construction proposal a contract?+
In most jurisdictions, yes — when the proposal contains scope, price, and identifying parties. The customer's signature creates a contract bound by the proposal's terms. If your proposal does not include the terms you want to govern the project, you are still bound by the proposal as the contract.
Can a contractor change the price after sending an estimate?+
Yes, an estimate is informational and revisable. As scope clarifies or unforeseen conditions surface, the estimate can be updated. The customer is not yet bound to the price. If the customer expects a firm price, they should ask for a proposal or bid.
Should I send an estimate or a proposal first?+
For early-stage conversations where scope is not yet defined, send an estimate. As the customer commits and scope finalizes, follow with a proposal. The estimate manages expectations; the proposal closes the deal.
What should be included in a construction proposal?+
Scope of work, price (with line items where appropriate), payment schedule, schedule (with substantial completion target), exclusions and clarifications, allowances (for items not yet selected), change order procedure, insurance certificate references, and signature blocks for both parties.
What is the difference between a hard bid and a soft bid?+
A hard bid is a firm fixed price submitted in response to a competitive ITB; if accepted it becomes the contract. A soft bid (sometimes called a budgetary number) is informational and revisable, used when scope is incomplete or as a budget estimate for owner planning. Soft bids are essentially estimates.
The bottom line
Estimate, proposal, and bid are three different documents with three different legal weights and three different customer expectations. Picking the wrong one for the audience signals inexperience and creates dispute risk. Picking the right one — and being deliberate about what the document does and does not bind you to — closes more deals and prevents most contract disputes before they happen.
