Skip to content
Faomu
Approach

Every stage ends in something you keep.

Our engagements move through five stages. Each ends with a written sign-off and a deliverable you own, so you can stop at any point without losing the work.

01 — Stages

What happens, and what you receive.

  1. 01

    Survey

    1–2 weeks · fixed fee

    Two engineers spend time with the people who use the current process and the people who maintain the systems behind it. We read the existing code and data before forming opinions.

    You receive
    • A map of the current systems and process
    • A register of risks and unknowns
    • A recommendation, including whether to build at all
  2. 02

    Specification

    2–4 weeks · fixed fee

    We write down what the system will do, what it will not do, how it will be tested and what it will cost to build. Acceptance criteria are written so that either side could check them.

    You receive
    • Functional specification
    • Architecture outline and security model
    • Acceptance tests
    • A fixed or capped price for the build
  3. 03

    Build

    Two-week increments

    Working software every two weeks, deployed to your environment and demonstrated to the people who will use it. Changes to scope go through a written change note that states the cost and the effect.

    You receive
    • A working increment every two weeks
    • Test reports for each increment
    • A running log of decisions and changes
  4. 04

    Handover

    2–4 weeks

    Your engineers pair with ours, run the release process themselves and handle a rehearsed incident before we step back. Access we no longer need is removed.

    You receive
    • Runbooks for operation and incidents
    • Architecture decision records
    • Training sessions for your engineers
    • All credentials and accounts in your name
  5. 05

    Run

    Optional · ongoing

    We operate the system under a service agreement with defined response times, or remain available to your team for the questions that only the original builders can answer.

    You receive
    • Monthly written report
    • A prioritised list of improvements
    • Response times agreed in writing
02 — Commitments

Written into every contract.

  1. 01You own the work from the first commit.Code, documentation and designs live in your repository and your accounts.
  2. 02You can stop at any gate.Each stage ends with a sign-off. End the engagement there and keep everything produced so far.
  3. 03The people you meet are the people who build.Named engineers, no subcontracting without your written approval.
  4. 04The build has a fixed or capped price.Agreed at the end of Specification, against written acceptance tests.
  5. 05Software is shown on your infrastructure.Every demonstration runs in your environment, so what you see is what you will run.

Start with a survey.

One to two weeks, a fixed fee, and a written recommendation, including whether to build at all. It is the cheapest way to find out whether we are the right team.

Arrange a survey