Trades: From Phone Call to Quote Without Losing the Evening

In most trade businesses the quote gets written after hours. The day belongs to the job site; the evening belongs to the desk — and to the stack of enquiries that has been sitting there since Monday.

That is the most expensive bottleneck in the business, for a reason that rarely gets said out loud: whoever sends a clean quote first wins disproportionately often. Not because they are cheaper, but because at that moment the customer has not yet kept looking.

What actually takes the time

Break quoting down and the split usually looks like this:

• Understanding the enquiry and asking back — what exactly, how much, when
• Measuring and technical assessment — the actual professional work
• Assembling line items — from the price book, templates, old quotes
• Writing, formatting, sending — cover note, layout, PDF, email
• Following up — the step that gets dropped most often

Only the second point is the service the customer is paying for. The rest is administration — and that is exactly where the automatable share sits.

What is worth automating

Structuring the enquiry. An enquiry arrives as a phone call, a WhatsApp message, a form or three sentences in an email. A model can reliably turn that into a consistent data sheet: trade, property type, rough scope, location, preferred date, contact details. Not a finished quote — an orderly basis.

Preparing the follow-up questions. Where details are missing, a short clarification email can be drafted automatically and only needs confirming. It rarely saves much time per case, but it happens immediately instead of in three days.

Pre-filling the quote draft. From the structured data sheet, standard line items and text blocks can be proposed. The tradesperson reviews, corrects quantities and adds what only they know — instead of starting from zero.

Scheduling the follow-up. A quote without a reminder is a quote you gave away. It is the cheapest automation step there is and usually the one with the clearest effect.

What deliberately stays with a human

The pricing decision. Technical feasibility. The judgement of whether this customer and this job are a fit.

A model that derives a binding price from an enquiry will sooner or later produce a quote that costs the business money. The sensible cut is therefore: automate up to the draft, human approval before it goes out. That is not a compromise; it is the point where the ratio of benefit to risk is best.

Frequently asked questions

Is it worth it at ten enquiries a month?

Probably not as a built workflow. At ten enquiries the better investment is a good quote template and a fixed follow-up reminder. It becomes interesting at roughly the frequency where quoting regularly slips into the evening.

What about our trade-specific software?

Many industry systems have an interface, some do not. Where none exists, the honest route is often an intermediate step (a structured data sheet somebody imports once) rather than a forced integration. That sounds unsatisfying, but it needs far less maintenance than a makeshift import that breaks with every update.

And data protection?

Customer data from enquiries is personal data. Before it passes through an external service, the processing agreement and the data flow need settling — before the build, not after. That takes time and therefore belongs in the effort estimate.

How do I start without changing everything?

With one trade or one enquiry type. The most frequent, most boring, most clearly defined one. Not the edge case where everything converges.

What you can do today

1. Count for one week how many enquiries come in and through which channel.
2. On three quotes, roughly track how much time goes to administration and how much to the professional work.
3. Run the capacity value through the AI automation ROI calculator — with an honest automation rate; see the business case.
4. Introduce the quote follow-up reminder first. It costs almost nothing and works immediately.
5. Only then the enquiry structuring — and only for one enquiry type.

If a workflow comes out of that which you would rather not build yourself: how we set these up is described under AI & automation — or talk it through in a first call.