Skip to content
MOHATech

Discover · Design · Build · Hand over

How we work

Four stages and a fortnightly rhythm. You see working software every two weeks, and you can stop at the end of any cycle.

The four stages

  1. 01

    Discover

    Weeks 1–2

    We map the process before we touch the code.

    We sit with the people doing the work, follow one job end to end, and write down every step, exception and hand-off. Most of what we learn changes the plan.

    You get
    A written process map, an architecture, and a costed plan.
  2. 02

    Design

    Weeks 3–4

    Interfaces, data and architecture agreed on paper first.

    Screens are designed and clicked through before they are built. The data model is agreed in the same fortnight, because it is the expensive thing to change later.

    You get
    A working prototype, a data model, and a build plan by cycle.
  3. 03

    Build

    Fortnightly

    Short cycles. Working software you can use every two weeks.

    Every fortnight ends with software in your hands, a short written update and a demo. Scope for the next cycle is agreed at the end of the last one.

    You get
    Working software, a written update and a demo, every two weeks.
  4. 04

    Hand over

    Final week

    Documentation, training and a clean exit. It’s yours.

    We write the documentation as we go, so the final week is training and transfer rather than archaeology. Then we step back, and you are not obliged to keep us.

    You get
    Documentation, runbooks, a recorded training session, and the keys.

The fortnight

The unit of work. Everything else is scheduling.

What you get, every two weeks

  • Software you can use, deployed where you can reach it
  • A short written update: what shipped, what didn’t, what’s next
  • A demo, and the scope for the next cycle agreed at the end of it

What we need from you

  • One person who can make decisions, for an hour a fortnight
  • Access to the people who do the work today
  • Accounts and credentials in your name, not ours

Ways to start

Pick the one that fits. They compose.

Discovery sprint

2 weeks

For when the problem is clear but the shape of the answer isn’t.

  • A written process map
  • An architecture and a build plan
  • A costed proposal, by phase

Ends with a decision, not a commitment. The plan is yours either way.

Build engagement

8–16 weeks

Design and build, in fortnightly cycles, to a date you can plan around.

  • Working software every two weeks
  • Fixed scope and price per cycle
  • Documentation written as we go

Ends with a hand-over: training, documentation and the keys.

Automation pilot

4–6 weeks

One workflow, measured before and after, with guardrails from day one.

  • One workflow automated end to end
  • A before-and-after measurement
  • A log of every decision made

Ends with a number you can take to your board.

Questions

How long does a project take?

Most builds run eight to sixteen weeks. A discovery sprint takes two, and an automation pilot four to six. You see working software every fortnight throughout, so the answer stops being a guess after the first cycle.

What does it cost?

We quote a fixed price per phase once we have mapped the work, which is what discovery is for. You approve each cycle before it starts, so the number never arrives as a surprise.

Who owns the code?

You do. Repositories, infrastructure and third-party accounts are in your name from the first commit. We work inside them rather than handing something over at the end.

Do you maintain it afterwards?

We hand it over working, documented and trained. If you want us on call for a support window afterwards we will quote for it, but nothing in the build obliges you to keep us.

Can you work with our existing team?

Yes, and it usually goes better when we do. We build alongside your engineers, review each other’s work, and leave a codebase your team already knows.

Can you take on an existing codebase?

Yes. We start with a short assessment: what is there, what it costs to keep, and what it would take to move. Sometimes the honest answer is to keep what you have.

Where are you based, and does it matter?

London. We work with clients across the UK and Europe, remotely by default and on-site for the parts that need a room and a whiteboard.

Have something to build?

Tell us about it. A founder replies within two working days.

Start a project