What happens in
the first two weeks.

The first engagement is called the Diagnostic. It runs two weeks for a fixed fee and ends in two artifacts: a written scope of what should be built, and a fixed price to build it. It is deliberately structured so that taking the scope and building it internally is a legitimate outcome, because for some companies that is the right answer.

Find out what is actually running. Which AI tools are in use, whose account each one sits on, which of them are load-bearing, and what breaks first if one stops. Most founders can name one tool and the real answer is longer, with some of it on personal accounts the company does not control.

Pick one process and count the systems it touches. That count drives the price almost linearly, which is why nothing is quoted before it exists. Name the owner for after handover. Put a rough number on what a month without the system costs, because a build with no cost of delay attached loses to every urgent thing.

A written scope you own, a fixed fee for the build, and a plain answer about whether to build it internally instead. No deck. No retainer starts automatically.

The Diagnostic is a fixed fee agreed before it begins, and details are on the Diagnostic page. It starts with a thirty-minute call where you bring one messy process and the list of systems it touches.