The sovereign company stack
A practical operating stack in which a small company owns its customer relationships, data, agents, security posture, and critical workflows without recreating every tool from scratch.
These are active questions, not polished predictions. If one overlaps with work you are doing, I would like to hear from you.
Last updated
A practical operating stack in which a small company owns its customer relationships, data, agents, security posture, and critical workflows without recreating every tool from scratch.
For home-service companies, the website, phone, follow-up, calendar, and CRM should behave like one owned system. The interesting question is not how many leads arrive—it is how few qualified jobs leak out.
Security software should move beyond producing longer vulnerability lists. The useful product loop discovers a weakness, proves it safely, proposes a repair, and verifies that the repair worked.
As AI workloads become operationally critical, energy becomes part of the software strategy. I am interested in modular, resilient power systems that make serious compute less dependent on a fragile grid.