Backstory Retiered 141 Accounts in Three Days With Claude

Backstory retiered all 141 of its accounts in three to four days, sorting 8 into Tier A and 21 into Tier B, per SaaStr.

VP of Customer Success Haya Kamola ran the same exercise in a previous role with her team plus four others, working a full quarter. This time it took one function, three or four days, and no handoffs between teams.

The setup, described in an August 8 SaaStr piece, was Claude running through Cowork. It connected to Amplitude for usage data, Atlassian/Jira for support history, Backstory's own MCP server, and Slack. No CS platform. No RevOps vendor. No data team.

Account tiering gets sold as an analysis problem, better scoring models, cleaner dashboards. Kamola's numbers point somewhere else. The bottleneck was always scheduling: getting four teams to hand over data and sign off on a method. Direct API access to that data removes the scheduling problem along with the teams.

Backstory built its own MCP server for this. A related report on scanning activity aimed at MCP servers is a reminder the protocol carries exposure most companies haven't priced in yet. SaaStr's piece doesn't say how the connector was secured.

SaaStr also reported CRM, support, and marketing tools getting repriced away from the seat the same week. Tiering tools built as a paid module inside a CS platform now compete with a Claude workflow that costs whatever the API calls cost. Watch whether Backstory or anyone citing this result starts asking their CS vendor for usage-based pricing instead.