AI is pushing startups to pay for scope rather than the size of the team a leader manages. Each hire owns more, so pay and equity for strong AI-fluent operators can rise, while leveling tied to headcount breaks. Platform teams help founders by rebuilding leveling, sizing option pools to real hiring plans and labeling every benchmark's source.
Comp questions reach platform teams more often than almost any other talent question, and lately they've changed shape. A founder used to ask, "What's the range for a VP Engineering at Series A?" Now platform leads tell me the question sounds more like this: "She'd run engineering with four people and a lot of automation. Is she a VP or a senior manager, and what do I pay her?" The old answer doesn't fit the new question.
One thing up front. The platform team doesn't set anyone's pay. The founder and the board do. Your job is to give founders a way to think about it and data with a named source, then get out of the way. The org-chart side of this is in how AI is reshaping startup org structures. This post is about the money.
Why leveling tied to team size breaks
Most startup career ladders borrow from big companies. A manager runs a team. A director runs managers. A VP runs directors. Pay bands follow the ladder, so the fastest way to a bigger offer has always been a bigger org.
That logic falls apart when a head of marketing runs the whole function with two people and a stack of tools. By headcount, the ladder says "manager." By what she owns (the pipeline number, the brand, the budget), she's doing a VP's job.
Founders then make one of two mistakes:
- They underlevel. The offer matches the team size, the candidate takes a better offer elsewhere, or takes this one and leaves in a year.
- They inflate the title. The candidate gets "VP" to close the gap. Two years later the company needs a real VP above her, and now there's a demotion conversation nobody wants.
Neither is about AI. It's an old leveling problem that smaller teams make much more common.
Level by scope instead
Help founders swap the headcount signal for scope signals. Here's a simple rubric a platform team can hand over:
| Dimension | Old signal | Scope signal |
|---|---|---|
| Size of the job | Number of direct reports | Outcomes owned, such as a revenue or retention number |
| Budget | Headcount budget managed | Total budget managed, including tools and vendors |
| Decision rights | Approves hires on their team | Decisions made without the founder's sign-off |
| Reach beyond team | Managers below them | Systems they built that other teams run on |
| External weight | Title on the org chart | Represents the company to customers, investors or press |
Score each dimension at the stage the company is at, then map the total to a level. The company still needs bands per level. It just stops using headcount as the only way in.
An illustrative case. Say a Series A company is hiring a head of growth who'll have two reports and own the full acquisition number. On headcount, that's a manager. On scope, it's the head of a function. So level her as a function head, set base at the band for that level and stage, and grant equity at that level too. Use the title "Head of Growth" rather than "VP" if the founder expects to hire above the role later. The pay reflects the job, and the title leaves room.
Where the money moves
When teams get smaller, the mix changes more than the total. Here's how I'd walk a founder through each piece.
Base salary should stay anchored to the market rate for the level. Don't pay a big base premium for "AI skills" on a résumé. Base is the hardest piece to take back if the hire doesn't work out.
Equity is where scope gets rewarded. If one person is doing a job that used to take a small team, the company can afford to give that person a bigger share of the pool, because the pool isn't being split as many ways. More on that below.
Tools budget isn't comp, but candidates now ask about it. Strong operators want to know they'll have the software they need. Put the tools budget in the offer conversation as part of the job, so it doesn't turn into a negotiation over salary.
Refresh grants matter more. In a small team, a person's scope can double in a year without a new title. Tie refreshes to scope growth, reviewed at least once a year, so the people carrying the most don't fall behind their own job.
Benchmarks lag the change
Most comp data is organized by title and stage. Titles assume the old ladders. So a benchmark for "VP Marketing, Series A" mostly reflects VPs who manage directors, and that can mislead a founder hiring a one-person function head.
Platform teams can handle this without making numbers up:
- Match on scope, not title. Pick the benchmark row that matches what the person will own, and say which row you used.
- Label every range. Source, date and sample size, every time. If a range came from a vendor tool, say so. If it came from three portfolio offers, say that.
- Use your own portfolio, with permission. Anonymized offers from other companies at the same stage are often the most relevant data you have. Ask founders before you share anything.
- Say when you don't know. "The data doesn't cover this shape of role well" is a useful answer. It's better than a confident range that's wrong.
A sample reply to a founder:
For a head of growth at Series A who owns the full acquisition number with two reports, the closest benchmark is the function-head row, not the manager row. Here's the range from our latest data (source, date, sample size). Two portfolio companies hired a similar role in the last year, and both landed near the top of the band on equity and the middle on base. Happy to talk through how you'd structure refreshes.
The basics of building benchmarks you can trust are in what portfolio companies need from VC talent teams.
Founder pay in a leaner company
Founders ask about their own salaries too, usually quietly. It's a board decision, and the partner owns that conversation. Still, the platform team can help in two ways.
First, share anonymized ranges from other founders in the portfolio at the same stage (with their permission). Founders rarely know what peers pay themselves, and many underpay out of guilt.
Second, push back on the idea that a lean company means the founder should earn less. A smaller burn is a reason the company can afford a founder who isn't distracted by rent. A founder worrying about personal finances makes worse calls on everything else.
How should startups pay AI-fluent executives?
Pay for the scope they own, not the size of the team they run. Benchmark against the level of responsibility, then use equity rather than an inflated base to reward the extra scope. And confirm the AI fluency in the interview, with a real workflow, before paying a premium for it.
"AI fluency" is easy to claim and hard to check. Before a founder pays extra for it, the candidate should walk through a workflow they actually rebuilt: what they automated, what broke, what they'd do differently. The post on AI and startup leadership has a scorecard and interview questions for this.
Once it's confirmed, a sensible offer has three parts. Base at the band for the level. Equity at the high end of the level, to reward the extra scope. And a written plan for the first refresh, tied to the outcomes the person owns. That last part tells the candidate the company has thought about how the job will grow, and strong candidates notice.
Do smaller teams mean bigger equity grants for early hires?
They can, but not automatically. A pool spread over fewer hires leaves more per person, so founders have room to grant more. Model the pool against the real hiring plan, keep a reserve for future executives and refresh grants, and don't hand out the whole pool to the first ten people.
A worked example, with made-up numbers. Say a seed founder sized the option pool for 30 hires over the next two years. With a leaner plan, she now expects to reach the same milestones with 15. If the pool stays the same size, the average grant could roughly double. That doesn't mean every grant should double.
Help the founder split the pool into three buckets before making offers:
- Planned hires in the current plan, with a grant range for each level.
- Future executives the company will need after the next round, who'll expect meaningful grants.
- Refreshes for early people whose scope grows.
There's another option worth raising, which is a smaller pool. If the company needs fewer people, the board could set aside less and leave more ownership with founders and existing holders. That's a board conversation, not a platform call. But a platform team that brings the question up early, with the founder's hiring plan in hand, saves everyone an awkward pool top-up later.