Service is a revenue function
Why Service / Customer Success sits alongside Sales and Marketing in the CORE™ model, at the same weight. Retention and expansion are revenue too.
- By
- Joe Birkedale, Founder & CMO
- For
- Customer service leaders
- Published
- 1 Jun 2026
- Read
- 2 min
- Source
- project36.io
Short answer
- In CORE™, Service / Customer Success sits alongside Sales and Marketing, at the same weight. That is not a nicety. Retention and expansion are usually the largest revenue lever the business has.
Key takeaways
- Treating Service as a cost centre rather than a revenue function is a structural mistake that shows up in churn and net revenue retention.
- Service owns three priorities in CORE™: proper onboarding, visible support, and retention and expansion.
- In HubSpot, Sales handover should be a defined moment, customer health a reportable property, and renewal a pipeline with stages.
- Reporting Service alongside Sales and Marketing gives the board one revenue picture, with forecast expansion pipeline and recorded churn reasons.
Most revenue operations conversations end at closed-won. That is where the real work starts. Once a customer is signed, the business has to keep them, grow them, and use what they learn to sharpen the next Sales and Marketing conversation. That is Service's job.
Why Service belongs in the revenue model
Retention and expansion revenue typically exceeds new-business revenue in mature businesses. Treating Service as a cost centre while Sales and Marketing get all the attention is a structural mistake that shows up in churn and net revenue retention.
The businesses we work with that grow well have a Service function tied directly to the same commercial vision as Sales and Marketing. Onboarding, support, expansion and feedback are structured, measured and visible in HubSpot at the same standard as pipeline.
Three priorities Service owns in CORE™
- Onboard customers properly: playbook, time-to-value target, health score at exit.
- Support with visibility: SLAs, sentiment, root-cause tags, weekly review.
- Expand and retain: renewal and expansion pipeline, health dashboard, QBRs where they matter, churn reasons captured.
How this shows up in HubSpot
Service Hub, or the ticketing and customer object model in whichever configuration you run, becomes a first-class part of the revenue architecture. Handover from Sales is a defined moment, not an email. Customer health is a property that reports on. Renewal is a pipeline with stages.
Reporting rolls up alongside Sales and Marketing, not underneath them.
What changes when Service is treated as revenue
- Sales-to-Service handover stops being lossy.
- Product and marketing get a real feedback loop.
- Churn reasons become data, not folklore.
- Expansion pipeline is forecast, not hoped for.
- The board sees one revenue picture, not two.
Frequently asked
Yes. Service can sit inside Sales or Ops early on. What matters is that its work is modelled, measured and reflected in HubSpot as a revenue function, not treated as after-sales admin.
Service Hub is one place we build against the model. Ticketing, knowledge, feedback and portal features map naturally to the three priorities above.
No. Any business with a recurring or repeat-purchase relationship benefits. B2B services, ecommerce and industrial businesses all fit the same model, adjusted for their commercial rhythm.