Account tiering used to eat quarters whole.
That’s not an exaggeration. Haya Kamola, who leads customer success at Backstory and spent years in sales leadership before that, recently described a project at SaaStr AI Day where her team re-tiered their entire customer base in three days. The same exercise previously required five teams and an entire quarter to complete. Three days versus ninety. That gap isn’t incremental improvement – it’s a structural shift in how go-to-market (GTM) teams can and should operate.
If your revenue team is still treating account tiering as a quarterly ritual that gets squeezed between planning cycles and QBRs, this is worth paying close attention to.
Why Account Tiering Is the Foundation of Everything Else
Get tiering wrong and almost everything downstream breaks. Your Ideal Customer Profile (ICP) becomes theoretical rather than operational. Sales reps waste cycles on accounts that will never expand. Your customer success team spreads too thin across accounts that don’t warrant the coverage, while high-value accounts quietly churn.
The problem has always been data. Tiering requires synthesizing firmographic signals, product usage, support history, expansion potential, and sometimes qualitative context from the account team – all at once, across hundreds or thousands of accounts. Doing that manually means someone has to own it, someone has to QA it, and someone has to fight for alignment across CS, sales, and RevOps. By the time you finish, the data is already stale.
Backstory’s approach – using AI connectors, custom signals, and multiple rounds of iteration – compressed that process dramatically. The key word is iteration. Four rounds of refinement in three days is only possible when the underlying analysis runs in minutes rather than weeks, and that speed changes not just the efficiency of the process but the quality of the output. Teams can actually test assumptions and course-correct instead of committing to a first draft.
What This Means for Pipeline Strategy
Faster, more accurate tiering has direct consequences for sales pipeline health. When you know which accounts genuinely belong in Tier 1, you can concentrate outbound effort, allocate senior reps strategically, and set realistic targets for expansion. You’re not guessing.
This matters more right now because AI is simultaneously changing the cost structure of lead generation. BrandJet AI’s recent acquisition of IGLeads signals that the market for AI-native prospecting tools is consolidating quickly. That means the top of your funnel is about to get noisier – more automation, more volume, more outreach hitting buyers from more directions. In that environment, precision matters more than ever. A well-tiered account list tells you where to focus before the noise hits.
Five9 raised its full-year AI growth outlook to 60% after a strong Q2 in 2026, closing its largest Google Marketplace deal to date – a signal that enterprise buyers are committing serious budget to AI-driven customer engagement infrastructure.
That kind of enterprise momentum reflects a broader reality: the buyers you’re trying to reach are already integrating AI into their own operations, and your GTM motion needs to reflect that. Showing up with a generic pitch to an account that’s mid-transformation doesn’t work. Tiering based on real-time signals – not last quarter’s spreadsheet – is what makes relevance possible at scale.
For teams thinking about Customer Acquisition Cost (CAC), there’s another angle worth considering. If AI can collapse the operational cost of tiering, that’s headcount and time that can be redirected toward higher-leverage activities – account strategy, competitive positioning, deeper discovery conversations. The efficiency gain isn’t just about speed; it’s about where human judgment gets applied.
The Headcount and Alignment Question
Salesforce’s ongoing workforce reductions tied to AI integration are generating significant industry discussion. The pattern is consistent with what’s happening across enterprise software: AI is absorbing tasks that previously required dedicated operations staff. This doesn’t mean revenue teams shrink – it means the composition of those teams changes, and so does the expectation of what each person produces.
For RevOps leaders, this creates a pointed question. If AI can tier your customer base in three days, what is your team’s time worth when it’s not spent on that? Most RevOps functions have a backlog of work they never get to: better sales forecasting, tighter territory design, more rigorous win rate analysis, or actually validating whether your sales qualification framework reflects how deals close in practice.
The teams that will pull ahead aren’t the ones that simply adopt AI tools. They’re the ones that redeploy the time those tools free up into decisions that are genuinely hard to automate – cross-functional alignment, strategic account planning, and building the institutional knowledge that makes tiering signals meaningful in the first place.
How to Actually Run This in Your Organization
If you want to attempt a Backstory-style tiering overhaul, here’s a practical starting point:
- Define your signals first, not last. Before touching any tool, align your CS, sales, and RevOps stakeholders on what a Tier 1 account actually looks like – product usage depth, contract value, expansion potential, strategic fit. Disagreement here will undermine any AI output downstream.
- Build in iteration from the start. Plan for multiple passes, not one definitive run. The first output surfaces assumptions you didn’t know you had. That’s useful, but only if you have time to act on it.
- Treat the output as a living input. A tiered account list that gets updated annually is still the old model. The goal is a system that reflects new signals as they emerge – product adoption changes, support escalations, new contacts entering the account.
- Connect tiering to coverage decisions explicitly. Tiering that doesn’t change how CS and AE capacity gets allocated isn’t really tiering – it’s categorization. Make the operational implications clear and agreed upon before you publish results.
- Track Net Revenue Retention (NRR) by tier over time. This is how you validate whether your tiering logic is actually predicting account health or just reflecting it retrospectively.
You can find a deeper breakdown of tools that support this kind of workflow in the CRM Tools Directory, and if you’re building out your RevOps function from scratch, the CRM Guides section covers team structure and process design in detail.
Backstory didn’t just save time. They changed what tiering could be – something that responds to the business rather than lagging behind it. That’s the standard worth aiming for: three days, not a quarter. And the teams that set that standard now will be the ones with the clearest pipeline priorities when the next planning cycle starts.