What Is GUVNR AI, and Who Is It Being Built For?

GUVNR is job-management software for UK trades, construction and facilities-management businesses, built around one idea: most job-management software stores your admin — GUVNR is being built to help do it.

That sentence is doing a lot of work, so this article unpacks it honestly. What GUVNR is. Who it is for. What actually runs in production today versus what is still being built. And why a working BMS and controls contractor decided the only sensible way to build it was to run their own business on it first.

One thing to say plainly at the top: GUVNR is not generally available. You cannot sign up today. The public site is a waitlist, and the only company running on GUVNR right now is the contractor that builds it. Everything below is written to that standard — where something is live, we say so and we say where; where it is not, we say that too.

What GUVNR actually is

Strip away the category names and a contracting business runs on a small number of loops. You price work. You win it. You schedule people to it. Those people do things on site and tell you about it. You buy materials against it. You bill for it. You wait to get paid for it. Somewhere in there you find out whether it made money.

Conventional job-management software gives you a place to record each of those steps. That is genuinely useful — it is a lot better than a filing cabinet and a shared drive. But it leaves the actual work with you. The system knows a timesheet is missing; you are the one who texts the bloke. The system knows an invoice is 40 days old; you are the one who writes the awkward email. The system knows a certificate expires on Friday; you find out on Monday when someone is turned away at the gate.

GUVNR's premise is that the second half of each of those sentences is software's job, not yours. Not "here is a dashboard showing you what is wrong" — a dashboard is just a more attractive way of telling you to do more admin. Actually drafting the chase, actually flagging the expiry to the right person, actually turning a set of site notes into something the office can read.

That is the direction. We are honest that it is a direction and not a finished product: today GUVNR does a lot of the recording and some of the doing, and the automation layer that closes the gap is still being built. More on exactly where that line sits below.

Who it is being built for

GUVNR is built for UK building-services and construction businesses where the person running the jobs is often also on the tools. Concretely, that means:

• Mechanical and electrical (M&E) subcontractors delivering a package under a main contractor, applying for payment monthly rather than invoicing on completion.
• BMS and controls specialists — installing, commissioning and maintaining building controls, usually inside a larger M&E or main contract. This is the trade GUVNR was born in.
• Electrical and mechanical contractors on commercial and construction work, dealing with CIS deductions, retention and the domestic reverse charge.
• Facilities-management firms running planned and reactive work across a portfolio of sites, with mobile teams and a lot of compliance paperwork.

Who it is not for, at least not first: a one-van domestic operation doing cash-in-hand jobs with no contract chain behind them. That business has genuinely good options already, and it does not need retention tracking or a payment-application workflow. We would rather say that than pretend to be for everyone.

The dividing line is simple. If you get paid by valuation rather than by invoice, GUVNR is built for you. If you send an invoice and expect the money, you are better served elsewhere.

Why the subcontractor money workflow is the centre of it

This is where GUVNR differs most sharply from the general trades-app category, and it is worth being specific, because it is the bit that gets waved away.

On a UK construction project a subcontractor typically does not simply invoice. You submit an application for payment against a valuation of work done to date. Some percentage of the value is withheld as retention, half released at practical completion and half after the defects period. If you are in the Construction Industry Scheme, tax is deducted from the labour element before you see it. And on most construction-to-construction work you invoice under the domestic reverse charge, so you do not add VAT at all — the customer accounts for it.

Four mechanisms, all of them normal, none of them optional, and each one a place where a generic invoicing tool gives you the wrong number. A tool built for domestic jobs will happily let you send a VAT invoice on reverse-charge work, or forget that this month's application has to reconcile against last month's. That is not a bug in those products — they were built for a different business. It is just a reason they do not fit this one.

We have written separately about what it costs to run this on email, WhatsApp and spreadsheets, which is what most firms this size are actually doing.

What runs today, and what we are still building

Here is the honest state of play as of August 2026. "Running in production" below means it is in real production use inside Alpha Controls LDN, the contracting business that builds GUVNR — live jobs, real invoices, real payroll periods — not that you can use it.

Running in production today

• Projects and jobs, with work packages beneath a project
• Scheduling and shifts, with operatives assigned through to a mobile portal
• Shift reports completed from a phone on site
• Quoting
• Invoicing with CIS deduction, and the VAT treatment you set carried onto the invoice you raise and every document it produces
• Purchase-order capture against jobs
• Timesheets
• AI call handling, so calls do not go to voicemail while everyone is on site

Currently being tested

• The tender workspace — taking in an ITT and pricing it in a structured place rather than a loose spreadsheet
• Applications for payment and valuations, including retention. Built, not yet a settled production workflow
• RAMS and method statements

Under active development

• Ask The GUVNR — a single place to ask questions of everything your business knows, rather than hunting through screens
• The automation engine that does the chasing, and the outbound delivery that sits on top of it
• Tender document extraction and classification
• Multi-tenant isolation, so a second company can be onboarded safely

Planned

• Self-serve signup and general availability
• Published pricing
• Project-profitability reporting as a product surface

If a feature is not on that list, assume it does not exist. We will keep this page updated as things move, and the classification only changes when the evidence does — a feature moves to "running in production" when there is real work going through it, not when the code merges.

Where the AI actually is — and where it is not

"AI-first" is a phrase that has been worn smooth, so here is what it means and does not mean here.

What it does today: AI answers the phone when nobody can, and captures what the caller wanted. That one is genuinely live — it has been handling calls in our business since February.

What we are testing: turning a set of rough site notes into a shift summary the office can read without ringing the engineer back. The generator works, but it has not yet earned a place in the weekly routine, so we are calling it what it is — in testing, not in production.

What it is being built to do: notice that a timesheet has not come in and chase the right person; notice that an application for payment is due and start it from the work already recorded; notice a certificate is about to expire and deal with it before someone is turned away at a gate.

What it will not do: price your job for you and expect you to trust it, or send anything commercial on your behalf without you seeing it first. Anything that leaves the business and touches money or a customer stays behind a human. That is a deliberate design position, not a limitation we are hoping to remove later — a contractor's reputation is not a good place to test an autonomous agent.

Who builds it

GUVNR is built by Alpha Controls LDN Ltd, a BMS and controls contractor working across Kent and London. Alpha Controls is tenant number one: the payment applications, the CIS handling, the reverse-charge invoicing and the shift reports all exist because someone had to do them for a real job, on a real deadline, for real money.

That is the whole reason the product looks the way it does, and we have written about the trade-offs of building it that way in why we are building GUVNR inside a real UK contractor.

How to get involved

We are selecting our Founding 10: ten hand-selected UK companies who will help shape and test GUVNR against their own real workflows. After that comes Early Access 30 — the next controlled cohort of thirty companies. Wider release comes after those stages, not before.

Joining the waitlist is how you follow what we are building and how you apply for one of the thirty Early Access 30 places. It is not a promise of a place — the cohorts are deliberately small, and we would rather onboard ten companies properly than three hundred badly.