Functions & people
Who owns which part of revenue, with a clear RACI. No orphaned motions, no duplicated ownership.
Definitions live in HubSpot, not a slide deck
Revenue teams on the same page.
Revenue Charter — Acme, Inc. · v4
Lifecycle & definitions
What everyone agrees a deal means
Assigned owners · sign to approveFully signed
PMMKSACSFI
5 of 6 signed offOne source of truth
Every definition, wired to the team that owns it.
Each team owns its part of the revenue model. In the charter, every definition is bound to one field in your CRM — so ownership is explicit and the system of record reads back exactly what the team agreed on.
Revenue Charter
In syncActivationProduct · Metric
binds to
HubSpotproduct.activated_at
MQLMarketing · Stage
binds to
HubSpotcontact.lifecyclestage
Qualified OpportunitySales · Stage
binds to
HubSpotdeal.dealstage
Net Revenue RetentionCustomer Success · Metric
binds to
HubSpotcompany.nrr
Recognized RevenueFinance · Metric
binds to
HubSpotdeal.amount
5 definitions · 5 ownersbound to HubSpot
The alignment problem
The same term means different things to each team.
Definitions drift the moment they leave the meeting. One word means four different things across marketing, sales, CS, and finance — and the CRM quietly stores whichever version was configured last. Dashboards diverge, handoffs leak, and no one can say why the numbers don't match.
The fix isn't another dashboard. It's a single document the whole team authors, signs, and keeps bound to the system of record.
One term
“Qualified lead”
Marketing
Anyone who books a demo counts.
Sales
Only with budget, authority, and a timeline.
Customer Success
Doesn't count until they're onboarded and live.
Finance
Not real until the contract is signed.
Four readings, one field. The CRM keeps whichever was configured last — so every report downstream is counting a different thing.
The charter
One document holding every definition the revenue team shares.
You write it as prose — the way you'd explain the business. RevOps Charter compiles it into a structured model, so the document stays readable and produces the definitions, stages, and metrics the rest of the system runs on.
Market & segments
The ICP, segments, and territories everyone sells and reports against — defined once.
Lifecycle stages
Every stage from first touch to renewal, with the entry, exit, and acceptance criteria that make it real.
Metrics & definitions
The exact meaning of each metric, tied to the stage it measures — so a win rate means the same thing everywhere.
Handoffs & SLAs
The moments work crosses a team boundary, who catches it, and the service level attached.
Review cadence
When the team revisits the charter, who signs off, and how change is governed over time.
The document
This is the charter your team actually opens.
One document with twelve sections. Page through the definitions, the metrics, and the sign-off block — each definition is bound to a HubSpot field and approved by the functions that own it.
Revenue Charter — Acme, Inc. · v4In sync
Section 4
Lifecycle & definitions
Qualified Opportunity
SAMK
A deal with a confirmed budget, an identified decision-maker, and a scheduled next step.
deal.dealstage bound
Marketing Qualified Lead
MKSA
A contact that crossed the agreed lead-score threshold and matches the ICP firmographics.
contact.lifecyclestage bound
Net Revenue Retention
CSFI
Trailing-12-month recurring revenue from existing accounts, including expansion, net of churn.
company.nrr bound
Recognized Revenue
FI
Revenue recognized on a ratable basis over the contracted service period per policy.
deal.amount bound
Revenue CharterPage 02 / 04
How it works
Define, choose, steward — the loop that keeps the team aligned.
- 1Define
Author the charter together
Product, marketing, sales, CS, and finance write each definition in one document, in plain prose. Everyone reads the same narrative and signs off on what a term actually means.
- 2Choose
Bind definitions to the CRM
Map each stage, metric, and handoff to the field that represents it in HubSpot. The charter stops being a slide and becomes the contract your system of record answers to.
- 3Steward
Keep it true over time
Continuous sync snapshots every binding, flags drift the moment a definition and the CRM diverge, and routes the change back through sign-off. Alignment is maintained, not assumed.
What a "Qualified Opportunity" means
01 / 03Qualified Opportunity
A deal is qualified once budget, authority, and a scoped need are confirmed by an AE — not when the form is filled.
PMMKSACSFI
5 of 5 signed offCRM bindings
Each definition binds to a HubSpot field and is monitored for drift.
Every term maps to the HubSpot field that stores it. Select a definition to see its live binding, its snapshot history, and what happens when the CRM value diverges from what the team signed.
Binding inspectorHubSpot · live
Charter
Qualified Opportunity
"qualified"
SAFIsigned
HubSpot
Dealdeal.dealstage
"qualified"
read from system of record
In syncCharter and system of record match.
Snapshot history
- v2Bound to deal.dealstage
- v3Threshold reworded, re-signed
- v4Confirmed against pipeline
Snapshot captured continuously · last run 2m ago
Proof it's working
Alignment reported as metrics from live CRM data.
Because the charter is bound to live data, it reports whether each agreed definition still holds in the CRM. A proprietary measurement model scores your definitions continuously and flags the ones that are drifting.
- Definition coverage
- 94%
- +18 pts
- Stage-to-CRM match
- 100%
- in sync
- Handoff SLA met
- 87%
- +9 pts
Alignment index
With charter Before
Wk 1
Wk 2
Wk 3
Wk 4
Wk 5
Wk 6
Assessments
See where your revenue model stands.
Two short self-assessments. Answer honestly and get an instant read on how aligned — and how mature — your operating model really is.
Ways to work together
Strategy and execution, on the commercial model that fits.
The charter is the constant. How we engage around it flexes — from a one-time build to full ownership of your RevOps function.
Project
A fixed-scope engagement to author your first charter and bind it to the CRM. Clear start, clear finish.
Ownership
We embed as your RevOps function and own the charter end to end — authoring, sign-off, and stewardship.
Subscription
Ongoing stewardship on a set cadence: continuous sync, drift review, and governed change.
Consumption
Pay for what you use as the charter scales across more definitions, bindings, and teams.
White papers
Go deeper on the model behind the charter.
Practitioner-grade references you can bring to your own revenue team. Each is a free download — we'll email the PDF.
From the blog
Field notes on getting revenue teams aligned.
Questions
The things teams ask before they start.
Straight answers on how the charter behaves, who signs, and what keeps it true once it's bound to your CRM.
A wiki holds words. The charter holds definitions that are bound to your CRM — so when the doc says "Qualified Opportunity means X," that meaning is wired to the exact field that enforces it. A wiki drifts silently; the charter detects drift and routes it back through sign-off.
Request a walkthrough
Get your revenue team on the same page.
Tell us a little about your team and we'll be in touch to set up a live session.
- A walkthrough of a real charter, bound to a live CRM
- How definitions are authored, signed off, and stewarded
- What alignment looks like measured, not assumed