When a family of businesses grows business by business, the systems usually fragment business by business. Logix takes the opposite approach: one operating blueprint, duplicated for each business, bound together by a permanent numbering system and a Knowledge Vault for every business and every person — with oversight across the family that is aggregate by design, never a master key.
The problem of scattered businesses
A family of businesses rarely struggles because it owns too many of them. It strains because every business it owns runs differently. One keeps its customer records in one place and its follow-up in somebody's inbox. Another rebuilt the same process from scratch the day it was acquired. A third depends on two experienced people whose knowledge has never been written down anywhere.
Each business works, after a fashion. The family does not. The cost is quiet and cumulative. A new hire learns a local method instead of a shared standard. A departing employee takes working knowledge out the door with them. Leadership asks a simple question — how is follow-up doing across the group? — and receives five different answers in five different formats, none of them comparable. Growth multiplies the fragmentation instead of the discipline.
Logix starts from a different premise: a family of businesses should run on one blueprint, set once at the top and repeated with intent — not improvised again inside every business.
The blueprint: one system, duplicated per business
At the top of the structure sits the family — the owners. Beneath it, every business operates on the same design. Each one receives a duplicated copy of the same operating blueprint, fitted to that business:
- Its own CRM and pipeline, with its own follow-up discipline. The business's data stays the business's.
- Its own marketing system, which its own people can run — content, campaigns, and lead capture feeding its own pipeline and its own view of results.
- Its own Knowledge Vault and Brain, described below.
- Its own calendar, with an individual calendar for every person inside it, rolling up to the business view.
- Its own phone numbers — outreach worked from rotating pools, alongside an assigned number for each person.
- Its own voice AI agent on its website and its phones, speaking with customers in that business's context, from that business's knowledge.
Duplication copies the system, never the data. A newly added business starts from the proven standard on day one, with empty records of its own — not with another business's customers, history, or knowledge mixed in. That separation is what makes the repetition safe.
Inside each business, the same principle continues one level down. Every person has their own login, their own assigned number, their own calendar, and their own Vault and workspace. The person is a distinct, permissioned part of the system — not a shared password and a shared inbox.
The spine, part one: the numbering system
What binds the businesses and everyone in them into one coherent structure is the numbering system. Every business, every person, every project, and every deliverable carries a permanent registry number. Projects are numbered in a standard format; people sit under their business's number as sub-numbers; deliverables carry suffixes that identify what they are — a website, a proposal, a report. Related families of assets, from landing-page masters to automations to Brains, each have their own numbered series.
Three rules make this more than labelling:
- Numbers are never reused. A retired number becomes an alias, not a vacancy for someone else.
- The number is the identity. Conversations, records, and oversight refer to the number, so owners, businesses, and people can connect without mixing data.
- The number outlasts the person. When someone leaves or a business changes hands, the registry still says what everything is and where it belongs.
It is unglamorous infrastructure, and it is the main idea. Without it, a duplicated system drifts into a row of lookalikes. With it, the family stays legible at any size.
The spine, part two: the Knowledge Vault
The second binding element is the Knowledge Vault. Every business has a Vault. Every person has a Vault. Inside each Vault sits its Brain — the trained knowledge that the business's, or the person's, AI works from.
Knowledge is versioned, owned, and permissioned: a business can see who holds what, what changed, and which version an answer came from. This is how continuity is built rather than hoped for. The way a business qualifies a lead, answers a recurring question, or handles a sensitive conversation is written down once, held in its Vault, and available to the next person who needs it — including the voice agent on its website, which works from that same approved knowledge instead of improvising.
Vaults are private by default. A business's Vault is that business's. A person's Vault is that person's. Sharing is per record and voluntary; there is no automatic pooling of knowledge across the family, and no silent matching of identities across the group.
A day in the system
Consider a clearly fictional illustration. Meridian Holding Group (SAMPLE) is a sample holding company with a sample roofing company, a sample dental group, and a sample logistics firm beneath it. None of these are real clients; they exist only to show the shape of a working day.
Morning begins on calendars. Each person opens their own calendar inside their business's calendar. A new enquiry on the roofing company's website is answered by that company's voice agent, which works from the roofing company's Brain, answers in context, and books onto the right person's calendar — not a generic company diary. Outreach runs from the business's rotating pool of numbers, so volume is spread and managed as a system rather than pushed through one line until it fails.
Each lead that lands becomes a record with an owner, a next action, and a review date — the worked queue, which the companion piece on this blog describes in full. At the top of the family, the owners see the day in aggregate: how many records are fresh, where follow-up is aging, which businesses need attention. They see it without opening a single customer's file, because the boundary is the design, not a promise.
Nothing about the day is heroic. That is the point. The blueprint carries the discipline, the numbers carry the identity, and the Vault carries the knowledge — so an ordinary Tuesday in any business in the family looks like an ordinary Tuesday in all of them.
Start with one business. A pilot puts a single business on the standard — one workspace, one workflow, worked live. See how a pilot runs →