Skip to main content

Role Capacity & Company Capacity

How full is each person's book compared to their target — and therefore where to hire, where to add clients, and where to deploy AI.

Written by Schae Lilley

Where to find them

Sidebar → Planning

Who can see them

Admins and above, or anyone given the Planning grant

Can you change data here?

Almost nothing — the AI log is saved to your browser only

How fresh is it?

Follows the same revenue and roster data as the rest of Signal

What they're for

Two pages, two questions.

Role Capacity answers "do we have the right delivery capacity in the right places?" It compares each role group in each division against their official targets. Below target means there's room for more clients and a hire probably isn't needed. At or above target means hiring or better tooling is justified.

Company Capacity flips the framing to "where should we deploy AI to grow revenue without hiring?" People at or above target are running full books, so efficiency tools there create real headroom. People below target need more clients first, not AI. It also quantifies the Revenue Gap — the monthly revenue unlocked if below-target people simply hit their number.

The two KPIs

Which target applies depends on the role. This is the thing to get right before reading either page:

Roles

Measured on

Account Director, Sr Account Director, Account Manager

MRR — the full book value of the clients they own

Strategist, Sr Strategist

RPE — their allocated share of client revenue

An Account Manager's MRR is much larger than a Strategist's RPE, and that's not a performance difference. They're different measurements. See the Glossary.

What you'll see

Role Capacity

  • Per role group and division — headcount, average KPI, the P75 (the 75th percentile — an internal "what good looks like" benchmark), the official target, % to Target, retention, and the spread of above/at/below.

  • An Individual toggle to switch from group rows to per-person rows.

  • Click any person for the same detail drawer used on Employees, including their month-by-month history.

  • A Non-KPI section at the bottom for everyone outside the five tracked roles.

  • CSV export.

Company Capacity

  • A KPI toggle at the top switching the whole page between the RPE population and the MRR population.

  • Headline cards including Revenue Gap.

  • A division table with headcount, below and at-or-above counts, At/Above %, the gap in dollars, and average KPI. Green At/Above means the team is full — and therefore a prime AI candidate.

  • An RPE Trend chart, one line per division.

  • An AI Influence Log for recording deployments and watching the numbers move afterwards.

  • Capacity Insights — an on-demand AI analysis of where to deploy next.

  • Excel export.

How the classification works

  • At target means within 5% of the official target, either way. Above and below sit outside that band.

  • % to Target colours green from 100%, amber from 85%, red below.

  • At/Above % bars colour green from 60%, amber from 35%, red below.

  • Revenue Gap adds up each below-target person's shortfall, floored at zero.

  • No matched target means the person is unclassified and appears in the Non-KPI section rather than in any group average.

How to use them

  1. Check capacity before approving a hire. Coming from the hiring pipeline, the division link lands here pre-filtered. If % to Target is red with healthy headcount, the team has unused book capacity — push back and route new clients there instead. If it's green and the P75 is far above the average, the top quartile is stretched and the hire is justified.

  2. Find who's dragging a group down. Spot a red division row, switch to the Individual toggle, sort by % to Target ascending, and open each below-target person to see their actual book and history before any coaching conversation.

  3. Decide where the next AI solution ships. On Company Capacity, pick the KPI population, then sort by At/Above % descending. The top rows are teams at full capacity where AI creates headroom without headcount. Use Capacity Insights for a written prioritisation you can interrogate.

  4. Size the "fill the book first" opportunity. The Revenue Gap card and per-division gap column quantify what's unlocked just by getting below-target people to their number. That's a sales and assignment problem, not an AI problem — and the page deliberately frames it that way.

  5. Track whether an AI rollout worked. Log the deployment in the AI Influence Log, which freezes that division's numbers as of that day. Weeks later the card shows the change since deployment, and the trend chart provides the long-arc evidence: a rising line with flat headcount.

Good to know

  • The AI Influence Log is saved to your browser only. It's per-browser and per-machine — your colleague sees their own empty log, and clearing site data erases yours. Don't treat it as an institutional record. Copy anything important elsewhere.

  • Capacity Insights answers aren't saved. The analysis and any follow-up questions exist only while you're on the page and vanish when you navigate away. Copy out anything you want to keep.

  • Headcount won't match your division's real headcount, and that's the most common confusion here. These pages count only the five revenue-carrying roles. Project Managers, Managing Directors, Group Directors, "Director of…" and "Head of…" titles, ops staff, and anyone whose job title didn't match a target all sit in the Non-KPI section at the bottom.

  • Targets come from the People-team sheet via KPI Targets, matched by job title. A title that doesn't match produces an unclassified person. That's the usual reason numbers don't add up.

  • You may hear specific target figures quoted from old documentation — don't trust them. There are legacy fallback numbers in the app that aren't the live targets. Whatever the KPI Targets page shows after a sync is authoritative.

  • Company Capacity has no filter bar but still inherits the app-wide division and department filters. So if you set a filter on another page, it silently applies here. This is the most common reason two people see different numbers on the same page. Clear the filters and compare again.

  • The aggregate "Official Target" is an average. When a role group mixes titles with different targets, you're seeing the mean of them, not a range.

  • VABO counts in an individual's RPE but is excluded from the RPE Trend chart, so trend values aren't directly comparable to individual figures.

  • The trend chart loads late. It waits for a background history load and shows a message telling you to navigate away and back. That's the intended fix, not a workaround.

  • The role list and the thresholds are set in the app, not configurable at runtime.

Common questions

Why doesn't the headcount match my division? Only the five revenue-carrying roles are counted. Everyone else is in the Non-KPI section. See "Good to know".

Where do the targets come from, and how do I change one? The People-team sheet, synced via KPI Targets. Change the sheet, re-run the sync. Nothing here edits targets.

What's the difference between RPE and MRR? See "The two KPIs" above. RPE is a share; MRR is a whole book.

Why doesn't the revenue match our finance system? It's the same underlying data, sliced differently: allocated across assigned leads, divided by the number of selected months, with VABO handled differently between the individual figures and the trend chart. Group numbers are averages of per-person allocations, not raw totals.

What does "at or above target — prime for AI expansion" actually mean? Within 5% of target counts as "at". Those people are running full books, so efficiency tooling there adds capacity without hiring. Below-target people need more clients first.

What is the Revenue Gap? The summed shortfall of every below-target person. It's the monthly revenue unlocked if they all hit target — a client-volume opportunity, not an AI one.

My colleague can't see my AI log entry. It's stored in your browser only. See "Good to know".

The trend chart says data isn't loaded. Navigate away and come back — that triggers the full history load. If it persists across sessions, report it.

Why do the numbers look different from what a teammate sees? Two usual causes: inherited filters from another page, and the RPE/MRR toggle. Check both.

Are the Capacity Insights answers saved? No. Copy out anything you need.

Related

Did this answer your question?