How we work

Every project starts with a conversation.

We review what you have, ask questions and plan the software product with you. Then you get a written plan and an agreed price before any build starts.

From first talk to support

  1. Talk it through

    We review what you already have, ask questions and brainstorm with you until we both understand what the product must do.

  2. A written plan

    You get a plan of what we will build, in what order and how you will see progress along the way.

  3. The price, agreed

    We agree a fixed price in writing. Nothing is built until you say yes.

  4. Build and launch

    We build it in the way that suits the project, then launch it with you.

  5. Support

    Once it is live, we can keep it secure and up to date for one fixed monthly amount.

Two ways to build

We pick the one that fits your product together, during planning. The steps above stay the same either way.

Release by release

We build in small releases, each with its own scope and price. Your users get working software early, and each release shapes the next.

Suits a new product that needs to reach users quickly.

One full build

We build the whole product in one go, often over six or seven months. At agreed checkpoints you see the progress and test it.

Suits a platform that must launch complete, such as a government service.

Once the plan is agreed, we put three things in writing

  1. You see the price before the build starts.
  2. You get the test results at every handover.
  3. You own the code from the first day.

If the plan has to change

You hear it from us before any work moves. We explain what changed and what it does to the price, and nothing goes ahead until you agree.

What you get at every handover

At the end of every release or checkpoint, you get a short report of the tests we ran, what passed and what changed for your users.

Support after launch

Once your software product is live, monthly support keeps it secure and working. You pay one fixed amount each month, priced after a first look at your product.

See how support works
  • Security updates, and fixes for anything that breaks
  • Small changes every month
  • A monthly note of what changed and what we tested
  • Stop any month with notice

Your code and your accounts

  • The code lives in your repository, not ours.
  • Every handover comes with notes another developer can follow.
  • At handover you get every login, key and account in your name.
  • Your code, notes and logins sit in your own accounts, so the project never depends on one person's laptop.

Your contract can change these terms.

Access to your systems

  • We ask only for the access the current work needs.
  • Passwords and keys never go into the code.
  • We test with made-up data, never your customers' real details.
  • When the work ends, you remove our access and we confirm it in writing.

Tell us what you want to build or improve. We reply in less than 24 hours to set up the first conversation.