Operating Principles

These exist to make decisions faster and to catch known failure patterns.

1. Infrastructure follows revenue#

Do not build, buy, or register anything before there is something to put in it.

The test before any setup action: what revenue decision does this enable? If the answer is "it will look more professional," it is deferred.

Known failure pattern: buying domains, registering entities, creating accounts, and adding pages feels like progress because it produces artifacts. It is not progress. It is the comfortable half of the work.

2. Services fund products#

Services revenue is proven. Product revenue is not. Nothing skips this order.

Concretely: no significant product time until services revenue is stable and recurring.

3. Build systems that produce artifacts, not systems that store records#

A proposal generator produces proposals. A component library produces interfaces. A CRM produces a table with one row in it.

If a proposed system manages, tracks, or organises something there is very little of, it is procrastination with a build step.

4. Never publish what cannot be defended on a call#

Every claim on the public site must survive a prospect asking about it live. No invented metrics, no demos for dormant products, no capabilities that have not been delivered at least once.

5. The client owns their code#

Full transfer on final payment, always. This is a commercial position, not just an ethical one — the fear of being locked out of their own product is one of the most common reasons a buyer hesitates, and removing it closes deals.

6. Async is the default, not the fallback#

Recorded walkthroughs, written proposals, and detailed email beat live calls for this operator and, on the evidence so far, for clients too. See ADR-006.

7. One brand#

Do not split into a cheap brand and a premium brand. Every lead that enters through the cheap door arrives anchored to the cheap price. See internal decision record ADR-009.

8. Effort is rarely the bottleneck#

The constraint is almost never hours worked. It is price, channel, and whether the uncomfortable task got done. Before working harder, check which of those three is actually blocked.