How to Bill Coaching Clients on Retainer Automatically

To bill coaching clients on retainer automatically, agree the recurring service, use a supported client-approved payment setup and verify each collection. The arrangement also needs an owner for failures, changes and ending. Creating a subscription request is not the same as receiving money.

A retainer pays for the service in its terms. It does not automatically mean unlimited messaging, a permanent commitment or a fixed number of installments toward a one-time purchase.

This guide follows a complete fictional transition from a finished service into ongoing monthly coaching. It includes client approval, a recovered renewal failure, actual delivery and a checked stop at the end of the paid period.

Choose the collection model that fits the agreement

A corporate buyer’s invoice process can be a sound arrangement. A participant should not have to use a personal card because an employer’s purchase approval is incomplete. Match the actual buyer and supported collection route.

A monthly charge alone does not identify the model. Twelve installments toward one package differ from a rolling service that renews monthly. State which arrangement you are offering before asking the client to authorize payment.

For the commercial document, see payment plans and late-fee terms. Do not copy a universal cancellation notice period without checking the agreement and applicable requirements.

Define the service independently from the payment

List the live work, preparation, written support, resources and administration the fee covers. Give each included component a usable boundary. “Four written coaching rounds” still needs a format, submission route, response pattern and treatment of extra questions.

If calls are included, check the actual session type and allowance period. Do not assume a program’s booking allowance follows the subscription’s billing anchor, or that writing “two calls” in descriptive copy creates the required entitlement.

Define what happens to unused work, canceled appointments and provider absences. These are commercial service decisions. A renewal worker cannot resolve an unclear promise about rollover or an owed session from the previous arrangement.

Specify how additional work is requested, priced and accepted before collection. Approval of a recurring base service is not an open authorization to charge every extra request.

Use the supported recurring-payment route in Coachful

Coachful is our #1 recommendation for organizing recurring coaching payments alongside the actual client work. Choose the route that matches the person’s existing access rather than creating another enrollment unnecessarily.

For a client who already has a Program, open Clients > the joined client > Billing > Recurring payments > Start recurring payments or the plus control. In Simple mode, More options reveals Billing. The existing Program’s Purchases row also offers a Start recurring payments shortcut.

This route requires an account-backed client, Stripe connected under Payments and the appropriate Payments permission. A “Hosted” client label means the person has an app account; it does not prove they have an active paid subscription.

1. Program and price: select the existing Program. Use its recurring price or Custom price for this client, with the actual amount, currency and frequency. A custom amount does not rewrite the Program’s general price.
2. Schedule: choose Today, when they approve; an eligible free trial; or On a date. Choose ongoing payments until stopped or the supported set number of payments. Review any setup fee separately.
3. Access after stopping: select Pause access or Keep access deliberately. Pause access follows the paid-period or unresolved-payment boundary and preserves progress. Keep access means billing can stop while Program access remains.
4. Review: check Today, Then, Until and If payments stop. Create the request, then use the secure link or its email option. The client must review and approve through the supported hosted flow.

Creating the request neither charges the client nor changes access. After approval, the subscription attaches to the existing enrollment; it does not create a second copy of the client’s Program or restart their progress.

Keep payment authorization distinct from a saved card

Stripe’s current payment-method guidance distinguishes saving details from making a payment and requires consent for the intended future use. Its terms guidance includes the timing, frequency, amount determination and cancellation arrangements.

Use the actual secure approval page. Do not collect full card details in a worksheet, message or coaching note. A services agreement can describe the arrangement while the payment setup still needs its own required client action.

A scheduled first payment is also different from a successful one. Check the displayed start date and later invoice result. A saved payment method or a completed sign-in should not become a “paid” label in your own reporting.

For a new service sold through an Offer, configure the actual recurring price and What they get, then inspect fulfillment after the supported purchase. Descriptive Additional benefits do not grant content, sessions or discounts. Give free access and They already paid create no charge and do not manufacture a paid subscription.

Begin the fictional written-coaching retainer

Coach Selene works with Dev, an existing account-backed client in an individual planning Program. Their earlier one-time service ends on 31 October. Its four written reviews have all been returned, and there are no unused paid sessions, remaining reviews or old recurring charges to transfer.

They agree a new rolling retainer from 1 November. It costs £400 GBP per monthly paid period and includes four written coaching rounds, relevant Program preparation resources and the agreed client conversation. This example assumes the checked tax settings add no tax, so each total charge is £400. These are invented amounts, not Coachful prices or general tax guidance.

Each round contains one selected preparation item of up to 300 words and one coaching question. Selene returns up to 400 words, with one clarification of up to 100 words and a reply of up to 150. The clarification belongs to that round, rather than starting an unlimited new exchange.

Both submission and reply use Dev’s individual private Coachful conversation with Selene, the sole authorized coaching staff member. Company colleagues are not added to the conversation. Operational decisions and urgent matters stay with the appropriate workplace owner.

All people, dates, checks, messages and results below are fictional. They illustrate a supported workflow; the author has not performed account actions or live billing tests.

Agree actual review dates and a deliverable capacity

The November submission dates are 3, 10, 17 and 24 November, each at 12:00 UTC. Replies are due by 16:00 UTC on 5, 12, 19 and 26 November. December uses submissions on 1, 8, 15 and 22 December, with replies on 3, 10, 17 and 24 December at the same times.

A clarification must be submitted within two working days of its main reply, and Selene replies within two working days of receiving it. Their working calendar is Monday to Friday, Europe/London, excluding 25 December and 1 January. A clarification can cross a billing boundary; it remains owed under the paid round and does not require renewal or another fee. Selene checks these outstanding obligations before confirming closure.

These are four slots per paid period, not a claim that every month contains exactly four weeks. A late submission needs an explicitly agreed revised arrangement. It does not automatically extend the period or add another round. Provider-caused missed delivery would require its own agreed correction.

Selene plans 80 minutes for four twenty-minute review blocks, 20 minutes of preparation and 20 minutes of billing and coordination. That is 120 minutes, or two hours per client. Six such retainers would require twelve hours per period before other business work.

Her planning ceiling for those six clients is fifteen hours, leaving three hours of reserve. This is a capacity allowance, not a claim that every client will use exactly two hours or that automatic billing removes the need to review actual work.

Create the request and record approval without claiming collection

On 27 October, Selene selects Dev’s existing Program and Custom price for this client: £400 GBP monthly. She chooses On a date with the first payment on 1 November, continuing until either party stops it under the agreement. There is no setup fee. She selects Pause access if payments stop.

The existing authorized access bridges the remaining days of the earlier service. Creating the request does not itself extend or remove access. Selene checks the review summary and uses Email the secure link.

The card initially shows Waiting for approval. Selene does not create an invoice marked paid or enter a receipt. On 28 October, Dev opens the link, signs in, reviews the matching terms and approves using his own card through the hosted Stripe page.

Selene then checks the dated-start state and the existing enrollment. The first charge is still future. Dev’s account, Program and earlier progress remain in place, with no duplicate enrollment.

Waiting links can expire, and a request is not permanent authorization. If a person does not approve, follow the actual request state rather than silently enrolling them in the paid arrangement.

Show the complete transition confirmation

After verifying Dev’s approval, Selene sends this message in their agreed private conversation:

“Your earlier service is complete: all four reviews have been returned, with no unused paid work to carry forward. We have agreed the new monthly written-coaching retainer.

Your first scheduled charge is £400 GBP on 1 November, followed by monthly renewal until stopped under our terms. You have approved the secure setup; the first payment has not yet been collected.

Each paid period includes the four bounded rounds described in our agreement. November submissions are 3, 10, 17 and 24 November at 12:00 UTC, with replies here by 16:00 UTC two days later. Use this individual conversation for both submissions and replies.

Please use the Program’s supported payment-management route for billing details or cancellation, and send any question about the arrangement here. I will reply about administration within two working days, Monday to Friday, Europe/London, excluding 25 December and 1 January. This is not immediate operational support.”

The message reports the checked state accurately. Approval is complete, while collection remains scheduled. It also names the old service balance rather than hiding an unresolved entitlement inside a new subscription.

Verify the first invoice and actual delivery

On 1 November, the first £400 payment succeeds. Selene checks the actual subscription-linked invoice, payment record and Program access. The correct next renewal is displayed as 1 December. She does not create a duplicate manual invoice or payment log for the same native receipt.

Dev uses the four November rounds, and Selene returns each response through their individual conversation by its agreed date. Her service record distinguishes submitted, returned and any clarification completed. A form being available would not prove that feedback had been delivered.

One round concerns preparing a weekly priority request. Dev chooses a concise message asking his manager which of two competing tasks should take precedence. The manager acknowledges the request but has not decided during that review. Selene records the request sent and acknowledgment received, without calling the priority conflict resolved.

After the 12 November reply, Dev asks one clarification on 13 November about identifying the decision owner. Selene replies in their private conversation on 16 November, within the agreed working-day window. She records that round’s clarification as complete. It does not consume a fifth November slot.

All four November responses are returned. The delivery record is complete for the agreed written service, while Dev’s workplace decisions retain their actual status. Payment does not establish a coaching outcome, and useful coaching does not replace proof of collection.

Resolve a failed renewal against the same invoice

On 1 December, the renewal attempt fails. The invoice is unpaid and the request card shows Payment failed. Selene reviews the actual invoice, subscription and access deadline. In this fictional record, the Program remains available during the displayed resolution window; no universal grace duration is promised.

She sends a factual billing message through the agreed conversation: the December £400 invoice is unpaid, and Dev should use its secure payment-management route. She does not ask him to send card details or buy a second retainer.

Dev completes the required secure payment action on 2 December. Selene checks that the same December invoice is now paid for £400 and that the subscription and access have recovered. A new card entry alone would not have been sufficient evidence.

The failed attempt and successful recovery refer to one obligation. They are not two payments of £400. Selene confirms the result and continues the four December rounds, including the response due on 3 December.

If the result had remained processing or uncertain, she would have reconciled that state before offering another checkout. If it remained unpaid, she would apply the agreed service and access policy against the actual record rather than invent an indefinite free extension.

Stop at the paid-period boundary and check the result

On 15 December, Dev says he wants to finish after the current paid period. Selene confirms the request and uses Stop at end of period on the active recurring-payments card. The saved record shows the service ending at the existing paid-period boundary on 1 January, rather than renewing.

They retain the December service. Selene returns all four December responses by their stated dates, with the final reply on 24 December. There are no outstanding provider-owed rounds, live appointments or agreed rollover items.

After the saved end boundary on 1 January, Selene checks that the subscription has ended and no January renewal was collected. The Program is paused under the selected policy, with progress preserved. She checks that no other active grant retains this Program and verifies the client-facing access state.

Dev’s account and billing history remain available; stopping this service is not deleting his account. This case includes no independently granted Course or other product whose access would need a separate ending decision.

Selene sends the checked closing result:

“The retainer has ended at its saved paid-period boundary. November and December each have one paid £400 invoice, totaling £800. All eight agreed written responses have been returned, and there is no January renewal charge.

The planning Program is now paused, with your progress retained. Your account and billing history remain available. There is no outstanding review round or appointment from this service. Any future coaching will need a new agreement and the appropriate payment approval.”

This closes payment, delivery and access separately. It does not imply that stopping a subscription automatically refunds a previous payment or that all of Dev’s workplace goals have been achieved.

Reconcile the money and the work honestly

Dev’s two successful £400 collections total £800. The earlier December failure contributes zero additional cash. In this fictional ledger, actual processor fees across the two paid invoices total £16, leaving £784 before other costs and tax effects.

There are no refunds or disputes in this case. The payout record is reconciled separately; a paid invoice is not proof that a particular net amount has already reached the bank. Do not substitute a standard percentage for actual fee and payout entries.

November delivery and administration take the planned two hours. December takes 2.5 hours, including twenty extra minutes resolving billing and ten extra minutes of review. Total continuing work is 4.5 hours. One initial hour of setup brings the complete case to 5.5 hours.

£784 divided by 5.5 hours is approximately £142.55 per hour before other business costs and tax. Excluding setup would show about £174.22 per continuing-work hour, but would omit work that actually occurred. Neither number is profit or a current pricing recommendation.

The forecast of six clients at twelve planned hours remains a forecast. This single client’s extra half-hour cannot prove the future roster will fit. Selene keeps the overrun visible when deciding whether the three-hour roster reserve is enough.

Keep corporate invoices and additional work on the right route

For an employer buyer, confirm the legal purchasing entity, authorized contact, purchase-order requirements and invoice details. The participant’s email address is not necessarily the legal buyer record.

UK government guidance lists the customer’s company name and address among the required invoice details, with additional rules depending on the circumstances. Check the actual document your selected system produces. Do not assume an internal note becomes a printed billing address.

Where an external accounting system is the authoritative issuer, retain one invoice authority and reconcile the actual receipts. Creating a second payable invoice merely to show a dashboard total can duplicate the financial record.

For additional coaching work, agree the scope and payment route first. A recurring base payment does not authorize an unscheduled extra charge. A changed service agreement and the payment setup each need the appropriate acceptance.

Troubleshoot the status you actually have

Waiting for approval: confirm the client received the correct secure request and understands its terms. Use the existing request’s supported resend or copy action. Do not report scheduled income as collected.

Payment processing: wait for a definite result and reconcile. Repeated checkout requests can create a second obligation while the first outcome remains unresolved.

Payment failed: identify the invoice, secure resolution route and actual access deadline. Recovery is complete only when the relevant records support it.

Needs review after cancellation: a payment already processing can complete after a request was canceled. The supported workflow stops that subscription, but does not automatically refund it. Check the payment and any required refund separately.

A pause request: distinguish payment collection from service access. Stripe’s documentation states that pausing collection does not itself change subscription status. The platform’s Pause access choice is a different decision; verify each relevant result.

A future price change: do not silently edit an existing client’s promise. Follow the appropriate agreed change and supported billing route. For related recurring-service notices, see billing and subscription renewals.

Frequently asked questions

Does creating a recurring-payments request charge the client?

No. The client must complete the required approval. A dated first payment still needs its later collection checked.

Is a retainer the same as a payment plan?

No. A finite plan pays toward a defined purchase; an ongoing retainer renews according to its terms. Choose the workflow that matches the agreement.

Does automatic billing guarantee monthly revenue?

No. Payments can fail, be refunded or disputed, and services can end. Plan from actual collections and a realistic contingency.

Can the client keep resources after payments stop?

That depends on the chosen access policy and any other active grants. Check the specific Program and independent products rather than assuming every resource ends together.

Does stopping at period end refund the current month?

Not automatically. Ending future collection, honoring paid-through service and issuing a refund are separate decisions and records.

Explore Coachful’s features to connect recurring payments with a clearly bounded coaching service.