How to tell if your business actually needs AI
Most AI projects fail during selection, not execution. A short test for whether the problem in front of you is one a model should be solving.
Insights
Writing on AI product development, engineering and the specific ways projects fail between a working prototype and a working product.
Most AI projects fail during selection, not execution. A short test for whether the problem in front of you is one a model should be solving.
The demo worked on every example you tried. Here is the specific set of things that breaks between there and real users, in the order they usually break.
A practical checklist for the gap between 'runs on my machine' and 'safe to put in front of users' — in priority order.
The instinct is to rewrite. It's usually wrong. A method for assessing what you have and deciding what to actually do with it.
Which parts of the 'proper' architecture you genuinely need on day one, and which are expensive ways to delay finding out whether anyone wants this.
AI coding tools get you to a working prototype remarkably fast. What they consistently leave out, and how to add it back deliberately.
In progress
Outlined and queued. Listed here rather than published as empty pages — these aren't live yet.
You don't need an evals platform to know if a prompt change helped. A fixed test set, a scoring function, and a number — the minimum that actually works.
The rejection reasons that catch first-time submitters every time, and the checklist that would have caught them before Apple did.
No documentation, no handover, no one to ask. A method for making an unfamiliar codebase safe to change before you touch a single line.
Model calls are the line item nobody models until the first invoice. A framework for estimating per-user cost before you launch, not after.
Three real options, three different failure modes. A way to reason about which one fits your team's actual constraints, not its ambitions.
Beyond reading
The writing is general. The engagement isn't.