Automate Quote Generation
A quote that takes three days to write is a quote that competes with someone who answered in three hours. Most estimators know this feeling. The customer called Monday, you measured on Tuesday, you built the numbers in a spreadsheet on Wednesday, and by Thursday the customer had already signed with the other company. They were not cheaper. They were first.
Speed is only half the case for automating quotes. The other half is that a quote is a promise with a price on it, and promises made from copied spreadsheets tend to carry old prices, forgotten line items, and last year's markup. If you are a contractor, an agency estimator, or anyone who builds proposals for a living, this article walks through how to automate the repeatable parts while keeping your judgment where it belongs.
What actually goes into a quote
Before you automate anything, separate the three things a quote mixes together.
- Facts about the customer and the job. Name, address, scope, measurements, dates, and constraints.
- Prices and rules. What a unit of labor, material, or service costs, and how you add markup, tax, and discounts.
- Presentation and terms. The layout, the payment schedule, the warranty, the exclusions, and the signature block.
Messy quoting happens when all three live in one document. The estimator types facts, remembers prices, and edits terms by hand, all in a single file. Automation works when each layer lives in its own place and the quote is assembled from them.
The quote data model, in plain terms
A good quote system, even a simple one, rests on a handful of records. You can store them in a database, a well structured spreadsheet, or a quoting tool. The tool matters less than the shape.
| Record | What it holds | Example |
|---|---|---|
| Customer and site | Who and where | Business name, job address, contact |
| Opportunity | The job being quoted | Roof replacement, 2,400 square feet |
| Quote | One priced offer for an opportunity | Version 2, valid 30 days |
| Quote line | One priced item | 60 bundles of shingles |
| Price book item | The standard price and unit | Shingles, per bundle, cost and sell price |
| Assembly | A bundle of items and labor for a common task | Tear off and replace per square |
| Terms template | Reusable clauses | Payment schedule, warranty, exclusions |
The two that matter most are the price book and the assembly. An assembly is a recipe. If your crew always needs the same underlayment, fasteners, labor hours, and disposal for a square of roofing, record that once. Then the estimator enters the number of squares and the system builds the lines. For an agency, an assembly might be a website discovery phase with defined hours by role. For a service business, it might be a standard maintenance visit.
The price book is the heart of it
A price book is a maintained list of what you charge. Treat it as a controlled document, not a convenience. Each item should record its unit, its cost, its sell price or markup rule, the date it was last reviewed, and who owns it.
Some practical rules.
- Store cost and sell price separately, so you can see margin on every line.
- Give each item an effective date. When a supplier raises a price, you do not want old quotes recalculated, and you do not want new ones using the old figure.
- Name an owner and a review rhythm. A quarterly review is enough for stable items, and a monthly one for volatile materials.
- Keep labor rates by role, not by person. People change, roles last.
- Add a check that flags any item not reviewed in a set number of days, so stale prices cannot hide.
If you remember one thing from this section, it is that most automation failures in quoting are price book failures. A flawless quote builder pulling a wrong price produces the wrong answer faster.
A worked example, with illustrative numbers
This example is hypothetical. Suppose a small contractor quotes a deck. The estimator enters 300 square feet, pressure treated lumber, and a stair with five steps.
The system pulls three assemblies. Framing is priced per square foot of footprint, decking per square foot of surface, and stairs per step. Suppose the price book gives framing at 14 dollars, decking at 11 dollars, and stairs at 120 dollars per step, all as sell prices.
Framing is 300 times 14, or 4,200 dollars. Decking is 300 times 11, or 3,300 dollars. Stairs are 5 times 120, or 600 dollars. The subtotal is 8,100 dollars. If the contractor adds a 5 percent contingency, that is 405 dollars, giving 8,505 dollars before tax. A permit fee line is added as a pass through at actual cost.
Now the important part. Suppose the estimator wants to give a 6 percent discount. The system checks a rule, discounts above 5 percent need a manager's approval. It routes the quote to the owner, who approves or changes it, and the quote moves on. Nobody had to remember the policy.
The arithmetic here is invented, but the shape is what you want. The estimator provides facts and a few judgment calls. The system does the multiplication, applies the rules, and flags exceptions.
Approvals, so exceptions have a path
Approval rules turn your unwritten policies into steps. Common triggers include a discount above a set percentage, a margin below a floor, a quote total above a set value, a nonstandard payment term, or a line marked custom with no price book match.
Keep the rules few and explicit. If you require approval for everything, people will route around the system. If you require none, you have a pricing tool with no guardrails. A good starting point is two rules, one on margin and one on total value, and then adding more only when a real mistake happens.
Record who approved, when, and what they saw. If a customer later disputes a price, you need that trail.
Versioning, the part people skip
Customers change their minds. A quote is rarely sent once. It goes out, comes back with a request, and goes out again. Without versioning, you end up with files named final, final2, and really final, and nobody can say which one the customer accepted.
Build versioning in from the start.
- Each revision is a new version with its own number, and old versions are read only.
- A quote has a status such as draft, in approval, sent, viewed, accepted, declined, expired, or superseded.
- The customer sees only the current version, and accepts a specific version.
- A validity date is printed on the quote, and the system expires it. Material prices move, and an open ended offer is a risk.
When the customer accepts, freeze that version. The contract should refer to a version number, and your records should show exactly the text and the figures they saw.
E-signature, and what it does and does not do
E-signature lets a customer accept the quote online. In the United States, electronic signatures are generally recognized for commercial agreements under federal and state laws, but the details vary by type of contract, so check with counsel for anything unusual. This is not legal advice.
For your process, what matters is the evidence the tool keeps. A good e-signature record includes who signed, the email or identity used, the time, the document as it appeared, and an audit trail. Ask any vendor whether you can download the signed document and the certificate, and whether you keep access if you cancel the subscription.
Do not let the signature tool become the only copy. Save the signed PDF in your own storage, linked to the opportunity.
Turning a won quote into a project
The quote system should not end when the customer signs. That is when the real work starts, and it is where duplicate entry usually creeps back in.
On acceptance, the system should do the following automatically.
- Mark the opportunity as won and record the accepted version.
- Create a project record with the scope, the customer, and the site copied from the quote.
- Turn quote lines into a budget, with materials, labor, and subcontractor lines carried over, so you can compare estimated cost to actual cost later.
- Create the deposit invoice if the terms call for one.
- Notify the project manager and schedule a kickoff task.
- Create purchase requests for long lead materials.
Doing this means the estimate becomes the baseline for the job. After completion, you compare what you estimated with what happened, and feed the differences back into your price book and assemblies. This is the loop that makes your next quote better.
Failure modes to plan for
Stale prices. Covered above, and worth repeating. Add review dates and alerts.
Over-rigid assemblies. A recipe that cannot handle the odd job leads people to bypass the system. Allow a custom line, require a note, and trigger approval.
Rounding and tax surprises. Decide whether you round per line or on the total, and be consistent. Tax rules depend on the jurisdiction and the type of work, so confirm the treatment with your accountant, especially if you work across the island and in the mainland United States.
Quote and invoice drift. If the invoice is built from different data than the quote, customers see two numbers. Generate the invoice from the accepted quote.
Lost context. Photos, site notes, and measurements belong on the opportunity record, so the person building the quote does not need to dig through texts.
What to ask a vendor
- Can I define assemblies, and can they contain other assemblies?
- Can prices have effective dates, and does the system keep the price used on each historical quote?
- Can approval rules be edited by me, or does that need vendor services?
- How are versions and acceptance recorded?
- Can I export every quote, line, and signed document in a usable format?
- What integrations exist with my accounting and project tools, and are they included or extra?
What to do on Monday morning
- Pick your five most common jobs and write down the lines each one always includes.
- Put those lines into a single sheet with unit, cost, sell price, and last reviewed date. That is your first price book.
- Turn each common job into an assembly with a quantity driver, such as square feet, hours, or number of fixtures.
- Decide two approval rules and who approves.
- Choose a naming and versioning convention and use it today, even before you buy any tool.
You may find that a disciplined spreadsheet gets you most of the way. When the volume or the approvals outgrow it, you will already have the data model a tool needs.
If you want a hand connecting a quoting tool to your accounting and project systems, that is part of what Ozcorp InfraOps does. But the best first step is the one you can take this afternoon, with a pencil and your last five quotes.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.