Customer proposals and approvals

What a customer proposal is

A customer proposal is a secure, customer-facing link for an official estimate revision. It starts with the estimate's base scope and lets the customer choose the approved add-ons or package options you prepared for that revision. The customer does not need a CrafterOps account.

Use it when the customer needs to choose between packages or add services without your team manually rebuilding the estimate after every choice.

Build options before sending

Open Customer options from a working estimate and add any of these choices:

• Required items that are always included.
• Optional standalone add-ons, which can be preselected or unselected.
• Choose one packages, where the customer selects exactly one option.
• Choose one (optional) packages, where the customer can select one option or none.

Each option can have a price, taxable status, unit, default quantity, allowed quantity range, description, and estimated internal cost. Keep the customer description focused on the result they receive; internal cost detail stays private.

Options can be edited only before approval or job conversion. Changing options after an estimate has been sent prepares a working revision, so send a new official revision when the customer needs to review the change.

What the customer sees

The proposal page shows:

• Base estimate total.
• Available add-ons and packages.
• A live options subtotal, tax on taxable options, final total, and deposit due.
• The customer name and consent required to approve.

CrafterOps recalculates the total from the saved revision snapshot—not from editable live estimate data. The proposal page does not accept credit-card payments.

Approval and the deposit

When the customer approves, CrafterOps records the selected lines, accepted base amount, options subtotal, options tax, accepted total, deposit due, approver name, timestamp, IP address, and user agent. The revision is locked and the estimate is marked approved.

The system creates a deposit record and queues the follow-up work: creating the job and sending contractor and customer confirmation emails. Your team records deposit payments, corrections, or an owner-approved waiver from the estimate. A job remains in the appropriate awaiting-deposit state until the deposit is received or waived.

Payment-term guardrails are recalculated from the customer-selected total, so the proposal cannot increase the due-at-approval amount past a configured applicable cap.

Safe operating rules

• Verify the option prices, tax, and payment terms before sending.
• Send a new revision for any scope or price change after delivery.
• Do not treat a proposal link as a payment page.
• Record deposits only after confirming the payment was actually received.
• Preserve the approval record; it is the evidence of the customer's selected work and consent.