When a card fails on the 1st, or a client asks to pause mid-project, the work should follow a rule you wrote down in advance. Below is one rule for each commercial event, what happens to the active request, the message to send, and how to keep good clients without discounting. The active request keeps moving for a short, stated grace period. A pause stops the next charge and parks the work on an agreed date. A cancellation runs to the end of the paid month.
Write one rule per commercial event
A design subscription has five money moments: renewal, failed payment, pause, cancellation and downgrade. Most studios write a rule for renewal and improvise the other four. That is how a client on £3,000 a month ends up with a designer working on an unpaid invoice. Or a half-finished homepage quietly stops moving.
Put the rules in one table. It goes in your terms, your onboarding email and the pinned note of each client's Slack channel. That way everyone reads the same version.
| Event | Active request | Queued requests | What the client can still access | Who tells them |
|---|---|---|---|---|
| Renewal succeeds | Carries on, no change | Stay in order | Everything | Nobody; Stripe sends the receipt |
| Payment fails | Carries on through the grace period, then pauses | Wait until payment clears | Board, delivered files, Slack channel | Account owner, same day, in the client's channel |
| Payment recovers | Resumes from where it stopped | Move up in the same order | Everything | Account owner, with a new delivery date |
| Pause | Finished, parked or handed back, as your pause policy says | Held in place, not deleted | Board read-only, delivered files | Account owner, confirming the restart date |
| Cancellation | Worked on until the paid period ends | Closed on the end date | Files until handoff, then a final export | Founder or account owner, in writing |
| Downgrade | Finished on the current tier | Re-checked against the new tier's limits | Everything | Account owner, before the next invoice |
Avoid using "pause" for several different arrangements without describing which obligations stop. If one client's pause means "no charge, keep my slot" and another's means "half price, slower turnaround", you have two products with one name. Someone will end up billed for the wrong one. Before you publish the table, read your sales page, your terms and Stripe's customer emails side by side. They should say the same thing about dates.
When a card fails on a £3,000 invoice
A payment failure should create an owned follow-up, not an unexplained disappearance of work. The usual mess looks like this: Stripe marks the invoice past due. The Trello card still says "in progress", the designer does not know, and the client only notices when their banner set stops moving. Nobody decided anything. The work simply went quiet.
Here is an example policy, not an industry norm: work continues for three working days after a failed payment, then the active request pauses. Queued requests wait. Files already delivered stay with the client. If a card fails on a Monday, the designer keeps going until Wednesday evening. If the payment has cleared by Thursday morning, the client never notices. If not, the request is parked with a note on the card saying where it stopped.
Three working days suits a client paying £2,500 to £4,000 a month. Most failures are an expired card or a finance team that missed an email. Pick your own number, but pick one and publish it.
Send this the same day the charge fails, from a person, not only from Stripe:
Hi Priya, this month's payment did not go through, probably an expired card. Nothing changes today. We will keep working on the pricing page until Wednesday. If the card is updated by then, you will not notice a thing. If not, we will park the pricing page exactly where it is and pick it straight back up once payment clears. Stripe has sent you a link to update the card.
Keep card details, bank names and invoice amounts out of request comments and the design board. They belong in the billing tool and a direct message to whoever pays.
Stripe's automatic retries and reminder emails are settings in your own account. Their defaults may not match the grace period you promised. Check them, then run a test failure before a real client has one. The billing software guide shows how to test a failed payment. On fees, Stripe Billing in the UK takes 0.7% of billing volume on pay as you go. Or it starts at £450 a month (about $600) on a one-year contract (Stripe pricing). On a £3,000 invoice that 0.7% is £21 (about $28), before card fees. ManyRequests, Zendo and Wayfront can also bill inside their client portals. Their pricing pages are on the ManyRequests, Zendo and Wayfront sites. Comparing them only makes sense if the portal already runs your requests, and the billing and subscriptions comparison covers what each one costs.
Pauses and cancellations in brief
Most subscriptions advertise flexibility. DesignJoy lists "Pause or cancel anytime" on its Monthly Club at $4,995 a month (designjoy.co). It also offers "75% back, no questions asked" within 7 days. The page does not say how pause days are counted. That promise sells well, and the detail usually gets written the first time a client asks.
For a pause, write down four things. When the next charge stops, whether the client keeps their capacity slot, what happens to the half-finished request, and the latest restart date. If you charge anything to hold the slot, put the amount on the sales page, not only in the terms. If your terms promise a refund window like DesignJoy's seven days, decide whether a pause clock counts against it before a client asks.
For a cancellation, the paid period runs out and the work runs with it. Make cancellation and final handoff clear even when the client is leaving. Name the date access to the board ends and share a Google Drive folder with every approved source file. Then send one closing message listing what was delivered. A client who leaves with their files and a clear final message is the one who comes back for the next rebrand.
What if the pause or cancellation lands with a request half done? The worked calendars for a mid-request pause or cancel show three pause policies side by side, plus two replies you can adapt.
One sequence for failed payments, pauses and downgrades
Whether the card failed, the client paused or they asked for a smaller tier, run the same sequence. It stops billing and delivery drifting apart.
- Confirm the event where it happened: the failed invoice in Stripe, the pause request in email, the cancellation in writing. Note the effective date and the account owner.
- Check the rule against current work. Find the active request, any open revision round and any promised file handoff.
- Tell the client what changed, what they still have and what they need to do, in one message. Make sure it agrees with any automatic email Stripe sends.
- Change delivery and access to match: move the card, adjust board permissions, update the queue. Send anything disputed or unclear to a named person instead of guessing.
- Reconcile billing and the queue the same week. On restart, recheck the brief and your capacity instead of promising the old delivery date.
Keeping clients without discounting
Nobody publishes churn or retention figures for design subscriptions, so we will not give you a benchmark. Track your own: who paused, who cancelled, and what they said in the last month before they did.
The earliest warning is usually the queue. A growing unused queue may signal incomplete briefs, changed needs or a capacity mismatch. An empty queue for two weeks says something too. Either way, book fifteen minutes and ask what is blocking them. Common answers: the marketing lead who wrote the briefs left, or a launch slipped a quarter. Sometimes they send small jobs to a freelancer because your turnaround feels slow for quick edits. Each has a fix that costs you less than a discount.
When a good client says the price is too high, offer a smaller tier only if your capacity maths allows it. Say a designer carries four clients at £3,500 a month, £14,000 on one seat. Drop one client to £2,500 while they still send a request a day. You have cut £1,000 without freeing any time. A smaller tier needs a real limit, such as one request every other working day or no web builds. Run the numbers in the pricing and capacity worksheet. Check the designer's load against capacity and profitability per designer, then write the new limit into the offer using how to define scope and price a design subscription.
A percentage off to stop a cancellation teaches every client that threatening to leave pays. A pause, a smaller tier with smaller scope, or a clearer brief keeps the price honest.