What should the plan promise customers?
Define services, visit frequency, response promises, discounts, exclusions, term, payment, and cancellation. Use terms staff can deliver and customers understand. Benefits can create more work than price or crews support. Match promises to actual operations before launching a broad list of appealing features.
The operations hub links staffing, price, dispatch, and records. Start with a useful customer relationship and service economics. A large pre-sale count is no substitute for that design. The operator needs to deliver the promises before asking buyer to value them.
Which benefits already belong to ordinary service? Which add cost? Discounts can reduce contribution on work customer would buy anyway. Included visits can use hours needed for other jobs. Show those assumptions explicitly rather than treat every benefit as costless or every added job as caused by membership.
How should price and delivery cost be tested?
Model each member and whole program. Include visits, labor, travel, materials, admin, payment fees, discounts, refunds, and relevant costs. Separate fixed, variable, and capacity effects. Price and staffing should use the same actual promises, with missing costs visible before calling the projected balance profit.
IRS Publication 583 supports records behind receipts and costs. Link model to invoices, payroll, visits, and admin where available. Label early estimates. Update them from actual evidence rather than present an untested launch assumption as a demonstrated cost or margin for the program.
Assume an invented plan has 100 members paying $120 annually: $12,000 fees. Two visits each at hypothetical fully burdened $45 per visit cost $9,000. Another $1,500 admin leaves $1,500 before other overhead and omitted costs. The calculation uses stated assumptions; it describes no real company or recommended fee.
This teaches design math, not a visit or margin benchmark. State excluded discounts, refunds, or service time and model them separately. Collected fees may leave weak contribution after promises are delivered. A launch budget needs the actual delivery plan, not only receipts under the most favorable assumptions.
What service capacity must be reserved?
Translate visits into jobs, field hours, travel, and scheduling. When do members seek work? Does it compete with emergency or other jobs? Assign delivery responsibility. A plan promising priority needs an operating method, not merely a sales phrase that crews cannot honor when demand peaks.
The technician-retention guide covers staff continuity. Headcount alone cannot support visits when needed skills, schedules, or lawful oversight are unavailable. Identify actual work and qualified staff. Cost that capacity before treating the listed crew size as proof every promised service can be delivered.
In the same invented example, 200 visits at assumed 1.5 field hours require 300 hours before added travel or work. Replace that input with real workflow proof. It supplies no universal visit duration. Also identify when those hours are needed, rather than only sum annual capacity.
Record missed or delayed service and resolution. These can leave refunds or work owed. Enrollment alone shows no delivery; buyer needs both records to assess future duties.
How should terms, consent, and cancellation be handled?
Review contract, sales channel, billing consent, renewals, disclosures, and cancellation. Place and channel matter. Save approved versions and customer-agreement proof with controlled access. Staff need terms actually in effect, while broader summaries should not expose every private customer field to every reviewer.
ROSCA addresses specified internet negative-option arrangements, including disclosure, consent, and stopping charges. It is no universal rule for all offline plans or state duties. Identify actual channel and facts. Review other applicable rules separately rather than extend this statute beyond its covered scope.
The FTC March 2026 notice seeks comment and refers to the vacated 2024 amendment. It is no new operative nationwide cancellation rule. The proposed process does not itself settle current customer duties. Confirm what applies to actual plan and channel instead of relying on the vacated amendment.
Verify duties and terms before launch or transfer. Settings establish neither consent nor assignment. Assign review and communicate approved versions to sales, dispatch, and billing so promises stay consistent.
Which measures should be kept separate?
Separate current members, members active during a period, new signups, eligible renewals, paying members, cancellations, visits, and remaining benefits. These answer different questions. Set dates and event definitions before reporting. One large count can conceal different populations rather than describe the actual closing-date program.
ServiceTitan's membership-report documentation includes historical status, deferred revenue, and remaining visits. Its active-date filter includes any membership active during part of the selected window. That may differ from a closing-date count. Check settings and reconcile actual dates rather than assume every vendor field answers the buyer's question.
| Measure | Practical definition question | Evidence to reconcile |
|---|---|---|
| Current members | Active at which exact date? | Status and start/end records |
| New enrollments | Signed, paid, or both? | Agreement and payment evidence |
| Eligible renewals | Which cohort reached its renewal opportunity? | Term and cohort dates |
| Retained members | Renewed under which rule? | Renewal and cancellation records |
| Collected fees | Which receipts and refunds belong to the period? | Billing and payment records |
| Remaining benefits | What services or rights remain promised? | Terms and delivery history |
| Net contribution | Which delivery and overhead costs are included? | Reconciled cost model |
This table guides reporting, not accounting policy. Define measures, save filters, and explain changes. Check setup and exclusions so reviewers can reproduce results.
How does renewal evidence become useful to a buyer?
Track groups that reached renewal. Billing attempts differ from successful payment and ongoing rights. Review cancellations, refunds, service, and term changes. New signups can increase current members without showing annual renewal. State observed outcomes and interval before forecasting what another group may do.
The membership-churn guide examines buyer's evidence. Keep reliable history in normal work; reconstruction at sale may miss old statuses and due dates.
Young groups are not proven renewals. Compare like terms and eligible windows; explain price and benefit changes. Strong small-group results retain their scope without proving every future member behaves alike.
Record leaving reasons where known and use them to improve service or terms. Keep unknown causes separate. Do not invent motives or assume every departure has a proven remedy.
What accounting and obligation review is needed?
FASB's January 2020 staff revenue questions discuss upfront fees and stand-ready promises. Actual rights and performance duties drive review. This educational staff document is not the authoritative Codification. Use accountant's applicable framework and actual agreement rather than treat the overview as one prescribed recognition pattern for all plans.
Ask advisers to separate cash, earned revenue, and duties. Vendor fields certify no GAAP treatment and fix no incorrect setup. Accounting balance and delivery cost differ; support both.
The membership sale-price guide links economics and sale. Reconcile cost models and accounting schedules while retaining different purposes. A cash-positive signup period can leave future work. Show who performs it and which balances remain before presenting all receipts as value transferable to buyer.
What records make the program transferable?
Keep plan versions, consent, status history, payments/refunds, eligible renewals, visits, credits, benefits, and definitions. Assign datasets and dates. Preserve which terms and status applied when customer paid or received service.
The pricing-and-dispatch guide covers reports and access. Check rights, permissions, provider steps, and customer terms under proposed transfer. A spreadsheet moves records, not necessarily every relationship or permission. Test actual handover and remaining work before forecasting the entire member book under new systems.
The marketing-cost guide separates enrollment spending and retained economics. Cost both acquisition and delivery. Do not present fees as an independent value driver without showing those costs. Repeat customer activity can be useful while still needing support for margin and any claim that program caused additional work.
What sequence supports a durable program?
- Define benefits, exclusions, service expectations, and customer terms.
- Cost delivery, discounts, administration, and capacity requirements.
- Obtain appropriate review of channel, consent, renewal, and cancellation rules.
- Establish point-in-time and cohort reporting with consistent definitions.
- Reconcile fees, obligations, delivered services, and contribution.
- Retain evidence and revise the program when actual results differ.