How we work

Four steps. Each one has its own output.

We do not start with code and we do not sell the whole system up front. We start with a fixed-price analysis — and every step after that is your decision, taken with the finished output of the previous one in hand.

Step 01

Initial analysis

The entry product. This is what we sell, not development up front.

What you get: Findings checked against how the operation really runs, a phase plan in person-days, and a specification with acceptance criteria.
How the step ends: With a specification you could hand to somebody else and build from. The output stays yours.

Step 02

Pilot

The first working version over your biggest bottleneck.

What you get: A deployed part of the system that solves one specific place — the one where the company loses the most time or control today.
How the step ends: With a version in live operation you can measure, and decide from that whether to continue.

Step 03

The business system

Finance and invoicing, CRM, projects, suppliers, contracts, reporting for management.

What you get: A system built around your process, with the data in one place and the links between modules that you keep in your head today.
How the step ends: With a go-live in the production environment and a handover with documentation and tests.

Step 04

Technology partner

We do not deliver a project and walk away.

What you get: A two-week delivery rhythm, separated environments, running the system and extending it as the company changes.
How the step ends: It does not. This is the product, not an extra service.

Price

What it costs

The initial analysis has a fixed price — not an estimate and not an hourly rate. Later phases are costed in person-days against the specification the analysis produces.

We always state the price excluding and including VAT (21 %).
Scope is phased in person-days, not hours — you can say yes or no to each phase on its own.
The code and the data are yours. Ending the engagement costs you neither.

We send the exact price of the initial analysis and the range for the pilot in a written offer — itemised, excluding and including VAT, with validity and a schedule. Write to us and you will have it within two working days.

Operation

What happens after handover

We do not deliver a project and walk away. This is what has been running at our main client for two years.

Two-week rhythm

New features and fixes go live on a regular rhythm. You know when the next batch lands without having to ask.

Four separated environments

Development, testing, acceptance and production are separate. A change is verified before it touches your data.

Automated tests

Daily automated tests over the main processes — a regression shows up before a user phones about it.

Public operational status

System availability is visible publicly, not only from our side.

Security verified from outside

A third-party security audit, most recently in April 2026, with no confirmed finding above CVSS 3.0.

Taking over

Inherited a system from another supplier?

Then the analysis starts with what already runs: what the system does, where the data is and what has to be preserved. Migration is additive — the old state keeps working until the new one passes acceptance.

Frequently asked questions

First step

We start with analysis, not code.

Tell us what grinds in your company. We will get back to you within two working days.

Book an analysis Proof