Founder-led specialty services company · ~$46M revenue · 190 people
Removing the founder as the bottleneck in a $46M founder-led company
Decision rights and a leadership operating rhythm moved the founder out of daily approvals and released two days a week to growth work.
- Disciplines deployed
- FOUNDATION → LEAD → GROW
- Measurement window
- 9 months
- Measures reported
- 4
Condition 04 of eight
Leadership capability is the bottleneck
The team cannot carry the next stage. Growth is capped at the capacity of the current leadership system.
All eight conditionsPresent reality
Nothing moved without the founder. Approvals queued, the leadership team escalated rather than decided, and the founder had no capacity left for the next growth curve.
Constraint
Escalation was free and deciding was risky: no threshold, standard or evidence existed that let a leader act and be judged on the process rather than the outcome.
Intervention — architecture installed
Decision-rights map by level, standard work for the leadership team, escalation criteria, and a weekly operating rhythm with named owners and evidence.
FOUNDATION → SIMPLIFY → LEAD → GROW
Mapped to the operating system
What was architected inside each discipline, and the measured consequence. Disciplines held out of scope are shown with the reason — nothing is implied by omission.
1. FOUNDATION
Build
Loaded in this engagement
Decision-rights map by level with escalation criteria — escalation given a cost and deciding given a standard.
Result: Approvals routed to the founder fell from ~140 to ~18 a month (−87%).
FOUNDATION →2. SIMPLIFY
Focus
Held out of scope
Not the binding constraint: the work itself was focused. What was unfocused was who could act on it.
Result: Scope stayed on authority and rhythm, which is why the result landed in nine months.
SIMPLIFY →3. LEAD
Execute
Loaded in this engagement
Standard work for the leadership team and a weekly operating rhythm with named owners and evidence.
Result: Leadership commitments closed on the date promised rose from 58% to 91% (+33 pts).
LEAD →4. GROW
Scale
Loaded in this engagement
The founder's released capacity was reassigned to enterprise work — market, capability and the next curve — rather than absorbed back into operations.
Result: Founder operational hours 22 → 6 a week; revenue per employee +16%.
GROW →
ARC™ — the renewal loop around all four
The leadership team revises the decision-rights map itself as thresholds and people change.
ARC™ →Measured result — what moved, and by how much
| Measure | Before | After (9 months) | Change |
|---|---|---|---|
| Approvals routed to the founder | ~140/month | ~18/month | −87% |
| Founder hours per week on operational escalations | 22 | 6 | −16 hrs |
| Leadership commitments closed on the date promised | 58% | 91% | +33 pts |
| Revenue per employee | $242K | $281K | +16% |
Approvals routed to the founder
−87%
Before140After18Standardized against Decisions escalated to one leader — Monthly average over a quarter.
Founder hours per week on operational escalations
−16 hrs
Before22 hrsAfter6 hrsStandardized against Leader hours per week on operational escalation — Calendar-sampled over four consecutive weeks.
Leadership commitments closed on the date promised
+33 pts
Before58%After91%Standardized against Commitments closed on the date promised — From the cadence record; re-dated commitments count as missed.
Revenue per employee
+16%
Before$242KAfter$281KStandardized against Revenue per employee — FTE basis, contractors treated identically.
The founder now works on the enterprise two days a week; the leadership team runs the operating rhythm.
Transfer — what the client now owns
The leadership team owns the decision-rights map and the weekly operating rhythm, and revises both without the founder or Compass.
Compass leaves business architects, not dependency.
Client identities, brands, and locations are withheld under confidentiality. Metrics are client-reported and measured over the window shown; they describe those engagements and are not a projection of results for any other enterprise.
Start with your own present reality
Every engagement above began with an honest read of the architecture already producing the results. Score yours, or schedule a conversation.
Share this
Share on LinkedIn