Property 19 of 50

eaxy.ai

The "AI employee" platform — my most ambitious build, and the one that spent months marked broken.

What this property was

Eaxy was conceived as the biggest swing in this entire book: an AI employee for small businesses. Not a chatbot widget — a platform. B2B customers would sign up, get their own tenant subdomain, have infrastructure provisioned for them automatically, and deploy an AI assistant trained for their industry to handle customer conversations.…

Evidence recorded in the manuscript

Confirmed revenue: none that I can verify. Checkout: present, unverified — the recurring refrain, but here it stings more because the build cost was the largest in the book. Leads: some, real, in the database. Downtime: months, in aggregate, across the crash-loop and orphan periods. The gap between engineering completeness and commercial results is wider on Eaxy than on anything else I own, and that gap is the honest headline number.

The lesson recorded after launch

Ambition has a carrying cost, and you pay it whether or not the product earns. Every system you build is a promise to maintain it, and a platform makes hundreds of promises at once. The discipline I took from Eaxy: never build past your maintenance budget, and know your own sales motion before you build a product that requires a different one. AI agents have made building almost free; they have made owning what you build more expensive than ever, because you can now own so much more than you can mind.…

Related property case files