The work we'd rather show than describe.

Three things live here. Work we've delivered for clients that we can talk you through even when we can't publish it. Work we've done for ourselves internally — the pattern we take to client engagements. And the platforms we can stand up for you. Start wherever fits the conversation.

Talk to us about a project See our platforms

01/ Client work

Work we've delivered for customers.

Most of what we ship for clients isn't publishable yet — not because it's a secret, but because clients like to decide when and how their story gets told. The ones we can publish, we do properly.

/ Case study / Client

Hobbs Recovery Services

Two sites, one portal — booking that runs itself.

Problem: A COVID-era web form with no real admin, high phone volume, double-bookings and document chaos across two independently-run sites.
Approach: A mobile-first PWA for customers with document upload at point of booking, and a full admin workflow for staff — single sign-on, role-based access, self-hosted on the customer's own server.
Outcome: 24/7 self-service bookings, staff out of the inbox, no double-bookings, and one operational picture across Polegate and Copthorne.

PWASSODocument uploadSelf-hosted

Read the HRS case study

/ Under NDA

More case studies we can walk you through in a conversation.

AI assistants, operational portals, integrations and workflow automation — delivered to clients we can’t name yet. We can talk you through what we’ve shipped, the problems it solved and the shape of the outcome.

Ask us about similar work

02/ Internal / Customer Zero

Work we've done for ourselves.

The fastest way to know whether we understand a problem is to ask whether we've solved it on ourselves first. This is the category we're most comfortable publishing, because it's our own.

/ Case study / Internal

M-Tech Systems · Customer Zero

M/uster — the operational platform we built to run our own business.

Problem: Eight separate registers — people, assets, software, compliance, fleet, physical access, contracts, lifecycle — scattered across spreadsheets and point tools, with leavers taking weeks to close cleanly.
Approach: One shared spine with a proper joiner/mover/leaver lifecycle, every register hanging off the same people record. Built for us, shipped to clients on the same platform.
Outcome: Running inside M-Tech Systems every day. Leavers close in a single pass, compliance is visible in one picture, nothing keeps billing after somebody's gone.

Operational softwareIdentityLifecycleCustomer Zero

Read the M/uster case study

03/ Platforms

Platforms we can stand up for you.

These aren't one-off projects — they're the shapes we've seen enough times to turn into platforms, ready to stand up for a client on the same spine we run ourselves.

/ Platform

M/uster — operational platform

The platform we run on ourselves. Ready to stand up for a client on the same spine, shaped to their registers and lifecycle rules.

M/uster

/ Platform

M/esh — PropTech platform

M/esh is the PropTech platform — network, access, CCTV, telephony, AV, audio, sensing, BMS, guest hotspot and workspace management pulled into one data layer. Framework in place; each space composed and deployed on top.

M/esh

/ Platform

M/agnet — guest hotspot software

M/agnet is the public Wi-Fi layer behind hospitality and public-venue networks — branded captive portals, low-friction sign-up, auditable consent, returning-guest recognition and Mailchimp sync. UniFi-first, multi-tenant, built to extend.

M/agnet

/ Start a conversation

Let's talk about what you're trying to build.

Book a discovery session and we'll walk through the workflow, the systems and the shape of the solution.

Book a discovery session Talk through a challenge