Proposal automation for field service businesses: how to quote the same day.

Where the time actually goes

Ask an owner why quotes take three days and the answer is usually "we're busy". Look at the process and the real cause is different. The engineer writes notes on paper or in their phone. Someone in the office reads them, opens last month's quote, changes the customer name, adjusts the line items and hopes they used the current labour rate. The document is saved as a PDF, attached to an email and sent. Nobody records that it went out, so nobody chases it.

None of those steps needs judgement. The judgement happened on site, when the engineer decided what the job required. Everything after that is copying, formatting and sending, and that is exactly the work a system does well.

What proposal automation actually is

Proposal automation means the quote is generated from data you already hold, rather than typed from scratch. A form or CRM record holds the customer, the site, the scope and the line items. A template turns that record into a branded document. A rule decides who needs to approve it before it goes out. The finished PDF is sent, filed against the customer record, and a follow-up is scheduled.

It is not an AI writing your quotes from a blank page. For pricing documents you want the opposite: fixed rates, fixed wording, and a person approving anything unusual. Where AI earns its place is at the edges, for example turning an engineer's rough voice note into a clean scope description that a human then checks.

The five parts of a working build

1. A single place the job details live

The proposal can only be as good as the record it is built from. That means one CRM record per opportunity, with the customer, site address, service type and survey notes captured in fields rather than in an email thread. For most small service businesses Monday.com is enough. Pipedrive and HubSpot work too. The tool matters less than the discipline of entering the job once, in one place.

2. A rate card the owner controls

Prices should not live inside a Word document. Put service types, labour rates, call-out charges and standard parts costs in one sheet or board that the owner maintains. When a rate changes, it changes once, and every proposal from that point uses it. This single step removes the most common quoting error we see: an old rate quietly reused because someone copied last year's file.

3. A template that produces the document

The template holds the layout, terms, payment schedule and cover wording. Merge fields pull in the customer details and line items from the record. The output can be a branded PDF, or a live web page the customer opens from a link, which also tells you when they have looked at it. Both are reasonable. The PDF is familiar; the web page gives you visibility.

4. An approval step for anything non-standard

Automation should not mean quotes leaving the building unchecked. A sensible rule is that standard jobs under an agreed value go straight out, and anything above it, or anything with a manual price override, is held for the owner to approve with one tap. In practice that approval can happen in WhatsApp or email rather than in a dashboard the owner never opens.

5. Sending, filing and follow-up

Once approved, the proposal is emailed to the customer, saved against their record, and the deal moves to a "quote sent" stage. A follow-up is scheduled automatically, and cancelled if the deal is marked won or lost first. This is the part most businesses skip and the part with the clearest payback: most quotes that go cold were not rejected, they were simply never chased.

How the pieces connect

The connecting layer is usually Make.com. It watches the CRM for a new survey submission, reads the rate card, fills the template, routes the approval and sends the result. It also writes the outcome back to the CRM so the pipeline is always current. If you want the detail on the document side, our proposal generation stack page covers the components, and the proposal and document automation service covers how we deliver it.

The same pattern extends beyond quotes. Once a proposal is accepted, the accepted record can raise the job, create the deposit invoice in Xero and notify the office. That is the point where a proposal system starts to become an operations system.

It also gives you data you probably do not have today: how many proposals go out each week, how long they take from survey to send, which service types convert, and how many are still open. Once every quote passes through the same pipeline, those numbers come for free, and decisions about pricing and capacity stop being guesses.

What it looks like in production

We have this running for a UK commercial kitchen extraction business, where proposals are generated from a WhatsApp conversation and approved by the owner before they are sent. In the first 90 days the system produced 14 proposals alongside 22 invoices, with roughly ten hours a week saved on CRM admin. The full 90-day write-up has the figures, and the walkthrough post shows the workflow itself. Those numbers come from one business and one build, so treat them as an indication of what is possible rather than a guarantee.

Quotes are only one document in the job. The other one every extraction cleaner has to produce is the compliance certificate, which we cover in TR19 certificate automation.

Where it goes wrong

• Automating a messy process. If nobody agrees what a standard job costs, a template will only produce inconsistent quotes faster. Fix the rate card first.
• Too many special cases. Try to cover every edge case and the build never finishes. Automate the 80% of jobs that are routine and let the rest go through manual approval.
• No owner for the rate card. If nobody is responsible for keeping prices current, the system will quote confidently at the wrong price.
• Engineers skipping the form. The survey has to be quick enough to complete on a phone, in the van, in a couple of minutes. If it takes longer, it will not be filled in.
• No follow-up. A proposal generator without the chase step captures perhaps half the value.

What it costs and how long it takes

A focused proposal build, meaning CRM set-up, rate card, template, approval routing and follow-up, typically takes two to four weeks depending on how much already exists. A business with a working CRM and clear pricing sits at the shorter end. A business starting from spreadsheets and email sits at the longer end. Running costs are modest: a CRM seat or two, a Make.com plan, and document generation, usually well under what the office time spent on quotes costs each month.

A simple test for whether it is worth doing: count the quotes you send in a month, multiply by the minutes each one takes to produce, and add the value of the jobs that went cold without a follow-up. If that figure is more than a few hours of admin and a handful of missed jobs, the build pays for itself quickly.

For more on how we work with contractors and service businesses, see the field services industry page, and the HVAC sales operations guide for the wider pipeline this sits inside.