The Sprint · ten working days · fixed price €12.500

The demo was impressive. Then it went quiet.

The prototype works. But is it allowed to touch customer data? Who is accountable when it goes wrong? And what does it really cost to take this to production? While those questions are open, nothing happens. In ten working days there is working code on the critical part, and a decision you can defend.

We have a prototype that has been waiting months for a decision.

I have three quotes and no idea which one is right.

Nobody dares to say whether this is reliable enough for production.

Every proposal I get starts with six months of discovery.

01 · Ten working days, one question

What is The Sprint?

One bounded question: can and should AI actually carry out this work, and how do you build that reliably? You end up not with a report, but with three outcomes you can check.

Outcome 01

The design

A drafting compass with a red point on a folded drawing.

What AI will carry out and where human judgement stays. Which data, integrations and architecture that needs. And which risks come with it, including the ones you would rather not hear about.

Outcome 02

Working proof

A small gearbox on a test block, with a lit red lamp.

Working code on the critical part: the piece the whole thing depends on. Running in your context, not in a clean demo environment.

Outcome 03

The decision

A Y-shaped pipe with one branch shut off by a red valve.

Build or no-build, with a concrete production path: what it takes in time, people and money, and in what order.

That working proof is what sets this apart from a consultancy: not a report, but the validation an investment decision rests on.

What a Sprint is not.

Works well when

You have an idea, a prototype or a pilot that has been gathering dust.
Someone can decide, and there are people who know the work and the systems.
You can give access to the relevant systems and data, or to a representative copy.

This is not

One question and one critical proof, not yet a full implementation.
It is not a generic AI roadmap for the whole organisation.
It is not unlimited discovery: we agree up front who the client is, which experts are needed and what access there will be.
There is no guarantee the answer is yes; no-build is a valid outcome, and usually the cheapest one.

02 · Your time: a day and a half

How does it work?

Your time: half a day of kickoff, half an hour of checkpoint and half a day for the decision. I do the rest.

A flip chart with a blank sheet and one red marker on the ledge.

Day 1

Kickoff with the people who know the work.

Where does the time go, what drives it, and what may AI touch?

A stack of rolled drawings with one red gear on top.

Day 2–4

The design and the critical part.

I work it out and decide what has to be proven before money goes into an implementation.

An hourglass, half run through, with red sand.

Day 5

A half-hour checkpoint.

This is the direction, this is what I will build, these are the risks.

A small hand-cranked machine with gears and a red crank handle.

Day 6–9

Working code on the critical part.

In your environment and on your data, not in a clean demo setup.

Day 10

Walking through the proof, and the decision.

We walk through the proof and you get the build-or-no-build recommendation with a production path.

Do you have a prototype like that?

A half-hour call costs nothing. If it turns out the question is too small for a Sprint, I will say so.

Book a Sprint

03 · What you can check

What can you check?

What is below runs in production or is publicly readable. Check it yourself before we talk money.

A conveyor belt with three boxes, the red one just rolling off.

I run my own delivery pipeline

Agents pick up tasks from my backlog, open their own branch and deliver the work as a pull request. I specify, review and merge. An agent cannot skip or talk its way past the quality gates: test suite, code style, front-end build and a separate review round.

How the pipeline works

To check · This site was built that way. An agent never merges by itself.

A ruled sheet of paper with a round red stamp in the corner.

MCP E-Invoice EU is public

An MCP server that makes the European e-invoicing rules (Peppol, EN16931) usable for AI systems. Open source, so you can read the code, the choices and the edge cases yourself instead of taking my word for it.

To check · The repository is public on GitHub.

04 · Price, next steps, questions

What does it cost, and then what?

One fixed price and no arguing about hours. Below it what can follow a Sprint.

The Sprint · ten working days

€12.500

fixed price, excl. VAT

Two weeks of elapsed time, starting within two weeks.
Kickoff, checkpoint and decision session.
Design, working proof and a production path.
All code and documentation are yours, even on a no-build.

A small device under a glass bell jar, with a red tag on a thread.

Also have a look at

A scaffold of blue tubes with one red plank on the top level.

Is the direction right? If the direction is right, I build the system or lead the implementation together with your team. Not a standalone demo, but software for the real environment: data, APIs, business rules, approvals, monitoring, exceptions. A Build starts with a fixed scope and is then quoted in phases.

See The Build

A drafting table with a rolled drawing and a red T-square.

Want someone who stays involved? Two or four days per month, per month, excl. VAT, three-month minimum. Structurally involved as a senior partner: assessing opportunities, guarding architecture, building critical parts. Usually what follows a Sprint or a Build, not something you start with.

See Fractional AI Architect

05 · What people want to know

Still have questions?

The questions that always come up, with short answers. If yours is not among them, just ask it.

What if the outcome is no-build?

Then for a fixed price you have avoided an expensive mistake, plus a design and working code you can reuse later if circumstances change.

Who owns what gets built?

You do. Code, design and documentation are your property, even on a no-build.

Do you work with our own data?

Preferably yes, because otherwise you prove nothing. If that is not possible we work with a representative copy and I state explicitly what stays unproven as a result.

Which models and vendors do you use?

Whatever fits the question, including locally running models when data cannot leave the country. I build so you are not locked into one vendor.

Can we start smaller?

Yes. If the question is not sharp enough for a Sprint yet, The Scan is the smaller step: two working days, fixed price, and half of it is credited if a Sprint follows.

Who runs this

Ten days and not one of them wasted.

I have seen too many AI projects stall at a report nobody dares to act on. Working code on the critical part reduces the biggest technical uncertainty, in two weeks instead of two quarters. And it works both ways: if it cannot be done, you know that now, for a fraction of what a failed implementation costs.

Daniel Plomp · AI Architect & Builder

Two weeks to a decision you can defend.

Describe briefly where you are stuck. You will hear straight away whether a Sprint is the right tool, and if it is not, I will say that too. A half-hour call costs nothing.