How we work

Measure first, build second

Projects like this tend to fail the same way: nobody agreed what better meant before starting.

  1. 01

    Consultation

    Free

    You describe the work, including the workarounds nobody has written down. We tell you what can be built and what it would take. If the honest answer is that you do not need us, you get that instead.

  2. 02

    Baseline and scope

    Before any build

    We measure how long the work takes today. That number is also how you will know afterwards whether it worked. We agree exactly what gets built and what it costs before anyone starts.

  3. 03

    Build and run in parallel

    A week to a few months

    The new system runs alongside your current way of working, and you compare the two. Nothing switches over on the strength of a demo — it switches when it is proven reliable enough that checking stops feeling necessary.

  4. 04

    Hand over and maintain

    You own it

    You receive the comparison against your baseline, plain-language documentation, and access to everything in your own name. We stay on to maintain it if you want us to.

We build around your business, not over it.

A system that asks everyone to change how they work is a system that quietly stops being used two months after handover.

Ownership

What you own

Everything built for you belongs to you, from the first day it runs.

We would rather keep clients because the work is good than because leaving is difficult. We recommend staying on maintenance for the same reason we baseline before we build: things change, and someone has to be watching when they do.

You receive

  • Accounts and access registered in your name
  • Plain-language documentation of what it does and how to change it
  • No licence or subscription owed to us to keep using it

Continuity

If we are not around

A fair question to ask a small firm, and worth asking early.

Nothing we build is a black box. If we disappeared tomorrow you would still hold a working, documented system and full access to it. More on how the practice runs →

What that rests on

  • Widely adopted, open tools — nothing only we understand
  • Documented so another developer could pick it up without meeting us
  • Tested against real cases before switchover, with alerts when something fails

Start with the work

Tell us what it looks like today. The first conversation costs nothing.

Book a consultation