Process

Four stages,
each with a result

From the first conversation to support of the live product. After each stage you get something concrete that you can check.

Project stages

01

Study

We learn how your business works, who will use the system and what limits the project. Then we agree on what counts as success.

We talk to the people who will use and maintain the system. We also look at what you already have: code, servers, data. Budget, deadlines and links to other systems come up early, before they turn into surprises.

What you get

  • Agreed goals and measures of success
  • List of limits and risks
  • Overview of your current systems
02

Plan

We plan the screens and the structure of the system and make the big decisions before development starts.

We sketch the main steps users take. We choose the structure, the technologies and how the system will exchange data with others. Each important decision is written down with its reasons, so you can come back to it later.

What you get

  • Plan of structure and connections
  • Main user steps or prototypes
  • Written decisions with reasons
03

Build

We work in short rounds, show you the result after each one and test the system as a whole.

Each round ends with something you can open and try. We test the parts together, not one by one, and set up automatic releases (CI/CD) and monitoring along the way.

What you get

  • Working versions to try
  • Tested code and automatic releases
  • Up-to-date documentation
04

Launch & support

We release the product, keep it running and improve it as your needs change.

At launch we put the system live, turn on monitoring and prepare a plan for what to do if something breaks. After that we can keep supporting it and adding features at the same pace.

What you get

  • Live release with monitoring
  • Step-by-step guides for support
  • Plan for support and growth

Rules we keep at every stage

Task before technology

We choose tools only after we understand what your business needs.

The system as a whole

Code, links to other services and server care are planned together.

Open process

You always see what we decided, what comes next and how far we are.

Work for years ahead

We build so the system is easy to change next year, not only at release.

Questions about the process

How do you record decisions?

We write down each important decision with its reasons and the options we turned down. You have access to these notes, so anyone who joins later can see why the system is built this way.

How often will we see progress?

We go through the results at the end of every round. How long a round lasts and how you prefer to meet, we agree at the start.

What happens after launch?

In the first days after release we watch the system closely and fix whatever comes up. Then you decide whether we continue with support and new features. That work is agreed separately.

Can we start with something small?

Yes. A short study of your task or a review of your current system is a good first step. You get a plan and see what working with us is like before a bigger project.

Have a task in mind?
Let’s talk it through

Write a few lines about what you need. We’ll reply with questions and suggest where to start.

Start a project