SaaS & IT services / Practical operating guide
Connect product activity to retention and service ownership
Bookings and ticket volumes can obscure failed activation, avoidable churn and founders acting as the support escalation system.
The practical answer
Connect onboarding to a defined customer value event, then reconcile retention with recurring revenue and service ownership. For SaaS, activation is more than a login; for managed IT, it may be accepted onboarding against a service boundary. Track starting cohorts separately from new sales and pair commercial measures with incident and change evidence. Product, customer success and support leads should own the corrections so the founder is not the default escalation route for every stalled account.
The Bettr Company / Operating editorial
Management framework, not client outcome evidence
Owner-led operating work
Six implementation steps. Four defined measures. A checklist you can use in your next leadership review.
Management guidance, not a claim of sector credentials or client results. Set baselines from your own data.
Worked hypothetical example / not a benchmark
Net revenue retention %
Starting recurring revenue plus expansion, minus contraction and churn, divided by starting recurring revenue. New customer revenue and one-time projects are excluded.
(USD $100,000 starting monthly recurring revenue + USD $8,000 expansion − USD $3,000 contraction − USD $5,000 churn) ÷ USD $100,000 × 100 = 100% net revenue retention.
Assumptions to record
- All movements belong to the same starting customer cohort and monthly revenue basis.
- New customers, one-time implementations and tax are excluded.
- Activation is a separately defined value event within an agreed cohort window.
Common measurement mistakes
- Adding new customer revenue to retention.
- Calling account creation or a login activation without evidence of customer value.
- Blending project IT revenue with subscriptions or using change metrics to rank individual developers.
Implementation sequence
Give each decision an owner.
01 / Product or service lead
Define the value event a customer must reach to activate. For managed IT, define successful onboarding and contracted service boundaries instead of borrowing a SaaS product metric.
02 / Customer success lead
Track onboarding cohorts with agreed start and activation events. Investigate stalled accounts through customer context, not logins alone.
03 / Finance lead
Reconcile starting recurring revenue with new, expansion, contraction and churn movements. Exclude one-time projects from recurring revenue metrics.
04 / Support manager
Agree incident severity, response clocks and restoration events. Give responders runbooks and escalation authority while protecting customer data.
05 / Engineering lead
Review failed changes, recovery and recurring incidents with blameless cause analysis. Measure service reliability alongside commercial retention, not individual developer rankings.
06 / Founder and functional leads
Review cohort activation, churn reasons and unresolved service risks weekly. Assign owners to product, onboarding and service fixes rather than promising features in every sales call.
Immediate working checklist
Bring this to the next review.
For each action record: baseline / target / data source / accountable owner / due date. Keep patient, participant, candidate and customer records in your authorized systems, not this page.
Related downloadable tool
The Bettr Weekly Scorecard
Review the same handful of leading numbers every week so problems surface early.
Existing general Bettr PDF. Use the industry measures above to adapt it. Your requested download does not require ongoing marketing permission.
Boundaries and further reading
Do not blend project IT revenue with SaaS subscription metrics. Privacy, security and service contracts govern implementations.
These original operating sequences apply measurement principles from the references below. The references do not endorse Bettr or prescribe these exact steps or commercial targets.
Questions owners ask
Is net revenue retention the same as logo retention?
No. Revenue retention includes expansion and contraction in the starting cohort; logo churn counts customers lost. Expansion can hide customer loss, so review both.
Can managed IT use the same activation event as SaaS?
Not automatically. Define accepted onboarding and service boundaries for managed IT rather than importing a product-use event that has no operational meaning.
Who owns a failed onboarding handoff?
The customer success or service lead owns the cohort workflow, with product and support owners responsible for their blockers. Agree escalation criteria rather than routing every exception to the founder.
Adjacent operating work
From useful numbers to operating ownership
The founder should not have to carry every correction.
Start with the tool, then assess your operating constraints. Private advisory brings Byron into the decisions and leadership rhythm while your leadership team owns weekly execution. Scope and the USD monthly fee are disclosed in the fit check.
A separate implementation need? Explore Bettr AI Systems for controlled recruitment and sales/CRM automation, with its own assessment and scope.