STATION 0.0000 · MANIFESTO

No company should staff the work that isn't its product.

00 · The Manifesto

Engineers stopped writing their own auth. Founders should stop running their own back office.

Every product needs the same plumbing — auth, billing, analytics, comms. You used to write it. Now you import it: Stripe for billing, Clerk for auth, PostHog for analytics. You kept the core logic and offloaded the rest.

The company around the product never got that treatment. Support still meant a hire. Legal still meant a retainer at $500 an hour [est.]. HR, marketing, analytics, tax — each one was a person, a vendor, or a weekend you didn't get back. A 2am support ticket. A Delaware franchise tax filing. A GDPR DPA a prospect asked for on a Tuesday. None of it is your product, and all of it lands on you.

You were never short on the idea. You were short on the company around it.

You were never short on the idea. You were short on a support queue you could trust at 2am, a contract you could redline by Friday, a franchise return filed before March 1. The product is the part a founder can already build alone. The company around it is what still takes [PLACEHOLDER · forty] hires.

The math bent before AI touched it. Instagram reached $1B with 13 people. WhatsApp sold for $19B with 55 — about $345M per employee. The value a company holds per head has been climbing for over a decade. AI is the next order of magnitude on a line that was already drawn.

Instagram reached $1B with 13 people. The constraint was never ambition.

Be precise about where this stands. No one-person company has crossed $100M in revenue yet, and the honest reason is not the product. It is headcount, and the back office is the last place headcount hides. We would rather say that plainly than sell you a milestone that has not happened.

horz is the same move, one level up. You added Stripe without hiring a payments team. You add horz without hiring support, legal, HR, marketing, analytics, or tax. Six functions on one company brain; seven layers, each returning an artifact you read and approve: a resolved ticket in your product's voice, a redlined DPA, a filed Form 1120. You import the back office the way you imported billing — as a dependency you don't maintain.

You import the back office the way you imported billing.

That changes what a small team can hold. Keep the one vertical only you can build. Run the seven horizontal functions off managed layers, and hold that line of headcount flat while the company grows. The nearly-solo company at real scale is no longer a thought experiment. It is an operational question, answered in revenue per employee.

Keep the one vertical only you can build. Import the rest.

STATION 0.0000 · THE ARCHITECTURE

HORZ-ARCHITECTURE

Scale Horizontally. Focus Vertically.

A company is a section. Read it as a cut and two things separate.

The horizontal is breadth: the seven functions every company runs no matter what it sells — customer service, legal, HR, marketing, analytics, the company brain, tax. They are the same at every company. They are not your advantage. horz owns them, stacked as layers 01 through 07.

The vertical is depth: the single core product only you can build. Your USP. The reason a customer chose you over the next tab. horz never touches it. That boundary is the entire trust signal: we run what isn't yours, and nothing else.

The old default was to build both. You wrote the product, hired a department for each horizontal function, and your vertical got whatever attention the back office left over. The new default inverts it. Import the seven horizontal layers; spend all your depth on the one vertical.

This holds at any size. A solo founder and a thousand-person company run the same seven horizontal functions; the difference is only how much headcount each has poured into them. The bigger the company, the bigger the back office it can hand back. Keeping only your core is not a small-company trick — it is what the best companies have shared at every scale.

The layers are not seven tools wired together after the fact. They share one graph — the Company Brain (layer 06), the substrate every layer reads from and writes to. The legal layer redlines a contract that knows your pricing. The support layer answers a ticket that knows your refund policy. The tax layer files a return that knows your payroll. Seven point tools can't read each other; that is the difference between a bundle and a backend.

Scale horizontally, and the company gets wider without getting heavier as horz adds layers beneath you. Focus vertically, and go as deep as you want on the one thing that is yours. That is the architecture. Breadth you depend on, depth you own.

00 · The team, in section

We run lean on purpose. horz is built by a small team, each person deep in one vertical, with the back office offloaded to the product we sell. The team is its own thin stratum in the section. Read it as a rack, not a wall of faces.

  • 01[PLACEHOLDER]Founder · Core systems
  • 02[PLACEHOLDER]Engineering · Layers 01–04
  • 03[PLACEHOLDER]Engineering · Layers 05–07
  • 04[PLACEHOLDER]Company Brain · Retrieval & graph
  • 05[PLACEHOLDER]Counsel in the loop · Layer 02
  • 06[PLACEHOLDER]Tax & compliance review · Layer 07
  • 07[PLACEHOLDER]Design & brand

[PLACEHOLDER] PEOPLE · 07 LAYERS · 1 CORE

07 · The Floor

Build the product. We run the company around it.

07 LAYERS · 1 CORE · 0 BACK-OFFICE HIRES

END OF SECTION · STATION 0.0000