The Logix Blog

Notes from the blueprint

How Logix thinks about running a family of businesses: one operating blueprint, a permanent numbering system, a Knowledge Vault for every business and every person — and the daily operating discipline that keeps all of it alive.

Local Models

Your AI Should Live Where Your Business Lives

Adopting AI quietly decides where a business's most private material lives. Custody decides where the model runs, and the sensitive work belongs in the building it belongs to.

Logix · Nov 1, 2026 · 4 min read

Read the piece →
The System

What a Local Model Means When You Own More Than One Business

Local, stripped of jargon: the AI lives on hardware the business controls and the thinking happens there. Across a family of businesses, the standard is shared and each business's data stays in its own walls.

Logix · Nov 1, 2026 · 5 min read

Read the piece →
The Front Door

The Phone Is the Front Door

For most businesses the phone is the front door — and it rings at exactly the moments nobody can answer it. What a front door is supposed to do, and what it takes to make the phone do it.

Logix · Oct 27, 2026 · 5 min read

Read the piece →
The Vault

Every Business Has a Vault

Every business runs on knowledge that lives in people's heads and leaves when they do. A Vault writes it down once — owned, versioned, permissioned — so the business keeps what it knows.

Logix · Oct 27, 2026 · 5 min read

Read the piece →
The Pattern

One System, Many Businesses

Owning a second business shouldn't mean inventing a second way to run one. The sameness ledger: what stays identical across the family, and what is always its own.

Logix · Oct 27, 2026 · 5 min read

Read the piece →
The Pilot

What a Pilot Actually Proves

Not a demo and not a teaser: one business, one workflow, worked live on the standard. What that proves about fit, knowledge, and discipline — and what it honestly doesn't.

Logix · Oct 27, 2026 · 5 min read

Read the piece →
The Marble

The Marble Rule: One System, Every Brand Its Own

One system does not mean one face. The operating system is shared across the family; every business's name, colours, and brand stay entirely its own.

Logix · Oct 27, 2026 · 4 min read

Read the piece →
After Yes

What Happens After the Lead Says Yes

Most pipelines are built for the chase and go quiet at the yes. In a worked system the yes is a stage change, not an exit — the record and its promises carry straight through.

Logix · Oct 27, 2026 · 5 min read

Read the piece →
The Thesis

The Worked Queue: Why Pipeline Software Isn't Pipeline Operations

Software holds the list; operations work it. The discipline that keeps a pipeline alive is an owner, a next action, and a review date on every record.

Logix · Oct 22, 2026 · 4 min read

Read the piece →
The Blueprint

One Blueprint for a Family of Businesses: How the Logix System Holds Together

One operating blueprint, duplicated for each business, bound by a permanent numbering system and a Knowledge Vault for every business and every person — with oversight that is aggregate by design.

Logix · Oct 22, 2026 · 7 min read

Read the piece →

How we publish

Every piece is written from Logix's documented positions — method, not client material. Statistics appear only when checked at a primary source, and are cited in the piece. Planned things are called planned. Illustrations are labeled as samples, never dressed up as clients.

Published by Anton Hocking and Erik Laine.

Anton Hocking, Founder. Anton works out front with clients, mapping how a business actually runs.

Erik Laine, Partner. Erik builds the systems underneath: websites, CRM builds, AI agents, and automations, and he leads engineering and release.

Press and media

Reading is the second step

The first is a look at the workflow itself — where records live, how follow-up happens, and what knowledge is written down.