Org-Design Diagnostic — 800-person B2B SaaS moving upmarket

This is an 800-person B2B SaaS workforce-management vendor pursuing a deliberate move upmarket into enterprise via a platform play: winning on integrated suite breadth and land-and-expand motion rather than price. The four remaining design points do not yet reinforce that strategy. The org remains a pure functional structure with no product-line or segment P&L, its processes (a 3-week deal desk, function-siloed quarterly planning, a shared support escalation queue) impose latency the enterprise motion cannot absorb, its rewards actively punish the expansion revenue the strategy depends on (CS is paid on gross retention with no expansion credit), and its people bench is half-built (strong enterprise AEs, but mid-market-era PMs and zero enterprise deployment PMs). The headline verdict: strategy is clear, but Structure, Processes, Rewards, and People are all still calibrated to the mid-market business the company is trying to grow out of — the misalignment, especially the reward-strategy contradiction, will stall land-and-expand.

Spans & layers (computed)

• Headcount by layer (top-down): [1, 6, 30, 160, 600] — total 797
• Layers: 5
• Spans of control: layer 0 → 6 · layer 1 → 5 · layer 2 → 5.33 · layer 3 → 3.75 ⚠ compressed
• Average span: 5.02
• Layer 3 (160 people) averages 3.75 direct reports — compressed span (< 4). Managers this thin usually signal an extra layer, title inflation, or micro-management structure tax.

Star Model alignment audit

Strategy

Clearly articulated: move upmarket into enterprise with a platform/integrated-suite play, competing on breadth and land-and-expand, explicitly not on price. This sets the alignment criteria for the other four points — it demands cross-functional deal execution, expansion-oriented incentives, enterprise-grade product and deployment capability, and low-latency decision-making. The strategy is coherent as stated; the audit question is whether the rest of the Star serves it, and it largely does not. Grounded in: Theoretical Grounding and Paradigm Selection · Conceptualization and Operationalization

Structure

Pure functional org (eng ~350, sales ~180, CS ~120, marketing ~60, G&A ~90) rolling to functional EVPs with no product-line or segment P&L. A platform + land-and-expand strategy is inherently cross-cutting (each enterprise account spans sales, CS, product, deployment), yet no one below the CEO owns an enterprise account or segment end-to-end. The computed analytics show 5 layers, average span 5.02, but layer 3 (160 people) runs a COMPRESSED span of 3.75 — the calculator flags this as a likely extra layer, title inflation, or micro-management structure tax, which adds decision latency the enterprise motion cannot afford. No integrating role (segment GM, account P&L owner) exists to counter the functional silos. Grounded in: Multilevel / Nested Data Structure · Dimensionality and Factor Structure

Processes

Quarterly planning is done by function (reinforcing silos rather than coordinating them around accounts). Enterprise deals require a deal desk pulling in product, legal, and finance that averages 3 weeks per approval — this is the one cross-functional process, but its latency is a direct tax on a land-and-expand motion where speed to close and to expand matters. Customer escalations route through a single shared support-owned queue, with no enterprise-tiered path — a mid-market process applied to accounts the strategy says are the priority. Processes are the lateral connective tissue a functional structure needs to serve a cross-functional strategy, and here they add friction rather than integration. Grounded in: Method and Model Selection Appropriateness · Analytic Rigor and Procedure Application

Rewards

The clearest misfit. Sales is on individual quota with accelerators (rewards landing, not necessarily the collaborative multi-function enterprise sell). Engineering is bonused on company EBITDA (diffuse, no line of sight to platform breadth or enterprise delivery). Most damaging: customer success is paid on gross retention ONLY, with explicitly no credit for expansion revenue — yet expansion is the 'expand' half of the land-and-expand strategy the company is betting on. The people best positioned to drive expansion are financially indifferent to it. Rewards contradict the stated strategy at its core. Grounded in: Predictor–Outcome Relationship · Individual Job Performance

People

Half-aligned. Strong senior enterprise AE hiring in the last year directly serves the land motion. But product managers are all mid-market-era hires — a capability gap for a platform/integrated-suite play that requires enterprise product depth — and there are zero enterprise-deployment program managers on staff, which is the exact role that makes enterprise land-and-expand deliver and expand. The talent bench is built for landing enterprise logos but not for deploying, integrating, or growing them. Grounded in: Individual Capabilities (Ability, Personality, Knowledge) · Individual Job Performance

Misalignments

• strategy × rewards: Strategy depends on land-and-expand (expansion revenue), but customer success is compensated on gross retention only with no expansion credit. Predicted symptom: CS optimizes for renewal/defensive behavior, expansion motion stalls, and the 'expand' half of the strategy fails to materialize despite strong AE-driven landing.
• strategy × structure: A platform + enterprise account strategy is cross-cutting, but a pure functional org with no segment/product P&L means no single owner is accountable for an enterprise account or the platform outcome. Predicted symptom: functional EVPs optimize locally, enterprise accounts fall between the seams, and no one is answerable for suite-breadth adoption.
• strategy × processes: Enterprise land-and-expand needs velocity, but the deal desk averages 3 weeks per approval and escalations run through a single undifferentiated support queue. Predicted symptom: slow enterprise cycle times, deals lost to responsiveness, and enterprise customers experiencing mid-market-grade service.
• structure × processes: Functional structure plus function-based quarterly planning provides no lateral integrating mechanism; the deal desk is the only cross-functional process and it is a bottleneck rather than an integrator. Predicted symptom: coordination happens only through slow escalation, compressed layer-3 spans add a structure tax, and cross-functional work backs up.
• strategy × people: Strategy requires enterprise product depth and deployment capability, but PMs are mid-market-era hires and there are no enterprise-deployment program managers. Predicted symptom: enterprise deals are landed by strong AEs but under-delivered, lengthening time-to-value and undercutting the expansion the strategy needs.

Realignment priorities

1. Fix CS rewards first — add expansion-revenue credit to customer success comp — because it is the cheapest, fastest change and directly unblocks the strategy's core 'expand' motion, which no other fix substitutes for.
2. Hire/appoint enterprise-deployment program managers and begin building enterprise product depth, because even with aligned incentives CS and PMs lack the capability to deliver expansion; talent lead times are long so start now.
3. Introduce a cross-functional integrating mechanism (enterprise segment GM or account-team model with shared goals) to counter functional silos, sequenced after rewards so the new integrator has aligned incentives to coordinate around.
4. Redesign the deal-desk process and add an enterprise-tiered escalation path to cut the 3-week latency, done alongside the integrating role so the new owner drives the faster process rather than layering it onto silos.
5. Address the layer-3 compressed span (3.75) as a structural cleanup — de-layer or de-inflate titles — last, since it is a structure-tax efficiency issue rather than a strategy-blocking contradiction.