Proposals & Estimates

Estimates vs proposals

When to send a ballpark estimate versus a signed proposal, and how to convert one into the other.

Updated 2026-11-20

FirstSlate's builder produces two kinds of document from the same scope and pricing: an estimate, which your client can approve without signing anything, and a proposal, which carries your contract terms and requires an e-signature. Use whichever matches how firm the number is.

Where to find it

There are two ways in. On the project's Proposal card in the Project Hub, once the brief is in, click Build Proposal for a proposal or Start with Estimate to open the builder as an estimate. Or open the builder and use the Proposal and Estimate buttons beside the client name. Switching is only available while the document is a draft; once it's sent, the type is locked for that document.

When to use an estimate

Send an estimate when you want to share pricing and scope before committing to a formal agreement, an early ballpark the client can react to, adjust, or approve. Estimates carry the same line items, add-ons, and pricing as a proposal, but no contract terms and no signature. The Contract Terms card appears dimmed in the builder to show it isn't part of the document.

When to use a proposal

Send a proposal when the number is final and you want a binding agreement. Proposals include your contract terms and require the client to sign before the project moves forward.

How your client responds

The two documents ask for different actions:

  • Estimate: your client reviews the scope, answers Yes, add it or No thanks on each optional add-on, and clicks Approve Estimate, typing their name to confirm. The public page is explicit that "No signature required at this stage." They can also click Request Changes with a note back to you instead of approving.
  • Proposal: your client reviews the same scope, then goes through an Accept Proposal flow that ends in Sign & Accept, a typed-name signature (with an optional script style or drawn signature) plus any initials you've required on individual sections.

You're notified either way. An estimate approval records the name and the time. A proposal signature also records the signer's IP address and a content hash of exactly what was signed; see how clients accept and e-sign.

Converting an approved estimate into a proposal

Once a client approves an estimate, the Hub card shows Convert to Proposal, and the builder shows an Estimate Approved banner with the same button. Converting switches the document type to proposal and drops it back to Draft, so you add contract terms and send it for signature without re-entering the numbers.

It carries over the scope, pricing, and the client's add-on choices. Add-ons they accepted become part of the base scope. Add-ons they declined stay as optional items, already marked as declined, so your client doesn't have to choose again. The estimate's approval stays on record on the Hub card. Because the proposal is a new document your client hasn't seen, its view count starts again from zero.

Plan availability

Both estimates and proposals, including e-signature on proposals, work on every plan, including Free. See plans and limits.

Common questions

Can I start with a proposal and switch to an estimate later?

Yes, as long as the document is still a draft. Once you send it, the type is fixed for that document; recall it to Draft first if you need to change it. See send and track.

Does an estimate expire like a proposal does?

Yes. An estimate's expiration date is enforced the same as a proposal's: once it passes, your client can no longer approve or request changes without you reopening it. Expired estimates also offer Convert to proposal when you resolve them. See proposal expiration and stalled deals.

Still stuck?

We read every message and reply fast.

Contact us