Two Series B SaaS companies. Similar ARR. Comparable ACV. One has 18-month sales cycles and CAC that keeps climbing.
The other closes in half the time at half the cost per deal.
The gap wasn’t pricing strategy. It wasn’t product differentiation. It was how work, roles, and decisions were structured.
McKinsey surveyed nearly 2,000 organizations and tested 25 attributes for their effect on enterprise-level EBIT. The winner wasn’t technology investment, talent acquisition, or even CEO sponsorship.
It was workflow redesign.
Organizations that fundamentally redesigned how work gets done saw EBIT impact at nearly three times the rate of those that didn’t.
– McKinsey
The CFO sees CAC rising, cycle times stretching, cost per deal climbing. These feel like financial problems with financial solutions. Price differently. Hire more reps. Cut headcount.
But these are lagging indicators. The leading indicators live upstream, in how roles are designed and whether anyone can measure what work actually produces versus just the effort required to produce it.
CFOs recognize that in capital allocation, the question isn’t which asset is largest. It’s where improvement generates the highest marginal return.
The same logic applies to workforce, but most organizations don’t run the analysis.
The Org Design Levers Hiding in Your Line Items
Consider what’s actually driving your fully loaded CAC.
A professional services firm deploys AI to cut proposal generation from 8 hours to 90 minutes. Impressive efficiency gain. But win rates don’t move. We’ve seen this pattern repeatedly.
The problem isn’t speed. Clients want clear answers, not faster 40-page decks. The roles reward volume, not results.
The response to low win rates was more people producing more proposals. Headcount rose and CAC climbed. The CFO cut. Nothing changed that broke the cycle.
The same pattern shows up in gross margin.
Less than half of employees say they know what’s expected of them at work, according to Gallup’s foundational research. Managers continue to describe jobs in terms of effort rather than results.
When people don’t clearly understand the specific outcomes to be achieved and how they’ll be measured, activity becomes their focus (we’re doing things). Activity requires coordination. Coordination requires meetings, handoffs, and check-ins. Each touchpoint adds cost.
Microsoft’s Work Trend Index, based on usage data from millions of Microsoft 365 users, shows employees spend 60% of their time on communication: meetings, email, and chat. For a team of 10 at $100,000 fully loaded, that’s like 6 FTEs spent on coordination and 4 on creation. Unclear role design makes the ratio worse.
That’s how unclear role design bleeds into margin.
If you can’t measure what people produce, you end up measuring whether they showed up.
The Manager Variable That Few Track
Here’s a line item that doesn’t appear in most financial reviews: manager quality variance.
Gallup’s study of 80,000 managers, published in First Break All the Rules, found that the single largest factor in business unit productivity, profitability, and retention wasn’t compensation, company culture, or the work itself.
It was the direct manager. Specifically, whether that manager defined outcomes or prescribed steps.
Managers drive the variance. But most have no framework for creating hyper-clarity around specific outcomes and target results, and no tools to make it easier. If they could fix it themselves, they already would have.
Time-to-productivity varies by manager. Quota attainment varies by manager. Engineering output varies by manager. Yet most organizations track these as aggregate metrics, not manager-specific ones.
If you knew that one manager’s new hires reached full productivity in 60 days while another’s took 120, you’d see exactly where margin was leaking. But that comparison only works if “productive” means the same thing for both.
Effort-based roles don’t give you that. They give you activity metrics: hours logged, tickets touched, meetings attended. You can’t measure manager variance on results that were never defined.
The Diagnostic a CFO Can Run
Trace the financial outcome backward to find the constraint. Start with four questions:
- Can your leaders describe, in one sentence, what each team is accountable for producing? Not doing. Producing.
- Does each person understand what their role must produce to support growth initiatives, or just the activities they’re supposed to complete?
- Where do deals, tickets, or projects get touched by three or more teams before resolution?
- Do you know time-to-productivity by role and by manager, and do you track the variance?
If you can’t answer these, you’re managing symptoms. The cause is upstream.
The Collaboration That’s Missing
Finance brings data and constraints. People operations brings workflow and role design expertise. The problem is they rarely work backward from the same metric.
The collaboration that works is to pick a unit metric that’s underperforming and then work backward together. What workflows drive that metric? What roles execute those workflows?
Are roles focused on outcomes or effort? Do the individuals accountable for the outcomes have specific targets?
When people own a number, they adapt until it moves. When people own a process, they execute until it’s done. Those aren’t the same thing.
The Divergence Ahead
Some CFOs will keep treating unit economics as financial problems. They’ll optimize pricing, scrutinize headcount, and pressure sales leadership while the upstream causes continue compounding.
Others will recognize that CAC, cycle time, and cost per deal are downstream of how work is structured. They’ll bring finance and people operations together around shared metrics. They’ll ask whether roles are designed to produce measurable outcomes or filled by people who are busy with activities that we can’t connect to results.
The difference isn’t financial discipline. It’s whether you’re measuring the right altitude.
Org design shows up in unit economics long before it shows up in the P&L. The CFO who sees it early has a chance to fix it. The one who waits for the lagging indicators is already behind.
Ready to see how role clarity impacts your unit economics? Try PropulsionAI 100% free