Discuss your project
Menu

How we work

A predictable process: you know what is being built, what it costs, and what you will see at the end of every two weeks.

From first call to live system

  1. 01

    Discovery

    1–2 weeks

    Workshops with the people who will use the software. We write user stories, map the data, and agree what is in and out of scope.

    You receive: Scope document, estimate and sprint plan

  2. 02

    Prototype

    1–2 weeks

    A clickable design of the key screens. You test it with your team before any code is written, when changes are cheap.

    You receive: Approved Figma prototype

  3. 03

    Sprints

    2 weeks each

    We build in two-week sprints. Each ends with a demo of working software on a staging site you can use.

    You receive: Working features every two weeks

  4. 04

    Launch

    1 week

    Data migration, final testing, training for your team, and release to production through the pipeline.

    You receive: Live system, admin guide, handover

  5. 05

    Support

    Ongoing

    30 days of fixes after go-live are included. After that, a maintenance agreement with agreed response times.

    You receive: Monthly health report

Agile, without the jargon

We follow Scrum. In practice that means a prioritised list of work you can see at any time, a short planning session every two weeks, daily stand-ups inside the team, and a demo where you decide what is ready.

You get one named project manager and a weekly written update: what was done, what is next, and anything we need from you.

DevOps from the first week

On day one we set up the pipeline: code review, automated build, tests, a staging site and a one-click release to production. Releases become routine instead of risky, and any release can be rolled back in minutes.

We use GitHub Actions or Azure DevOps, with Docker where it helps.

Ways to work with us

  • Fixed price

    Best when the scope is clear

    We agree the scope after discovery and quote a fixed price. Changes go through a simple written change request.

  • Dedicated team

    Best for ongoing product work

    Engineers work as part of your team on a monthly fee. Scale up or down with one month's notice.

  • Time and materials

    Best when requirements will change

    You pay for the hours used, tracked against the sprint board, with a monthly cap you set.

Quality and security practices

We follow the practices behind recognised quality and information-security standards in every project. NDAs are signed on request before we see any of your data.

  • Every pull request is reviewed by a second engineer
  • Automated tests run on every change
  • Separate development, staging and production environments
  • Secrets kept out of code, access limited per project
  • Encrypted backups, tested by restoring them
  • Dependencies scanned for known vulnerabilities
  • Documentation written as we build, not at the end
  • Source code in a repository you own

Have a system in mind?

Tell us what it needs to do. We will reply within one working day with questions, a rough budget range and the next step.

Discuss your projectMessage on WhatsApp