Bespoke
When it doesn’t exist yet.
Some problems do not have a product. When the tool you need has not been built, we build it with you — bespoke to your organisation, or white-label under your own name — drawing on the same intelligence and data practice behind everything else Pitot does.
Most problems have a product. Some do not.
The market is well supplied with tools for the ordinary half of the problem.
If a licence would solve it, buy the licence. We will tell you so.
- The workflow crosses systems no single vendor spans
- The data is proprietary, sensitive, or shaped unlike anyone else’s
- The advantage is the difference — standardising it away defeats the point
- The organisation is the client’s client, and the tool must carry their name
Instruments, not applications.
Everything we build reads something, and turns the reading into a decision.
Measurement is where the work begins. Build is where it holds.
A conversation first, always.
- Qualification. One session, no fee. We establish whether the problem is one only a built tool can answer — and say so plainly when it is not. A meaningful share of these conversations end with a recommendation to buy something off the shelf.
- Definition. Two to four weeks. The problem is written down properly: what the tool must read, what it must decide, who it must serve, and what has to be true for it to be judged a success. Priced separately, and yours to keep whether or not we build.
- Build. Delivered in working increments against the definition, not against a Gantt chart. You see something running early and often. Scope moves by agreement, in writing.
- Handover. Documentation, source, and a named route back to us. We do not build systems that hold an organisation hostage to their maker.
Bespoke work is selective — we take on what we can carry at the standard the rest of the practice is held to. When the fit is wrong, the honest answer arrives at the qualification stage rather than three months in.
When the tool you need does not exist yet.
Bespoke and white-label work is selective. Start a conversation, and we will establish whether the problem is one only a built tool can answer.