How we work

A process that protects both sides

Six stages with clear outcomes. At every stage you know what you get and when.

We build systems in six stages: discovery, prototype, development in sprints, testing, launch and SLA support. Each stage ends with a concrete result that can be evaluated before moving on to the next.

01
Discovery
2-4 weeks

Process analysis together with the people who actually run the processes. We find out what really happens, not what the documentation says.

What you get: A process description, scope, architecture decision and cost estimate. This is a paid stage with a concrete result that you keep even if you decide not to go further.
02
Prototype
1-2 weeks

A clickable mock-up before any code is written. The cheapest moment to notice that something is missing.

What you get: An interactive prototype of the main scenarios and agreed interface logic.
03
Development in sprints
every 2 weeks

At the end of every sprint you see a working part of the system, not a progress report.

What you get: A working piece of functionality in a test environment and agreed priorities for the next sprint.
04
Testing
in parallel

Functional, security and load testing. For public sector projects, WCAG 2.1 AA accessibility as well.

What you get: A test report with fixed defects and an accessibility review.
05
Launch
1-2 weeks

Data migration, training and documentation. The old system usually runs in parallel for a while.

What you get: A working system, trained staff, documentation and access credentials.
06
SLA support
ongoing

Agreed response times, monitoring, updates and further development.

What you get: A support agreement with clear response times and a monthly report.

FAQ

Questions about the process

Why is the discovery stage paid?

Free analysis tends to be superficial because it has to be done quickly. A paid stage allows real time for it: talking to your staff, reviewing the data and preparing an estimate you can rely on. The result belongs to you and is useful even if you take it to another developer.

What if the estimate exceeds our budget?

That is exactly what discovery is for. The scope can be split into phases: the part that delivers the most value goes live first, and the rest is built later. It is better to find this out before starting than halfway through the project.

How do we work together during development?

Every two weeks there is a short meeting with a demo of the working part. In between we communicate by email or a channel of your choice. On your side you need one person who can make decisions about the process.

What happens if the project has to be paused?

Because we work in stages, at any point you have working code, documentation and access credentials. There is no scenario where stopping leaves you with nothing.

Do you work with the public sector?

Yes. In these projects we also address WCAG 2.1 AA accessibility, GDPR and SLA requirements, and documentation is prepared to match the tender requirements.