Our process

From first sketch to working software.

You see the plan, try the product and make decisions at each stage. A project director keeps you in touch with the people designing and building it.

Illustration / Mapping a handoff in a discovery workshop.

How a project runs

Some projects start with an existing platform. Others start with a sketch. We shape the scope and review points around what your team already has.

  1. Discovery workshop

    Walk us through a real task. Together we map the users, handoffs, data and constraints, then choose what success looks like.

  2. Scope & proposal

    We set out the proposed first release, costs, timing and assumptions. You can see which decisions affect the estimate before committing to a build.

  3. Design & development

    Try the main user journey in a prototype. Once it fits, we build and test the software in short increments you can review.

  4. Release

    We check the workflows with your team, confirm the rollout plan and agree what needs attention as people start using the system.

  5. Support & improvement

    We can help with monitoring, security updates and changes after launch. Feedback from real use helps decide what to build next.

Before the first call

What should we bring?

Bring an example of the job, a list of the tools involved and someone who does the work. Use an anonymised example if records contain personal or commercial information.

Use the project brief guide
What affects the estimate?

The number of user roles, how systems connect, the quality of existing records and rollout constraints all matter. We make those assumptions visible in the proposal.

What happens if priorities change?

At each review we discuss what you’ve learned, what matters most and how a change affects cost, timing and the next release.