A Weekend Build, and the Slow Years That Made It Possible
I built working software in a weekend. The speed is the least interesting part — it was borrowed entirely from the slow years before it.
Read →FOLLOW A THREAD
The rules, records, and routines that hold the business together as the tools change.
Oldest first. Follow how the thinking developed.I built working software in a weekend. The speed is the least interesting part — it was borrowed entirely from the slow years before it.
Read →Working software came together in a weekend. The judgment behind it came from years of deals, spreadsheets, and unfinished systems.
Read →Doing it later doesn't just cost time — it costs truth. Why I capture the work in the moment, not after.
Read →Recording a decision in the moment preserves the reasoning that gets lost when the story is reconstructed later.
Read →I let AI run almost everything in my business. The one line I won't move: it never decides the numbers.
Read →Everyone building with AI is standing on shifting ground. The shift that fixed it for me wasn't technical — it was deciding what I refuse to let change.
Read →The buy box, approval gates, and operating record become the stable part. Models and interfaces can change around them.
Read →Salesforce put its CRM inside Claude and told the world its own interface no longer matters. The architecture is right. The piece they left out is the one that compounds.
Read →Edge holds the shared operating record, with Cowork and the apps working through Control.
Read →Underwriting moved into conversation. The app is back as one screen to review the numbers and make the decision.
Read →Build still handles the scope in the app. Wiring the estimator to conversation is in progress.
Read →Blogs and social content now move through Claude Cowork and publishing skills. I still review and approve what goes out.
Read →Specialist bots and a thin Chief of Staff now run on Grok with lane skills and Control MCP emit.
Read →