Customer Success
/Portfolio Review
Portfolio Review
Portfolio Review continuously aggregates Customer State across a CSM's own book, applies the company's health, risk, renewal, expansion and segmentation logic, and gives the CSM and their manager the same evidence-backed read of which accounts need a decision before their one-to-one starts.
Customer Success
Which of my accounts actually need to come up with my manager?
What changes across the three columns isn't whether the CSM and manager end up looking at the same accounts, it's whether they get there from two separate reads stitched together in the room, a shared score neither of them actually trusts, or the same evidence-backed exceptions both of them are already looking at before the conversation starts.
01 | The Current Way
02 | AI Added On
03 | AI-Native
The CSM opens the one-to-one with their own read
An unchecked personal read
The CSM walks in with whichever accounts feel urgent from memory, notes and the dashboard, a read nobody has checked against anyone else's yet.
Opinion with a number
A ranked list or health score gives the CSM something to open with, but without the company's own risk and renewal logic behind it, it is still their opinion with a number attached.
Same evidence before they meet
Customer State aggregates across the CSM's book beforehand, so the CSM opens holding the accounts carrying a material change or exception.
The manager arrives with a different read
Different read, same book
The manager has formed their own view beforehand from whatever dashboards and renewal reports they had time to check, built from different signals than the CSM used.
One number, two conclusions
The manager can check the same ranked summary the CSM saw, but a shared score does not stop two people reading the same number into two different conclusions.
One state, two vantage points
Manager and CSM both work from the same Customer State and evidence, so if their reads differ, it is a judgement call, not a data gap.
They disagree about which account actually needs attention
Opinion against opinion
The relationship the CSM feels good about and the renewal risk the manager flags have nothing shared to argue from, so the disagreement usually gets shelved rather than resolved.
A score with no reasoning
A bolted-on score can rank the account for either of them, but it does not explain itself, so the disagreement is still two opinions plus an unexplained number.
Evidence settles what it can
The specific change or exception behind the flag is visible to both, so the disagreement narrows to which piece of evidence should carry more weight, not whose gut to trust.
They agree what happens next
Filed in someone's notebook
What gets agreed lives in whoever took notes that day, disconnected from the account's state the next one-to-one will start from.
Transcribed but not attached
An assistant can write up what was said, but a tidy summary still is not an intervention attached to the account and the person who owns it.
Owned, part of the state
The intervention or question they agreed attaches to the account and the person owning it, in the same place next week's one-to-one will start from.
The following week shows whose read was right
Nobody checks back
Whether the CSM's confidence or the manager's concern turned out to be the right call is rarely revisited once the next one-to-one starts.
Scored the same regardless
A bolted-on ranking scores the account the same way next time, whether last week's flagged risk actually turned into a save or a loss.
Outcome sharpens the read
What actually happened to the account feeds back into the risk and prioritisation logic for both of them, and RevOps configures whether that update applies automatically or waits for approval before the next one-to-one.
It reads Customer State across the CSM's portfolio against the company's health, risk, renewal, expansion and segmentation logic, and returns the accounts needing attention with the evidence behind each. It's delivered into the one-to-one with their manager, every read traceable back to what produced it.
More manager capacity for every one-to-one, and stronger retention and expansion outcomes, because the conversation starts from the accounts that actually need a decision.
One system that understands, decides, acts and learns.
Every GTM signal flows through an AI-native operating layer into a system that runs on the surfaces your team already uses.
Explore the GTM System →Churn Drivers
Expansion Signals
Product Usage
Expansion Opportunity
Account Plan
Intervention Priority
QBR Prep
Sales Handover
Save Plays
Upgrade Onboarding
Upgrade Playbook
Upgrade Forecast
The GTM teams that learn fastest will win.
Build yours a system that learns. An advantage competitors cannot buy back: years of success and failure, codified.
Frequently Asked Questions
AI-native GTM Systems didn't exist two years ago - here are the questions everyone wants answered.
Talk to Us→Portfolio Review is not the same as Customer Weekly Review. Portfolio Review is the one-to-one between a CSM and their manager, working through the CSM's book to agree which accounts need attention. Customer Weekly Review is the manager and leadership meeting that looks across the whole team's portfolios and turns a week of evidence into decisions and system learning. One is coaching a book, the other runs the team's operating rhythm.
Portfolio Review never hands the CSM or their manager a bare ranking to interpret alone. Every account it surfaces carries the evidence behind it, drawn from the company's own health, risk, renewal and expansion logic, so both people can see why an account needs attention. Humans still own the actual intervention and resource decision; either of them can challenge or override the read.
The picture reflects Customer State as it stands the moment the one-to-one starts. Health, risk, renewal and expansion logic recalculates against the CSM's book on demand, so an account that changed yesterday shows up as an exception today, not at next month's scheduled review.
Portfolio Review's prioritisation does improve, because the outcomes of what was agreed in the one-to-one feed back into it. When an account the CSM felt confident about churns anyway, or one the manager flagged as at risk turns out fine, that result adjusts the health and risk logic behind the next one-to-one, and RevOps configures whether that change applies automatically or waits for their approval before it applies portfolio-wide.
AI improves customer portfolio reviews by giving the CSM and their manager the same evidence-backed read of the book before they sit down together, instead of two separate opinions stitched together in the room. CS teams stop spending the one-to-one comparing dashboards and start with the accounts that actually need a decision, evidenced against the company's own health, risk, renewal and expansion logic.
AI prioritises customer accounts by aggregating Customer State across the CSM's book and ranking exceptions against the company's own health, risk, renewal and expansion logic. Portfolio Review surfaces the accounts needing attention alongside the evidence and the specific intervention or question required, so the CSM and manager start their one-to-one already looking at the same short list.