RevOps Charter: Purpose, Definitions, Owners, Handoffs, Metrics and Cadence
RevOps charter explained: the eight sections it contains, how each definition binds to a HubSpot property, who signs it, and how changes are versioned.
Paul Maxwell, PhD
AUTHOR
GET WEEKLY REVOPS INSIGHTS
No spam. Unsubscribe anytime.
A revenue team agrees its definitions in a workshop and records them in a slide deck rather than a signed RevOps charter. Two quarters later the CRM computes something else: a workflow sets the marketing qualified stage on a score threshold nobody signed, a new sales manager has added a deal stage, and a renewal report counts expansion when it was signed rather than when it started billing. Nobody broke the agreement on purpose; nothing in the system knew it existed, so nothing could refuse a change to it, and a later review can call the portal inconsistent without saying with what.
This article sets out what the charter contains and how each part is bound to HubSpot, so that the system, not memory, enforces the agreement. It starts with the charter's position before tooling and audits, then covers the eight sections, what each binds to, and where a binding stops holding. A sample charter follows, with its definitions, its handoffs and one disagreement it settles, and the article closes with change control, an authoring procedure, costs, symptoms and the limits of the evidence.
A RevOps charter, or revenue operations charter, is the signed document that states what revenue operations is for, the shared definitions and their owners, the handoffs between teams, the metrics and the cadence of review. A binding is the link between a definition and the HubSpot property, stage or setting that carries it. A signatory is a person whose signature a definition needs: its owner, and the head of each function that uses it in a decision.
A charter can live in any shared document. For a HubSpot portal, RevOps Charter is a tool built for the purpose: its site describes one document that binds each definition to a HubSpot field, records sign-off by the owning functions, and flags drift from the signed wording. Disclosure. RevOps Charter is a product of Paul Maxwell, the founder of RevOps HQ.
The Charter as the Reference for Configuration and Audit
HubSpot's default lifecycle stages describe a Marketing Qualified Lead as a contact or company the marketing team has qualified as ready for sales, which names who decides and leaves the criterion to whoever configures the workflow that sets the stage. A portal configured before a charter exists therefore encodes its administrator's judgement, and a tool bought before one exists encodes the definition of the team that led the purchase.
Audits share the dependency. A HubSpot audit scores a portal against the charter, where each bound property carries the signed criterion or does not and each finding can be ranked by the decision it corrupts. Without a charter, the audit can score only against HubSpot's defaults or the auditor's preferences, and the people asked to act on the findings agreed to neither.
The white paper on the foundations of revenue operations argues that every consequential metric should be traceable to a construct, an owner, a record and a decision. A charter is where those links are written down and signed, and a binding is where each one meets a field that HubSpot can hold to it.
RevOps Charter Template: Sections and CRM Bindings
What goes in a RevOps charter can be tested section by section, since each must state something a revenue decision depends on; the eight below pass that test in the sample.
| Section | What it states | Binds to in HubSpot |
|---|---|---|
| SectionPurpose | What it statesThe decisions the revenue model serves, and its scope | Binds to in HubSpotNothing: held in the document |
| SectionFunctions | What it statesTeams, owners and decision rights | Binds to in HubSpotTeams, the Edit property settings permission, property access |
| SectionMarket | What it statesTarget customer profile, segments and territories | Binds to in HubSpotCompany properties and segments |
| SectionLifecycle | What it statesStages from first touch to renewal, with entry and exit criteria | Binds to in HubSpotLifecycle stage, deal pipelines and stages, pipeline rules |
| SectionDefinitions | What it statesEach term's criterion, owner and signatories | Binds to in HubSpotThe properties that carry each criterion, and each property's Description |
| SectionMetrics | What it statesFormulas, with population, date, stage and value rules | Binds to in HubSpotReport filters and calculated properties |
| SectionHandoffs | What it statesExit criteria and a service level at each join between teams | Binds to in HubSpotRequired stage properties and Date entered stamps |
| SectionCadence | What it statesReviews, change control, versions and sign-off | Binds to in HubSpotThe audit log of property and pipeline changes |
Functions, Lifecycle and Handoffs bind to settings that refuse a departure: a user cannot move a deal into a stage until its required properties hold values. Market, Definitions, Metrics and Cadence bind to places that record the wording and stop nobody, so a second report with other filters sits beside the signed one without warning. Purpose binds to nothing, yet it settles disputes, because every other section is read against the decisions it names.
Binding Definitions to HubSpot Properties
A definition that is not bound to a property is not enforced; it lasts as long as the people who agreed it stay in their roles. Binding names the property that carries each definition, the value or stage that represents it, and the workflow, integration or person that writes it.
Lifecycle definitions bind to the Lifecycle stage property, internal name lifecyclestage, whose stages a Super Admin can create and rename under Settings, Data Management, Objects, Contacts, on the Lifecycle Stage tab. Imports, forms, workflows and the API move the property forward only, so those tools can set an earlier value only after the current one is cleared. Each stage carries Date entered and Date exited properties, with latest and cumulative time in stage on Professional and Enterprise; where a returned record sits is covered in lead status and lifecycle stage.
Opportunity definitions bind to deal stages, internal name dealstage, whose configuration only users with the Edit property settings permission can change. A conditional stage property marked Required stops a user creating a record in a stage, or moving one into it, until the property has a value. On Professional and Enterprise, pipeline rules set by a Super Admin can limit where records are created, block skipped stages and backward moves, and limit who edits records in a given stage, and the first three rules also apply to lifecycle stages.
Ownership binds to property access on Enterprise: the owning team holds View and edit, and other teams hold View only. View access cannot be restricted on Lifecycle stage, Deal stage, Pipeline or Close date, so those take their protection from pipeline rules. The wording binds to the Description field of the property editor, whose Monitor section shows where the property is used and its fill rate.
Enforcement Boundary of a Bound Definition
Every binding above has a documented exception of the same shape. HubSpot states that deal approval cannot be bypassed, but that all other pipeline rules can be bypassed by Super Admins, by users with Edit property settings, and by records created or edited by workflows or the API; the same page says some rules hold for API edits that pass a user ID, so the API exemption should be tested in the portal. Property access is bypassed by the API and by manual record creation. The audit log records only actions by HubSpot users, so a value written by a form submission does not appear in it.
The finding follows from those statements: a bound definition binds everyone except the people able to change the binding and the automation that writes the property, so a charter is enforced in HubSpot only when two lists match. The first sets the signatories against the users holding Super Admin or Edit property settings, which an export of users shows in its permissions column. The second sets the writers the charter names for each bound property against the workflows and integrations that actually write it, which the property's usage and history show.
A mismatch in the first list lets someone who never signed the charter change a definition's machinery unopposed. A mismatch in the second means a workflow applies a criterion nobody signed, and every count built on the property inherits it. Neither mismatch can be seen by reading the charter.
Sample Charter: Definitions, Owners and Signatories
The charter below is sample data and describes no client. The company sells annual software subscriptions to other businesses, runs a HubSpot Enterprise portal, and has five functions: marketing, sales development, account executives, customer success and finance. Version 2.0 of its charter took effect on 1 July 2026.
| Definition | Criterion or formula | Owner | Bound property | Signed by |
|---|---|---|---|---|
| DefinitionLead | Criterion or formulaContact with a business email who submitted a form or attended an event | OwnerMarketing | Bound propertyLifecycle stage = Lead | Signed byMarketing, sales development |
| DefinitionMarketing qualified lead | Criterion or formulaLead at a company in the target segment, with a demo request or a lead score of 60 or more | OwnerMarketing | Bound propertyLifecycle stage = Marketing Qualified Lead, set by one named workflow | Signed byMarketing, sales development |
| DefinitionSales qualified lead | Criterion or formulaMarketing qualified lead accepted after a connected call that confirms a need and a buying date | OwnerSales development | Bound propertyLifecycle stage = Sales Qualified Lead | Signed bySales development, account executives |
| DefinitionOpportunity | Criterion or formulaDeal in Discovery with Amount, Close date, Deal type and Next step set | OwnerAccount executives | Bound propertyDeal stage = Discovery, with those four required on entry | Signed byAccount executives, finance |
| DefinitionQualified pipeline | Criterion or formulaSum of Amount on open deals past Discovery with a Close date in the next two quarters | OwnerAccount executives | Bound propertyDeal stage, Amount, Close date | Signed byAccount executives, finance |
| DefinitionWon | Criterion or formulaDeal with a countersigned order form attached | OwnerAccount executives | Bound propertyDeal stage = Closed won, Order form required on entry | Signed byAccount executives, finance |
| DefinitionChurn | Criterion or formulaRecurring revenue from a cohort customer that is no longer collected, whatever the reason | OwnerFinance | Bound propertyRecurring revenue inactive reason = Churned, Churn reason (custom) | Signed byFinance, customer success |
| DefinitionNet revenue retention | Criterion or formula(Starting ARR + expansion started − contraction − churn) ÷ starting ARR, for customers on day one, trailing twelve months | OwnerFinance | Bound propertyRecurring revenue properties, Service start date (custom) | Signed byFinance, customer success, chief executive |
Three design rules are visible, each the sample's own standard rather than an industry convention. Every definition has one owner, who alone can propose a change. Every definition is signed by each function that uses it in a decision, which puts finance on everything that reaches revenue reporting. Where the owner is measured on the figure, as account executives are on Won, a function not paid on it co-signs.
Lifecycle Ownership and Handoff Service Levels
The sample's Lifecycle and Handoffs sections assign each stage to one team and place a handoff, with a service level, wherever the owning team changes.
| Handoff | Exit criterion from the sender | Service level | Clock in HubSpot |
|---|---|---|---|
| HandoffH1: marketing to sales development | Exit criterion from the senderMarketing qualified criteria met; contact owner assigned | Service levelAccepted, or returned with a reason, within 5 business days | Clock in HubSpotDate entered Marketing Qualified Lead to Date entered Sales Qualified Lead, or to the return |
| HandoffH2: sales development to account executives | Exit criterion from the senderDeal created in Discovery with its four required properties | Service levelQualified or closed within 10 business days | Clock in HubSpotDate entered Discovery to Date exited Discovery |
| HandoffH3: account executives to customer success | Exit criterion from the senderClosed won with order form, scope and success criteria recorded | Service levelKickoff held within 10 business days | Clock in HubSpotDate entered Closed won to the onboarding kickoff date |
A service level with no property to measure it from can only be argued about. HubSpot's lifecycle documentation gives the pattern: a workflow that creates a follow-up task when Date entered Sales Qualified Lead is more than five days in the past.
In August 2026, 120 contacts entered the marketing qualified stage between 3 and 24 August, so each had five business days before the month closed. Sales development accepted 86 and returned 16 with a reason in time: 102 of 120, or 85%, against the charter's own standard of 90%. Of the rest, 12 were decided late and 6 were undecided on 31 August. The shortfall becomes a report rather than a dispute about lead quality: the head of sales development, as owner of H1, explains the 18 late or undecided records at the monthly review.
Net Revenue Retention Under Three Rules
Version 2.0 exists because version 1.0 defined net revenue retention by name and formula and left two rules unstated. The cohort was 40 customers holding $2,000,000 of annual recurring revenue on 1 July 2025. In the year to 30 June 2026, $420,000 of expansion was signed, of which $120,000 starts billing on or after 1 July 2026; contraction removed $60,000; and churn removed $140,000, of which $50,000 came from two customers lost when they were acquired.
| Rule | Account executives | Customer success | Finance |
|---|---|---|---|
| RuleExpansion counted | Account executivesAt signature: $420,000 | Customer successAt service start: $300,000 | FinanceAt service start: $300,000 |
| RuleChurn counted | Account executivesAll: $140,000 | Customer successExcluding acquisitions: $90,000 | FinanceAll: $140,000 |
| RuleContraction | Account executives$60,000 | Customer success$60,000 | Finance$60,000 |
| RuleNet revenue retention | Account executives111.0% | Customer success107.5% | Finance105.0% |
Each figure is correct under its own reading of version 1.0. The six points between account executives and finance are the $120,000 of unstarted expansion over the $2,000,000 base, and the 2.5 points between customer success and finance are the $50,000 lost to acquisitions. No record is wrong, so no clean-up could have closed the gap; the general case is catalogued among the RevOps antipatterns.
The charter settled it through its Purpose section, which states that net revenue retention is reported to the board as the revenue the existing base produces in the period. Unstarted expansion produced no revenue in the period, and an acquired customer produced none either, so version 2.0 counts expansion at its service start date and churn whatever its reason. The signed figure is 105.0%.
The other readings keep their own names. Expansion bookings, $420,000, is owned by account executives and used for compensation. Churn by reason is owned by customer success and records Acquired against the $50,000. The timing rule binds to a custom Service start date property that only finance can edit, beside HubSpot's recurring revenue properties, which need Sales Hub or Service Hub Enterprise. The same reconciliation applied to forecasts is set out in aligning the sales and finance forecasts.
Signatories, Versions and Change Control
The chief executive, or the chief revenue officer where one exists, signs the charter as a whole, and each function head signs the definitions their function owns or uses. A charter signed only by its author is a proposal, because nobody whose figure it changes has agreed to be measured by it.
A major version changes a definition's population, date, stage or value rule and so breaks its series; it takes effect at the start of a reporting period, and the first period after it is reported under both rules. A minor version changes wording, not what is counted, and needs the owner's signature alone.
Change control runs through the owner: a request names the definition, the new wording, the reason and the bound properties affected; the owner accepts or rejects it, the signatories sign, and only then does a Super Admin change the binding. Each binding change in the audit log should match a register entry, and an unmatched change is the next review's first finding.
The audit log sets the review interval. Its All Logs view covers the last 30 days, its property update and pipeline change categories need Professional or Enterprise, and reading it needs Super Admin. A review at least every 30 days therefore keeps every user change since the previous review inside that view, and a longer interval needs exports kept in between. The sample reviews bindings every four weeks, definitions quarterly, and collects signatures once a year.
Charter Authoring Procedure in HubSpot
- Write the Purpose section first: the decisions the revenue model serves, such as board reporting, the forecast and compensation, since later disputes are settled against it.
- List the functions, the head of each, and the definitions each may decide.
- Collect every term used in the last quarter's reviews and board pack, and write each as a criterion or formula with its population, date, stage and value rules.
- Assign each definition one owner and its signatories, adding a second function wherever the owner is measured on the figure.
- Bind each definition to a property, its internal name, the value or stage, and its writer, configuring stages under Settings, Data Management, Objects, with Required conditional stage properties and pipeline rules for each exit criterion.
- Copy each definition's signed wording into the Description field of every property bound to it.
- On Enterprise, give the owning team sole View and edit access to each custom property that carries a definition.
- Under Settings, Users and Teams, choose Actions, then Export all users, and compare the holders of Super Admin or Edit property settings with the signatories, resolving each difference.
- Collect signatures and record version 1.0 with its effective date.
- Verify: as a user without Edit property settings, try to move a test deal into a stage without its required property and to skip a restricted stage, and confirm both are refused. In Audit Logs under Account Management, confirm each binding change matches the version register, then rebuild one metric from its signed formula and confirm the report returns the same figure.
Costs and Returns of a Revenue Operations Charter
A charter buys a dispute settled by reading a signed text instead of holding another meeting. It gives an audit an agreed standard, lets a definition outlive its authors, and records the reason behind each configuration choice.
The costs fall on senior time and on each team's room for manoeuvre. Every function head reads and signs, a named owner runs the reviews, and a signed definition removes a team's latitude to report generously. Required stage properties add entry work for sellers and prove only that a value was entered, not that it is true. Pipeline rules need Professional or Enterprise, and property access and the recurring revenue properties need Enterprise.
RevOps HQ is a HubSpot Solutions Partner and is paid to write charters and configure their bindings, and RevOps Charter belongs to its founder, as disclosed above. A charter needs neither: it can be written in a shared document and bound by hand in any CRM.
The case is strongest where several teams report shared figures to a board, revenue recurs, sales development hands records to account executives, or an audit, migration or tool purchase is about to be scoped. It is weakest in a founder-led company where one person spans marketing and sales, and on a Starter portal, where pipeline rules and property access are unavailable and the signatories are the only enforcement.
Symptoms of an Unbound Charter
A lifecycle stage count moves with no change to the charter. A workflow or connected app writes the property unnamed; the property history shows the source, and the fix is to name the writer or remove it.
A team reports a figure under a charter name with a different value. The metric lives in a report bound to nothing, so a second report with other filters carries the same name; the variant needs its own name and owner.
Records reach a later deal stage without an earlier stage's required properties. They skipped that stage, and the rule against skipping exempts Super Admins, users with Edit property settings, workflows and the API; the property history shows which moved them.
An audit lists inconsistencies and cannot rank them. Without a charter there is no record of which decision each property serves, so the findings cannot be prioritised until one is written.
Evidence on Written Rules and Coordination
The research bears on two questions: whether structural links between marketing and sales are associated with better outcomes, and how written rules coordinate interdependent work. Homburg, Jensen and Krohmer surveyed 337 companies based in the European Union and found that the configurations with the strongest outcomes combined strong structural linkages between marketing and sales with high market knowledge in marketing (Journal of Marketing, 2008, DOI 10.1509/jmkg.72.2.133). Okhuysen and Bechky's review identifies plans and rules, objects and representations, roles, routines and proximity as coordination mechanisms that produce accountability, predictability and common understanding (Academy of Management Annals, 2009, DOI 10.5465/19416520903047533); a charter combines rules, roles and a shared representation in one signed document.
Adler and Borys distinguish formalisation designed to enable employees from formalisation designed to coerce them, and argue that the effect of formal rules depends on their design, not only on their number. A charter that states the purpose behind each rule and a route for changing it sits on the enabling side.
None of these studies tests a RevOps charter, and the Homburg finding is a cross-sectional association rather than an effect. The enforcement claims here rest on HubSpot's documentation of its settings, not on outcomes measured in firms that adopted a charter.
Scope and Limits of This Article
This article covers the charter and its bindings in HubSpot, and leaves compensation design, territory design, forecasting method and object-model design aside. HubSpot behaviour is as documented in September 2026, and the knowledge base pages cited were read on 1 October 2026; tier gates and permission names change with the product, and the documentation is authoritative over this text.
The sample illustrates arithmetic and structure, not prevalence, and no claim is made about how other firms define retention or set service levels. The bypass behaviour is documented by HubSpot and was not reproduced in a test portal for this article.
Frequently Asked Questions
Which Sections Go in a Revenue Operations Charter?
Eight: Purpose, Functions, Market, Lifecycle, Definitions, Metrics, Handoffs and Cadence. Each binds to a HubSpot property or setting except Purpose, which names the decisions the other sections are read against.
Which Roles Sign a RevOps Charter?
The chief executive or chief revenue officer signs the whole charter. Each definition is signed by its owner and by the head of every function that uses it in a decision.
Can a RevOps Charter Template Be Copied From Another Company?
The section structure can be copied and the definitions cannot, because each criterion depends on the company's own segments, sales motion and reporting decisions.
Does a RevOps Charter Require HubSpot Enterprise?
No. A charter can be written and signed on any tier, and HubSpot documents lifecycle stages, deal stages and required stage properties for all plans. Pipeline rules need Professional or Enterprise, and property access and the recurring revenue properties need Enterprise.
In Summary
A RevOps charter states what revenue operations is for, the shared definitions and their owners, the handoffs and their service levels, the metrics and the review cadence. Written before tooling is configured or an audit is run, it gives each a standard to work against. Its sections bind to HubSpot unevenly: three to rules that refuse a departure, four to places that record the wording, and Purpose to nothing, although Purpose settled the sample's three readings of net revenue retention at 105.0%. Enforcement stops where HubSpot documents it stopping, since Super Admins, holders of Edit property settings, workflows and the API pass through pipeline rules.
Two lists decide whether the signed charter is the one HubSpot computes. One sets the holders of Super Admin and Edit property settings against the signatories; the other sets each workflow and integration that writes a bound property against the writers the charter names, and where both match, the signed definitions are the ones in force.