News Backstory retiered 141 accounts in 3 days with AI signals, down from a quarter
## The Exercise
Backstory retiered its entire customer base in three to four days. Same project used to take Haya Kamola's team plus four others a full quarter.
The scope: 141 accounts. Define what good customers look like, measure everyone against that definition, produce a tiering framework the exec team can act on. Board request, short turnaround.
Kamola leads customer success at Backstory, a revenue intelligence startup. She presented the workflow at SaaStr AI Day, and the before-and-after is the part worth noting.
## What Changed
The old version: cross-functional data pull across product, BI, finance, and several other teams. Manual collection of TAM, health scores, renewal risk, feature requests, and adoption metrics for every account. Quarter-long exercise.
The new version: four connectors replaced the data pull. Amplitude for usage data. Atlassian and Jira for feature requests. Backstory's own conversation history tool. Slack, because the company runs an internal channel per customer and that is where account strategy and risk get flagged first.
Only manual step: CSV export from Salesforce with account name, health score, renewal date, and ACV.
## The Signals That Mattered
Kamola started by asking account teams to describe what made one or two customers different. Not largest contract, not longest tenured. What they landed on: customers who treated Backstory as core infrastructure, built systems around it, planned five years out with it at the center, and kept finding new use cases.
That definition produced the signals they measured. AI maturity: a five-level framework covering culture, investment, tech stack, talent, and willingness to engage on hard problems. Previously required account teams to categorize by hand. Now runs as a systematic prompt against CRM fields, public company data, and full conversation history. Output is a maturity level per account plus reasoning.
Tech stack mix got the same treatment. Pre-sales scorecards from two years ago were stale. Current picture was sitting in unread conversations.
Deployment velocity: did they land small and expand fast across the stack. Executive visibility: was Backstory data being used by execs to make decisions. White space: TAM within the account and what remained.
## What This Means for Sales Orgs
The Slack connector is the replicable piece. Most account teams run internal channels or threads per customer. That dialogue is usually the earliest read on account health, expansion opportunity, and risk. It almost never makes it into structured systems.
The broader pattern: account tiering and segmentation exercises typically bottleneck on data collection, not analysis. If the signals that matter are conversation history, feature requests, usage patterns, and internal account team dialogue, those are all capturable without asking four teams to pull reports.
Backstory is not disclosing headcount, ARR, or ANZ presence. The company sits in the revenue intelligence category alongside People.ai, Clari, Gong, and 6sense. Kamola's background is sales and sales leadership before moving to customer success.
Worth noting: she ran four iterations to narrow eight signals down to four scoring buckets. One signal was scoring backwards and had to be flipped. The definition came before the data, which is the part that prevents you from scoring accounts against whatever fields happen to be populated in your CRM.