CertaVent
← Back to Blog

Why We Didn't Build 'Yet Another' Field Service App

CertaVent Team

Most software used by UK duct cleaning businesses was built for every trade at once — plumbers, electricians, landscapers, and duct cleaners, squeezed into the same generic template. Here's why we built something narrower on purpose.

There's no shortage of software that will happily manage a duct cleaning business. Type "duct cleaning software" into Google and you'll find scheduling tools, invoicing platforms, and all-in-one field service suites, most of which list duct cleaning somewhere in a long dropdown of trades — usually between carpet cleaning and drain clearance.

That's not a criticism of those tools. Many of them are genuinely well built. It's an observation about what they were built for, which is everyone, which in practice tends to mean no one in particular.

The dropdown problem

Software built for every trade at once has to speak the lowest common denominator of all of them. A job. A customer. An invoice. A calendar slot. That covers a plumber replacing a tap and a duct cleaner producing a TR19-compliant post-clean report equally badly, because it wasn't built with either in mind specifically — it was built to be flexible enough to avoid offending anyone's workflow.

The trouble is, duct cleaning isn't a generic trade with a generic paperwork trail. It has a named standard, in two flavours. It has a register that expects specific evidence in a specific structure. It has deposit thickness readings that mean something only in relation to a "before" reading from the same access point. None of that fits neatly into a field marked "job notes."

So what actually happens is that duct cleaning businesses buy the generic tool for scheduling and invoicing, then build a second, informal system alongside it: a folder of photos, a spreadsheet, a Word template someone put together a few years back, to handle the part of the job that's actually specific to duct cleaning. The software manages the business. It just doesn't manage the thing that makes the business compliant.

What that looks like day to day

The difference shows up fast in practice. A generic platform can tell you a job is booked for 2pm and send an invoice once it's marked complete. It has no opinion on whether the photos taken during that job would satisfy an EHO, whether the readings were logged against the right access point, or whether the outcome should be labelled a full clean or a partial clean under the current standard. Those decisions still sit entirely with the technician's memory and whatever spreadsheet the office maintains on the side.

A tool built around TR19 from the ground up can prompt for exactly that information, in exactly that structure, because it was designed knowing the structure in advance, not guessing at it from a support ticket six months after launch.

Narrow, on purpose

We built Certa Vent the other way round. It starts from TR19, both Grease and Air, and from what a genuinely defensible report looks like under the current standard, including the new Section 9 structure BESA introduced in 2026. Everything else — the scheduling, the client records, the certificate history — is built to support that core, not the other way round.

That's a smaller starting scope than a platform trying to serve every trade in the country. It's also, we think, a more honest one. A tool that tries to be everything to everyone tends to be excellent at nothing in particular. A tool built around one standard, for one industry, can afford to get the detail right, because the detail is the whole point.

"Sic Parvis Magna"

It's the motto we chose for a reason: greatness from small beginnings. Not because we're promising to build the next all-purpose giant that swallows every trade under one roof — plenty of well-funded companies are already trying that — but because we think there's more lasting value in getting one thing right first. A duct cleaning company that can produce an audit-ready TR19 report in minutes, on site, without a second system running quietly in the background, doesn't need us to also handle their payroll. It needs the compliance side to be genuinely, quietly excellent.

Built with the industry, not just for it

The other difference worth naming: this isn't software imagined by people who've never stood inside a plant room. It's shaped around how the work actually happens — what a technician can realistically manage standing on a ladder with gloves on, what an office actually needs to hand over when an insurer calls with no warning, what a compliance officer is actually going to check first.

Compliance reporting is the starting point here, not the ceiling. We see this growing into more of the everyday infrastructure a duct cleaning business runs on. But whatever gets added next will be built the same way the first part was: specific to this industry, not adapted from a template that was never really about ventilation hygiene to begin with.

We'd rather be the tool duct cleaning businesses reach for specifically, than one more line in a dropdown menu that happens to include their trade. If that means staying smaller and more focused for longer, that's a trade-off we're entirely comfortable with.