We build production software using agentic development, and we help teams adopt the workflow that's changing how software gets built. If your organization is ready to stop talking about AI and start shipping with it, we're the ones who push past "known limitations."
Agentic development isn't just a tool we use. It's the entire way we build.
We build production software using agentic development frameworks. Not prototypes, not demos — real applications that deploy, scale, and deliver. The kind of work that used to take months, delivered in weeks.
We work alongside your existing development team to adopt agentic workflows. Not a slide deck about the future — hands-on, embedded, working on your actual codebase until the new way of building becomes second nature.
Keynotes, deep-dive sessions, and hands-on workshops for teams and conferences. Real stories from the field, practical frameworks, and live demonstrations — not theoretical slides from the sidelines.
“With willing hearts and skillful hands, the difficult we do at once; the impossible takes a bit longer.”
— The Seabees
Notes from the frontier of agentic AI development.
A client who hasn't written code in years sent me two feature requests and a plan he'd gotten from Claude. The plan was good, and it was written blind. So instead of writing the ticket myself, I set him up to write it inside the repo, with the process loaded. Here's what happened.
Read more →I gave my agentic development process a rule borrowed from the Ritz-Carlton. Then I went to bed with ten tickets and woke up with twenty. A story about deferred debt, unintended consequences, and why 'later' means something different when an agent is running the show.
Read more →Seven weeks designing a way to run orchestrators in parallel. Three cold reads, each ending with more questions than the last. Then a go-around, and a two-day rebuild of the simple version Claude had been suggesting all along.
Read more →In March I described version 3 of my agentic development framework. Version 6 just shipped. The phases haven't moved; what changed is that every failure the process had became a numbered rule. The progression, version by version, and why each one happened.
Read more →