How a project runs, from first message to support

The same principles apply whether we’re building something new or fixing something that exists. The steps differ a little — choose the one that fits you.

Building something new

  1. 01

    Understand the requirements

    We talk through what you want to build, who will use it and what success looks like.

    You getA shared summary of goals and constraints

  2. 02

    Shape the scope

    We break the idea into features, separate essentials from later additions, and identify unknowns.

    You getA prioritised feature list

  3. 03

    Propose a solution

    We recommend an approach and technology that fits your needs and budget, with an estimate.

    You getA written proposal to review

  4. 04

    Develop in steps

    We build in reviewable increments so you can see progress and adjust early.

    You getWorking software at each step

  5. 05

    Test, deploy and validate

    We test against the agreed requirements, deploy, and confirm it works in production.

    You getA live release and handover notes

  6. 06

    Agreed follow-up support

    Fixes, maintenance or further development, as we agree.

    You getContinuity after launch

Improving an existing application

  1. 01

    Understand the problem

    You describe what is happening, since when, and how it affects users or the business.

    You getA clear problem statement

  2. 02

    Review the existing system

    We look at the code, infrastructure and logs to understand how things currently work.

    You getAn initial assessment

  3. 03

    Propose a fix

    We explain the likely cause, the options and their trade-offs, with an estimate.

    You getA recommended next step

  4. 04

    Implement the fix

    We make the agreed changes, keeping them as small and safe as the problem allows.

    You getReviewed changes in your repository

  5. 05

    Test, deploy and validate

    We verify the fix, release it carefully, and confirm the issue is resolved in production.

    You getConfirmation and a written summary

  6. 06

    Agreed maintenance

    Optional ongoing support to keep the application stable and up to date.

    You getFewer repeat incidents

What you can expect from us

  • A written scope before work begins, including what’s out of scope
  • Regular updates at an agreed rhythm, with early warning of risks
  • Work committed to your repository, not held on our side
  • Documentation that lets someone else continue the work

What helps from your side

  1. 1One person who can answer questions and make decisions
  2. 2Access to existing code, environments and accounts, when needed
  3. 3Feedback on each delivered step within a reasonable time

Step one is a conversation. Tell us what you need.

Discuss your project