Quote automation for heat pump installers: from survey to signed quote

Yes, most of it. Quote automation for heat pumps can take an enquiry from a website form to a priced, signed quote with very little typing: the property details are captured once, public registers fill in what they can, grant eligibility is checked against current rules, the kit and labour are priced from a list, and the quote, the grant breakdown and the performance estimate are generated from the same record. What cannot be automated away is the design. A heat loss calculation, emitter sizing, the choice of unit and the position of the outdoor unit need a qualified designer's sign-off, and the system's real job is to refuse to issue a quote until that sign-off exists, the noise assessment has passed for that exact design, and the grant check is current.

That reframes the project. The arithmetic of a heat pump quote is not hard. The expensive mistakes are a quote sent before a gate was passed, a grant figure from last quarter, or a price list nobody updated, and each of those is a regulatory or commercial problem rather than a typo. Automating the speed without the gates makes those mistakes faster.

A heat pump quote is the end of a chain of inputs, and several of them are set by a standard or a scheme rather than by the installer. The table lists them with the source of each rule and whether it can be automated.

The grant, as it stands in October 2026

Under the Boiler Upgrade Scheme the installer, not the homeowner, applies to Ofgem, and the grant reaches the customer as a discount on the quote. Ofgem's current guidance gives £7,500 for air-to-water and ground source heat pumps, £2,500 for air-to-air heat pumps, and an uplifted £9,000 for air-to-water or ground source heat pumps in eligible off-gas-grid properties heated by oil or LPG, for applications made on or after 21 July 2026 and available until 31 March 2027. The installer must be MCS certified, and the property generally needs a valid EPC, though the current guidance describes other evidence it accepts where there is none.

Three details matter to a quote engine. The quote must be itemised: the total before the grant, the grant value and what the customer pays after it. After the installer applies, Ofgem emails the property owner, who has 14 days to give consent or the application may be rejected. And the voucher has a validity period: the installer must install, commission and redeem it within three months for air-to-water and air-to-air heat pumps, or six months for ground source. Each of those is a field, a status or a deadline the system has to hold.

The noise assessment, and why the method matters

For an air source heat pump installed under permitted development, the outdoor unit's noise is assessed with the MCS sound calculation. MCS split the method in 2025, and MCS 020 a) now covers air source heat pumps. The older MCS 020 expressed its limit as 42 dB(A) including a nominal 40 dB(A) background level; MCS 020 a) states 37 dB(A) at the assessment position. Check the current issue rather than this summary. MCS 020 a) also says that passing the calculation does not on its own confer permitted development rights, so other planning conditions still apply.

The performance estimate and the cooling-off period

MCS 031 a) requires a performance estimate for hydronic heat pumps, an estimate of the system's annual energy use, given to the customer in writing before the contract is awarded. MCS is explicit that it is not a design tool: the design sits in MIS 3005-D. Where no room-by-room heat loss calculation has been done, the estimate uses a default flow temperature of 60°C for existing radiators, and a higher flow temperature generally means a less efficient system, so running the design before the estimate can change what the customer reads.

For a contract made off the installer's premises or at a distance, which includes a quote signed online with no site visit, the Consumer Contracts Regulations 2013 give the customer a cancellation period of 14 days. For a service contract it ends 14 days after the day the contract is entered into. Work may start inside the period only if the customer expressly asks, and for an off-premises contract the request must be made on a durable medium. How the period runs for a contract that also supplies goods is a question for your legal adviser, and it is one more reason to hold the rule in one place.

Draw the line at judgement that carries a signature. Anything that collects, looks up, calculates from approved inputs or formats a document can be automated. Anything a qualified person would put their name to stays a sign-off, and the automation's job there is to prepare the work and then wait.

• Automate: enquiry capture and qualification, address lookup, property register and EPC lookups, smart-meter data where the customer consents, the grant eligibility check, the price from the kit list and labour rates, the itemised quote with the grant shown, the performance estimate from the approved design, e-signature, the cooling-off clock, the reminder when Ofgem's consent email has gone unanswered, and the voucher expiry warning.
• Prepare, then wait for a person: the heat loss calculation, emitter changes, unit selection and the outdoor unit's position. Software can run the numbers and propose; the designer reviews the inputs and approves.
• Never automate: the designer's approval itself, an override of a failed gate, and any decision to start work inside the cooling-off period. Each of those needs a named person and a recorded reason.

Our first-hand evidence is one engagement: a regulated sales platform for a UK heat-pump installer, aimed at taking a homeowner from a website enquiry to a fixed-price quote with no site visit. It is in build. Enquiry to indicative price is built and working, and remote survey and design is well advanced. The quote and signature stage, and scheduling, installation and commissioning, are not yet started, and nothing is in front of customers. Prices, grant figures and copy are placeholders by design. So what follows is how the gates are built and tested, not a result.

• Stage changes go through one function. It checks a frozen map of allowed transitions, runs the guards for the target stage and writes the change and an audit event in one transaction, with an optimistic check so two callers cannot both advance the same job.
• The noise assessment must be a pass for the design currently approved. A later fail overrides an earlier pass, and a pass on a rejected or superseded design does not count.
• Approving a design hashes its identity, version, key figures, approver, timestamp and the stored design-pack file, and the approval is recomputed against that hash when it is read. A database trigger refuses edits to an approved design and allows it to move to superseded only once a successor exists.
• The cooling-off period is computed on the UK calendar day of signing, so a signature at 23:30 in summer counts as that day, and the earliest install is midnight UK time after the fourteenth day. The design does not start work inside the period at all.
• Grant rules, price bands, the kit list, VAT, savings assumptions and customer copy live in forty-two settings keys, each validated on read. A missing or malformed setting stops the quote rather than producing a plausible wrong number.
• Where a fact is unknown at enquiry, the assumption is made in the customer's favour and shown on screen. Cost price never reaches the browser: margin is applied on the server, an allow-list defines the public fields, and a test plants sentinel values and fails if one appears.
• Phone scans of rooms are interpreted on the server, and confidence is capped below the threshold for standard routing, so a designer reads every scanned survey until scans have been checked against a tape measure. Those scanning flows ship switched off until they have run on real devices.

Each gate has a test for the path where it blocks, and the platform has over a thousand automated tests across the web and mobile apps. That proves the gates hold in code. It does not prove the business case, the remote survey's accuracy or customer uptake, and we claim none of those.

A second engagement shows the quote engine side in a related trade. On a UK commercial solar installer's operating system, which is live with the client's team, the original quote tool had the same arithmetic written out six times and the copies had drifted. They were reconciled into one module of pure functions with tests, the cost build is stripped on the server before a quote leaves it, and the pipeline refuses to advance a deal until the data the next stage needs exists, with an override that needs its own permission and a recorded reason.

One rule organises everything else: an issued quote is a snapshot that points at the versions it was built from, and it is never recalculated. If the price list, the grant rules or the design change, you issue a new quote or a contract variation. You do not edit the old one, because the customer signed what they read.

On the heat-pump platform the audit table refuses update, delete and truncate for every role, including its owner. A plain revoke does not bind a table's owner in Postgres, so the protection is statement-level triggers, with a test that tries to rewrite the log and fails. A log that the application promises not to edit is not the same thing as one that cannot be edited.

Third-party calls belong behind one wrapper. On the same platform every call out, from property registers and address lookup to SMS, email and smart-meter consent, goes through a wrapper that gives it an idempotency key, retries with backoff and, when it finally fails, raises a task for the office instead of throwing. A lookup that is down should leave a visible gap and a task, not a default that looks like data.

For most installers, start with software built for the trade. If you survey every job in person, a designer works in an established heat loss tool, and your volume is a few quotes a week, an installer CRM with quoting templates will do the job, and building your own would be paying for a system to do what a product already does. MCS also publishes its own heat load calculator, so the design calculation does not have to be yours to write.

Test any product, and your current process, against three questions. Will it refuse to issue a quote when the design is unapproved or the noise assessment failed, or does it only show a checklist someone can skip? Does an issued quote keep the price list and grant figures it was built from when those change? And can you change the grant amount yourself on the day Ofgem changes it, without waiting for a release? A product that passes all three is probably enough.

Where a build breaks: you own every rule change from then on. When Ofgem uplifts a grant or MCS issues a new method, nobody ships you an update, and a custom system whose owner has moved on is worse than a product that is a release behind. Software also does not make you compliant. MCS certification, the competence of your designer and your contracts are yours whatever you run. A build is the right answer when your process is genuinely different from the trade's default, and the wrong one when you are only paying to replace a tool that fits. Our build-versus-buy article sets out the general arithmetic.

The failures that matter are the quiet ones: the quote goes out, looks right, and is wrong in a way nobody notices until a customer, Ofgem or MCS does.

Two of those rows are recent rule changes, not hypotheticals. The off-gas uplift applies to applications from 21 July 2026, and MCS changed the air source noise method in 2025. A quote engine written in 2024 with either rule in its code would have produced confident, wrong quotes this year. Our article on why automations break covers the general pattern; in a regulated sale the cost of that pattern is higher.

1. 01Write down your gates: what must be true before a quote is issued, before a contract is signed and before anyone goes on site. Name who signs each one.
2. 02Move every rule that changes, grant amounts, prices, VAT treatment, copy, out of documents and code and into one dated table someone owns.
3. 03Make the issued quote a snapshot that records the design, price list and grant rule versions behind it.
4. 04Automate the clocks next: cooling-off, Ofgem consent and voucher expiry. They are cheap to build and expensive to miss.
5. 05Then automate capture and lookups, so the designer receives a complete survey rather than chasing gaps.
6. 06Only then decide whether the product you have can enforce the gates. If it can, configure it. If it cannot, build the piece that does, not the whole system.

If you would like a second opinion on where your quotes leak time or risk, we are happy to look at the process as it runs today. Our ops platforms service describes how we work.