Three ways to start, one person doing the work.

Which one

It comes down to who owns the technical decisions once I’ve gone, and whether the decision that matters has been made yet.

If it’s settled and all that’s left is the software, that’s Build. If it’s still open, and likely to stay open because the next year keeps throwing up decisions nobody senior is making, that’s Partner. Consult is the narrow one: a single question and an answer you can act on.

Choose wrong and it costs you nothing, because I’ll tell you on the first call which one you’re really in, and nothing’s agreed before then.

• A number you can’t explain, or a decision you can’t size: start with the diagnostic, whichever of the three you end up in.
• You know what needs building: Build.
• You need someone to own the technical decisions: Partner.
• You need a straight answer to one hard technical question: Consult.

Three questions I get asked have a page of their own: whether AI will pay (AI implementation), what a company you’re buying has built (technical due diligence), and who owns the systems you already run (software audit).