The first membership-onboarding question should not be “Which plan do you want?”

One-line takeaway

A membership goal is a design constraint; it should change the rules the company configures and the failures it watches.

Source-backed signal

Housecall Pro's Service Plans starter kit asks for the goal of the program before it moves into payment timing, sales strategy, reminders, dashboard use, visit scheduling, and billing.

The guide lists predictable revenue, long-term customer loyalty, and operational efficiency as possible goals. It describes pay-now and pay-later structures as different choices: pay now can collect monthly or annual revenue in advance, while pay later collects after completed work and allows more job-level pricing flexibility.

The setup does not end with a plan template. Housecall Pro's dashboard documentation separates plan status, recurring revenue, due-for-billing items, and unscheduled visits. Its visit-scheduling guide documents the additional work of scheduling a promised visit, linking it to a job, and marking or associating completed work.

Source boundary: this is one software vendor's setup framework, not a universal membership model or proof that a particular goal, payment structure, price, visit cadence, or configuration is right for every HVAC company.

Interpretation

Interpretation, not a sourced fact:

“Which plan do you want?” is too late to be the first onboarding question.

Before choosing tiers, prices, payment cadence, recurring services, or reminders, the operator should choose the program's primary job. Revenue stability, retention, capacity smoothing, and pull-through work can coexist, but they create different design pressure. Treating all of them as equally primary makes it easier to configure benefits without deciding which operating tradeoffs the company is willing to manage.

No single goal produces the one correct membership. The goal is useful because it makes downstream decisions testable:

• Revenue stability — What collection timing, failed-payment state, cancellation rule, and cash-flow measure support the intended model?
• Retention — What customer promise, communication rhythm, renewal state, and fulfillment measure show whether the relationship is being maintained?
• Capacity smoothing — What service windows, scheduling rules, exception paths, and workload measure protect the intended seasonal rhythm?
• Pull-through work — What covered-equipment data, visit findings, customer permissions, human handoffs, and attributed outcomes connect maintenance to appropriate future work?

These are decision lenses, not claims that the four goals are exhaustive, mutually exclusive, or equally valuable for every operator.

Operator lesson

Write the primary job in one sentence before opening the FSM setup screen.

Then translate that sentence into the customer promise and the operating rules required to keep it. A company choosing capacity smoothing as the primary job may need tighter service windows and exception rules than one prioritizing customer retention. A company prioritizing revenue stability may care more about collection timing and failed-payment ownership. A pull-through model needs reliable equipment and visit data plus permissioned human follow-up; a plan sale alone does not establish an opportunity.

Payment architecture is part of the offer, not a back-office detail. Pay now and pay later change when money is collected, how work is priced, what the customer expects, and which administrative states must be managed. Monthly and annual timing add another choice. The guide describes available options; the operator still has to test them against the agreement, margin, accounting treatment, customer experience, and team's ability to fulfill the promise.

The onboarding output should therefore be a short operating decision record—not just a configured template:

• primary job;
• customer promise;
• payment and visit rules;
• known exception states;
• accountable owners; and
• one measure that would reveal whether the design is working.

Practical playbook

1. Choose one membership type and one customer cohort. Do not mix legacy plans, billing structures, or service promises in the first decision.
2. Write one primary job: revenue stability, retention, capacity smoothing, pull-through work, or another operator-defined purpose. List other desired outcomes as secondary.
3. Write the customer promise in plain language. Name what is included, when it should happen, and what is not promised.
4. Compare payment structures before configuring one. Document collection timing, pricing flexibility, failed-payment handling, cancellation or refund escalation, accounting review, and customer communication.
5. Map the full operating loop: selling, activation, billing, reminders, visit scheduling, fulfillment, exceptions, renewal, and reporting. Give every queue an owner.
6. Configure the FSM only after the decision record exists. Preserve unknown as a state; do not let blank fields count as successful billing, fulfillment, or renewal.
7. Trace ten same-type records through the configured loop. Ask whether the rules actually support the primary job and customer promise.
8. Review after one operating cycle. Change a rule only with evidence from the selected cohort, and record the reason for the change.

Do not use the primary goal to excuse an unprofitable offer, an unclear customer promise, unowned exceptions, or unsupported accounting assumptions. It is the first design constraint, not the entire operating system.

Email version

The first membership-onboarding question should not be:

“Which plan do you want?”

Ask what job the program needs to do first.

Is the primary job revenue stability, retention, capacity smoothing, pull-through work, or something else the operator can state clearly?

That choice should affect payment timing, visit rules, reminders, ownership, and the metric the team watches. Pay now and pay later are not just billing settings. Service visits are not complete because a recurring template exists. Selling, activation, collection, scheduling, fulfillment, renewal, and reporting form one connected operating system.

Choose one primary job. Write the customer promise. Map the rules and owners. Then configure the FSM and trace ten records through the loop.

No single configuration is right for every company. The useful test is whether the configured rules support the job this program is supposed to do.

LinkedIn post

The first membership-onboarding question should not be:

“Which plan do you want?”

Start with:

“What is this program's primary job?”

• Revenue stability
• Retention
• Capacity smoothing
• Pull-through work
• Another clearly defined purpose

The answer should change the payment model, visit timing, exception rules, ownership, and measurement.

Pay now and pay later are not cosmetic settings. A recurring-visit template is not fulfilled work. Selling, billing, reminders, scheduling, fulfillment, renewal, and reporting are connected.

There is no universal best configuration. There should be a visible reason behind the one you choose.

Short post / thread starter

Choose the membership program's primary job before configuring its plans. If the goal does not change payment, visit, ownership, or measurement rules, it is still a slogan—not a design constraint.

Community-answer suggestions

• Ask the operator to name one primary job and keep other desired outcomes secondary for the first design pass.
• Ask how the chosen job changes payment timing, visit rules, ownership, or measurement.
• Separate the documented customer promise from internal growth expectations.
• Compare pay-now and pay-later structures without prescribing one universal model.
• Ask who owns due billing, unscheduled visits, failed payments, exceptions, and renewals.
• Suggest tracing ten same-type records before changing tiers or adding plan volume.
• Preserve unknown states and require evidence before calling a transition complete.
• Keep accounting, concessions, disputed charges, and unusual fulfillment under qualified human review.

Sources

• https://help.housecallpro.com/en/articles/5232530-service-plans-starter-kit
• https://help.housecallpro.com/en/articles/2932107-service-plans-dashboard-overview
• https://help.housecallpro.com/en/articles/3075085-schedule-service-plan-visits