mmitech

Case studies

Every claim on this site points back to one of these - a live URL or a public repo. Nothing on the site is a hypothetical or a stock-photo proxy for work we'd like to do; if a page describes a build, there's a clickable case study below the description and a working product on the other end of it. That's the whole proof discipline of the studio: we'll talk about what we'd build for you in terms of what we've already built for someone else, and link the someone else.

Two tiers. Own-brand are the studio's own software - the operating businesses the founder runs day-to-day, the legacy system the studio is modernising on its own sister brand, and the three productised builds that started inside those businesses before they shipped for anyone else. These ship full-fat from day one because we're the customer, and we're allowed to talk about ourselves. Named-client are real builds shipped for real UK businesses - the live URL, the build shape, and the outcome shape publishable now in studio voice (direction not numbers), with specific £/% / time-saved figures attributed to the named client deliberately omitted until each detail clears permission.

The named-client pages describe what the build was designed to do rather than fabricated achievement figures - the reader understands the difference, and the legal exposure is bounded. When a piece of outcome detail clears permission, it lands on the same page in the same place; there's no big-reveal moment for the visitor, just more detail filling in where the studio-voice description sits now.

If one of the shapes below is close to your business and you'd like the same hands on yours, tell us about it - we'll come back with a sketch of what we'd build for you and the closest live case study to pattern-match against.

Own-brand - full-fat from day one

Software the studio built and runs on its own businesses. No permission gate, no held figures - these pages ship complete from day one.

The founder's UK device-repair business - one site that takes repair enquiries, sells refurbished phones, and tracks every order against the same live data the in-shop counter sees.

Visit the live build ↗

A multi-tenant workshop platform - takes a thing in, books it onto a bench, communicates through the process, hands it back. Built for our own shop first, with an iOS companion for the bench.

Visit the live build ↗

Our own multi-channel AI receptionist - voice, web chat, WhatsApp, SMS, Messenger, Instagram DM - trained on your business, productised for any UK SME with substantial inbound.

Visit the live build ↗

A platform that generates sector-appropriate social content, schedules it across every major platform, and publishes - with AI imagery that looks like your business, not a stock-photo proxy.

Visit the live build ↗

A consumer-shaped product end-to-end - native iOS, native Android, marketing site, serverless backend. The reference build for *"we ship the whole mobile-app-plus-server stack"*.

Visit the live build ↗

A two-surface build for an analytics consultancy - a marketing site that sells the service, and a private per-client dashboard that *delivers* it. The answer the buyer wants is the dashboard.

Visit the live build ↗

A 2008-era line-of-business claims system, sat behind a modern marketing surface, modernised in place rather than rewritten - the reference for *"we can take over what you've got"*.

Visit the live build ↗

Named-client

Real builds shipped for real UK clients. The live URL, the build shape, and the outcome shape ship now in studio voice - direction not numbers - with specific £/% deliberately omitted until named-client permission lands on each detail.

The live trades-electrician build - public site, cert-and-quote engine, EICR recall annuity, letting-agent batch billing, EV-installer grant tracker, agent portal - all in production.

Visit the live build ↗

The live roofing build that runs the Haverhill catchment - public site, storm-damage triage, commercial-maintenance recall, photo-evidence record. Outcome described in studio voice (direction, not numbers).

Visit the live build ↗

The live independent-gym build - public site, member record, access-control, recurring billing, retention loop, branded iOS app. One stack under the gym's brand rather than five SaaS subscriptions stitched together.

Visit the live build ↗

Tell us what's slowing the business down

Send an enquiry - what you do, what's slowing you down, what you've already tried. We'll come back with a sketch of what we'd build and what it would cost. No calendar, no demo to sit through.

No calendar widgets. Email reply, scoped sketch.

Tell us what's slowing the business down

Email reply, scoped sketch, you decide. No calendar widgets, no demo to sit through.

No calendar widgets. Email reply, scoped sketch.