Updated, 2026-10-03: This Q3 2026 offer closed on 2026-09-30 and is no longer open. The page is kept as a record of what was offered.
Correction, 2026-10-03: An earlier version of this page listed fee ranges, described one company conversation as a paid engagement, said companies had consented to public naming when our records show no such consent, named a company before naming it had been cleared, listed vendor integrations and product rollouts as examples that our records do not support, and said most engagements ran without an NDA. Those statements have been removed.
Six diagnostic engagements were open for Q3 2026. Each was scoped at one of the categories below; the public frame was the same for every slot: paid, time-bounded, ship a written operator-lens report plus a one-day pairing session with Jeremy. No NDA required to start.
If you self-discovered this work in public and have wanted to engage with the practice, this is the door.
The offer
Three things, every engagement:
- A written diagnostic report: operator-lens analysis of the AI tooling at your org, mapped against the eight-stage gate framework that came out of the trucking-DOT regulatory practice. Twenty to forty pages. Delivered as a private PDF, six weeks from kickoff, against a published outline you sign off on.
- A one-day pairing session with Jeremy, scheduled within four weeks of the report. Walk through the report together, run live triage on whatever is hot, and lock the next three concrete moves in writing.
- A short follow-up: one written check-in at the four-week mark confirming the moves stuck, plus an open Slack channel for questions during that window.
No NDA. The report stays private; the framework stays public (the case studies that come from these engagements ship on this blog, anonymized unless you opt in).
The six slots
| # | Track | Cadence | Public examples |
|---|---|---|---|
| 1 | Time-series forecasting | 6 weeks | Past time-series forecasting work with Nixtla |
| 2 | AI agent security + spend guards | 6 weeks | Agent spend-guard research (IRSB, testnet) |
| 3 | AI tooling operations | 6 weeks | Inbound operations conversation, Eight-Stage gate framework deployments |
| 4 | Diagnostic AI migration (DiagnosticPro-arc) | 8 weeks | DiagnosticPro post-mortem case studies, enterprise platform migrations |
| 5 | Open slot: fifth inbound category | 6 weeks | A pending inbound: once it lands, slot 5 becomes the matching category |
| 6 | Reserve slot | as available | For an inbound we have not heard from yet. |
Fees were to be scoped per engagement and are not published here.
What you get that other consultancies do not
- Operator-lens scoping: comes out of twenty years of restaurant + trucking + AI, not a software-engineering background. Most consultancies scope AI tooling as a code problem; the operator-lens scoping scopes it as a people + process + tooling problem in that order.
- Receipts from public: every framework we ship in the diagnostic has been used in a published case study or it is not a framework. The verification posture is the publishing-gates methodology, not invented claims.
- No NDA to start: the engagement begins with a public kickoff conversation. The NDA, if a final report needed confidentiality, was to be a one-page addendum.
- Forty-five minutes, no slide deck: kickoff was a live call with Jeremy and the operator lens, without pre-reads or a positioning deck. The first thing we would ship was the kickoff outline as a public doc you can read or reject.
How to start
This offer closed on 2026-09-30. Replies to it are no longer being taken.
Frequently asked
Why public? Because the diagnostic report is private but the methodology that produced it is not. The diagnostic engagement has to live in the same transparency posture the rest of this practice lives in or it doesn't work.
Why no NDA? Because NDA-first engagements attract engagements that need NDAs to describe themselves. The honest engagements: the ones worth taking: can be scoped without confidentiality up front. If a real confidentiality need surfaces during scoping (for example, a regulatory exposure), the one-page addendum is six paragraphs and takes two days to sign.
Why six slots? Because six is what fits around the briefing cadence without burning the operating lane that produces the case studies. Constraint-driven capacity is the only honest answer to capacity questions.
Why DiagnosticPro-arc slot separate? Because the DiagnosticPro-arc is the bigger engagement. 8 weeks vs 6 weeks, scoped differently. The diagnostic AI migration work is half technical (the post-mortem / migration plan) and half organizational (the people who have to live with the new stack afterward).
Why a fifth inbound slot? Because a pending inbound had not yet landed, and the practice has a habit of accepting inbound without outbound. The slot is reserved against the inbound that has not yet landed but probably will.
Top comments (0)