Something that does not exist yet
Concept, architecture and a first release. We keep the initial version small enough to ship and structured enough to grow.
Or it does not exist yet, and it has to.
Both are our work, and most of it is the first: we stay with systems that already run a business — on a monthly retainer or as engineers inside your own team. When something new has to exist, we build it so it can still be maintained in five years.
Pick the one that describes you. The rest of the site follows that choice — services, work and the first question on the contact page.
Concept, architecture and a first release. We keep the initial version small enough to ship and structured enough to grow.
A running application, a database with history, and integrations that cannot be switched off. This is where most of our work starts.
Engineering on an existing system starts with understanding it. This is the part that decides whether everything after it is cheap or expensive.
The code, the database, the integrations, the cron jobs nobody documented. We write down what the system actually does — which is rarely what the documentation says.
An undocumented system that only builds on one laptop is not maintainable. First milestone: it runs locally, from a clean checkout, for anyone.
Enough automated coverage on the paths that carry money or data that a change can be judged before it reaches users.
The first release is deliberately small and reversible. Only after that do we touch anything structural.
A system nobody can build from a clean checkout is not maintained — it is survived.Working principle
Every system we work on is somewhere on this line. Where yours sits decides what the work actually is.
A first release small enough to put in front of real users, and structured so the second release does not require a rewrite.
The data model that looked right at launch meets how the business actually works. Integrations arrive. Someone asks for a report nobody planned.
The people who wrote it have moved on. The framework is three majors behind. The system is still running the business.
We have worked on platforms whose clients, brands and internals we cannot name. Rather than dress that up as a case study, we leave the frame empty and describe the problem shape instead: high order volume, per-location menus and pricing, point-of-sale and delivery integrations, and releases that cannot take a storefront offline.
An NDA can be in place before you share requirements, architecture or commercial detail — and stays in place afterwards. That is the same protection your project gets.
Before anyone commits to a retainer, both sides should know what they are taking on.Why the check comes first
System-Check: three working days in your code, database and deployment, at a fixed €1,290. You get a written report — what the system actually does, where the risks are and what an upgrade path costs — and a call to go through it. If you continue with a retainer within 60 days, the full amount is credited against the first month.
A short description is enough to begin. If the system already exists, tell us what it does today and what needs to change.