The rules your GTM already runs by, encoded for every agent
Your calendar, your personas, your ICPs, your playbooks, your stages. RevSure encodes the semantic rules of your go-to-market motion once, so every agent acts on your definitions instead of guessing at generic ones.
GTM & Semantic Context encodes the rules your go-to-market motion already runs by — Operating Calendar, Buyer Personas, ICPs, Value Propositions, Playbooks, Messaging Playbooks, Funnel Life Cycle Stages, Buyer Stage, Case Studies & Collateral, Campaign & Channel Taxonomy, GTM Team Organization, Interactions Context, Core Entities & Dimensions, GTM Metrics & Analytics, and a glossary of Metrics, Labels & Terminology — as structured, tenant-defined context that every RevSure agent reads on the context layer before acting.
Agents without context guess. And they guess wrong in ways that look confident
Clean CRM data tells an agent what happened. Memory tells it what was said. Neither tells it what any of that means to your business — whether this account is your ICP, which persona is in the room, whether this is a good quarter to push a close date into, or what your team actually does at this stage of a deal.
"Is this a good lead?"
An agent that doesn't know your ICP scores on generic firmographics, not the profile your team actually converts.
"What quarter does this close in?"
An agent that doesn't know your fiscal calendar computes "this quarter" wrong, every time it matters most.
"What do I say to this buyer?"
An agent that doesn't know the persona and playbook reaches for a generic pitch instead of your proof points.
"Who owns the next step?"
Without team organization encoded, agents flag stalled deals with no clear handoff — and the signal dies in a queue.
Your fiscal calendar. Not the agent's guess
Your fiscal year start and end, quarter boundaries, week-start convention, and timezone — the same calendar your revenue team plans against. Without it, "this quarter" and "last quarter" are an agent's best guess. With it, every date range an agent computes lines up with the one a revenue leader would draw by hand.
- Fiscal year start, end, and quarter boundaries
- Week-start convention and operating timezone
- Planning cadence agents use for forecasts and rollups
- Date ranges that match finance, not a calendar default
Who you sell to. Defined once
Buyer Personas classify contacts into the buying-group roles your motion actually uses — Champion, Economic Buyer, Technical Evaluator, and the rest — plus the rules that decide who qualifies. ICPs are concrete, tenant-defined descriptions of an ideal account and an ideal lead, not a generic firmographic filter borrowed from someone else's business.
- Buying-group roles with qualification rules per persona
- Ideal account and ideal lead definitions you own
- Scoring, routing, and prioritization measured against your ICP
- Agents read the committee correctly: who to loop in, whose objection matters
What you say. And how you work the deal
| Persona | Primary angle | Handles objection |
|---|---|---|
| Economic Buyer | ROI & payback period | "Not now" → cost of inaction |
| Champion | Internal enablement kit | "Too complex" → guided rollout |
| Tech Evaluator | Integration & API depth | "Security concerns" → architecture doc |
| Security / Legal | Compliance posture | "Data residency" → EU hosting option |
Value propositions map the specific pitch and proof points to each segment, persona, and use case. Playbooks cover ICP guidance, persona detail, deal-stage steps, and messaging per entity type. Messaging playbooks go one level deeper: the angle, proof point, and objection response keyed to the persona in the room.
- Segment-, persona-, and use-case-specific value props
- Named playbooks for lead, opportunity, and account
- Messaging angles and objection handlers per persona
- Agents follow your motion, not a generic sales framework
Two stage models. Both encoded
- Explore — discovery complete
- Pre-SQL — champion identified
- SQL — economic buyer engaged
- Alignment — not yet reached
- Contract — not yet reached
Funnel Life Cycle Stages are the named stages your funnel is built from — stage keys, display names, and TOFU / MOFU / BOFU groupings, including where pipeline ends and booking begins. Buyer Stage is where a specific buyer sits in their own journey — Explore, SAL, Pre-SQL, SQL, Alignment, Proposal, Contract — distinct from the funnel stage the deal is recorded under.
- True funnel shape with TOFU / MOFU / BOFU groupings
- Pipeline vs booking boundary your finance team uses
- Buyer journey state separate from CRM funnel stage
- Stage-mismatch alerts when the two drift apart
Proof and channels. Tagged to the same definitions
| Asset | Tagged to |
|---|---|
| Acme Corp case study | Enterprise |
| SOC2 & security one-pager | Security / Legal |
| vs. Legacy CDP battlecard | Economic Buyer |
| ROI calculator | Economic Buyer |
| Mid-market rollout story | Mid-Market |
Case studies, one-pagers, battlecards, and ROI tools are tagged to the same ICP, persona, and segment definitions used everywhere else. Campaign & Channel Taxonomy is the defined set of channels and campaign types your team tags touches with — and the naming convention that keeps them consistent for reporting and attribution.
- Collateral matched to ICP, persona, and segment
- Shared channel and campaign-type buckets
- Naming conventions agents and humans both use
- Attribution that doesn't fracture across tag variants
Who owns what. Which touches count
| Owns | Escalates to |
|---|---|
| Marketing · TOFU/MOFU campaigns | → RevOps |
| SDR/BDR · Stage1→Stage2 qualification | → AE |
| Sales (AE) · Pipeline→Closed | → Sales Lead |
| RevOps · data & process | → Platform Owner |
| CS · post-sale expansion | → CS Lead |
GTM Team Organization encodes who owns what across Marketing, SDR/BDR, Sales, RevOps, and CS — and where a deal or lead escalates when it needs a human. Interactions Context is the taxonomy of every interaction type your motion recognizes: paid media, website visits, chat, email, conversations, ABM engagement, sales outreach, and non-digital touches.
- Ownership and escalation paths per funnel stage
- Concrete handoffs instead of "someone should act"
- Interaction types agents use to judge engagement
- Paid impressions and live conversations weighted differently
Shared vocabulary. Shared math
- MQL
- Score ≥ 75 AND ICP match
- Pipeline
- Open opportunities in Stage 4 or later
- At Risk
- No activity in 21+ days AND close date under 30 days out
- Champion
- Primary internal advocate persona on the account
- Closed-Lost
- Stage = Closed AND Outcome = Lost, excluding Nurture
Core Entities & Dimensions fix the objects everything else is defined against: Leads, Visitors, Accounts, Products, Regions, Channels, Customers, and Segments. GTM Metrics & Analytics pins canonical metric definitions — Pipeline Health, Funnel Analytics, Journey, Incrementality, Campaign Performance, Attribution, Sales Efficiency, and Marketing Mix. Metrics, Labels & Terminology is the living glossary for ambiguous terms, formulas, and CRM field labels.
- Canonical objects every other module stands on
- Metric formulas that match the board deck
- Plain-English labels for CRM fields and picklists
- One definition of MQL, pipeline, at risk, champion, closed-lost
One context layer, used by every agent that touches your GTM motion
The same context, applied everywhere an agent has to make a judgment call
Lead scoring
Every propensity score is measured against your ICP definition, not a generic industry model — so "high scoring" means what your team means by it.
Forecast rollups
Pipeline and booking numbers respect your fiscal quarter boundaries and your funnel's real pipeline/booking split, so the number an agent reports matches the one finance expects.
Meeting and outreach prep
An agent walks into a meeting or drafts a message already knowing the persona in the room, the playbook step that applies, and the value proposition that fits.
Stage-mismatch alerts
When a deal's funnel stage and buyer stage drift apart, agents can flag it — a signal that's invisible without both definitions encoded.
Context that's actually yours, not a category default
Tenant-defined, not generic
Every calendar, persona, ICP, and playbook is configured for your business, not inferred from a category template.
One source, every agent
SDR, forecasting, meeting prep, outreach, and RevOps agents all read the same current definitions — no drift between them.
Kept current as you evolve
Update a playbook or redraw an ICP once, and every agent's behavior updates with it — no re-training, no re-prompting each workflow.
Sits on clean, enriched data
Built on top of RevSure's CRM Data Automation, so the semantic rules apply to records that are already normalized and complete.
Related capabilities
Data Harmonization
Map every schema to one model the platform reasons over.
ExploreIdentity Resolution
Reconcile every system into one account agents act on.
ExplorePredictions & Signals
The scores and signals RevSure extracts, writes back, and exposes via MCP.
ExploreMemory
The one shared memory every agent reads before it acts.
ExploreQuestions, answered
What is GTM & Semantic Context in RevSure's Context Layer?
It's the module that encodes the semantic rules a company's GTM motion actually runs on — its Operating Calendar, Buyer Personas, ICPs, Value Propositions, Playbooks, Messaging Playbooks, Funnel Life Cycle Stages, Buyer Stage, Case Studies & Collateral, Campaign & Channel Taxonomy, GTM Team Organization, Interactions Context, Core Entities & Dimensions, GTM Metrics & Analytics, and a glossary of Metrics, Labels & Terminology — so every agent interprets data and takes action against that company's specific definitions rather than generic assumptions.
What does the Metrics, Labels & Terminology glossary actually define?
It pins down the exact formula behind every named metric, the plain-English label for every CRM field and picklist value, and the definition of ambiguous business terms such as MQL, pipeline, at risk, champion, and closed-lost — so two agents, or two people, never interpret the same word two different ways.
Which metrics does GTM Metrics & Analytics cover?
Pipeline Health, Funnel Analytics, Journey Metrics, Incrementality Metrics, Campaign Performance Metrics, Attribution Metrics, Sales Efficiency & Effectiveness Metrics, and Marketing Mix Performance Metrics — each computed the same way the revenue team already computes them, so an agent's number reconciles with the one in the board deck.
What counts as an interaction, and how is that different from Memory?
Interactions Context is the taxonomy — the categories of touch a GTM motion recognizes, such as paid media, website visits, chat, email, conversations, ABM engagement, and sales outreach. Memory is the actual record of what happened in those interactions over time. The taxonomy defines the buckets; Memory fills them.
Why define core entities like leads, accounts, and segments explicitly?
Every other module on this page — ICPs, personas, playbooks, funnel stages — is only meaningful if agents agree on the underlying objects. Core Entities & Dimensions fixes what counts as a lead versus a visitor, an account versus a customer, and how a segment or region is drawn, so every other definition has firm ground to stand on.
Why does a channel taxonomy matter for agents?
Agents roll up channel and campaign performance using the exact bucket names and naming convention a team already reports against, so a campaign tagged 'Webinar' by one person and 'Events' by another doesn't fracture the numbers an agent produces.
How does GTM Team Organization affect routing?
It tells an agent exactly who owns a stage and where to escalate — which team handles a lead at each point in the funnel and who to hand a stalled deal or hot lead to, instead of flagging it with no clear next step.
How are case studies and collateral connected to this context?
Case studies, one-pagers, battlecards, and ROI tools are tagged to the same ICP, persona, and segment definitions used everywhere else in this layer, so an agent citing proof can find the piece that actually matches the account it's talking to, instead of the most recently published one.
How do messaging playbooks relate to value propositions?
Value propositions set the core pitch for a segment, persona, or use case. Messaging playbooks go one level deeper, giving the specific angle, proof point, and objection response to use with a given persona in the room.
How is this different from CRM Data Automation?
CRM Data Automation makes sure the underlying records are clean, normalized, and enriched. GTM & Semantic Context supplies the business meaning layered on top of those clean records — what counts as an ICP match, which persona a contact plays, what stage a deal is really in — so agents can reason about the data, not just read it.
How is this different from Memory?
Memory captures what happened in past interactions — meetings, chats, product usage. GTM & Semantic Context captures the rules of the game those interactions are judged against: whose objection matters, which quarter a deal needs to close in, what stage comes next.
Who defines the calendar, personas, ICPs, and playbooks?
Your team does. RevSure stores these as tenant-owned configuration — your fiscal calendar, your persona and ICP definitions, your named playbooks, your funnel stage keys and groupings — and every agent reads the same, current copy.
Do agents use this context automatically?
Yes. Every RevSure agent — SDR and qualification, forecasting, meeting prep, outreach, RevOps — loads this context before acting, without needing to be told which persona, ICP, or playbook applies on each run.
Give every agent your rules, not a generic set of them
Book a walkthrough of GTM & Semantic Context on your own calendar, personas, ICPs, and playbooks.