One platform, two industries

A property developer in Liverpool and an industrial lifting-and-inspection group operating across the UK and Ireland do not look like the same business. One chases service-charge arrears, books gas safety checks, and triages repairs. The other hunts tenders, runs a strict ISO and EN test regime, and invoices across jurisdictions. Different customers, different regulators, different software, different vocabulary.

Yet both run on the same Usermode fleet — the same named AI employees, the same scheduler, the same governance layer, the same channels. We did not rebuild the platform to move from Legacie (property development and block management) to WH Scott Group (industrial test, inspection and certification, under the WH Scott, Re-Ropes and Metlab brands). We swapped the integrations and the rules each role works against, and left the operating model alone. This piece is about why that works, and where the line sits that we will not cross.

The Thing That Actually Transfers

The mistake most automation makes is to encode the operations — this exact workflow, this exact form, this exact handoff. Encode operations and every new company is a new build, because no two companies do arrears or inspections the same way.

What we encode instead is an operating model, and that part is genuinely industry-agnostic:

• •Named roles. A Credit Controller is a Credit Controller whether the debt is a service charge or a calibration invoice. A Bid Writer writes bids whether the buyer is a housing association or a steel plant. The job's shape survives the change of subject.
• •Schedules. Agents run on standing daily and weekly crons and act when something needs doing — they do not sit waiting to be prompted. "Every morning, pull what's overdue and chase it" is the same instruction in both companies.
• •Governance. Fail-closed tool-policy, signed authorisation on every external send, human approval gates on spend, an append-only audit ledger. None of that cares what industry you're in.
• •Channels. Email, WhatsApp, Teams, SMS. The pipe is the same; only the message content is local.

The operations differ. The operating model repeats. That is the entire portability story.

Everything below the operating model — the systems of record, the regulatory rules, the data each role reads — is configuration. That is the part we swap.

Property At Legacie

At Legacie, the fleet runs block management and development operations end-to-end.

The roles in context

Sarah, the Credit Controller, works service-charge arrears: she reads the ledger each morning, identifies what's overdue, and chases it through email and WhatsApp rather than leaving it to drift. Henry, the Property and Compliance Manager, tracks safety certificates — gas, electrical, EPC — against their due dates and books the work before things lapse, then triages repairs as they come in. Ruby handles the executive-assistant load; Aaron keeps the management accounts; Scarlett runs marketing.

The integrations underneath

Property is its own software estate, and the agents read and write through it directly:

• •MRI and Blocks Online for property, leaseholder and finance data.
• •Fixflo for repairs and maintenance triage.
• •Companies House for entity and director checks.
• •Microsoft 365, Outlook, Graph and SharePoint for correspondence and documents.

When Henry decides a gas certificate is about to expire, the due date came from the property system, the contractor sits in Outlook, and the booking is a real, logged outbound action — not a note saying someone should do it.

Industrial Inspection At WH Scott Group

Now move the same fleet to WH Scott Group. The roster looks familiar; the work does not.

Different jobs for the same archetypes

Jacob and Chloe, the Bid Writers, hunt tenders — finding live opportunities, assembling branded, priced, compliant bid packs, and getting them out the door. Georgia, the Business Analyst, builds reporting across the group's operational systems. Sharon runs group credit control, which here means chasing invoices that may sit in different jurisdictions with different terms. Brian carries HSQE. Hugo handles contract and document control against a test regime where the paperwork is the product.

A different software estate, and a stricter rulebook

Industrial TIC runs on its own systems, so the integrations change wholesale:

• •Microsoft Business Central for finance and ERP.
• •CoreRFID for asset, equipment and inspection records.
• •Procore and Glenigan around project and opportunity data.
• •Microsoft 365 again for correspondence — one of the few constants.

The harder difference is regulatory. Inspection and certification live under a strict ISO and EN standards regime, where a result is only worth anything if the method, the calibration and the traceability behind it hold up. Jurisdiction-aware credit control means Sharon cannot treat an Irish invoice exactly like a UK one. Hugo's document control has to respect which standard governs which job. None of that is a new platform — it is the same roles configured against tighter rules and different data.

What Gets Swapped Versus What Stays

It is worth being precise about the line, because "configurable" is an easy word to over-claim.

What we swap per company:

• •The systems of record each role connects to (MRI/Blocks/Fixflo versus Business Central/CoreRFID/Procore).
• •The domain rules a role enforces (safety-cert cadences versus ISO/EN traceability; single-jurisdiction versus multi-jurisdiction credit terms).
• •The durable memory each agent builds about that business — its properties or its plant, its people, its history over months.
• •The specific schedules that make sense for the work.

What stays identical across both:

• •The named-role model and the delivery contract — a run cannot end without a real, logged outbound action; agents escalate rather than go quiet.
• •The governance spine: fail-closed policy so a read-only role is technically prevented from mutating systems, HMAC-SHA256-signed and recipient-bound authorisation on every external send, approval gates on spend, and a tamper-evident audit ledger.
• •The security posture: per-tenant Azure isolation with each company in its own subscription, Key Vault and container environment; an OAuth 2.1 gateway on Entra ID; redacted logs that hold no PII or memory; prompt-injection sandboxing of untrusted inbound mail.
• •The channels and the automated end-to-end guardrail tests that gate every change, alongside gitleaks and CodeQL in CI.

That split is the whole design. Industry-specific logic lives in configuration and memory; the trustworthy parts live in the platform and never get re-implemented per customer.

The Firewall Between Them

Running two companies on one platform only works if they cannot see each other. The per-tenant Azure isolation is not a convenience — it is the firewall. Legacie's fleet and WH Scott Group's fleet live in separate subscriptions, separate Key Vaults, separate container environments. There is no shared data plane where one tenant's leaseholder records could brush against another's inspection certificates.

This matters operationally as much as legally. Sarah's memory of a Legacie arrears case is hers and Legacie's; it does not leak into Sharon's view of a WH Scott debtor. The governance ledger is per-tenant. The signing keys are per-tenant. When we say the operating model repeats, we mean the shape repeats — never the data.

On certifications, we stay honest: the platform inherits the certified infrastructure of Azure underneath it, but formal attestations such as SOC 2 are on the roadmap rather than in hand. We would rather tell you that than imply otherwise.

Why This Is The Cheaper Path

The economic argument is simple. If onboarding a new company meant rebuilding the fleet, every customer would carry the full cost of the platform again — and every customer would re-introduce the risk of getting governance wrong. By holding the operating model and the governance spine fixed, the marginal work of a new tenant collapses to integration and rule configuration: connect the systems of record, encode the domain rules, let the agents build their memory.

Property to industrial inspection is about as far apart as two mid-market operations get, and the carry held. That is the test we cared about. The next industry is not a rewrite — it is a new set of integrations behind roles that already know how to do the job.

If you'd like to see the same fleet pointed at your own systems, you can book a demo at /demo.