# How We Work: Four Steps, No Surprises

A predictable process is the cheapest risk control in software. This is how a typical engagement runs, from the first conversation to life after launch.

ON THIS PAGE

- The four steps

- Discovery: write down the problem first

- Design: make the expensive decisions early

- Build: weekly, visible, tested

- How we communicate

- Operate: launch is the start

- What you own

- Common questions

## The four steps

- STEP 01 Discover We listen, read your existing systems and write down what to build and what not to. The output is a short specification, a list of assumptions and the risks that could change the plan. Engagement models

- STEP 02 Design Architecture, data model and a clickable prototype you can react to. Decisions that are expensive to reverse are made here, with you in the room. UI/UX design

- STEP 03 Build Weekly releases to a staging site, automated tests on every change and code reviewed by senior engineers. You see working software every week, not a report. Web development

- STEP 04 Operate Monitoring, support and a repository you own from day one. After launch we either keep running the system with you or hand it over cleanly. Cloud and DevOps

## Discovery: write down the problem first

Most projects that go wrong were never clearly defined. In discovery we interrogate the problem, the users and the constraints: who uses this, what they do today, what success looks like and what must not break. We also read the systems your software has to live with, because integration surprises are the most common source of overruns.

If you are still shaping an idea, the AI Idea Validation Assistant can give you a structured starting point, and a scoping sprint turns that into a specification and estimate you own.

## Design: make the expensive decisions early

Architecture is the first conversation, not a retrofit. We agree on how data is modelled, how customers or tenants are isolated, how the system authenticates users and where it can fail safely. A clickable prototype lets you test the experience before engineers invest in building it.

## Build: weekly, visible, tested

- Work ships in weekly increments to a staging environment that mirrors production.

- Typed API contracts keep the front end and back end in step.

- Unit, integration and end-to-end tests run in CI; a change that breaks them does not merge.

- Every change is reviewed by a senior engineer, with performance, accessibility and security part of review.

- Deployments are scripted, so releasing is routine and repeatable.

## How we communicate

You get one accountable point of contact, a shared backlog you can read and re-order, and a short demo each week. Questions get answered by the person who knows the answer. Changes of scope are written down with their effect on time and cost before work begins, so the invoice never surprises you.

## Operate: launch is the start

Software is only valuable while it runs. We set up monitoring and alerting, document how the system works and keep dependencies current. We know what operating software costs because we run our own products in production.

## What you own

Repository, documentation and infrastructure are created in your accounts from the first commit. You can move the project to another team at any time with no licence fees or exit negotiation.

## Common questions

## Have a project in mind?

Tell us what you are building. A senior engineer replies within one business day.
