Guide
How to automate quotes and estimates without losing control of your prices
Most of the time in a quote is not spent pricing. It goes into retyping notes, rebuilding documents and chasing supplier prices. Those parts can be automated or assisted. The price itself should stay with a person.
Where the time goes in a typical quote
A quote usually passes through the same stages, whatever the trade:
- Request. An email, a web form or a phone call, logged somewhere.
- Scope. A site visit, photos or a call to understand the job.
- Takeoff. Measurements and quantities, often from paper notes.
- Supplier prices. Requests to two or three suppliers, replies compared by hand.
- Pricing. Quantities × rates, plus labour, plus a margin someone decides.
- The document. A template copied, scope wording pasted from an older quote, exported to PDF.
- Review and send. The owner or a senior estimator checks it.
- Follow-up. If someone remembers.
Only stage 5 needs the estimator's judgment. Stages 3, 4 and 6 are mostly moving information from one place to another, and that is where the hours go.
What to automate, what to assist, what to keep human
| Stage | Class | What it looks like |
|---|---|---|
| Logging the request | Automate | Email and form requests create a job record with the customer's details and attachments. |
| Takeoff entry | Automate | A short form filled in on site feeds the estimate template directly; photos file themselves to the job. |
| Supplier price requests | Assist | AI drafts the requests from the quantities and lines the replies up in one table. The estimator approves the requests and picks the supplier. |
| Line items from a written request | Assist | For simple jobs, AI proposes line items from the request and similar past jobs, using your price list. The estimator edits and confirms. |
| Pricing and margin | Human | Stays with the estimator. The spreadsheet does the arithmetic; the judgment is theirs. |
| The quote document | Automate | Generated from the priced estimate and a library of standard scope wording. Nothing is sent from this step. |
| Review and send | Human | A named person approves every price before it reaches a customer. |
| Follow-up | Assist | Drafted from the thread on a schedule, approved in a batch, stopped when the customer replies. See automating client follow-ups. |
A worked example
Take an estimator who prices 12 quotes a week, spends about 20 minutes typing site notes into the estimate and about 25 minutes building each quote document. That is 12 × 45 minutes, or 9 hours a week, roughly 432 hours a year, spent moving information rather than pricing.
Those two steps are the ones to automate first: the data already exists in the estimator's notes, the template already exists, and a mistake is caught at review before anything is sent. Our example workflow map shows the same two steps inside a full quote-to-cash workflow.
Illustrative numbers. Measure ten of your own quotes before you decide.
What you need in place first
- A current price list or rate table. Automation that generates line items should only use your prices, never invent them. If your prices live in someone's head or in last year's spreadsheet, fix that first.
- One estimate template. If every estimator has their own version, agree on one.
- Standard scope wording. Collect the paragraphs you paste most often into a small library.
- One place where a job lives. A job tracker, a CRM or even a well-kept spreadsheet, so each step knows which job it belongs to.
Mistakes to avoid
- Letting AI set the price. It can propose quantities and line items from your price list. The margin and the final number need a person.
- Sending without review. Quotes are commitments. Keep an approval on every quote that leaves the business, including when the owner is away: decide who approves then.
- Automating a messy template. If the template is wrong, automation produces wrong quotes faster.
- Skipping the "before" measurement. Time ten quotes from request to sent, stage by stage, before you change anything.
How to start this week
- Time your next ten quotes, stage by stage. A notepad is enough.
- Mark each stage automate, assist or human, using the table above.
- Total the hours in the automate and assist stages. Put them into the ROI calculator.
- Start with the stage that has the most hours and the cheapest mistakes, usually the document or the takeoff entry.
For the full method behind this, see how to find what to automate.
Get started
Start with one workflow.
Book a free 20-minute build call. You'll leave with a clear view of what to automate first, and a proposal the same day.