For those following. We were delayed 4 hours because @united had rodents running around the plane. As an "im sorry" for all the folks on the plane having their day ruined, they gave us salami snack packs free of charge. Oh also.. the fire alarm is going off on the plane for the last hour but there is "no fire".

Everyone's focused on AI writing code faster. The bigger unlock is WHERE the code gets written. What happened on this call is a preview: the sales conversation itself becomes the spec, and the build happens inside the deal cycle instead of after it. The economics here are wild if you think it through. Traditional SaaS: prospect asks for a feature, it goes on a roadmap, maybe built in 2 quarters, deal stalls or dies waiting. Customization is a cost center, so vendors say no by default. AI-native platform: the feature gets built during the call. Customization becomes a sales leverage point with near-zero marginal cost. The vendor says yes by default. Closed monoliths win by being 80% right for everyone. Open, AI-native platforms win by being 100% right for each customer and proving it before the contract is signed. "Time to value" used to be measured from onboarding. Now it starts in the middle of the pitch.

We are so excited to have Connor Kuehnle joining @DaltonMillsAI as Head of Product this week. I want to explain why this matters, because it says something about the kind of company we’re building, and who we’re building it with. Connor spent 9 years at Housecall Pro, then led Product for Construction & Field Service at Intuit. Over a decade inside trades software, at two of the companies that defined the category. He knows what the trades love, what they tolerate, and what they stopped asking for out of frustration. But what we’re most excited about is how Connor works, because it’s exactly how we work. Connor is an engineer who became a product leader, and on his first day he was on customer calls in the morning and building features on our platform in the afternoon. Most software companies don’t work that way. They still run the old model: product teams who write, engineers who build, customers who wait. That model is a relic. We believe the companies that win in this AI era will be the ones where the people closest to the customer can build, and the people who build are closest to the customer. The trades deserve a product leader who has lived their problems and can build the answers with his own hands. Now they have one. Welcome, Connor. It’s time to let the builders build!

Mythos / Fable is unbelievable. Was on a customer call today and had Claude transcribing in the background. As they were telling me about the features they wish their current software had, Claude was building the features in real time. By the end of the call I was able to show a fully working product, with the exact workflow they mentioned 15 minutes earlier. Autonomous looped building triggered from a customer call. 🤯

A landscaper sent me this. He’s building his own software with Claude, because his current software isn’t built for him, it’s built for the masses. The trades are building!

Sad about the Knicks…. BUT. I’m with a friend who has early access to Mythos because he works at a major cyber company. Holy hell it’s a comptroller step function better than Opus and gives you that magical feeling again.

Luke Alvarez is an off-road tour guide, search and rescue volunteer, and the founder of Black Hills Bronco Adventures in South Dakota. Thanks to AI.. he's also the unofficial "CTO" of his entire town. Let me explain. Most days, Luke is driving tourists out to Mount Rushmore, Crazy Horse, and Devils Tower. But when wildfires tore through his rural county (fewer than 2,000 people), he realized that the local first responders needed better software.. so he built it himself. And now his software is saving lives.