What we mean by a clear pipe

Every business is a pipe. Attention goes in one end. Money comes out the other. In between there is a run of segments — marketing, sales, delivery, support, billing — and each one either moves the contents along or holds them up.

That's not a metaphor I picked because it sounded good on a landing page. I picked it because it's the only model I've found that explains failure as well as it explains success. When a company is working, the pipe is flowing. When it isn't, one of exactly two things has gone wrong: the pipe is clogged, or the pipe has gone dark.

Everything on this site — the book, the portfolio, this blog — is an attempt to take that seriously enough to build on.

The two laws

Pipes connect. A segment of pipe is useful because it snaps onto another segment. It has a defined inlet and a defined outlet, and it does not care what's upstream or downstream as long as the fitting matches. Build your company that way and growth stops being reinvention and starts being assembly. You add a segment. You swap a segment. You run two in parallel when volume demands it.

Glass reveals. A clear pipe lets anyone look in at any point and see what's actually moving. Not a summary of what moved last quarter. Not a number that a person assembled by hand on a Thursday. The thing itself, in flow, visible to the people who depend on it — including the customer.

Those two laws are simple enough to sound obvious and hard enough that almost nobody runs their company by them.

Why connection is the harder discipline

Most companies are not built out of segments. They're built out of situations. Someone needed a thing done, so a person started doing it, and over time that person accumulated a job that no one else can perform because no one ever defined what goes in or what comes out.

You can spot this immediately. Ask a team what their inputs are and watch what happens. If the answer is a list — "a signed contract, the onboarding form, and the account ID" — you have a segment. If the answer is a story about how work usually arrives, you have a situation.

Situations don't connect. They can't be extended, tested, replaced, or automated, because there's no fitting on either end. A company made of situations grows by adding people who each learn a private version of the process. A company made of segments grows by adding pipe.

The practical test I use: can I describe this part of the business as a function? Inputs, outputs, and a promise about what happens in between. If I can't write that sentence, the segment doesn't exist yet — I just have people being helpful near each other.

Why clarity is the harder sell

Connection is a design problem. Clarity is a nerve problem.

Making your business visible means accepting that people will see it on a bad day. The dashboard that shows a great month also shows the month where onboarding took nineteen days. The audit log that proves your agent made a good call also preserves the one where it didn't. Every company says it wants transparency until transparency has a cost, and then it discovers a sudden enthusiasm for "context."

But opacity has a cost too, and it's larger — it's just deferred and diffuse, so nobody bills you for it directly. Opaque processes can't be debugged, because you can't fix what you can't observe. Opaque metrics can't be trusted, because the only proof is the assertion of the person reporting them. Opaque products lose to transparent ones the moment a customer has a choice, because trust compounds and mystery doesn't.

What can be seen can be trusted, fixed, and scaled. What can't be seen gets replaced by something that can.

Why now

This model has always been right, in the way that "eat well and sleep enough" has always been right. What changed is that it became cheap.

Instrumenting every joint in a business used to be a project. You needed a data team, a warehouse, a quarter, and the political capital to make five departments agree on what a "customer" is. Making a process explicit enough to hand off used to mean writing documentation that went stale before it was read.

Now, an agent can read the process, run the process, and log the process — and the log is the documentation. The cost of making a business legible has fallen through the floor, which means opacity is no longer a constraint you inherit. It's a choice you're making.

That's the bet behind everything here. Not that AI makes companies faster — it does, and that's the least interesting thing about it. The bet is that AI makes companies legible, and legible companies beat opaque ones over any timeframe that matters.

What this blog is

A working log. I'm building four companies on this model — Largo, Richie, OnChainMind, and PLAY.PAUSE.PLAI. — and writing the book that explains it. This is where the parts that don't fit in either one go: the playbooks, the teardowns, the things that broke, and the gauges we ended up adding after they broke.

Published in the open, on the same principle as everything else. If the thesis is that clarity beats opacity, the site had better be able to show its own work.