SECTION 04 · SP

§ 04 Systems & Playbooks

Operational
intelligence from
people actually
building.

The only section a reader can use the morning after they finish the issue. Founder Stories asks how it felt. Systems & Playbooks asks how it worked.

Reader question

How is it actually done?

Form

Two to three playbooks per issue. 1,500 – 2,500 words each. Set in sans-serif. Closer in register to an engineering document than a magazine article.

Visual contrast

Diagrams, checklists, step-by-step breakdowns, before-and-after numbers. Visually distinct from Founder Stories.

Non-negotiable

Specific numbers required. “We grew quickly” is not a playbook. “Week-four retention rose from 12% to 38% in seven weeks” is.

Six playbook types — rotated two or three per issue

Type 01

GTM Breakdown

A founder’s specific path from zero to first 100 customers. Channel by channel. Cost per acquisition. What did not work, and why.

Type 02

Fundraising Teardown

An actual seed deck, with the actual investor reactions, annotated. Sanitized versions are not accepted. Founders unwilling to share underlying numbers do not appear.

Type 03

Hiring Playbook

How the first ten people were hired. Including which hires were wrong, the reason they were wrong, and the cost of unwinding them.

Type 04

AI Stack

The real technical stack of a Series A company. Real cost figures. Real latency. Real tradeoffs the team would not write down anywhere else.

Type 05

Growth System

A single growth mechanism, fully dissected. Inputs, leverage points, failure modes, the version that was discarded.

Type 06 · most valuable

Post-mortem

A specific failure, traced to its root. The category in this section that ecosystems normally lose. Doing this honestly is one of the publication’s most defensible commitments.

Non-NegotiablesWhat every playbook must contain.

  • Specific numbers. Every claim grounded in a quantity. Every quantity dated.
  • At least one counter-example. What was tried and did not work, and why.
  • A transferable framework. Not just a story — a structure another founder can use.
  • Source willingness. Founders unwilling to share underlying numbers do not appear. We do not run sanitized versions.

The Same Founder, Two SectionsHow this differs from Founder Stories.

The same founder may appear in both sections of the same issue — the first as the subject of a long emotional portrait, the second as the source of a numerically rigorous teardown of, say, their first 100 customers.

The two pieces are written by different people, with different goals, and read like different genres. The reader registers the difference visually before they read a single word: serif body in one, sans-serif in the other.


If we cannot publish the numbers, we do not publish the piece.