Hey {{first_name}} ,
I was reading a vendor's pricing page last week. Standard practice for me on a Sunday, I keep a list of about a dozen enablement and revenue platforms and I check what changed every few weeks. Their language. Their packaging. What they've started gating that used to be free, what they've started bundling that used to be separate, what new tier they've quietly added in the last quarter.
Something quiet bothered me about this particular page, and it took me about an hour to name it. The word “agentic” appeared on every tier. The actual agentic capabilities, the ones a buyer would care about, the ones the marketing copy was selling, lived only in the top tier.
That gap isn't a quirk of one vendor's pricing strategy. It's a category-wide pattern. And once you see it, you can't unsee it. It's also the single most useful diagnostic a buyer can run on any enablement platform that calls itself agentic. This issue is about that diagnostic.
Sreedhar Peddineni,
CEO, GTM Buddy
You're receiving Revenue Activators because you subscribed.
No longer want these? Unsubscribe here.
THE ACTIVATION
Tier-gated AI is the architectural tell.
Most legacy enablement vendors have responded to the agentic era the same way. They have taken the existing platform, a content management system, a learning management system, an analytics layer and added an AI license that you can purchase, separately, on top. Sometimes that AI license is sold as a tier upgrade. Sometimes it is sold as a separate SKU. Sometimes the existing tiers have been renamed ‘Agentic’ across the board, with the actual agentic capabilities concentrated in the highest-priced one.
The packaging is creative. The architectural reality is not. If a platform's AI requires a separate license, an upgraded tier, or any paywall beyond the base product, the AI was added on top of an existing architecture. It is not native. The pricing page is the place where that architectural fact becomes visible.
This is not a criticism of any vendor's product. Legacy platforms were built before agentic AI was a possibility, they were built when sales enablement meant storing content in a portal and tracking who downloaded it. The AI capabilities being added now are real engineering work and they are not bad products. But they are bolted-on products. The architecture underneath them was designed for a different problem.
“If the AI is a separate license tier, it's bolted on, not native. Native means it comes with the platform.”
That single sentence is the diagnostic. It is also the question every CRO, VP of Enablement, and CFO should be asking before they sign a renewal or commit to a new contract in the next eighteen months. Because the architectural choice being made on that signature between platforms designed for the agentic era from day one and platforms retrofitted onto a legacy core will shape the next decade of how revenue work gets done.
The reason this matters operationally, not just architecturally: bolted-on AI cannot reach where the rep actually works. It can answer a question if the rep tabs out of the deal to ask it. It can score a call after the call is over. What it cannot do is operate inside the workflow at the moment the deal is on the line, because the underlying architecture was never designed to surface anything in-flow. That's why every agentic capability on a legacy platform feels like a feature, not a system. A great feature, often. But not the system the agentic era requires.
Native AI is a different shape. The architecture is built so that AI operates as the substrate, not the layer on top. The capabilities don't require a tier upgrade because there is no version of the platform without them. The buyer doesn't have to evaluate “which AI tier do we need” because the question doesn't structurally exist.
Whether a particular vendor's platform is native or bolted-on isn't something the vendor's marketing copy can tell you. The pricing page tells you. The packaging tells you. The number of separate SKUs and tier names tells you. Those artefacts are public, verifiable, and they cannot be argued with because they're written by the vendor itself.
One Move for This Week: Pick the enablement platform your team currently uses or is currently evaluating. Pull up its public pricing page. Identify which AI capabilities are in the base tier and which require an upgrade. Count the number of times the word ‘Agentic’ appears. Then run Framework 1.3 below on what you find. The output of that diagnostic is the conversation you should be having with your CFO and your VP of Enablement before the next renewal cycle.
THE PROMPT
Framework 1.3: The AI-Native Vendor Diagnostic
From the Revenue Activation Playbook · A diagnostic for any enablement platform claiming to be agentic
What it does:
Takes a vendor's pricing page, marketing materials, or any public-facing product documentation and runs it through a structured architectural test. Outputs a clear read on whether the AI is native to the platform or bolted on top, with the specific evidence that supports the conclusion and the operational implications for the buyer. Pair it with one question to ask the vendor before signing.
Why it matters:
Every enablement vendor now claims to be agentic. The word has lost descriptive power; it now functions mostly as a marketing label. Buyers need a diagnostic that cuts through the labelling and tells them what they're actually about to commit to architecturally, on a contract that's typically multi-year. Framework 1.3 is that diagnostic. It runs in twenty minutes. It produces evidence-backed conclusions. And it works on any vendor, including the one you're already on.
Time required:
20 to 30 minutes per vendor.
What you'll need:
The vendor's public pricing page. Most vendors publish at least tier names and capability matrices, even if exact prices aren't listed.
Any public marketing copy or product documentation that describes the AI features. The vendor's website, their resource centre, their G2 page, all useful inputs.
If you're already a customer: your current contract, which shows which tier you're on and which AI capabilities you actually have access to.
Claude, ChatGPT, Gemini, or CoPilot. Any of them work.
How to use it:
Gather the vendor materials. Pricing page screenshot or URL, plus any marketing pages that describe AI capabilities.
Open your AI tool. Either upload the screenshots or paste the URLs and let the AI fetch them.
Copy and paste the full prompt below. Include your materials in the Inputs section.
Review the AI's architectural classification. Does the evidence cited match what you see on the page?
Look at the gap analysis. Which capabilities are in the base tier? Which require an upgrade? What does the pattern reveal about the architecture?
Take the one question the diagnostic generates and bring it to the vendor in your next conversation. Listen to how they answer it. The quality of the answer is itself diagnostic.
Run it again on a second vendor. Then a third. The pattern across vendors is more revealing than the read on any single one.
Copy-Paste this Prompt
You are a B2B technology architecture analyst specialising in AI-native versus AI-augmented platforms
YOUR TASK
Analyse a vendor's public pricing and product materials and produce an architectural diagnostic.
CONTEXT
In 2026, every enablement and revenue platform vendor claims to be “agentic.” The word has lost descriptive power. A meaningful architectural distinction still exists between platforms that were designed AI-native from inception and platforms that have added AI capabilities on top of a legacy architecture.The AI-native test: if a platform's AI requires a separate license tier or any paywall beyond the base product, the AI was added on top, not designed in. Native means it comes with the platform.
YOUR JOB
Apply this test rigorously to the materials provided, identify the specific evidence in the vendor's own materials, and produce a structured diagnostic for the buyer.
THE STRUCTURE
For the vendor materials I provide, produce:
Architectural classification: Native AI, Bolted-on AI, or Mixed (with reasoning)
The capability map: Which AI capabilities are in the base tier, which require an upgrade, which exist only at the top tier
The pricing pattern: How many tiers, what the tier names suggest about positioning, where the genuinely agentic capabilities live
The architectural inference: What the tier structure reveals about how the platform was built
Operational implications for the buyer: What the architecture means in practice, especially for in-workflow AI behaviour
The one question to ask the vendor before signing: The diagnostic question whose answer will reveal more than any demo
STEP 1: ANALYSE MY MATERIALS
I have attached or pasted the vendor's pricing page and any relevant marketing materials. Read them carefully and extract: The number of pricing tiers and their names- Every AI capability mentioned, with the tier it lives in- The vendor's own language about their AI, do they describe it as “native,” “embedded,” “integrated,” or as a separate licence/upgrade?- Any patterns in how capabilities are bundled across tiersSummarise what you found in 3-4 sentences before proceeding.
STEP 2: APPLY THE AI-NATIVE TEST
Based on the materials, classify the platform: NATIVE AI: All AI capabilities are included in every tier. There is no “with AI” upgrade. The pricing structure assumes AI is the substrate, not a feature.- BOLTED-ON AI: AI capabilities are gated behind tier upgrades, separate licences, or a paywall above the base product. The pricing structure treats AI as a feature to be sold separately.- MIXED: Some AI capabilities are in the base tier; others are gated. Common when a vendor is in transition.State your classification and cite the specific evidence in the materials that supports it.
STEP 3: BUILD THE CAPABILITY MAP
Produce a table or list showing every AI capability the vendor mentions, and for each one: Which tier it lives in- Whether it's included in the base tier or requires an upgrade- What the capability would cost a typical mid-market buyer if they wanted it (in terms of tier movement, not dollars)
STEP 4: INFER THE ARCHITECTURE
Based on the tier structure and capability map, infer what this reveals about how the platform was architected: Was the platform clearly designed AI-native from inception?- Was AI added on top of a pre-existing architecture? If so, what was the legacy architecture (CMS, LMS, analytics, etc.)?- Are there signs the vendor is in transition. e.g., rebranding existing tiers to include the word “agentic” without restructuring the actual gating?
STEP 5: OPERATIONAL IMPLICATIONS
Translate the architectural read into concrete operational implications for a buyer: If we sign at the base tier, which agentic capabilities will our reps actually have?- If we want the full agentic stack, which tier do we need to be on?- What's the cost of finding out at year two of a contract that we need to upgrade? What does the in-workflow experience look like, will AI surface in the rep's existing tools, or will reps need to leave their workflow to interact with it?
STEP 6: THE ONE QUESTION
Based on everything above, produce the single most diagnostic question to ask the vendor in the next conversation. Not five questions. One. The question whose answer reveals whether the vendor will defend the architectural pattern, deflect from it, or honestly explain it.
INPUTS:
Vendor name: [Optional - you can leave this blank if you want a brand-neutral analysis]
Pricing page: [Paste URL, paste text, or upload screenshots]
Marketing materials: [Paste any additional public-facing copy about the AI features]
Current contract (if you're a customer): [Tier you're on, capabilities you have access to]
Specific concern (optional): [Anything you specifically want the diagnostic to focus on - e.g., “We care most about deal coaching capabilities” or “We need to know whether their AI will work inside Salesforce”]
Why this prompt works
Most vendor evaluations are run on the dimensions the vendor's sales team wants the buyer to evaluate on. Demo flow. Feature breadth. Customer logos. Time-to-implementation. Those dimensions are legitimate but they all happen on the vendor's terms. Framework 1.3 runs the evaluation on a dimension the buyer controls and the vendor cannot reshape the architecture revealed by the pricing page.
The other thing the prompt does well: it produces a single diagnostic question, not a list. Most vendor-evaluation tooling generates fifty questions a buyer can supposedly ask. In practice, the buyer asks three, and most of them are demo-flow questions the vendor has heard before. One sharp question, asked seriously, will move the conversation further than a list will.
If you ship this with your team and the diagnostic produces something useful or something a vendor pushes back on, reply to this email. The pattern across vendors is what I most want to learn from this issue.
You're receiving Revenue Activators because you subscribed.
No longer want these? Unsubscribe here.
THE ACTIVATOR
Shana Thuener
Sr. Director, GTM Enablement at Zendesk · San Francisco Bay Area
Third spotlight in the Wednesday Women × GTM Buddy Revenue Activators series
Shana Thuener runs GTM Enablement at Zendesk, one of the largest and most mature enablement environments in B2B SaaS, where she has been driving a structural shift in how enablement is measured at enterprise scale. Her POV on what activation actually requires is one of the cleanest articulations I've seen of why most enablement programs still struggle to defend their ROI.
She has been arguing, for several years now, that enterprise enablement is at an inflection point: the function that measures itself on completion rates and adoption metrics is the function that gets cut first when budgets tighten, regardless of the actual revenue it produces. The function that measures itself on behavioural outcomes, what reps can actually execute, how that shows up in deal velocity, what changes in pipeline mix as a result is the function that earns the seat at the revenue table. The distinction sounds technical. It's actually existential for the discipline.
Shana's POV on what activation requires:
Stop measuring success by completion rates. Start measuring by behavioural outcomes.
That single sentence captures the architectural shift Shana has been building toward in her work from enablement-as-content-distribution to enablement-as-behaviour-engineering. It's also the operational sibling of the architectural argument I made in The Activation above. Native vs bolted-on AI is the platform-level version of the same shift. Behavioural outcomes vs completion metrics is the function-level version. Both are about refusing to measure correlation when causation is what you're being asked to produce.
Shana's work at Zendesk is happening at exactly the scale where the legacy enablement model breaks down most visibly, thousands of reps, dozens of segments, multiple regions, every single content asset versioned, tagged, and almost certainly out of date the moment it ships. The way she's responded to that complexity by refusing to measure the things that are easy to measure, and insisting on measuring the things that actually move the deal is the discipline more enablement leaders will need to adopt over the next eighteen months.
Follow Shana Thuener
THE SIGNAL
Three external links worth your time this week.
1. The architecture pattern, in long form
If you want the deeper version of the argument I made in The Activation Era, the piece “From Storage Architecture to Context Architecture” on the GTM Buddy site walks through why the legacy enablement category was always going to struggle with the agentic era. It's a category-level read, not a vendor critique, and the structural argument is one I keep coming back to in customer conversations.
2. The capacity-vs-productivity worldview, from the CMO's chair
My CMO, Karthi Ratnam, published the operator-level companion to Issue 2's argument last week. Her piece names what most CMOs are quietly feeling about agentic-era planning but haven't articulated. The capacity-vs-productivity distinction in, The Activation in Issue 2 came partly out of her thinking. If you missed it, this is the moment to read it.
3. Bessemer State of the Cloud, efficiency benchmarks for AI-native operators
The Bessemer State of the Cloud report has new data on Revenue Per Employee benchmarks across public SaaS companies, broken out by AI-native versus AI-augmented operators. The gap between the two cohorts is meaningfully wider than it was eighteen months ago, and it's showing up in efficiency ratios rather than in growth rates. That's your competitive context for 2026 planning, particularly if you're being asked to justify investment in agentic platforms.
Got something we should signal in issue 4? Reply with it.
We read everything.
THE SKILL
Native vs bolted-on AI, explained for buyers.
If you're going to defend the AI-native test in front of your CFO, your VP of Enablement, your procurement team, and your board, you need the vocabulary to do it cleanly. Here's the minimum framework, designed to be quotable in a meeting and defensible under scrutiny.
The architectural distinction in three layers
Native AI: the platform was designed from inception with AI as the substrate. There is no version of the platform without AI. The data model, the workflows, the user experience, and the integrations all assume AI is doing meaningful work at every layer. Native platforms are typically newer (most are post-2022) and are usually built by founders who had previous AI or machine-learning experience before starting the company. The pricing structure typically does not gate AI as a tier.
Bolted-on AI: the platform was designed before AI was a possibility, and AI has been added on top. The underlying data model is still the one designed for the original use case - most commonly, content management or learning management. The AI capabilities work, often quite well, but they operate as features layered above the existing platform rather than as the substrate beneath it. The pricing structure typically gates AI as a separate tier, a separate SKU, or both.
Mixed: the platform is in transition. Some capabilities have been re-architected; others remain layered on top. Pricing pages often reveal this state most clearly, multiple tier names that include “Agentic” as a label, but the underlying gating still reflects the pre-AI architecture. This is the most common state in the legacy enablement category in 2026.
Why this matters for you
Native AI can operate in-workflow because the platform was designed for that interaction model. The AI surfaces in the rep's existing tools: Salesforce, Slack, Gmail, because the platform was built to push there, not to be pulled from there.
Bolted-on AI requires the rep to leave the workflow to access it. The AI lives in the platform's own UI, the platform's own portal, the platform's own search bar. The rep has to context-switch to interact with it, which means in-deal moments, the moments that actually matter are precisely the moments where the AI is least likely to get used.
Mixed architectures inherit the limitations of the legacy core. A platform that has
re-architected its search but not its core data model will surface AI inside its portal beautifully and remain invisible to reps inside Salesforce. The pieces that work feel sophisticated. The pieces that don't are the pieces that matter most for in-deal execution.
The question to ask your vendors:
“Is your AI native to the platform, or does it require a separate licence or upgraded tier? And if it's tier-gated, which tier do I need to be on for the agentic capabilities you describe in your marketing materials?” If the vendor cannot answer cleanly, or if the answer involves a tier above the one you're currently on, you've learned what you needed to know. The answer to that question is more diagnostic than any demo.
That's issue three.
Reply and tell me what landed and what missed. I read every response. Especially on this one, the pattern across vendors that readers run Framework 1.3 against is the data I most want to learn from. Tell me what your diagnostic returned.
Three things you can do right now:
Run Framework 1.3 on your current enablement vendor this week. The result will shape your next renewal conversation more than any demo will.
Take the Revenue Activation Assessment. It diagnoses where your team's capacity is most constrained across the Five Levers - revenueactivator.ai/assessment
Follow Shana Thuener on LinkedIn. Her POV on behavioural outcomes versus completion metrics is the function-level companion to the architectural argument in this issue.
See you in two weeks.
Sreedhar Peddineni
CEO and Co-Founder, GTM Buddy
LinkedIn