LoadIQ
Demo — synthetic data. Every company, person and number here is invented. Distributions and team shape mirror a real pod so the tool behaves realistically, but no customer appears. Warehouse and Slack signals are switched off, so this also shows what “not measured” looks like.
Account manager view

Load against each person's ceiling

The notch is that person's own ceiling. Past it means over capacity.

Customer view

Are important customers getting the attention they need?

Tiers from your strategic-importance rules. Health is about servicing conditions, not churn.

Health of the top 10% of the book

What they hold vs what they carry

Both in median-account equivalents, so they compare directly. Where the dots separate, counting accounts misleads.

Accounts held Load carried
▾
Customer view

Most important accounts, and their health

Strong Watch Needs attention
Across your whole book
▸
Customer view · service & adoption

Top service-request accounts

Benefit adoption and claim-journey NPS, from the Plum warehouse
▸
Account manager view

Newly assigned accounts

Twelve months of arrivals per person. A burst of new accounts is load that has not settled yet, even when the count looks small.

Account managerLast 12 months 30 d90 d90 d loadMost recent arrivals

Capacity in detail

Click a row for what is driving that load. Ceilings come from job level, ramp, people managed and analyst support.

Account ManagerAcctsActive GWPActive Revenue Take rateInsurerLivesLoadCeiling UsedNext step

▾

Hire, or move work?

Only load sitting in accounts that can actually move counts as redistributable.

▸

Where should new work go?

Room in whole median accounts, with what each person is routed for.

Account managerUsedRoom for Active GWP bandMNCGeography
▸

What should move

▸
Account manager view

Insurer dependency

Share of each book's Active GWP placed with one insurer. A concentrated book means less leverage at renewal, and one insurer's service standards setting the tone for the whole book. Measured by premium, because that is where the dependency bites.

By account manager

By pod

Can a pod absorb more as a unit, even when someone inside it cannot?

▾

Who should own this account?

Describe an account and get a ranked shortlist. Eligible on geography and MNC policy first, then by whether the size fits their usual band, then by who has genuine room — spare capacity alone is not a qualification.

▸

Can the team absorb a batch of new accounts?

Describe what's landing next month. Each account is routed one at a time through the same rules and ceilings as everything else, and the book is re-scored with them included — so the answer accounts for them shifting the scale, not just added on top.

▾

What the answer rests on

Nothing in pod.json is measured — it is all judgement. Each assumption is pushed to both extremes here and the effect measured on the thing you act on: how many people read as over capacity, and whether the hire-or-move verdict flips. Ranked by how much it matters, so the estimates worth chasing are the ones at the top.

What's open in my portfolio?

Answers are computed from the scored book, not generated — so they are reproducible and cannot invent a number. It answers the topics below.

Adjust the model

Ceilings by job level, and how much each factor adds to effort.