Skip to content

Software development

How a software project runs, from first call to launch

Every project follows the same six steps. Each one ends with something you review and sign off before the next one starts.

Six steps from brief to launch

  1. Discovery

    A call about what the software must do, who will use it and by when. We ask early about the things that tend to surface late: integrations, existing data, sign-in, languages and hosting.

    A short brief we both agree on.

  2. Proposal

    We write the scope: features, what's out of scope, milestones, acceptance criteria and what we need from you. Commercial terms, and an NDA if you want one, are agreed at this step.

    A proposal ready to sign.

  3. Design

    Wireframes, then a clickable prototype and the visual design of the main screens. Where the project allows, a few of the people who'll use it try the prototype first.

    Approved designs that development follows.

  4. Development in sprints

    We build in sprints. At the end of each one you try a working build on a staging server, and we agree what comes next.

    A working build and release notes after every sprint.

  5. Testing and launch

    QA on real devices and browsers, speed and accessibility checks, forms, redirects and backups. The software goes live once you've signed off.

    The completed launch checklist and the documentation to run the software.

  6. After launch

    Bugs found after launch are fixed during a warranty period agreed in the proposal. After that, a maintenance plan can take over.

    With a maintenance plan, a monthly report of what changed.

How we run the project

  • One project lead

    Your contact from the first call to launch, who knows every part of the project.

  • Changes approved before they're made

    A new request is estimated first and added to the scope only once you approve it, so you decide what moves.

  • Regular check-ins

    A standing call at a time that works in both time zones, agreed at kick-off.

  • Risks raised early

    If something puts a date at risk, you hear about it as soon as we find it.

Ready to start with a brief?

A few paragraphs on what the software must do are enough for the discovery call.

Contact us