A firm that sells systems should run on its own
Common Ground is five people acting as the operating team for a small group of ventures: capital, brand, technology, development and construction. None of us came from a software company, and none of the systems in this room started as a product idea. Each one started as a specific thing one of us was stuck on inside a real engagement, with a deadline attached and no vendor that fit the shape of the actual problem.
A public bid sweep started because reading a dozen government portals by hand every morning is not a job a person should have to do twice. A voice-replication engine started because every draft that went out under a partner's name needed to sound like that partner, not like an assistant being careful. A claims register started because the same number was getting told three different ways on three different pages, and nobody could say which one was right. A CRM migration started because the tool we picked in a hurry turned out to answer the wrong question. A data room pattern started because building one from scratch for every new relationship does not scale past the second one. Sales agents started because most of what is sold as AI sales tooling is a script wearing a chatbot skin, and we did not want to sell that to anyone, including ourselves. An operating system for our own sessions started because the cost of running the firm on AI tools is paid on every turn, whether anyone is watching it or not.
How we came at this one
The question asked first, on every system in this room, was the same: does this get used inside the firm before it gets offered to anyone else. That question fit because a system nobody here depends on is a demo, not infrastructure, and a demo teaches you nothing about where it actually breaks.
Eight systems, one discipline
What ties the eight together is not the subject matter, which ranges from public procurement to database migration to session architecture. It is the discipline of building the thing you need and then living inside it long enough to find out where it is wrong. Several of these systems have already been rebuilt once, in the open, because the first version did not hold up against real use. That is the point of building for yourself first: the rebuild happens on your own time, against your own mistake, before a client ever sees it.