Notes from the workshop.
Field notes on shipping AI products to production, from the people writing the code.
- When not to use an LLMaug 2026
Half of what we scope does not need a model. The test we use: agents only where open-ended probing earns its cost, ordinary code everywhere else.
- A constant beats a vector database, until it doesn’taug 2026
Eight thousand words of playbook fit in a cached prompt. Why we shipped a constant instead of retrieval, and the honest line where that decision flips.
- How we get a trustworthy number out of a bank with no APIaug 2026
Mexican banks offer no Plaid-style sync, so the data arrives as a PDF. Here is how we split that job between a model and ordinary code, and why an import that refuses beats one that is quietly wrong.
- What an AI agent that acts does on WhatsAppjul 2026
A chatbot answers questions. An agent takes the next step for you. Here is what that difference looks like on WhatsApp, and why the channel makes it real.
- Meta Business verification, and why it breaks WhatsApp launchesjul 2026
The fastest way to miss a WhatsApp launch date is to discover Meta Business verification in the last week. Here is what it checks, why it stalls timelines, and how to de-risk it.
- How we price a fixed-scope AI buildjun 2026
Most AI work is sold by the hour and ends without a finished product. We sell a plan and a price, agreed before we start. Here is how fixed scope works, and where it does not.
- Why we ship a working slice in week onejun 2026
The demo is the easy part. In week one we ship a working slice instead, one real path running end to end. Here is why that de-risks the whole build.