Back to Blog
MEP

Why we built WYRM MEP

James Reed|June 9, 2026|8 min read

Key Takeaways

  • -The drain in a building-services practice is in the deliverables, not the design — drafting specs, rebuilding schedules, chasing coordination, answering RFIs. It repeats on every project and it is the first thing a deadline squeezes.
  • -WYRM MEP is an agentic layer above the stack you already run — Autodesk, Amtech, IES, Aconex, Office. It reads your files, coordinates like a design team, and writes back in your formats. A layer, not another island.
  • -On the production tasks it handles, the workflow runs up to ~90% faster — and the recovered time is fee-earning capacity you cannot simply hire, with 92% of firms reporting skills shortages.
  • -Two independent Principal-QA gates check every output. Nothing reaches your engineer unchecked and nothing is applied without a human decision — your engineer reviews, signs, and stays responsible.

Anyone who has run a building-services practice knows the shape of the problem, even if they have never named it. You hired qualified MEP engineers to design buildings. They spend a large part of every week not designing — drafting specifications from templates, rebuilding equipment and cable schedules by hand, chasing which change affected which discipline, checking compliance under deadline pressure, and answering repetitive RFIs. The work is necessary. It repeats on every project. And it is the first thing that gets squeezed when a programme slips. That is the problem WYRM MEP was built to solve.

The instinct, when the workload grows, is to add headcount. That instinct is getting harder to act on. Building-services pay is rising, associate salaries faster still. Employer National Insurance and pension stack roughly a third on top of the headline salary, so the true cost of a head is well above what the offer letter says. And the head often cannot be hired at all: 92% of building-services firms report skills shortages, with electrical engineers acutely scarce. When labour both costs more and cannot be found, productivity is the only lever left that scales.

WYRM MEP is that lever, and the design decision that matters most is what it is not. It is not a replacement for the tools you already own and have trained your teams on. The usual approach in this market is a bespoke build or a single-problem tool — each one another dataset to migrate, another interface to learn, another silo that does not talk to the others. WYRM MEP sits above the stack you already run: Autodesk, Amtech, IES, Aconex, Office. It reads your files, coordinates across disciplines the way a design team does, and writes back in your formats. A layer, not another island.

Underneath the surface it is a team of specialist agents, not a chatbot bolted onto a toolbar. Leads, discipline engineers, drafters, checkers, and external specialists plan the work, divide it between them, hand off across disciplines, and review one another the way a real studio operates. You can follow who did what and why. The point of the agentic structure is auditability: the output is a coordinated team you can inspect, not a single opaque model handing back one answer you have to take on trust.

Holding the job together is the Project Terminal. Change an air-conditioning unit and it instantly flags the affected electrical loads and drawings, proposes the fix, and tracks sign-off — batched into a daily digest rather than a stream of pings. The expensive failures in MEP are rarely the first design; they are the change that ripples through six documents and gets missed in one. Modelling the job as a connected whole is what stops that.

Across all of it sit two independent Principal-QA gates. Nothing reaches your engineer unchecked, and nothing is applied without a human decision. WYRM does the legwork and shows its working; your engineer reviews, signs, and stays responsible for the deliverable. That division is deliberate and it is the line that makes the tool usable on real projects: the speed comes from the agents, the accountability stays with the human.

The commercial case follows from the staffing one. For roughly half the loaded cost of one senior engineer, every engineer on the team gets a document- and drawing-production workflow that runs up to ~90% faster on the work WYRM handles. The savings model we share with practices is deliberately conservative — it counts only the production share of each engineer's week, not the whole week — and even on that basis the recovered capacity dominates the subscription cost. The recovered time is valued at your charge-out rate, because it is fee-earning capacity handed back to a team you cannot grow fast enough by hiring.

WYRM MEP is one of two flagship engineering products at WYRM, sold alongside WYRM Data and bundled as WYRM Engineering at £250 per seat. It is in active pilot now, and the pilot cohort is enlisting. If your practice feels the deliverables tax every time a deadline tightens, that is exactly the problem this was built for — and the fastest way to see it is on your own numbers.