Org Design for Scale-Ups.
Org design is GTM infrastructure. This playbook helps scale-ups move from heroic execution to clear ownership, decision rights, capacity planning, and repeatable operating cadence.
- Strategy is clear. The operating model is not.
- Founder is still the router for every decision.
- Capacity is not tied to revenue or renewal load.
A company can have a strong product, clear market, and real demand — and still stall because the organization isn't designed to execute the strategy. Org design is not HR work. It is commercial infrastructure: it determines how fast the company can sell, onboard, retain, expand, and learn. This playbook turns founder-led execution into a repeatable operating system across leadership cadence, decision rights, RACI, role scorecards, capacity planning, and global/local accountability.
Representative engagement pattern from team builds, regional launches, post-acquisition integrations, and global/local operating models across 1 → 1,500+ headcount environments. Client names, decision-makers, and revenue targets are masked; operating logic and public career anchors are retained.
How an "8 AEs in seats" headcount becomes $7.6M of actual attained capacity.
- 8 AEs · avg quota $1.25M (nominal) $10.0M
- − Ramp dilution (4 new hires at avg 50%) −$2.5M New AEs: 0% Q1 · 50% Q2 · 75% Q3 · 100% Q4 — avg ≈ 50%.
- − Attrition impact (historical 15%, mid-year) −$0.9M Replacement hires don't close in-year.
- − Manager-as-IC tax (1 in 8 at 60% selling) −$0.5M When the CRO / sales lead carries pipeline.
- + Tenured-AE over-attainment uplift +$1.5M 4 tenured AEs at avg 130% historical.
- = Net attained capacity $7.6M
A headcount plan is not a capacity plan. The same "8 AEs in seats" can produce anywhere between $5.5M and $9M of actual revenue depending on ramp, attrition, and the manager-as-IC tax. Capacity planning starts where the org chart ends.
What changes when the company shifts from heroic execution to a designed operating system.
- Founder routes every meaningful decision — pricing, hiring, deal terms, partner intros.
- Pipeline is "what the founder remembers from yesterday's calls."
- Headcount plan = roles the founder thinks the company needs next.
- RACI exists in the founder's head; everyone "owns" the customer.
- Operating cadence = whatever meeting got scheduled.
- Region / category launches stall because the founder is the only sponsor.
- CS is reactive; expansion happens when customers ask.
- Decision-rights matrix in writing. Founder owns 3–5 things; the org owns the rest.
- Pipeline math is wired backwards from the target. Coverage ratios live in the CRM.
- Capacity model ties headcount to attained revenue, not seats. Quota-to-capacity reviewed monthly.
- RACI for sales · CS · AM · product · finance signed off. No "everyone owns it."
- Weekly forecast · monthly capacity · quarterly board cadence. Reason codes review every 30 days.
- Region / category launches have a named GM with a 90-day operating plan + escalation path.
- Customer health scoring + expansion triggers feed plays before the renewal call.
If any of these sound like your meeting last week.
-
We're growing, but every important decision still routes through the founder.
-
We need a first US / regional leader — but we haven't defined what they truly own.
-
Sales, CS, SE, and product all touch the customer — nobody owns the journey end to end.
-
Global wants consistency. Local teams need flexibility. Nobody has defined the rules.
- You're Pre-Series A / Pre-PMF with no operating-system pressure yet.
- You want a single dashboard built, not a redesigned operating motion.
- There is no decision owner who can move on the read inside 30 days.
- You're looking for fractional leadership, not embedded operating design.
- You want a slide deck for fundraising, not an operating decision.
Three operator anchors.
- 01
Operator across 1 → 1,500+
Built and scaled teams from founder-led GTM through 1,500+ headcount across HotelClub.com (founder), Lotame (EVP), Hearts & Science (Executive MD), Verve Group (EVP/GM, $100M+ P&L), and Samba TV (Global Head of Enterprise). Knows the inflection points where org design has to change shape — first US hire, first regional GM, first solutions org, first center-of-excellence.
- 02
Global / local operating model
Designed and run operating models across APAC, EMEA, LATAM, MENA, and US — including the specific question of what's global, what's local, and what's shared. Knows the difference between US enterprise pod design and APAC/EMEA founder-led pods. Survived multiple post-acquisition integrations on both sides.
- 03
RACI as a speed system
RACI is not a spreadsheet exercise — it is a decision-velocity system. Designs decision rights and customer-journey ownership so that ICP definition, pricing exceptions, product escalations, renewal risk, regional launches, and partner approvals all have clear owners. The output is faster decisions, not more meetings.
From heroic execution → repeatable system.
Founder-led hub on the left becomes a scaled operating model on the right: leadership cadence at the top, functional ownership with explicit decision rights and RACI in the middle, and regional / customer pods at the edge — each with capacity tied to revenue, renewal, and implementation load.
When ownership is unclear, speed becomes political.
- Founder as router
- Informal priorities
- Heroic ICs
- Inconsistent customer handoffs
- Regional improvisation
- Slow escalation
- Unclear accountability
- Leadership cadence
- Decision rights
- RACI
- Customer-journey ownership
- Role scorecards
- Regional operating model
- Measurable accountability
Six layers, one operating model.
Org design isn't a single move — it's six interconnected layers. Skip any one and the whole system slows down.
Six layers stacked into one system that the company can actually execute.
Each layer informs the next. Strategy defines what the organization has to be good at. Decision rights define how fast it can move. Role clarity defines what each function owns. Capacity defines how much work the team can absorb. Cadence defines how decisions actually get made. Talent sequence defines what to hire now, later, or not at all.
What the system has to define.
- 01
Strategy-to-org fit
What does the strategy require the organization to be good at?
- 02
Decision rights
Who decides, who recommends, who is consulted, who is informed?
- 03
Role clarity
What does each function own — and where do handoffs begin and end?
- 04
Capacity model
How much work can the team actually absorb at current headcount?
- 05
Operating cadence
Which meetings create decisions, which create accountability, and which should not exist?
- 06
Talent sequence
What roles should be hired now, later, or not at all?
What ships, shaped like this.
Org Design package for a scale-up GTM transition
Complete operating-model package — diagnostic through 90-day transition. Designed for scale-ups moving from founder-led execution to a leadership-led operating system.
- Org diagnostic (current-state friction map)
- Operating-model map
- Decision-rights matrix
- RACI across sales / CS / SE / product / marketing / partnerships
- Role scorecards (first 3 hires + next 3 hires)
- Hiring sequence
- Regional / US operating model
- Customer-journey ownership map
- Capacity model (sales · SE · onboarding · CS · partner load)
- Meeting cadence design
- Leadership dashboard
- Escalation paths
- 90-day transition roadmap
Sample structure only — no client data. Final artifact is shaped to the engagement, the data available, and the decisions the read needs to drive.
Choose the org shape before you hire into it.
- 01
Founder-led pod
Early GTM, first 10–20 customers, high founder involvement.
Why this shape worksRight shape for the first inflection — keeps speed high and learning loops tight. Stops being right around 20-30 customers.
- 02
Functional model
Clear departments, repeatable sales and CS motion.
Why this shape worksRight shape for scale-out — when the motion is repeatable enough that specialization pays.
- 03
Regional GM model
Market localization, US expansion, regional accountability.
Why this shape worksRight shape when local buyer nuance + local partner sequencing + local proof matter more than central consistency.
- 04
Enterprise pod model
Complex multi-product accounts, strategic customers, solutions-heavy sales.
Why this shape worksRight shape when single accounts justify dedicated teams across AE / CSM / SE / product.
- 05
Center-of-excellence
Global standards, enablement, playbooks, shared technical support.
Why this shape worksRight shape when global consistency matters more than local autonomy — usually post-Series-C or post-acquisition.
- 06
Hybrid model
Global consistency with local commercial flexibility.
Why this shape worksRight shape for most US-headquartered AdTech / data companies operating in 3+ regions. Hardest to design well — easiest to get wrong.
Global consistency. Local execution.
US market entry, regional expansion, and global customer coverage fail when companies don't define what's global, what's local, and what's shared. Three lanes — explicit ownership in each.
- 01Global ICP
What global owns
Standards that should not vary by region — positioning, product truth, brand, pricing guardrails, core enablement, reporting model.
Trigger moments- Positioning spine
- Product truth + roadmap
- Brand standards
- Pricing guardrails
- Core enablement
- Reporting + dashboard model
- 02Local ICP
What local owns
Decisions that need market-specific judgment — buyer nuance, partner sequencing, events, account strategy, local proof, market feedback.
Trigger moments- Buyer nuance
- Partner sequencing
- Events / community
- Account strategy
- Local proof
- Market feedback into product
- 03Shared ICP
What is shared
Cross-cutting concerns that need both global standard and local input — ICP refinement, product feedback, strategic accounts, hiring plan, operating cadence.
Trigger moments- ICP refinement
- Product feedback loop
- Strategic accounts
- Renewal risk
- Hiring plan
- Operating cadence
A working RACI looks like this.
Not a spreadsheet exercise — a decision-velocity system. Five sample rows showing how a scale-up codifies ownership across the customer journey. The exact roles vary; the shape does not.
| Decision | R · Responsible | A · Accountable | C · Consulted | I · Informed |
|---|---|---|---|---|
| ICP definition | CRO / CMO | CEO | Product, CS | Sales |
| Pricing exception | Sales | CRO | Finance | CEO |
| Product escalation | CS / SE | Product | Sales | Leadership |
| Renewal risk | CSM | CS Lead | AE, Product | CRO |
| Regional launch | GM | CEO / CRO | Marketing, Product | Board |
Sample structure — actual decisions, owners, and escalation paths are tuned to the company's stage, geography, and product complexity.
0-30-60-90 org transition plan
- 010–30 days · Diagnose the operating model
Map current-state ownership, friction, decision routing, customer-journey handoffs, and capacity baseline.
- Org map
- Friction map
- Decision-rights audit
- Customer-journey handoff map
- Capacity baseline
- Leadership / founder / function interviews
Milestone Clear read on which decisions slow the company, which handoffs leak, and where capacity is under-modeled. - 0231–60 days · Design the system
Build the operating model — decision rights, RACI, role scorecards, hiring sequence, global / local split.
- RACI across sales / CS / SE / product / marketing / partnerships
- Role scorecards
- Operating cadence design
- Hiring sequence (next 3 + next 6)
- Global / local operating model
- Customer-journey ownership map
Milestone Operating model sanctioned by leadership. First-90-day transition plan locked. - 0361–90 days · Operationalize
Install the cadence, escalation paths, and dashboards. Run first leadership review. Validate against live execution.
- Weekly leadership cadence
- Escalation paths
- Leadership dashboard
- Team rituals (1:1s · standups · QBR)
- First leadership review
- First optimization loop
Milestone Operating system live. Founder is no longer routing every decision. Speed measurable.
The failure modes are predictable.
- 01
Founder is still the router
Every decision — pricing exception, hire approval, product escalation, partner sign-off — still goes through the founder. Speed decays as the org grows. The founder becomes the bottleneck.
Fix — Codify decision rights. Move from "founder decides" to "founder is informed" for everything below the strategic line.
- 02
No customer-journey owner
Sales hands to CS, CS hands to SE, SE hands to product. Each handoff loses context. The customer feels it. NRR suffers and nobody owns the leak.
Fix — Assign single-threaded customer-journey ownership. Map RACI across every handoff. Make the journey, not the function, the unit of accountability.
- 03
Capacity is fiction
Headcount plans aren't tied to revenue targets, renewal calendar, onboarding load, or product complexity. New hires arrive into ambiguous capacity assumptions and burn out.
Fix — Build a real capacity model — sales-quota math, onboarding load per CSM, SE coverage ratio, partner-management load — and tie hiring to the math.
- 04
First US hire is asked to do ten jobs
The job description reads "Head of US." The actual scope is sales + marketing + BD + partnerships + recruiting + events + customer success + product feedback — without a system underneath.
Fix — Define the operating model before the headcount plan. The first hire delivers against a designed role, not an ambiguous mandate.
- 05
Meetings without decisions
The leadership team meets weekly. Updates get shared. Calendars fill. But the decisions that the company actually needs — pricing, hiring, segment focus, partner sequencing — happen offline, late, or not at all.
Fix — Redesign the cadence: which meetings create decisions, which create accountability, and which should not exist. Decisions get an explicit owner and timeline.
Org design is GTM infrastructure.
Org design works in concert with the commercial system. MSales orchestrates marketing + sales + CS as one quota-bearing supply chain — but the org has to be designed to execute that orchestration. RACI, decision rights, customer-journey ownership, and capacity planning are the underlying infrastructure that makes MSales actually run.
See the Growth Operating System →Operator vocabulary, defined.
- Decision rights
- Who decides, who recommends, who is consulted, and who is informed — per decision type (ICP definition, pricing exception, product escalation, renewal risk, regional launch, partner approval). The fastest companies make this explicit; the slowest leave it implicit and let it route through the founder.
- RACI
- Responsible · Accountable · Consulted · Informed. A speed system, not a spreadsheet exercise. Done well, RACI removes ambiguity from the customer journey and compresses decision time.
- Role scorecard
- A one-page contract per role — what success looks like in 90 / 180 / 365 days, the metrics that matter, the decisions owned, and the people the role works with. Replaces the generic JD.
- Operating cadence
- The rhythm of meetings, reviews, and rituals that actually create decisions and accountability — not just updates. Designed against the customer journey, not the org chart.
- Center of Excellence
- A team that owns the global standard for a discipline (enablement, solutions, playbooks, technical support) while operating teams localize. Used when the company needs both global consistency and local flexibility.
Same system. Different vertical lens.
When the operating motion is set, the next question is which vertical lens to apply it through.
- Travel Travel tech operator + travel data insider — for vendors unifying portfolios or modernizing the data graph.
- Audio When audio platforms fight for US brand budget, the bottleneck isn't reach — it's the buyer narrative.
- Gaming Game advertising is now a scaled media channel — not a niche buy. Translating that into Americas GTM.
- Native Native + recommendation platforms grow fast — the US enterprise bottleneck is rep productivity and ACV expansion.
- Attention Attention measurement is a category that has to be created — not just sold.
- App Growth App-first DSPs and mobile growth platforms turning existing US demand into a focused, lean commercial engine — not a cold market entry.
- Growth Operating model for aligning marketing, sales, data, and customer feedback into one revenue system for scale-up growth.
Market references last validated: June 7, 2026. Revalidate before pitch use.
Strategy clear, operating model not?
If the company has traction but the operating model is slowing growth, the next step is not another strategy deck. It is a clearer system of ownership, cadence, capacity, and decision rights.