← All notesMoney

Nobody decided to leave.A card just expired.

Every month, a handful of your best members stop paying you — and not one of them decided to. A card expired on holiday. A bank shipped a replacement after a breach. A fraud filter looked at a routine renewal and blinked. The member keeps booking classes, keeps showing up, and has no idea anything happened, because the one person a declined payment never notifies is the person who owns the card.

This is the quietest money a studio loses, and the cheapest to get back: these members want to stay. Nothing needs winning back — no discount, no campaign, no difficult conversation. Someone just has to notice the decline this week and send a friendly note with a link. The entire problem is that "someone" and "this week."

A month, seen from the bank statement
Maya R. · card expired on the 3rdstill booking classes
Jordan M. · card reissued, autopay misseddoesn't know
Priya S. · bank flagged the renewaldoesn't know
Revenue this month−$567, silently
recreation · demo data · three happy members, zero payments, no alarm anywhere

Why auto-pays fail — and why it isn't the member's fault

It helps to be precise about what a decline usually is, because the mental image — someone whose account ran dry — is the least common case and the worst guide to tone.

Cards expire on a schedule and nobody updates the twelve places they are stored. Banks reissue cards constantly — every breach at every retailer triggers a wave of replacements, and each new card silently breaks every subscription attached to the old one. Fraud models flag perfectly ordinary charges. A daily limit clips a renewal that happened to land on the wrong day. Genuine can't-afford-it exists, but it is one cause among several — and even then, the member usually intended to sort it out and got busy.

A failed payment is not a member deciding to leave. It is a member being unsubscribed by their bank.

Which is why this belongs in a different column from churn. A cancellation is a decision you have to change someone's mind about. A decline is plumbing — and plumbing has a repair, not a persuasion. (If you want the full case for keeping the two apart, it's in the churn piece.)

What happens to a declined renewalRenewals runevery monthMost approvethe quiet 95–98%A few declinenobody is notified✓ Worked this weekrecovers ~2× ad-hoc✗ Lost in the rushquiet cancellationThe fork is the whole game:same decline, same member — the only variable is whether anyone acts this week.what happens to a declined renewal · the ~2× multiple is our observation across studios we work with, systematic vs ad-hoc follow-up

What it costs a studio like yours

Modeled boutique benchmarks put unrecovered failed auto-pays at roughly 1% of annual membership revenue. That sounds small until you run it against a real studio's numbers:

Studio sizeMonthly priceAnnual membership revenueModeled leak, per year
150 members$169$304,000≈ $3,300
240 members$189$544,000≈ $6,000
400 members$199$955,000≈ $10,500
600 members$189$1,360,000≈ $15,000

These are modeled figures, not measurements of your studio — your version depends on your decline rate and how fast declines get worked. The leak calculator runs the same model against your own member count and price in about ten seconds. But notice what kind of money this is: not new revenue to win, just revenue you already earned, leaking through a gap in follow-through.

Where to see it in Mindbody

None of this is a Mindbody problem, incidentally: the same decline, the same silence and the same seven-day window apply on any booking platform, and the numbers behind them are the same five either way (the Mariana Tek version of this reading).

Mindbody records every one of these declines — it is a proper system of record, and the data is all there. The catch is where the decline surfaces. Whatever your version calls the screens, the failed auto-pay generally lives in two places: a payments report you have to go looking for, and an account balance that pops up at the worst possible moment — check-in, with a class about to start and a queue behind the desk.

So the decline is technically visible twice and practically visible never. The report gets pulled when someone remembers, which in a busy month is nobody. And the front desk sees it exactly when they cannot act on it — mid-rush, member standing there, class in four minutes. The kindest thing anyone can do in that moment is wave the member through, which is also how a decline quietly ages into a lost member. (This is the eighth report in the Mindbody reports piece — the one that has to come to you, because nobody goes to it.)

Where the decline surfaces · and why both fail
The payments report · complete, accuratepulled when someone remembers
The check-in screen · right person, wrong momentmid-rush, class in 4 min
What the moment needsa list that comes to you
the data exists twice; a workflow exists nowhere · that gap is the leak

The seven-day playbook

Recovery is not a clever trick; it is a small schedule, kept. The whole playbook fits in a week, and the order matters more than the wording:

The seven-day recovery timelineDAY 0DAY 1DAY 3DAY 5DAY 7Retry + checkFriendly textEmail + linkPersonal callDecidewas it temporary?with an update linkstill no rusha person, not a botpause or keepevery step this week · because next week it is a win-back, not a savethe seven-day playbook · a schedule, kept — not a clever trick

Day 0 — retry, and read the decline. A temporary decline (a limit, a network hiccup) often clears on its own; a retry catches the easy share. But do not let retries be the whole plan — the hard declines (expired, reissued) will fail every retry forever, silently.

Day 1 — the friendly text. Short, warm, zero shame: "Hi Maya — your card ending 4421 didn't go through this month, happens all the time. Here's a link to update it. See you Thursday!" Most members fix it the same day, because most members never knew.

Day 3 — the email. Same tone, same link, slightly more formal. Different channels catch different people.

Day 5 — the call. By now you are in the minority of cases: something real is going on. A person calling — not a payments bot — either resolves it or learns something worth knowing about a member who may be quietly struggling.

Day 7 — decide, deliberately. Pause or keep, on a known day, communicated. The failure mode you are preventing is the silent lapse the member discovers at the front desk, in front of a class.

Why the front desk can't do this — and it isn't their fault either

Read that schedule again and count the touches: a retry check, a text, an email, a call, a decision — per member, per decline, on the right days, in a voice that sounds like your studio. Now put it on a front desk that is also greeting a 6pm wave, untangling a booking, and selling a retail shelf. The math does not close. The follow-up loses to the rush not through negligence but through arithmetic — the same arithmetic every time, which is why the gap is so consistent from studio to studio. If you are the owner working that desk yourself, the owner-operator page is this argument written for your week.

Recovered share of declined dollars: ad-hoc vs systematicRecovered share of declined dollarsAd-hoc chasingthe baselineSystematic follow-uproughly 2× the baselineour observation across studios we work with · the multiple is the pattern — your exact rate depends on your declines

From what we see across the studios we run and work with, systematic follow-up recovers roughly double what ad-hoc chasing achieves. Nothing about that multiple is magic — it is simply what happens when every decline gets the full schedule instead of the fraction that survive a busy week's memory.

What systematic looks like when nobody has to remember

This is the specific job Xyzios does for a Mindbody studio. Overnight, it reads the studio's own booking and payment history and finds the declines. By morning, each one is on a board with the member's name, what happened, and what it is worth — and the follow-up message is already drafted in your studio's voice, queued for your approval. Nothing sends without a human saying so. Payments themselves stay exactly where they are today; Mindbody remains your system of record.

Recovery queue · Tuesday morning
Maya R. · card expired · day 1text drafted · approve?
Jordan M. · reissued card · day 3email drafted · approve?
Priya S. · resolved yesterday+$189 · in the ledger
Recovered this month$1,134 · traced
recreation · demo data · drafted, approval-gated, and every recovered dollar traced to the action that saved it

The ledger is the part owners end up caring about most: every recovered dollar is traced to the message that recovered it, so "is this actually working" is an audit, not a feeling. Revenue you already earned, back on the books, with a receipt.

Start with the size of your own leak — the calculator takes ten seconds — and if the number annoys you enough, here is exactly how the recovery works, step by step.

Straight answers

Common questions.

How much do failed payments cost a fitness studio?

Modeled boutique benchmarks put unrecovered failed auto-pays at roughly 1% of annual membership revenue — about $6,000 a year for a 240-member studio at $189 a month, and it scales with size. The real number depends on your decline rate and how quickly declines get worked, which is exactly why it is worth measuring rather than estimating.

Why do member auto-pays fail?

Mostly for reasons the member never chose: the card expired, the bank reissued it after a breach, a daily limit clipped the charge, or a fraud filter flagged a routine renewal. Genuine insufficient funds is only one cause among several. That matters because most of these members intended to stay — and many do not know the payment failed at all.

How many times should you retry a failed auto-pay?

Retries alone recover only the easy share — the temporary declines. A short schedule of two or three spaced retries is worth having, but the recoveries that move the number come from pairing the retry with a human message: a friendly note the same week, a link to update the card, a call if it is still unresolved. Silent retries followed by silent suspension is the pattern that loses members.

Should you pause a membership after failed payments?

Yes — but as a decision made on a known day, communicated to the member, not as a silent lapse discovered at check-in. A workable rule: retries and friendly messages through the first week, a personal call by day five, and a deliberate pause-or-keep decision at day seven. What you are avoiding is the member finding out at the front desk, in front of a class.

Does chasing failed payments annoy members?

Almost never, because most of them do not know the payment failed. A short receipt-style note — "your card ending 4421 didn’t go through, here’s a link, no rush" — reads as competence, not collections. The version that genuinely annoys people is the opposite: weeks of silence, then a suspended membership and an awkward conversation at the desk.

Can Xyzios recover failed payments in a Mindbody studio?

Xyzios reads the declines from the studio’s own booking data overnight, drafts the follow-up for each member in the studio’s voice, and queues it for approval — nothing sends without a human saying so. Payments themselves stay in your booking platform, and Mindbody stays your system of record. Every dollar that comes back is traced to the action that recovered it, in a ledger you can audit.

Try it on your own numbers

Every board in this piece is a screen in the product.

Shown here on demo data. Connect Mindbody and it fills with yours. The first month is $99: the whole OS, every board, hands-on onboarding.

No card today · billing starts when you're connected and say go

Every number, one screen. The studio grows.

Studio notes

A sharper studio,
one email at a time.

Occasional notes on running a tighter studio — leaks, saves, and what the numbers say. No spam, no drip campaign, unsubscribe any time.

Written by the people who build Xyzios — not a content farm. Read the latest notes →