How Backstory AI sequenced a three-step company transformation using the strategy diamond framework | Jason Ambrose

How Backstory AI sequenced a three-step company transformation using the strategy diamond framework | Jason Ambrose19 Jun32 min

Listen on SpotifyAlso works in your browser

7 more apps

<a href="https://www.backstory.ai/">Backstory AI</a> — formerly People AI — is building what CEO & Board Member <a href="https://www.linkedin.com/in/jason-ambrose-0b223/">Jason Ambrose</a> calls the "revenue reasoning layer." Even with full CRM visibility, leaders still go ask a person, that person comes back with an answer, and there are ten more questions about how they got it. That trust gap hasn't been solved by RevTech. In this episode, Ambrose walks through the full reset — from an MCP demo that changed his read on the market, to rebranding out of People AI, to rearchitecting the pricing model.Topics Discussed:<ul><li>The MCP demo that triggered the strategic pivot</li><li>Why the "revenue reasoning layer" sits above automation — and what that means for GTM</li><li>How rebranding out of "People AI" clarified Backstory's market identity</li><li>The mechanics of consumption pricing that avoids in-year budget variance</li><li>The strategy diamond framework for sequencing a company transformation</li><li>The board conversation: beat-and-raise vs. "become the right business"</li></ul>GTM Lessons For B2B Founders:<ul><li> The market signal is in the demo, not the deck: Ambrose's pivot started when he watched Claude autonomously ask twenty follow-up questions of Backstory's software during an early MCP demo — a moment he compared to loading a web page in Mosaic. When he brought it to customers, the reaction repeated. The signal worth chasing isn't market-size data. It's the demo that resets how a buyer thinks about what your product is.</li><li>Position where reasoning replaces interpretation: Red Hat CEO Matt Hicks told Ambrose that across their AI-paired org, automation was most impactful at the individual contributor level — but as seniority increased, reasoning took over. Senior leaders don't need faster dashboards; they need explainable answers that don't trigger ten follow-ups. The automation layer is crowded. The reasoning layer above it is a different conversation.</li><li>Build consumption pricing that survives the budget cycle: "I don't want consumption pricing" almost always means "I can't have in-year variance." Ambrose's approach: year one, contain costs; year two, look at actual consumption patterns and set a committed spend level — or use prepaid blocks. Engineer the model so in-year variance isn't possible.</li><li>The strategy diamond forces you to confront economics first: Ambrose used a five-element framework — arenas, vehicles, differentiation, sequencing, economic model — because it surfaces how each element constrains the others. Example: routing through a hyperscaler means giving margin to that partner, which reshapes field economics and seller comp. Set GTM without working the economic model and you'll ship conflicting commitments.</li><li>Sequence the transformation before anything else ships: Backstory's reset followed a deliberate order: state the strategy clearly enough that every person applies it daily; rebrand (People AI kept getting confused for HR tech); then realign the roadmap. Skip step one and steps two and three become incoherent.</li></ul>// Sponsors: Front Lines — We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership.<a href="http://www.frontlines.io"> www.FrontLines.io</a>The Global Talent Co. — We help tech startups find, vet, hire, pay, and retain amazing marketing talent that costs 50-70% less than the US & Europe.<a href="http://www.globaltalent.co"> www.GlobalTalent.co</a>//Don't Miss: New Podcast Series — How I Hire Senior GTM leader