Most of what the house makes lives on a shelf: systems already built and running. A commission is the other door, for those who want something that does not yet exist. Whole systems, designed and built end to end, by one person.
There is no intake form pretending this is a transaction. The work begins with the person who will actually build it, not a junior, not an account manager. An intake agent takes in everything I need from you: what the system is, who it is for, what it has to hold. You brief it your way, in your own time, and it closes only when it genuinely has what it needs.
After the conversation, I take what you gave me and turn it into something concrete: a brief, the research underneath it, and a recommendation that cuts across business, technology, and product. Then we meet and go through all of it together. You leave with the deliverables either way.
The intake agent extracts everything needed from you, resumable and on your terms.
I break it down into a brief, run the research, and draw the recommendation across business, tech, and product.
We meet and go through all of it together, honestly, side by side.
The deliverables are yours, whether or not we go on to build.
Whether or not we build together, you leave with a clear, honest reading of what you want to make, yours to take anywhere. And if we do build: a commission ships in weeks to months, not quarters — scope decides, but there are no handoffs to lose seasons in.
Your project as I have understood it, written back to you clearly. Made concrete and coherent, so the thing you described becomes a thing that can be built.
yours to keepThe reading underneath the brief, shown openly: the real competitors studied, the honest question of whether it differentiates put plainly, the people it is for and how it would reach them.
yours to keepNot just a technical outline. A recommendation that cuts across all four: the business and strategy, the technology and architecture, the product and UX, and the cost to build, stand up, and run it at more than one level of engagement. The whole reading, from one hand.
yours to keepIt is the systems the house built for itself, owned end to end, from the first decision to the running infrastructure.
Not work done quietly for someone else under an NDA. A flagship in production solving the problems around Pillar Two, and an ecosystem of tools. Owning a system end to end is a thing you can only prove by having done it for yourself.
When it is done you own the system completely: the repository, the infrastructure, and code written to be read, documented, and handed over cleanly. Built to outlive the commission.
You are not being put through an assessment. We look at the same reading from two sides and decide whether it is a match. You keep everything either way.
One person builds this. So ask the uncomfortable question early — the answer is structural, not reassuring words. A commission is not a service you rent from me; it is a system you own, the way you own anything made to measure. Nothing sits behind my login, and nothing needs an escrow clause — escrow protects code a supplier keeps, and here nothing is kept. And the build itself lands core-first wherever the problem allows: a runnable spine early, components added onto it — so an interrupted build is a smaller system, not a dead one.
The repository, the code, the infrastructure, the documentation — yours, in your hands, from the start of the build. Not licensed, not gated, not hosted behind my account. There is nothing to hand over, because it was never mine to hold.
Every commission carries its own paper trail: the research, the project documents, the record of what was decided and why, kept as the work happens. The next developer doesn’t just inherit code — they inherit the reasoning behind it.
If I disappear tomorrow, you lose your builder — not your system. Code written to be read, documented to be picked up, running on infrastructure you control. Bring in any competent developer and the work carries on without me.
Three things hold together, and they are chosen. The quality is high, built by one hand to a doctrine. It arrives fast, because there are no handoffs to lose time in. And it is priced deliberately, because that combination is rare.
The build that may follow is never a list price — its frame is set from the reading, because no one can honestly scope a system they haven’t understood: not you writing a procurement brief in the dark, and not me pricing one blind. But so you can place it: commissions start at €50,000, deliberately. This house builds systems, not small apps. Most land between €75,000 and €200,000 depending on scope.
And a system is not done because it shipped: many commissions continue as a standing retainer — from €1,500 a month, covering monitoring, upkeep and up to five hours of hands-on work. Anything larger gets its own scope and its own agreement, so the retainer stays honest.
A deliberate fixed amount, set on purpose. No lower tier and no discount, because a discount would say the wrong thing about the work. And if we go on to build, the full amount counts toward the commission — you only ever end up paying for the reading itself when there is no build. The process starts when payment is received.
Every commission gets its own agreement — but the shape of it is not a negotiation, so here it is, in the open.
The frame exists because I once built without one. Years ago I agreed to deliver a set of systems on a broad-strokes scope — a bullet list of what was in, a few things explicitly out. Two days after the handshake, the first extra component landed: three weeks of work on its own. By the end the scope had grown seventy to a hundred per cent past what we had shaken hands on, nothing was written sharply enough to point to, and it ended in dispute — the systems never shipped, and everyone lost. The lesson was never technical. It was that you cannot set an honest frame for a build no one has properly understood — which is why the reading comes first, and why the frame below is not negotiable.
A quarter on start. A quarter across the milestones. The remaining half on delivery of the finished system. Until the system stands, you hold the larger share of the money — the risk sits with the builder, where it belongs.
A milestone is a runnable stage of the build, not a status report. Interrupted at any point, you stand with a smaller working system and everything already paid for in your hands — never a folder of promises.
Adjustments and refinements within the agreed scope are part of making a system — expected, included. A new part of the system, or a rethink of its structure, is a new decision: scoped, priced, and agreed before it is built. The line is drawn in the brief, so neither side has to argue about it later. And the reverse holds just as plainly: when something is my technical mistake, it is mine — fixed immediately, at my cost, never billed.
What “delivered in full” means is defined in writing before the build starts — measured against the brief and recommendation you already own, with an agreed acceptance window. An EU agreement, under EU law.
There is no rate card, because this is not time sold by the hour. It is a system, scoped to the problem and priced for what it is.
The house takes on only a handful of commissions, because each is built by the same single hand that builds everything else. The arithmetic of one person doing the whole of the work.
A confidentiality understanding sits under all of this from the outset, for your protection. The ordinary caveat applies, that it cannot cover an idea already in motion elsewhere. It is assumed, not the point.