How a project runs

Four steps, the same for every project, so you always know what happens next and what it costs.

  1. 1

    Discover

    We learn how the work moves today and agree what to build first, with a written scope and price.

    You get

    • A written scope: what we build first and what comes later
    • A fixed price and an agreed timeline

    We need from you

    • A call about how the work runs today
    • Access to the tools you already use, if we connect to them
  2. 2

    Design

    Flows, screens and the data model, reviewed with you before code starts.

    You get

    • User flows and screens for the main tasks
    • A clickable prototype where it helps
    • The data model, written down

    We need from you

    • Feedback on the screens before any code is written
  3. 3

    Build

    Working software in short rounds on your own accounts, tested on every change.

    You get

    • Working releases you can use and test as we go
    • The code in your own repository, tested on every change

    We need from you

    • Trying each release and telling us what feels wrong
  4. 4

    Improve

    After launch you get guides and a walkthrough, and we stay your contact as it grows.

    You get

    • A walkthrough with your team and written guides
    • Hosting, monitoring and backups on your accounts
    • The same people as your contact as it grows

    We need from you

    • Telling us what to improve next

What you can count on

  • A price that holds

    The price in your scope is the price. Anything added is agreed, with its cost, in writing first.

  • Progress you can try

    You get working software to use during the build, not a big reveal at the end.

  • Answers within a working day

    Questions get a reply within one working day, from the people doing the work.

Still have questions? Read the answers to common ones