Yuzu — Transmission Infrastructure Operating Doctrine
A one-page memo for founders, team members, new joiners, VCs, and design partners — a shared operating model that keeps the company aligned on what Yuzu is, why it exists, and how it executes as it scales.
Why this doc: to create clarity and alignment on the operating model — so execution stays coherent as the company scales.
✓Build a proprietary metric (IMTR).
✓Build a proprietary surface (Deal Room).
✓Build a proprietary dataset (Transmission Data Graph).
✓Be above the CRM — not inside it.
Doctrine in 7 lines
1 Position
Yuzu is infrastructure: it runs after the call, where deals decay.
2 Primitive
Insight is useless unless it propagates intact through the account.
3 Object
We ship decision artifacts — not notes, not recaps, not content.
4 System
If it can’t be run weekly, measured, and improved — it’s not a system.
5 Pilot
A pilot proves structural lift. If lift is unclear, we stop.
6 Talent
We hire operators who run loops and own penetration — not theatrics.
7 Capital
Capital scales what already works. It doesn’t create inevitability.
Read it as an operating model: if we follow this, the system compounds.
Deck library
All referenced decks in one place.
Deck
—