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.
Fixed-scope build
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.
Discovery and business case
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.
Dedicated team
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.
Run and evolve
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.
Pricing reflects scope, risk and accountability.
The number of systems, data quality, exception paths, security requirements and the level of operational ownership influence the cost more than a feature list alone.
The smallest standalone engagement is a fixed-fee discovery phase. It gives you the information needed for an investment decision, regardless of who delivers the implementation.
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.
SLA and operations
We are accountable for keeping it running
Availability targets, response times, monitoring, backups and updates under a single SLA. Named owner, defined escalation path.
Ownership and exit
You know who owns the code before we write it
The contract states who owns the code, the data and the documentation, and defines the handover procedure if the relationship ends.
Security and governance
Security is designed in, not bolted on
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.
The solution can run in your environment, in a chosen cloud region or on-premises. Data residency, subprocessors, retention rules and access controls are defined before implementation, based on the architecture and your requirements.
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.