Glossary

Every term Atomic Scaling has named

The vocabulary of scaling performance instead of headcount — defined once, precisely, so it can be quoted correctly. The six pillars of the 3P3R Method® are People, Prediction, Playbook, Reach, Retention and Revenue.

3P3R Method®People, Prediction, Playbook, Reach, Retention, RevenueMethod

The 3P3R Method® is the six-pillar framework at the centre of Atomic Scaling, created by Ludovic Bodin: three operating pillars — People, Prediction and Playbook — and three growth pillars — Reach, Retention and Revenue.

Problem it names: Scaling advice arrives as disconnected tactics, so teams cannot tell which constraint is actually binding.

3VVision, Vehicle, VelocityOperating model

The 3V Framework — Vision, Vehicle, Velocity — is the Atomic Scaling replacement for the annual plan: a 36-month vision, a 12-week vehicle, and a weekly velocity check.

Atomic ScalingMethod

Atomic Scaling is an operating model for growing revenue without growing headcount, created by Ludovic Bodin and drawn from how the gaming industry built the highest revenue-per-employee businesses in history.

Problem it names: Companies add people to add output, and their economics get worse as they grow.

Atomic Scaling ScoreDiagnostic

The Atomic Scaling Score is a free two-minute diagnostic that rates a company across the six pillars of the 3P3R Method® and names the single constraint holding growth back.

BRAWBig, Relate, Access, WantGrowth

BRAW — Big, Relate, Access, Want — is the Atomic Scaling market test: pursue a market that is Big enough, that you Relate to, that you have Access to, and that you Want to serve.

CPDTMCustomer, Problem, Distribution, Technology, MonetizationGrowth

CPDTM — Customer, Problem, Distribution, Technology, Monetization — is the Atomic Scaling way of writing a startup as five explicit bets, so a pivot becomes a decision about which bet stopped being true.

EPICEmployees, Profit, Impact, CostOperating model

EPIC — Employees, Profit, Impact, Cost — is the Atomic Scaling hiring test: every role must improve all four at once, or it is headcount rather than leverage.

H2H, H2A, A2AHuman-to-Human, Human-to-Agent, Agent-to-AgentAI-native organisation

H2H, H2A and A2A are the three communication layers of an AI-native company as defined by Atomic Scaling: Human-to-Human, Human-to-Agent and Agent-to-Agent — with H2A the managerial craft that replaces prompting.

HAAOHuman-Assisted Autonomous OrganizationAI-native organisation

A Human-Assisted Autonomous Organization (HAAO) is a company in which AI agents are the default operators and humans govern the exceptions — a term coined by Ludovic Bodin of Atomic Scaling to describe the org chart that replaces the human-run company.

Problem it names: Teams bolt AI onto a company designed for humans, and get demos instead of operating leverage.

JTOJudgment, Taste and OverrideAI-native organisation

JTO — Judgment, Taste and Override — is the Atomic Scaling framework naming the three decisions that stay human when AI agents run the work: judgment on ambiguous calls, taste on what is good enough to ship, and override on stopping an agent that is confidently wrong.

Problem it names: Automation quietly removes the human decisions a business actually depends on, and nobody notices until an agent ships something wrong.

OBEOwn, Buy, EarnGrowth

OBE — Own, Buy, Earn — is the Atomic Scaling distribution model: traffic you Own, traffic you Buy, and attention you Earn, each run as a system rather than a campaign.

OPCOne-Person CompanyAI-native organisation

A One-Person Company (OPC) is a business run by a single human on top of a full agent stack. Atomic Scaling treats it as the lower-ceiling alternative to a HAAO, where a small team plus agents removes the complexity ceiling a solo operator hits.

QDSAAQuestion, Delete, Simplify, Accelerate, AutomateOperating model

QDSAA — Question, Delete, Simplify, Accelerate, Automate — is the Atomic Scaling sequence for fixing a process before automating it, so that automation compounds a good system rather than entrenching a bad one.

Revenue per employeeOperating model

Revenue per employee is the metric Atomic Scaling optimises for — total revenue divided by headcount, and the test of whether a company is scaling performance or merely scaling headcount.

Scale performance, not headcountOperating model

Scale performance, not headcount is the operating stance of Atomic Scaling: treat revenue per employee as the number to grow and headcount as a cost of last resort, so that adding capacity does not automatically worsen the economics.

Problem it names: Most companies buy capacity with people, so every increment of growth makes the business less efficient than it was.

TTHGTiny Team, Huge GrowthOperating model

Tiny Team, Huge Growth (TTHG) is the Atomic Scaling operating stance: scale performance and revenue per employee rather than headcount, so growth compounds instead of diluting.

Put it to work

Which pillar is holding your company back?