Eleven domains. Twelve elements. Twelve gates.

What is published here is the what and the why. The how — the workshops, the tools, the playbooks, and the people trained to install them — is what we deliver. You do not need any of it to use this page. Read the gates, score yourself honestly, and close the ones you can.

Book a free Standard SessionTake the free ScoreGo to the twelve gates

The nine Laws

The supreme law of the framework. Everything below is derived from these, in this order.

Tier 1 — Existence
Law 1 — Clarity Precedes Scale.Before revenue, systems, or people: know who you serve, what you solve, and why you win. Without clarity, everything downstream is wrong. Confusion compounds fragility.
Law 2 — Revenue Proves Relevance.Ideas are not businesses; attention is not revenue; hope is not strategy. If customers don't consistently pay, the market hasn't validated you.
Law 3 — Profit Is the Test of Discipline.Revenue without margin is immaturity disguised as growth. If you can't produce consistent profit, the model is unstable. Protect margin before pursuing expansion.
Law 4 — Cash Is Strategic Power.Profit alone doesn't protect you. Growth without reserves is recklessness. Cash buys stability; stability enables scale.
Tier 2 — Structure
Law 5 — Rhythm Replaces Chaos.Urgency is not an operating system. Mature businesses run on cadence — review, metrics, decision lanes. A reactive week is an immature structure.
Law 6 — Systems Outlast Hustle.Hustle builds revenue; only systems sustain it. If processes live in memory, the business is dependent. Maturity requires documented, transferable structure.
Law 7 — Ownership Is Explicit.Shared responsibility is concealed irresponsibility. Define who owns outcomes, who decides, who is accountable. Ambiguity is immaturity.
Tier 3 — Evolution
Law 8 — The Founder Must Evolve.A business cannot outgrow the maturity of its founder. If the founder is still the primary executor, the company is fragile.
Law 9 — Scale Is Earned.You don't feel ready for scale — you qualify for it: predictable revenue, consistent profit, founder evolution, operational rhythm, defined accountability, cash discipline. Until then, you are still building.

The seven Principles

How to reason when the framework doesn't speak directly to your situation.

The eleven domains

All eleven are measured by the Score. Seven carry the twelve Essential Elements — the load-bearing floor, necessary and sufficient to meet The Standard. Four are Strengthening domains: scored, woven through the others, and built up once the floor is in.

Domain 1ClarityEE1
Domain 2StrategyStrengthening — scored, not gated
Domain 3FinanceEE2 · EE3
Domain 4OperationsEE4 · EE7 · EE12
Domain 5RevenueEE8 · EE9 · EE10
Domain 6FounderEE6
Domain 7LeadershipEE5
Domain 8TechnologyStrengthening — scored, not gated
Domain 9InnovationStrengthening — scored, not gated
Domain 10Risk & ComplianceStrengthening — scored, not gated
Domain 11People & CultureEE11

The twelve Essential Elements and their gates

In build order. Each gate is quoted from the element's own document; the words are the standard, and drift in the words is drift in the standard.

EE1 · ClarityEE2 · Financial VisibilityEE3 · Profit DisciplineEE4 · Operating CadenceEE5 · Role Clarity & AccountabilityEE6 · Founder Dependency ReductionEE7 · Core Process DocumentationEE8 · Marketing SystemEE9 · Sales SystemEE10 · Customer Retention SystemEE11 · People & Culture FoundationEE12 · Delivery & Quality
EE1

Clarity

Domain · Clarity
Named system: Six Clarity Workshops™
The gate — as written

The Clarity essential element is met when both conditions are true — not one. Both:

  • A stranger can read the One-Page Business Definition and accurately describe what the business does, who it serves, why someone would choose it, and what working with them looks like — without asking a single clarifying question.
  • Three different people in the business — including people who are not the founder — can give a consistent answer to the question: "What does your business do and who is it for?"
EE2

Financial Visibility

Domain · Finance
Named system: The Financial Standard™
The gate — as written
  • The multi-account banking system is installed and operating for at least 60 days.
  • The allocation schedule has been executed at least four times without exception.
  • The Monthly P&L Review has happened for at least two consecutive months with full leadership-team participation.
  • The founder can confirm the current balance of every account without logging into the bank — because they checked on Monday.
  • The Tax Account has never been touched for any purpose other than paying tax obligations.
EE3

Profit Discipline

Domain · Finance
Named system: The Financial Standard™
The gate — as written
  • The business has a defined profit target.
  • The multi-account system is allocating profit on every allocation cycle.
  • Every active offer has a calculated gross margin that meets or exceeds the minimum standard.
  • No expansion decision in the prior 90 days was made without passing the Expansion Gate.
  • The founder can state current net margin — and whether it is above or below target — without looking anything up.
  • The last condition matters most: the systems enforce discipline, but the founder has to own it.
EE4

Operating Cadence

Domain · Operations
Named system: The Standard Rhythm™
The gate — as written

Operating Cadence is met when:

  • The Daily Heading is running in the format appropriate to the business size.
  • The Leadership Weekly has run for eight consecutive weeks without cancellation — facilitated by a designated leader, not the founder.
  • The Team Weekly has run for eight consecutive weeks — facilitated by a team member, not leadership.
  • The Friday Financial Close is running weekly.
  • The first Quarterly Compass has been completed — with business context presented by leadership, team plans built against calculated realistic capacity, draft plans reviewed by leadership, teams given adjustment time, final plans committed to publicly by each team member, and concern surfacing completed.
  • The Standard Rhythm Calendar is locked for the next 12 months.

The critical signal is the Quarterly Compass capacity calculation. When the team calculates realistic capacity and leadership adjusts priorities based on what is actually achievable, the organization has made the fundamental shift from optimistic broadcasting to honest alignment. Until that conversation happens in planning, it will keep happening in crisis.

EE5

Role Clarity & Accountability

Domain · Leadership
Named system: Accountability Chart · Role Clarity Documents · Decision Rights Matrix
The gate — as written

Role Clarity & Accountability is met when:

  • Every person on the leadership team has a completed, signed Role Clarity Document.
  • The Accountability Chart reflects current reality (function-based, one owner per function, displayed).
  • The Decision Rights Matrix is documented and known by the full team.
  • The Team Working Agreements are co-created, signed, and displayed.
  • The Performance Management Protocol is documented and has been used at least once — demonstrating the business can address underperformance with process, not just instinct.
  • The 1:1 rhythm is running consistently.
  • The founder can identify at least five decisions made in the last month by team members that previously would have come to the founder.

The critical signal is that last condition. When decisions are being made at the right level without the founder, role clarity is working. Until then, the founder is still the decision system — regardless of what any document says.

EE6

Founder Dependency Reduction

Domain · Founder
Named system: Dependency Audit · Transfer Plan · Two-Week Away Protocol
The gate — as written

Founder Dependency Reduction is met when:

  • The Founder Dependency Audit is complete across all five categories.
  • The Dependency Transfer Plan is documented with named recipients, transfer mechanisms, timelines, and success definitions for every high-risk dependency.
  • The Founder Time Audit is complete and the target time allocation for the chosen destination OS is defined.
  • At least one high-risk dependency has been successfully transferred and is running without the founder for at least 60 days.
  • The Founder Independence Test has been scheduled — even if not yet completed.
  • The Founder Evolution Tracker shows movement from Stage 1 toward Stage 2.

The critical signal is the successful transfer. Not the plan. Not the intention. Not the delegation the founder keeps overriding. A dependency that has actually transferred — where another person owns it, runs it, and the founder hasn't stepped back in for at least 60 days. One transfer. Running. Without the founder. That's the gate.

Gate vs. the two-week test (don't conflate them). The EE6 gate requires the Two-Week Away Protocol to be scheduled, not passed. Passing the two-week test — the business runs fine for two weeks without the founder — is the separate, higher milestone called founder-stable achieved, which is the trigger to move into the destination OS phase. EE6 is "met" at the gate above (one proven 60-day transfer + the machinery installed + the test on the calendar); founder-stable is the deeper threshold reached later. This distinction is deliberate: dependency reduction is an ongoing evolution that continues through every destination path, so the gate certifies the system is installed and demonstrably working rather than requiring full independence at first assessment.

EE7

Core Process Documentation

Domain · Operations
Named system: The SBS Flow System™
The gate — as written

Core Process Documentation is met when:

  • The Process Inventory is complete — every process listed with documentation status and priority.
  • The SBS Business Value Flow Map is complete — showing how value flows at the business-model level and identifying the primary flow constraints.
  • The SBS Process Value Analysis has been applied to every priority process — each designated document as-is, redesign first, or eliminate. Any "redesign first" processes have been improved before documentation began. Any "eliminate" processes have been removed.
  • The three to five highest-priority processes have been documented in SBS format (all eight elements), have passed the Process Transfer Test, and are housed in the Process Library with named owners and maintenance schedules.

Two critical signals:

  • The Transfer Test — not "we wrote it down," but a real person who had never done the process before followed the document and succeeded. Until that test is passed, the process is drafted, not documented.
  • The eliminations — when a business removes at least one process that existed only by habit (consuming time and energy without creating value), the Value Analysis has done its job. If no processes get eliminated, the analysis was probably too gentle. Every business has processes that exist only because they always have; the Value Analysis is what gives permission to ask: does this actually need to exist?
EE8

Marketing System

Domain · Revenue
Named system: The SBS Demand Engine™
The gate — as written

The Marketing System is met when:

  • The Marketing Audit is complete and the current state is documented honestly.
  • The one-page Marketing Strategy is built on the Clarity foundation and defines who, what, where, how often, and how measured.
  • At least one documented marketing channel is producing consistent inbound leads without requiring the founder to personally generate every opportunity.
  • The Content System is running — anchor content published on schedule for at least eight consecutive weeks.
  • The Referral System is active — the referral-ask protocol is in use and at least three referral-partner relationships are established.
  • The Lead Capture System is operational — a primary offer exists, a CRM is configured and used consistently, and a nurture sequence is running.
  • The Marketing Scorecard is in the Leadership Weekly and leads are tracked by source.
  • 30%+ of new leads come from non-founder sources.

Two critical signals:

  • Eight consecutive weeks of consistent content — not a burst of marketing followed by silence, but the same channel at the same frequency, running without the founder doing it all personally. Consistency is the only thing that makes marketing work over time; eight weeks proves the system runs on rhythm rather than on the founder's energy.
  • 30%+ of leads from non-founder sources — the proof that lead generation is becoming a system rather than a founder activity.
EE9

Sales System

Domain · Revenue
Named system: The Standard Sale™
The gate — as written

The Sales System is met when:

  • The Sales Audit is complete — actual conversion rates and cycle lengths; track determined.
  • The Standard Sale is documented across all five moves.
  • The Standard Sale Playbook is complete — all nine sections.
  • At least one non-founder is trained and certified to run The Standard Sale independently.
  • The pipeline is visible in the CRM — every active opportunity staged, with the low force identified on any stall.
  • The Revenue Scorecard (including the no-decision/stall rate) runs in the Leadership Weekly.
  • The Demand-to-Decision handoff is operational (the Demand Engine's qualified interest enters the pipeline).

Three critical signals:

  • Three non-founder closes through the documented Path — proof the system, not the founder, produces the decision.
  • A demonstrated graceful walk-away — the team turned down a bad-fit deal, proving the system is run with integrity, not bent to a number.
  • A stall recovered without a discount — at least one hesitant buyer brought to a confident yes by de-risking (Move 5), not by cutting price. This proves the team can actually kill a stall the way the data says works.
EE10

Customer Retention System

Domain · Revenue
Named system: The Retention System
The gate — as written

The Customer Retention System is met when:

  • The Retention Audit is complete — churn, CLV, concentration, and an NPS baseline established.
  • The Client Health System is operational — every active client scored, with intervention plans on every yellow/red.
  • The Touchpoint System is running — every client has a 90-day calendar with named ownership (not the founder).
  • NPS has been sent at least once, reviewed, and detractors followed up.
  • At least one Quarterly Client Review has been completed for every major client.
  • The Onboarding System is documented and has run at least one new client since installation (founder-optional).
  • The Expansion conversation has been introduced to at least three existing clients.
  • The Referral Integration is connected to the Demand Engine's Referral System.
  • The Client Alignment Assessment has been applied to every active client, and any client with red criteria has been through the alignment conversation.
  • The Retention Dashboard is running in the Monthly Health Check.

Two critical signals:

  • Health-score distribution — 80%+ green, with active intervention plans on every remaining yellow and red. Not "we know our clients are happy" — we measured it, we have the data, and there's a process running for every client who isn't.
  • The business has said no. At least one client relationship released through the documented process (or brought back into alignment through the alignment conversation) — proving the discipline to act on alignment data. A business that cannot say no has no client standards; standards only become real when tested against revenue.
EE11

People & Culture Foundation

Domain · People & Culture
Named system: Culture Definition Workshop™
The gate — as written

The People & Culture Foundation is met when:

  • The System-Culture Alignment Audit is complete — no published value is contradicted by a standing system (each contradiction was resolved by changing the system or the value).
  • The four culture documents exist (Core Values with behavioral descriptions, Culture Commitments, Culture Indicators, Culture Story), drawn from real behavior, and are in active use.
  • The Hiring System is documented (five stages, role + culture scorecards, Motivation-Based Job Ad) and has been used for at least one hire since installation.
  • The Team Onboarding System is documented and has run at least one new hire.
  • The Performance Management cadence (1:1s + quarterly + recognition) is running with at least one person/team.
  • A Team Health baseline has been taken, with an action plan on the lowest dimension.
  • The Compensation Framework exists (base ranges + performance link + profit-sharing decision).
  • The Team Offboarding System is documented — both departure paths, the exit-interview template, and the knowledge-transfer protocol. (Documented only: a business cannot be required to have had a departure. But it can be required to know what it will do.)

The critical signal: values are demonstrably used in real decisions and hiring — including at least one hire made through the full process AND at least one strong candidate declined for culture misalignment. A business that will not decline talented people who don't fit the culture has no culture standard; the standard only becomes real the first time it costs you a capable candidate. (This parallels EE9's walk-away and EE10's client release — the standard is proven by what it's willing to say no to.)

EE12

Delivery & Quality

Domain · Operations
Named system: The Delivery Standard™
The gate — as written

Delivery & Quality is met when:

  • A written Delivery Standard exists for every core offer, with a named owner, traced to the Offer Definition in EE1.
  • The acceptance check runs on every delivery of those offers, performed by someone other than the person who did the work, with defined stop authority.
  • The defect loop is operating — misses captured, categorized, taken to root cause, with process-origin causes visibly routed to the EE7 Bottleneck Loop.
  • The Service Recovery Protocol is written and has been used at least once, with the recovery producing a captured defect.
  • The Delivery Transfer Test has passed — three consecutive agreements between the team's call and the founder's independent call, including at least one fail.
  • The Delivery Dashboard is running in the Monthly Health Check with at least a rolling three-month history.

Two critical signals:

  • Escape rate is measured, and the majority of misses are now caught internally. Not "we have a quality process" — we know what fraction of our failures our customers found for us, and that fraction is falling. A business that cannot state its escape rate has not installed this element regardless of how many documents exist.
  • The check has stopped a delivery. At least once, the acceptance check held work that would otherwise have gone out, and the business absorbed the cost of being late rather than the cost of being wrong. A check that has never stopped anything is not a check; it is a formality. This is the delivery-side equivalent of EE10's "the business has said no" — a standard only becomes real when it is tested against revenue and holds.
Open to read. Marks retained. This page may be read, shared, and used to build and run your own business. Small Business Standard™, The Standard Score™, the element names and the gate language above, and the named systems are marks of Small Business Standard IP, LLC. No one may certify, badge, or represent a business as meeting The Standard except through Small Business Standard IP, LLC and its licensed Standard Architects. The workshops, tools, playbooks, and assessment rubrics that install these elements are not published here and remain the property of Small Business Standard IP, LLC.
Book a free Standard SessionScore your business against itSee our own score