€4,900 buys a week. A week ends with something running.

That is the number, and the unit is the thing to read twice: a week ends with a version running that you can put in front of the people you want to sell to. Then you decide whether there is another one, at €4,900 as well. About $5,700 at September 2026 rates; the invoice is in euros.

There is no total on this page, and that is not an omission. You buy a week at a time and there is nothing to commit to beyond the one you are in. The assessment gives you an estimated number of weeks in writing, revised once after week one; it is an estimate, not a total either of us has agreed to. One client bought forty of these weeks, one at a time, and could have stopped after any of them.

Seven terms, and two of them change what you sign

1. Provenance.The senior engineer who wrote your assessment is on your weekly call and answers for what ships. That does not get delegated to the fleet.
2. Cancellation.Company to company, after any week. No notice, no setup fee, no seat cost, no long commitment: the week being built is the whole of what either of us is committed to. There is nothing to cancel.
3. Every week.You don't check this at the end. A demo recording arrives 24 hours before we talk, you watch it first, and then you decide whether there is another week. That is the answer to hiring a supplier you have no references for: the shortest possible first bet, checked immediately.
4. Custody.Repository and cloud accounts in your company's name from day one. The repository lives in a GitHub or GitLab organisation you own; the owner field is the proof, and someone you didn't hire can verify it in under a minute. The escrow conversation is moot before it starts, because the code never had a custody problem.
5. Acceptance.A written definition of done for the week, agreed before it starts, including the three tests the documentation has to pass. If a test fails, the week is not done, at no extra charge.
6. What you send us.Named before work starts: what the fleet may read, what it may write, and what never leaves your accounts. We show what you send to nobody, and we sign your NDA before opening it if you ask.
7. After you stop.It keeps running in your account, because it was never in ours. The documentation was tested by somebody who did not write it. If something needs doing later, a dependency patched, a certificate renewed, a provider changing something underneath you, that is a week, or a conversation about whether it is one. There is nothing to subscribe to and nothing to cancel. If you have someone who can do it, you should.

For the engineer this gets forwarded to: the in-house column is the strong one

Hiring has a real advantage this doesn't: the capability ends up inside the company and stays there. That is worth saying plainly rather than arguing around. What the comparison leaves out is who assesses those candidates before anyone signs, the months of recruiting before they start, and the ramp after that. And the throughput isn't like for like: a team is a group you have to run, where this is one senior engineer deciding and a fleet building. Whoever scoped it on day one is on the call every week after.

Not for you if

You want a fixed quote against a frozen spec, or what you want fits in one prompt. The full list is on the how-it-works page.

The first call is free and the first week is the whole commitment. That is deliberately the cheapest way to find out whether this is wrong for you.