# Category narrative and point of view > Build a category narrative sales can actually use: the old world and new world structure, the enemy, the proof stack, and where the narrative gets deployed. Source: https://saas-marketing.net/playbooks/category-narrative-and-point-of-view/ Topic: SaaS Branding Type: playbook Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/playbooks/category-narrative-and-point-of-view/ ## Short answer A category narrative is a five beat story a company tells about a shift in the world, who loses because of it, what new capability that shift demands, why the incumbent category cannot deliver it, and what the new category is called. It works as a sales asset before it works as a brand asset, so it should be written to be spoken aloud in a first sales call rather than read on a homepage. ## Key takeaways - A category narrative is a sales asset first: if a rep cannot say it in ninety seconds, it is not finished. - Name a practice as the enemy, not a competitor, because a practice creates urgency without picking a fight. - The shift must come from customer interviews and third party data, not from a whiteboard session with the founders. - If every competitor could sign your narrative without objecting, you have written a trend report instead of a point of view. - Review the narrative every six months and rewrite it whenever the underlying shift stops being news. --- Most category narratives get written as brand documents and then quietly ignored by the people who would benefit most from them. That's backwards. The test of a narrative isn't whether it reads well on an about page. It's whether an AE two quarters into the job can deliver it on a first call without slides and get a prospect to say "that's exactly our problem." Write it for the mouth, not the page. Everything else follows. ## Why the narrative belongs to sales before it belongs to brand A category narrative earns its keep in the first eight minutes of a discovery call, when a buyer is deciding whether this conversation is about a tool or about a problem they already lose sleep over. Brand deployment comes later. This ordering has a practical consequence. You draft the narrative, then you have three reps use it on live calls for two weeks, then you rewrite it based on where prospects interrupted, nodded or went quiet. Only after that does it touch the homepage. Gong did this well: the revenue intelligence story was audible in their sales calls and their content long before it became the tidy website version. Read your draft aloud, standing, with no slides, to someone who does not work at your company. If you find yourself adding "so basically what I mean is", the sentence you just read is the one to cut. That phrase is a reliable detector of abstraction. ## The five beat structure Every category narrative that works in B2B uses roughly the same skeleton. The beats are not optional and the order isn't decorative. **Beat one: an undeniable shift.** Something in the world changed, and it changed for reasons outside your company's control. Remote work. Product-led buying. The collapse of third party cookies. The shift must be verifiable by someone hostile to you. - **Beat two: the losers of that shift.** Who is now structurally disadvantaged and does not fully realise it yet? This beat creates the emotional stake. Zuora's version was direct: companies built around one-time transactions are competing against companies with recurring relationships, and they will lose. **Beat three: the new capability it demands.** The shift creates a job that did not previously need doing. Not a feature. A capability, described in the customer's language. - **Beat four: the old category's failure.** Explain why the tools people already own cannot deliver that capability. This is where you name the practice you're against. Do it structurally, not snidely. **Beat five: the new name.** Give the capability a label. Revenue intelligence. Experience management. Conversational marketing. A name lets buyers request budget for something, which is the entire commercial function of category work. ## Where the shift comes from, and where it must not come from The shift is the load bearing beat, and it's the one most teams invent. A founder has a strong intuition, it goes on a slide, and eighteen months later nobody can find a buyer who agrees. Source it from two places instead. First, customer interviews: listen for the sentence that begins "we used to be able to..." followed by something that no longer works. Twenty win loss calls will surface the same three tensions. Second, third party data you did not commission, because a narrative anchored to your own marketing survey is worth very little in an analyst briefing. Practical test: can you state the shift as a sentence a journalist could fact check? "Buyers now complete most of the purchase before contacting sales" is checkable. "Buyers demand authenticity" is not. This connects directly to how buyers actually remember you. The [Category entry point](/glossary/category-entry-point/) concept explains why the shift should map to a moment when someone starts looking, and [Mental availability](/glossary/mental-availability/) explains why repeating it consistently matters more than saying it cleverly. ## The enemy question: name a practice, never a competitor Naming a competitor feels brave and is usually a mistake. It hands them awareness, it dates your narrative the day they reposition, and it drags marketing into a fight where the winner is whoever spends more. Naming a practice does the same work with none of the downside. The practice is doing quarterly forecasts on gut feel. Or hiring on instinct. Or running annual planning cycles in a market that moves monthly. Your buyer probably already resents that practice, often because it makes them look bad to their own boss. There's a second advantage. Reps can use a practice-enemy without sounding aggressive. "Most teams are still forecasting off rep opinion" is an observation. "Most teams are still using Clari" is a sales objection you just invited. Your narrative is a trend report, not a point of view, if any of these are true. Every competitor could sign it without objecting. It contains no sentence someone in your market would argue with. It would have been equally true three years ago. You could delete your company name and nothing would change. The word 'AI' is doing the work a real claim should be doing. ## Deployment map: where the narrative actually appears A narrative that lives in one deck is a document. A narrative deployed across five surfaces becomes a position. The versions differ in length, not in content. The careers page is the surface most teams forget, and it's a useful honesty check. If the narrative doesn't make a talented engineer want to work on the problem, it probably doesn't make a buyer want to fund it either. Voice matters across all five surfaces, and inconsistency here is what makes a strong narrative feel hollow. The [SaaS brand voice and tone](/guides/saas-brand-voice-and-tone/) guide covers how to keep the keynote version and the sales version recognisably the same company. ## Three narratives worth studying Gong's revenue intelligence story argued that the most valuable data in a company was sitting unanalysed in sales conversations. The shift was the move to remote selling and recorded calls. The loser was any sales leader coaching on anecdote. The name gave CROs a budget line. Zuora's subscription economy keynote is the cleanest example of beat two ever executed in B2B. Tien Tzuo's version put named public companies on a slide as casualties of a business model change. Uncomfortable, specific, and impossible to sit through neutrally. Qualtrics split the world into operational data and experience data, then argued that companies measured the first and guessed at the second. That framing did something subtle: it made every existing analytics investment look incomplete rather than wrong, which is far easier for a buyer to accept. What all three share is a shift sourced outside the company and an enemy that's a practice. What none of them do is claim to be better than a named rival. ## The narrative worksheet Fill this in as five sentences before you write a single paragraph of prose. If you cannot complete a row with evidence, that beat is not ready. **Narrative worksheet** That last item is the one to take seriously. If you can't name three companies who'd push back, the narrative is safe, and safe narratives don't move budget. ## Review cadence, and knowing when it's dead Put a calendar reminder at six months with three questions. Do new customers still describe the shift as a live problem, or is it now assumed? Has a competitor adopted your category name, and if so is that flattery or dilution? Does the proof stack still contain current data, or are you citing a 2024 report in 2026? A narrative typically has eighteen to twenty four months of useful life before it needs real surgery. The warning sign is prospects agreeing too easily. When the shift becomes consensus, it stops creating urgency, and you need to find the next unresolved tension in the same market. Honest tradeoff: category narrative work is expensive and slow to show returns. Expect six to nine months before analysts and buyers repeat your language, and expect nothing at all in pipeline for the first quarter. Companies under about $5M ARR usually get more from sharper positioning than from a new category. [Category design for SaaS](/guides/category-design-for-saas/) covers the full commitment, and [Brand marketing vs performance marketing](/comparisons/brand-marketing-vs-performance-marketing/) is the budget argument you'll need to win first. Measuring any of this is genuinely hard, but not impossible. [SaaS brand measurement](/guides/saas-brand-measurement/) covers the tracking approaches that survive CFO scrutiny, and [SaaS brand benchmarks](/research/saas-brand-benchmarks/) gives you comparison points. For the wider context of how narrative fits with everything else you're building, start at the [SaaS Branding](/saas-branding/) hub or the [SaaS brand marketing](/guides/saas-brand-marketing/) guide. Next step: write the five sentences, then book three sales calls where a rep delivers the spoken version. Rewrite on Friday based on what happened. That loop, run twice, produces something better than any offsite. ## Frequently asked questions ### What is a category narrative? A category narrative is a structured story explaining a change in the world, who it hurts, what new capability it creates demand for, why existing tools cannot supply that capability, and what the resulting new category is called. It is longer than a tagline and shorter than a manifesto, typically 300 to 600 words in written form and roughly ninety seconds when spoken. ### How is a category narrative different from positioning? Positioning is a comparative claim about a market you already compete in: who you are for and why you beat a specific alternative. A category narrative argues that the market itself should be redrawn. Positioning answers why pick us. Narrative answers why this whole class of problem now deserves budget. Most companies need positioning. Fewer genuinely need a new category. ### Should we name a competitor as the enemy? Usually not. Naming a competitor gives them free awareness, invites a public fight, and dates your narrative the moment they pivot. Naming a practice works better: manual forecasting, gut feel hiring, the annual planning cycle. A practice has no legal team, no PR response, and most of your buyers are already quietly frustrated by it. ### How long should a category narrative be? Write the master version at 400 to 600 words. Then cut a ninety second spoken version for first calls, a three sentence version for the homepage hero, and a single sentence version for the boilerplate. If the ninety second version does not survive being said out loud without slides, rewrite the master rather than the summary. ### What are good examples of category narratives in B2B SaaS? Gong argued that revenue conversations were the largest untapped dataset in a company and built revenue intelligence around that claim. Zuora's subscription economy keynote reframed one-time purchase businesses as structurally disadvantaged. Qualtrics separated experience data from operational data to justify experience management. Each names a shift, a loser and a new capability. ### How often should you update a category narrative? Review every six months and assume a real rewrite every eighteen to twenty four months. The failure mode is a narrative built on a shift that has fully arrived. Once your claimed change is obvious to everyone in the room, it stops creating urgency and becomes background. That is the signal to find the next unresolved tension. ### Who owns the category narrative internally? Product marketing writes it, the CEO owns it, and sales validates it. If the CEO cannot deliver it from memory on a podcast, it will not survive contact with the market. If a mid-tier AE cannot use it in a discovery call, it is too abstract. Both tests must pass before anything goes on the website.