Pick the one that matches how much you want to hand over.
They are not tiers and there is no upsell path built into them. Most clients start with the second and move to whichever of the other three fits what they learned.
A defined deliverable with a fixed price and a fixed date. Best for the eight recurring patterns and for anything where the specification is genuinely stable.
Stages one and two on their own, at a fixed fee agreed before it starts. You get a process map, a measured baseline and a documented business case — yours to keep, with no obligation to build with us. If you do go ahead, it is credited against the build.
A named team of engineers working as an extension of yours, billed monthly. Common when the client is an IT company that needs specific capability — agents, integrations, data engineering — without hiring for it. You direct the work; we handle staffing, continuity and quality.
We take operational ownership of what is already built, yours or ours, under an SLA with a monthly retainer covering monitoring, support and a defined development capacity.
Whichever model you pick, this is the room.
Two of ours and two of yours around one table. Not a pitch deck and a projector — a laptop, your actual process on the screen, and the awkward questions asked early enough to still change something.
No price list, and the reason is not coyness.
We do not publish a price list. For work that is built rather than licensed, a range honest enough to be true is too wide to help you, and a narrow one is a guess dressed up as a number — and either way it anchors the conversation before anyone knows what is being built.
Four things move the figure, and you can assess three of them yourself right now: how many systems have to be reached, whether they have usable APIs, how clean the master data underneath is, and how many exception paths the process really has. That last one is almost always larger than people expect, which is exactly why we measure it before quoting rather than after.
What we can commit to up front is the shape of the risk. The smallest possible first step is the discovery phase: fixed fee, agreed before it starts, and it ends with a process map, a measured baseline and a business case that is yours to keep whether or not you build with us. If the numbers do not work, that document is what tells you so — and we have handed over exactly that more than once.
Size it yourself first.
Four inputs, an order-of-magnitude estimate, no email required.
Open the calculator →We plan the ending at the beginning.
This is the part most suppliers leave for the contract review, by which point the leverage has moved. It is easier to read it now.
Availability targets, response times, monitoring, backups and updates under a single SLA. Named owner, defined escalation path.
The contract states who owns the code, the data and the documentation, and defines the handover procedure if the relationship ends.
EU cloud or fully on-premises. Encryption in transit and at rest, role-based access, and a complete audit trail. GDPR and the EU AI Act are addressed at design time.
The practical questions, answered up front.
We work on Central European Time, so our standard day overlaps with the US East Coast until around 11:00 a.m. Eastern. Delivery teams work asynchronously by default.
Contracts in English, invoicing in EUR or USD.
For European clients we stand on Azure, so the data stays inside Europe and GDPR is a design decision rather than a discussion. For a US engagement, hosting follows from the consulting phase rather than leading it: we work out what you already run and where we can genuinely help, and the answer falls out of that.
All delivery documentation, code comments and client communication in English by default.
Things we will turn down.
The cheapest credibility on this site. A supplier who says yes to everything is telling you where their limit is anyway — just later, and at your expense.
We do not take on a build without measuring the baseline first. Without it there is no way to tell later whether it worked, and we are not interested in that argument in month nine.
We do not sell proofs of concept that have no path into production. If a process cannot realistically go live, we will say so in stage two rather than bill for a pilot.
We do not put an agent in front of a decision that should stay with a person — pricing, credit, hiring, anything with legal exposure. The agent prepares the case; a human signs it.
We do resell Microsoft licensing where we implement it. We disclose the margin, and it does not drive our architecture recommendations — if the right answer is a competitor's product or no product at all, that is what the business case will say.