Three engagements, one investigation.
Executive technical briefings, independent AI and technology advisory, and technical due diligence and systems diagnosis, shallowest to deepest. All three are the same scientific investigation at different depths, the one I run in my own research applied to your technology: go down into it, then come back up with an evidence-based account a team can act on. Start wherever the question is.
Executive technical briefings
What the state of the art actually is, what it does, and what it means for this organization, delivered so an executive team can act on it, not just be impressed by it. An independent read from a scientist with no product to sell you.
Includes board sessions, conference keynotes, and internal-event speaking.
- executive briefings
- board sessions
- conference keynotes
- internal events
A briefing or talk calibrated to the audience, from a closed session with your executive team or board to a conference keynote.
- A live session, in person or remote
- Slides tailored to your organization's situation
- A short written summary of the take-aways
A single session, 45 to 90 minutes, plus prep.
Independent AI and technology advisory
AI strategy, architecture review, and build-vs-buy, judged against how these systems actually behave rather than how they are marketed. Includes whether a proposed direction rests on sound technical assumptions, and how far the tools your teams already use deserve to be trusted, and no further.
Ongoing or fixed-scope. The output is an evidence-based recommendation you can act on, with the reasoning shown.
- AI strategy
- architecture review
- build vs. buy
- technical assumptions
A working relationship on a specific decision or a standing question: a direction, an architecture, or a technology claim the organization is about to act on.
- Working sessions with the relevant people
- A written recommendation with the reasoning shown
- Optional follow-through as decisions land
From a focused two-week engagement to a standing monthly retainer.
Technical due diligence and systems diagnosis
Going all the way into a system, a stack, a pipeline, or a set of technical claims, and returning an evidence-based account of how it actually operates: what it does, where it fails, and why. The object is always a technical reality: a vendor's claims, a proposed architecture, an AI pipeline, an acquired stack, or the production system itself.
Name the object and I'll go in. The account is delivered as a written report, which is what makes the engagement procurement-legible.
- a vendor's claims
- a proposed architecture
- an AI pipeline
- an acquired stack
- the production system
A scoped, independent investigation of a defined technical object, done from the outside by a working scientist with no stake in the answer being reassuring.
- A written report of findings, the deliverable
- Each finding traced: what happens, why, and what decision follows
- A walkthrough of the report with your team
Scoped to the object, commonly two to six weeks.
Priced in the open.
A public rate card pre-qualifies better than a form does. The direct-client rate card is below; channel and partner pricing is arranged separately and is not published here.
Direct-client rate card
Day rates and typical engagement pricing for briefings, advisory, and due diligence and diagnosis engagements. Opens as a PDF in a new tab.
Open the rate card (PDF)Working through a channel partner? Pricing comes through them, get in touch and we'll route it.