How we work
Plan the work, then work the plan
The unglamorous version of that phrase: decide what the thing must do and what it must never do, write it down while changing it is still cheap, and keep the record so that in two years somebody can answer why.
Contract review
Before we quote, we determine whether we can actually meet what is being asked, including the statutory and regulatory requirements you may not have stated, and which side of the hosting boundary the engagement will sit on. If the answer is that we are the wrong supplier, that is a legitimate outcome and you hear it in week one.
Design and development
Planned stages with defined inputs and outputs. Review, verification and validation are separate recorded activities. Security and accessibility are requirements in the same list as the features, not a phase at the end.
Release acceptance
A defined acceptance against the recorded requirements, with nonconforming outputs handled explicitly rather than shipped with a note. Nothing reaches production on the strength of a verbal yes.
Go-live and service transition
The workload enters the hosted estate inventory with its backup schedule, monitoring, restore test date and named owner. This is the step most suppliers skip, and it is the one that decides what the next three years feel like.
Run, measure, improve
Incidents, patches, restores, capacity and satisfaction are measured and reviewed, and the findings go back into the build stream, because we are the ones who will live with them.
What we hold to
Small on purpose
Say the true thing early
An uncomfortable assessment in week one is cheaper than a comfortable one in month nine. This applies to our own gaps as much as to your architecture.
The record is part of the work
If it was not recorded, it did not happen. For an auditor, for the next engineer, and for you in two years when you need to know why.
Nobody hands it over
The team that builds it is the team that runs it. It changes what people choose to build.
Inside the EEA
We are established in the Netherlands and our people work within the EEA under our policies. Data location is a design decision, not an afterthought.
We built our own tooling
We build software for a living, so we built our own: more than twenty internal tools and AI automation that take the repetitive half of building and running. That is why a team this small can do both. The judgement stays with the person whose name is on the work. By default, client personal and production data does not go to third-party AI services.
The first step is a conversation, not a proposal
Tell us what you are trying to do and what is currently in the way. If it turns into a project, good. If it turns into advice you act on without us, that is a reasonable outcome too.
The first step is a conversation, not a proposal
Tell us what you are trying to do and what is currently in the way. If it turns into a project, good. If it turns into advice you act on without us, that is a reasonable outcome too.