Customer Support

How to watch for churn risk accounts as Fitness Studio Founders

Customer SupportFor Fitness Studio Founders2 apps11 steps~22 min to set up

You run a 200-member yoga studio and you know three members are about to quit — you just can't tell which three. Mindbody gives you attendance reports that show totals, not trends. MarianaTek has no alert when someone who used to book every Tuesday hasn't shown up in three weeks. So you do what every studio owner does: export a CSV on Sunday night, open it in Google Sheets, sort by last visit date, squint, and try to remember who you haven't seen lately. By the time you've identified the at-risk members and drafted a check-in text, it's Monday morning and two of them already cancelled their memberships.

Build this on Starch → See the apps used

Customer SupportFor Fitness Studio Founders2 apps11 steps~22 min to set up

Outcome

What you'll set up

A daily churn-risk dashboard that surfaces every member whose visit frequency has dropped below their personal baseline — pulled automatically from Mindbody or MarianaTek through browser automation

An automated alert that flags members who've missed their usual class slot two or more weeks in a row and drafts a personalized check-in message for each one

A CRM view that tracks every at-risk member, logs your outreach history, and shows whether they rebooked — so nothing falls through the cracks between you, your front desk, and your instructors

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM

Data sources & config

Starch automates your Mindbody or MarianaTek account through your browser — no API needed — pulling attendance records, booking history, and membership status on a daily schedule. Gmail is connected so Starch can sync your outreach thread history directly into the CRM view. The Email Triage starter app (Email Agent is a separate coming-soon product; use the live Founder Inbox / Email Triage app here) handles drafted check-in messages queued for your review.

Prompts to copy

Pull my Mindbody attendance data every morning through browser automation. Flag any member whose visit frequency this month is more than 30% below their average from the previous 90 days. Show them in a dashboard sorted by how long since their last visit, with columns for: member name, usual class type, days since last visit, and lifetime membership value.

For each flagged member, draft a short check-in text message from me — warm, not salesy — referencing the specific class they usually attend. Queue the drafts for my review each morning at 8am and let me approve or edit before they send.

Create a CRM view called 'Churn Watch' that shows every at-risk member with a status field (flagged / outreach sent / rebooked / churned), the date I last contacted them, and a notes field where I can log what they said. When a member rebooks a class, automatically move them off the watch list.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect your Mindbody or MarianaTek account: Starch automates these platforms through your browser — no API required. Log in once inside Starch and it handles the rest on a daily pull.

2 Tell Starch what 'normal' looks like for your members: describe your prompt — 'a member who usually books 3x per week is at-risk if they drop below 1x for two consecutive weeks' — and Starch builds the detection logic.

3 Starch pulls attendance and booking data each morning and scores every active member against their personal baseline, not a studio-wide average.

4 The churn-risk dashboard surfaces flagged members ranked by urgency: days since last visit, their usual class, and their membership tier (drop-in, monthly, annual). You see this before you look at anything else.

5 For each flagged member, Starch drafts a check-in message in your voice — referencing the class they usually attend, not a generic 'we miss you' blast. Drafts queue in your inbox for one-click approval.

6 Connect Gmail from Starch's integration catalog so the agent queries your sent messages live — if you already emailed someone this week, they're skipped from the draft queue automatically.

7 Approved messages send via Gmail. Starch logs the outreach timestamp and message text back into the Churn Watch CRM view so you always know the last touchpoint.

8 When a flagged member rebooks a class, Starch detects the new booking on the next daily pull and automatically moves them from 'at-risk' to 'rebooked' in the CRM view.

9 Set a weekly automation: every Monday at 7am, Starch sends you a Slack message (connect Slack from Starch's integration catalog) with the count of members who moved off the watch list vs. those who went from flagged to churned that week.

10 Build a secondary view by instructor: 'show me which instructors have the highest share of at-risk members in their regular classes' — Starch builds this from the same attendance data so you know whether the problem is a segment of members or a specific class time.

11 Over 90 days, Starch builds a retention trend: churn-risk flags per week vs. actual cancellations. You can show this in your monthly owner review to track whether proactive outreach is moving the number.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 churn watch — 47-member studio

Sample numbers from a real run

Members flagged as at-risk (week of Apr 7)	11
Check-in messages drafted by Starch	11
Messages approved and sent (after owner edits)	9
Members who rebooked within 7 days of outreach	6
Estimated monthly revenue retained (6 × $120 monthly memberships)	720
Members who churned despite outreach	2
Members flagged but already contacted that week (skipped by Gmail check)	2

In the first week of April, Starch's morning pull flagged 11 members whose visit frequency had dropped more than 30% below their 90-day baseline. The biggest cluster was in the Tuesday 6am Vinyasa class — six of the eleven hadn't booked that slot in two weeks, which matched a pattern the owner had noticed anecdotally but never confirmed with data. Starch drafted nine check-in messages (two members had already received an email from the owner that week, so they were skipped). The drafts came through at 8am; the owner spent about four minutes editing two of them to add a personal note about an injury one member had mentioned. Six of the nine members rebooked within the week — recovering an estimated $720 in monthly recurring membership revenue that would otherwise have quietly lapsed. The two who didn't respond eventually cancelled, but both cited scheduling conflicts rather than dissatisfaction, which the owner noted in the CRM for future win-back timing. The instructor breakdown view revealed that four of the six Tuesday Vinyasa at-risk members had joined specifically for that instructor, who had subbed out twice that month — a piece of context that changed how the owner handled substitute scheduling going forward.

Measurement

How you'll know it's working

Member visit frequency vs. personal baseline (30-day rolling, per member)

Churn-risk-to-rebooked conversion rate from proactive outreach

Days since last visit for at-risk cohort (median and worst case)

Revenue at risk per week (flagged members × their membership tier value)

Instructor retention correlation: share of at-risk members by class and instructor

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Mindbody built-in reports

Shows aggregate attendance totals but has no per-member trend detection or automated outreach — you still have to export and sort manually to find who's slipping.

MarianaTek analytics dashboard

Better than Mindbody for class fill rates but still doesn't flag individual members against their personal baseline or integrate with your outreach workflow.

Google Sheets + manual CSV export

Flexible but entirely manual — Sunday night exports mean you're always reacting to churn that happened a week ago, and there's no connection to Gmail or your messaging workflow.

Gymdesk or Glofox CRM add-ons

Designed for larger gym chains; the churn alerts are based on fixed thresholds (e.g., '30 days no visit') rather than each member's individual pattern, which means you miss early signals on your most consistent members.

ActiveCampaign or Klaviyo for automated follow-ups

Good at sending sequences but requires you to define segments upfront in the email platform — there's no live connection to your attendance data, so the trigger logic is always lagging behind reality.

On Starch RECOMMENDED

One platform — crm, founder inbox all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Mindbody and MarianaTek don't have open APIs for independent studios. How does Starch actually get my attendance data?

Starch automates your Mindbody or MarianaTek account through your browser — the same way you'd log in and pull a report yourself, just automated on a daily schedule. You log in once inside Starch and it handles the session from there. No API key needed, no special plan required with your booking software.

What happens if Mindbody changes its interface and breaks the automation?

Browser automation can break when a site updates its layout — that's an honest limitation. Starch monitors for failures and will alert you if a pull doesn't complete. For a critical daily workflow like churn watching, you'd want to check your dashboard is updating each morning until you've built confidence in the cadence.

Can Starch actually send the check-in texts to members, or just draft them?

Starch drafts the messages and queues them for your review via Gmail — you approve and send with one click, or edit first. Sending SMS directly from Starch to members isn't a current workflow, but if you use a text platform that has a web interface (like a SimpleTexting or EZTexting account), Starch can automate submission through your browser. Describe what tool you use and Starch will tell you what's buildable.

Is this only useful for studios with hundreds of members? We have 60 active members.

60 members is actually the sweet spot. You probably already know most of them by name, which means Starch's drafts will feel accurate to you and you'll edit them quickly. The value isn't replacing your memory — it's making sure you catch the quiet early signals before someone cancels without a word.

Does Starch store all my member data? What about privacy?

Starch is not SOC 2 Type II certified today — that's worth knowing. Member names, visit history, and contact details pulled from Mindbody or MarianaTek will be stored in Starch's database to power the dashboard and CRM. If your membership agreement or local privacy rules create constraints on third-party data storage, check those before connecting.

Can I track which instructors are driving the most churn risk?

Yes — describe the view you want and Starch builds it. For example: 'Show me the share of at-risk members by instructor for the past 60 days, broken out by class type.' You can combine this with class fill rate data from the same Mindbody pull to see whether at-risk members are concentrated in specific timeslots or with specific teachers.

What's the difference between using this and just setting up a Mindbody automation email?

Mindbody's automated emails trigger on fixed conditions — 'no visit in 30 days' — applied the same way to every member. Starch's detection is per-member and relative: someone who usually comes four times a week gets flagged after two weeks of absence; someone who comes once a month doesn't get flagged at all until they've missed two or three months. That distinction matters a lot in a boutique studio where you know your members' individual habits.