Which retention question is the buyer trying to answer?
Does buyer want renewals, losses from active members, or continuing collections? These are related questions with different events and denominators. Choose question before percentage. A rate can be correct for its stated method while answering a different question from the one needed for the acquisition earnings plan.
List plan versions, term, billing, benefits, renewal method, and cancellation rights. Annual prepaid plans differ from monthly ongoing service. Distinguish free enrollments and trials from paying members. Check written terms and actual practice; one active label may group customers with different rights and payment status.
The buying hub supplies context. The P&L guide connects reporting to earnings and duties. Seek collected contribution that can continue under transferred rights. Largest count of active names is not the goal. Buyer needs to know which economics and obligations carry into the real post-close plan.
What member-level records are needed?
Use stable member IDs with signup, renewal date, plan, billing, payment, service, cancellation, refunds, and expiry. Keep status history. Current fields may hide departures; record events and dates for the measured group.
Bridge starting members, additions, reinstatements, cancellations, expirations, and ending members. Explain duplicates, households, software moves, and changed active definitions. Save original and separate adjustments. An export can be complete for its current settings without proving a comparable history; make corrections and exclusions visible to reviewers.
This analysis is no required regulatory report. Limit sensitive fields to authorized need. Coded records can support early rates before named contract or billing review. Later access should match the question.
How should renewal cohorts be defined?
Group by signup or due period and identify who reached the measured point. Keep relevant pre-renewal departures. Do not remove them simply because they were inactive at due date. State exclusions and purpose. Otherwise the reported rate may improve through population changes rather than a real improvement in customer behavior.
Separate paid renewal, failed billing, cancellation, expiry without renewal, and unknown status. Young groups have limited observed history. Keep forecasts separate from completed intervals. Buyer needs the length and scope of actual evidence before comparing a new plan with a program whose members already faced a full renewal cycle.
| Cohort element | Evidence | Diligence question |
|---|---|---|
| Original population | Enrollment and plan history | Which members entered the cohort? |
| Renewal eligibility | Term and due-date records | Who reached the measured interval? |
| Voluntary departure | Cancellation record | Why did the member leave? |
| Collection failure | Billing attempt and resolution | Did the relationship continue without payment? |
| Successful renewal | Payment and continued rights | Was the renewal actually completed? |
| Unresolved status | Missing or conflicting records | What cannot yet be classified? |
What does an illustrative cohort calculation show?
Assume an invented group of 100 members scheduled for annual renewal. Seventy renew and pay; fifteen cancel; ten expire; five remain unresolved. Under this definition, confirmed paid renewal is 70%: 70 ÷ 100. This calculation describes the stated outcomes. It supplies no company result or industry acceptable rate.
Keep five unknown records visible. Calling them renewed overstates confirmed proof. Removing canceled members changes the question and may strengthen the percentage without changed behavior. Explain denominator and status rather than silently select the version that looks better. The buyer should be able to repeat the stated calculation.
These assumptions are no averages. Use actual contracts, payments, and consistent periods. Young plans or incomplete exports may need narrower findings than seller's headline rate.
Why should failed payments be separated from voluntary churn?
Failed cards, expired methods, and processor errors differ from a choice to leave. Check retry, notices, cancellation, and resolution. Did unpaid members keep benefits? Were balances collected or written off? These facts matter for cash and obligations. Preserve separate causes rather than count every failed attempt as voluntary churn.
Billing attempts are not collections. Bridge processor activity, refunds, fees, chargebacks, settlement dates, and ledger. A software-active member may supply no cash. Check actual receipts and status together. This avoids treating a current label as payment proof or counting the same gross activity and net bank deposit as two receipts.
Separate causes where records support them. Changes may fix some collection failures, but do not assume all will be recovered. Put improvements in forecasts. Expected recoveries are not historical earnings. Retain actual unpaid outcomes and show evidence, cost, and conditions behind any assumed benefit from the buyer's proposed process.
How do service delivery and contribution affect retention value?
Cost visits and benefits with labor, travel, materials, dispatch, and relevant support. Check discounts and waived charges. Retained customers can supply little contribution if service uses more resources than expected. The member count needs a delivery-cost view before buyer can assess earnings that fund the permanent operation.
The technician-productivity guide links duties and capacity. Check when benefits are used and whether peak demand strains schedules or staffing. Priority access is a promise with real work behind it. Include that obligation in the plan rather than assume crews have spare hours whenever members request service.
Do not credit all member spending to the plan. Customer overlap does not prove every dollar disappears without membership or transfers after purchase. Separate observed activity from claims about its cause.
Why must cash, book revenue, and tax income remain separate?
FASB's January 2020 staff revenue questions discuss stand-ready promises and upfront fees that may supply no distinct service. This is educational material, not the Codification. It sets no single pattern for all plumbing contracts. Apply actual promises and accounting framework with advisers before relying on reported deferred revenue.
IRS Publication 538 covers tax methods and advance payments. Tax recognition does not erase remaining service rights. Reconcile method, books, and actual duties with accountant. A tax figure, accounting balance, and estimated cost can differ; explain each rather than assume one measure settles all closing treatment.
Who keeps prepaid cash, performs work, and handles refunds at closing? Terms may use working capital or other agreed treatment. Avoid both separate price and working-capital credits for the same duty without intentional support. Define actual balance and reasoning so distinct labels do not conceal duplicate treatment of one obligation.
What consent and cancellation rules should be reviewed?
ROSCA applies to covered internet negative-option transactions. Review channel, disclosure, consent, and cancellation. Do not automatically extend it to every sale method. Other duties may apply separately. Actual contract and sales facts are needed before a buyer can assess compliance rather than rely on the recurring-billing label.
The FTC March 2026 announcement says the 2024 amended rule was vacated and seeks comment. It is not a replacement final rule. State duties need specific review. The agency's new process does not establish that all other laws disappeared or supply one currently effective cancellation standard for every plan.
Compare terms and practice. Check notices, price changes, cancellations, refunds, and complaints. Identify correction and exposure from evidence. Charges or software settings alone prove neither compliance nor violation; keep missing proof distinct.
Can the membership book survive the transaction and systems change?
Review assignment, change-of-control terms, provider rules, consent, and purchase structure. Confirm supported account and data handover. Keep tokens and credentials out of routine diligence folders. An asset or equity label does not alone settle transfer events; the actual agreements and provider process determine what steps need review.
Test status, dates, contract versions, payment history, and benefits in data mapping. Upload success proves neither transferred rights nor correct billing. Check sample records and needed permissions against the supported handover plan before forecasting ongoing receipts.
The buyer roadmap connects handover. The current SBA SOP requires appropriate covered-loan credit review. Recurring-revenue labels do not replace supported earnings, management, or lender review.
What should the buyer conclude before relying on membership earnings?
- Reconcile the member population and preserve status changes.
- Calculate defined cohorts and separate unresolved outcomes.
- Verify collection, service cost, and remaining customer obligations.
- Confirm applicable consent, cancellation, and transfer requirements.
- Build a supported post-close forecast distinct from historical results.
State supported result: retained contribution, limited history, or corrective work. Keep proof, scope, and open questions. No universal churn cutoff is established.