How to sell maintenance plans online

A maintenance plan sold online follows one path: a defined package, a storefront where the customer chooses it, checkout with the payment provider you connect, and then renewals, changes and invoices after the first payment. This guide follows one example from start to finish. Set the price and scope from your own numbers first; the pricing guide covers that step.

Quick answer

To sell a maintenance plan online, define the package with its scope, price, billing period and exclusions, publish it on a storefront, let the customer pay through a checkout connected to your provider, and then manage renewals, plan changes and invoices as the plan runs. Give each step a clear owner, because the first payment is only the start of the relationship. Komashi covers the offer, the storefront, the checkout and the subscription workflow. Payments run through the provider you connect, and Komashi does not process payments or hold customer funds.

Define the package

Write what the customer buys: the covered work, cadence, response expectations, billing period and exclusions. Set the recurring price and any one-time setup charge as separate lines. In Komashi this is one service with its packages, billing periods and optional add-ons.

Publish the storefront

The storefront shows each package with its price, billing period and included services before the customer chooses. Keep names and exclusions identical to your agreement, so the customer does not see one scope on the storefront and a different one in the contract.

Take payment through a connected provider

The customer selects a package, reviews the recurring total and any one-time charges, then continues to the provider you connected. Stripe runs a hosted checkout; Barion, Mollie and PayPal send the customer to their own payment page. Bank transfer and cash orders count as paid only after a payment reference and admin approval.

Manage renewals, changes and invoices

After the first payment the plan runs on its subscription record. Customers can see their plan, its status and invoices where the provider supplies a PDF. Upgrades apply now with a prorated charge, downgrades take effect at renewal, and cancellation ends the subscription at the end of the current period unless your provider is set to end it at once.

One example from storefront to renewal

Hypothetical example with illustrative values. A small web studio sells Care Plus at $190 per month, with a $150 setup charge once and an Extra pages add-on at $30 per month. Step 1: the studio writes the scope and exclusions and sets the billing period to monthly. Step 2: the storefront shows Care Plus with its price and the add-on. Step 3: the customer pays through the provider checkout, $340 before tax for the setup and the first month. Step 4: a month later the customer asks for Extra pages, the studio adds it to the subscription, and the monthly total becomes $220. Step 5: invoices for each charge stay on the customer record where the provider supplies a PDF, and any downgrade waits for the next renewal.

Three mistakes that create support work

  1. The storefront and the agreement disagree

    If the storefront shows a different scope or exclusion from the contract, the first request for extra work becomes a dispute.

  2. Setup and recurring prices are mixed

    The customer cannot tell what repeats, so the renewal and the invoice look like a surprise.

  3. No owner for changes

    Changes, cancellations and failed payments need a named person. Without one, a request waits in a message thread until the customer leaves.

How Komashi fits

Komashi connects the offer, storefront, checkout and subscription record for a service. You set the packages and billing periods, connect a supported provider, and manage plan changes from the subscription. Komashi does not process payments: customers pay through your connected provider, and bank transfer and cash need admin approval before they count as paid.

See the checkout

What to check before you go live

  • Each package states its covered work, cadence, response expectations and exclusions.
  • The storefront and the agreement describe the same scope and price.
  • You have confirmed how renewals behave with the provider you use.
  • Setup and other one-time charges are shown separately from the recurring total.
  • A named person owns plan changes, cancellations and failed payments.

Ready to put this into practice?

Create a service with Komashi.