Other firms sell you a project. We sell you the thing. Custom software and ML models on a contract you'd recognise as sane: fixed price, fixed date, and if we don't deliver, you don't pay.
The contract — three terms, nothing clever
Most firms won't commit to this because they can't. The padding in their quote is there to cover the uncertainty they know is coming. We can commit to it because we've removed most of the uncertainty on purpose.
01 · Fixed price
You know the number before the work starts. No T&M. No discovery-phase billing. No change orders without a new, fixed number.
Why we can commit: small, sharp team — everyone on the build ships. Opinionated stack we've shipped before, not a snowflake rebuild each time. Scope defined on paper in the Scope Sprint, not negotiated during build.
02 · Fixed date
You know when you'll have it, and it's not measured in quarters. Typical build is six to twelve weeks, end to end.
Why we can commit: small team, no handoff theatre — the people who scope are the people who ship. AI-accelerated where it helps (glue code, scaffolding, test coverage), not where it doesn't. No steerco. Weekly demo, decisions by end of call.
03 · No delivery, no pay
If we miss the date or the acceptance criteria we signed, you don't pay. Not a discount. Not partial credit. Zero.
Why we can commit: we scope small enough to be confident — if we're not, we won't quote. Acceptance criteria written in plain English before work starts. We eat the overrun, not you. Has happened. Will happen again. Priced in.
The thing you're paying for, in the end, is the alignment of incentives — not the code.
What you're avoiding — the typical enterprise build
Every exec has been through this. The shape is always the same.
Month
Phase
What happens
M0
Kickoff deck
Slides. Optimism. A steerco is formed.
M2
Discovery
Workshops. Personas. A Miro board no-one reopens.
M5
First change order
"We found integrations we didn't price for."
M9
Scope creep
Three features added. One quietly dropped.
M13
Demo, sort of
It runs on a laptop. Not in your stack.
M18
Re-scope or cancel
Budget spent. Need has moved. Decision deferred.
A perfectly ordinary enterprise build. No-one is cartoonishly incompetent. This is just what the shape looks like. What you actually want to buy: a delivered product, on a date you can plan around, at a price you already know.
What we build — three shapes of work
Not a catalogue, an orientation. Every engagement is scoped from scratch, but most of them look like one of these. If yours looks like two, that's fine — we'll price it as one.
01 · Operational apps
The tool someone uses on Monday morning to get the job done. Schedulers, dispatch consoles, sales workbenches, internal portals. Full stack, real users, lives inside your systems.
AI scheduler for a multi-site operator
In-house sales tool for a BESS integrator
Internal workbench replacing four spreadsheets
02 · Forecasting & optimisation models
The maths that turns signals into decisions. Forecasting, classification, operations research. Shipped as a service inside your stack, with retraining and drift monitors baked in.
Rarely a product on its own, almost always needed. Getting the data clean, consistent, and somewhere the models and apps can reach it. We do this when it's in the way, and only then.
Pipeline from five legacy systems into one warehouse
Entity resolution across CRM, ERP, and support data
Cleanup before agents or models can run on top
If your problem doesn't fit any of the three, tell us anyway. Half our engagements started as "this probably isn't your thing."
How it goes — four acts
We don't run multi-month discoveries. We run four short acts, in order, and the contract is signed before act two. By the time a traditional build is still writing its kickoff deck, we're usually done.
We sit with whoever does the work today. We write down what the thing needs to do, what counts as done, and what it would cost to build. You walk away with a fixed-price quote and written acceptance criteria — whether or not you continue with us.
02 · Build — Signed · fixed price · 6–12 weeks
Two to three people, full-time on your project until it's done. We start with the riskiest part first, not the easiest, so if something is going to break the plan, it breaks the plan early enough to talk about. Weekly demo · decisions by end of call · no steerco.
03 · Hand-over — Acceptance
Against the criteria you signed in act one. Not against vibes. If we clear the bar, we invoice. If we don't, we keep going on our time until we do — or we don't invoice at all. Code, infra, models, docs — all yours. No lock-in.
04 · Keep it running — Optional retainer
Most clients take a small monthly retainer so someone is on call when a model drifts, an upstream API changes, or a new feature is wanted. You can skip it and run the thing yourselves. Plenty do. Monitoring · small changes · model refresh.
Pricing — typical engagements
Engagement
Range
Scope Sprint
€1,500 – €2,500
Build (small)
€20,000 – €40,000
Build (typical)
€40,000 – €70,000
Build (large)
€70,000 – €90,000
Above €90k
We'll tell you to split it
Engagements should be forecastable. Past a certain size they stop being that.
Selected case studies
Battery Energy Storage operator — ML forecasting model for energy prices. Higher average profits, less manual work via automated forecasts and simulation-based strategy testing.
Logistics scaleup — Optimisation model for distributing 360,000 tons/year from France across Europe. Geospatial demand analysis and route optimisation across regulatory regimes.
Construction / energy — EMS for a top-tier corporate, charging/discharging factory batteries automatically against real-time prices.
Public sector (EU) — GDPR-safe traffic optimisation: computer vision + an optimisation model that cut wait times at intersections.
Frequently asked
What does "no delivery, no pay" actually mean? Partial credit?
Zero. If we miss the date or the acceptance criteria we signed with you, we don't invoice the build. We eat the overrun. This has happened to us. It will happen again. It is priced into how we scope and how many engagements we take at once.
What if we change scope halfway through?
Then we write a new fixed price for the new scope and you decide whether to take it. What you don't get is a surprise invoice at the end. The original contract holds or is explicitly renegotiated — never drifted.
How are you 5× cheaper than the other quotes?
Three things. First, no account managers, no delivery managers, no juniors — just senior people who scope and build. Second, we use AI heavily for the parts of engineering it's good at (boilerplate, test scaffolding, integration glue) so two people do the work that used to need eight. Third, we refuse engagements where we don't already know the shape, so we don't bill you to learn.
Is this just outsourcing with a different haircut?
No. Outsourcing sells you hours. We sell you an outcome on a date at a price. The incentive structures are opposite: an outsourcing partner makes more money the longer it takes; we make money by shipping and moving to the next one.
Who owns the code after?
You do. Code, infrastructure, documentation, models, training data. Yours. Handed over, written down. You can walk away from us and keep running. We don't lock builds to our infra.
What's your stack?
Typescript + React on the front. Python or Go on the back. Postgres by default. Torch or scikit-learn for models, frontier LLMs where judgment is needed. EU-hosted. Every choice is reversible, but we default to boring so the code is boring to inherit.
How fast can you start?
Scope Sprint usually starts within two weeks of the first call. Build kicks off within one to two weeks of the Sprint signing off. We cap concurrent engagements on purpose, so sometimes there's a queue — and we'll tell you.
Why don't big firms offer this contract?
Because the economics don't work at scale. A firm with ten layers of management and two hundred people on the bench has to bill hours to stay alive. A small senior team that says no to most requests can afford to sell outcomes. This is a feature of our size, not a trick we've figured out that they haven't.