LESSON 12 / 14 · FREE BUSINESS COURSE
A recurring subscription creates recurring responsibilities. Customers need the service to work next week as well as on signup day. A short, dependable routine makes those responsibilities visible before urgent requests consume all your time.
By the end: design a manageable operating routine for support, billing, maintenance and customer retention.
Begin with four daily signals
Review availability, new customer activation, payment exceptions and unanswered support requests. Decide which events need an immediate alert and which belong in a scheduled review. A failed signup may need attention sooner than a small change in weekly traffic.
Give alerts an owner and an action. A monitor that sends hundreds of ignored messages creates noise without improving reliability. Define how you will recognize an incident, confirm who is affected and keep customers informed while investigating.
For FitSite, a morning check could confirm that existing sites respond, newly created sites have the right template, billing events were processed and support messages have owners. A reporting SaaS would substitute successful data imports and report delivery for site provisioning. Follow the customer’s task through the system.
Promise support you can deliver
Set clear support channels, coverage hours and response targets. A response target means acknowledging and assessing a request; it is not a promise to resolve every issue within that time. Distinguish a general question from an outage affecting access or payments.
The original guide illustrates different support levels by plan. Use that idea only when you have capacity to honor it. A four-hour promise is misleading if you work alone and do not provide that coverage. Describe business hours and time zone explicitly instead of letting customers assume continuous availability.
Create a short intake checklist: affected account, task attempted, observed result and time of failure. Ask for only the information needed to investigate. Never ask a customer to email a password or full card details. Give support staff access appropriate to their responsibilities.
Turn repeated requests into product improvements
Tag recurring questions and look for the underlying cause. Several customers asking how to change a timetable may indicate a missing help article, a confusing screen or a task the product does not support well. Writing documentation is one response, not the answer to every usability problem.
An effective help article names the task, shows the current steps, explains how to recognize success and offers a next step if it fails. Recheck it after changing the product. Keep a route to a person for cases that do not fit the article.
Suppose an illustrative FitSite support review finds six questions about adding a trainer. The team could improve the relevant template instructions, watch someone attempt the task, and compare subsequent requests. Do not claim that a help article reduced support unless you have measured that result.
Reconcile billing and access
Recurring billing depends on the configured gateway, subscription settings and payment events reaching your application. Automation does not remove the need to review exceptions. Compare the membership state with the payment record before manually changing access or issuing a refund.
A failed payment can have several causes. Check the provider’s actual decline or event information rather than assuming it is an expired card or an intentional cancellation. Use the provider’s supported retry and customer-notification settings, and explain how the customer can update payment details through a secure route.
For the WordPress track, review Ultimate Multisite memberships and payments alongside your gateway records. Verify upgrades, downgrades, trial endings and invoices on your configured version. Check the timing of changes and any prorations rather than promising that every plan change behaves identically.
Keep cancellations straightforward. Confirm the effective end date, future billing state and any export or retention arrangements. An optional feedback question can help you learn, but cancellation should not depend on answering it. Apply refunds consistently with the terms you actually offered.
Maintain a service you can recover
Schedule routine maintenance and keep a path for urgent security updates. Do not postpone every update until a monthly meeting. Prioritize according to the issue and exposure, test as safely as possible, and maintain a recovery plan if a change causes trouble.
For WordPress Multisite, a shared plugin or theme change may affect many customer sites. Test representative plans, templates, checkout and access on staging. Use data protection and access controls appropriate to the staging copy; a test environment should not expose customer information.
Maintain backups of database content and necessary files, and test restoration. Record recent successful restores, not merely successful backup jobs. Keep monitoring for resource exhaustion, failed background work and delivery errors as well as whether the home page loads.
Learn why customers stay or leave
Define customer churn for a stated period: customers lost during the period divided by active customers at its start. Record your counting rules, including how you treat pauses and unpaid accounts. Revenue churn is a different measure and should be labeled separately.
If an illustrative business starts a month with 50 customers and loses two of them, customer churn for that group is 4%. New customers acquired during the month do not change that starting denominator. With small numbers, one cancellation can move the percentage sharply, so review individual reasons too.
Separate product problems, budget changes, business closures and customers who never reached their first useful outcome. Offer help or an appropriate plan when relevant. Do not assume a discount solves a missing feature, and respect communication preferences before sending return offers.
Recommend upgrades when a customer has a relevant need and understands the extra cost. Hitting a limit may be an opportunity to clarify the right plan, but the message should not hide the option to reduce usage or stay on the current tier.
Give the routine a calendar
Daily checks handle availability, urgent support and billing exceptions. Weekly reviews look for unresolved tickets, activation failures and recurring problems. Monthly reviews examine recurring revenue, costs, retention and documentation. Quarterly reviews revisit pricing, capacity and whether the offer still fits the audience.
Use this cadence as a starting point, then adapt it to the service’s risk and workload. A business processing time-sensitive bookings needs different monitoring from a monthly research subscription. The purpose is to prevent work from disappearing between responsibilities, not to create meetings for their own sake.
Your exercise: write an operating sheet
Create four sections: monitoring, support, billing and maintenance. For each, name the owner, frequency, evidence to check and the action for an exception. Include a backup owner for important tasks.
Draft your support promise in plain language, including hours and the difference between first response and resolution. Then check whether your current schedule can support it during illness or holidays.
Choose one recurring customer task and write a help article. Test it with someone unfamiliar with the product. Record whether they complete the task without extra explanation.
Finally, rehearse one incident on paper: a customer has paid but has no access. List the records you would compare, how you would communicate, and how you would confirm recovery without issuing a second charge.
Before you move on
Sustainable operations combine ownership, clear promises and recovery. Automate dependable steps, review exceptions and use customer questions to improve the experience. Track retention with explicit definitions rather than relying on a dashboard label alone.
Sources and further reading
Adapted from the original Lesson 12: Running the Business. FitSite is an illustrative business used for learning, not a customer success story. WordPress backup guidance explains the components of a restorable installation.