Something that does not exist yet.

Published prices

Machine, support and engineering prices are listed together at /pricing. Work built to order is quoted against its agreed scope.

What this is

A project, not a package.

A bespoke project is one where the answer is not a product we already run. It might be a tool that only your organisation needs, a bridge between two systems that were never meant to meet, a migration nobody has a script for, or a piece of the open stack bent into a shape it does not ship in.

It is written, built, documented and handed over the same way everything else here is: on infrastructure you can inspect, with the decisions written down, and with an exit designed before the start.

• Software written for one organisation and owned by it
• Integration between systems that have no ready connector
• A migration with no existing path, planned and rehearsed before it runs
• An existing open component changed and maintained under your name
• A second opinion on a build somebody else is quoting for

How it starts

Four steps, and the first one is free.

We read what you send and answer with questions, not with a quote. A price before the questions is a guess dressed as a number.

01 · A letter

What you run now, what has to change, and by when. Two paragraphs is enough to start.

02 · Questions

We come back with what we need to know. This costs nothing and commits neither side.

03 · An assessment

A written read of the problem, a target shape, and a scope you can sign off. Priced in days at 110 EUR an hour, with no VAT added: 3 days for an ordinary estate.

04 · The build

Priced from the scope, not from the hours. Engineering at 110 EUR an hour where the work is open-ended.

The assessment is useful on its own. It can end with the advice not to build the thing, and that is a result we are paid for.

What we need from you

Four answers, and none of them technical.

• What the thing has to do, described the way you would describe it to a colleague
• Who has to use it, and roughly how many of them
• What it has to talk to that already exists
• What decides that it is finished

If you can answer those four, we can tell you whether this is a project or a product you should buy instead.

What you get

The thing, and everything needed to keep it.

• The source, under a licence that lets you keep it
• The deployment, rebuildable from files rather than from memory
• Documentation written for the person who inherits it, not for us
• Architecture decision records: what was chosen, and what was rejected and why
• A named owner for every part, and the training to take it over

What we would refuse

Named here so nobody finds out halfway through.

• Work we cannot inspect: a closed component we would be asked to certify
• A deadline that only holds if nothing goes wrong
• A scope priced before it is understood
• Work requiring a clearance or certification
• A build we would not be allowed to hand over

Refusing early costs a conversation. Refusing late costs a project, and it is usually the customer who pays for it.