People & HR

How to onboard a new hire as Fitness Studio Founders

People & HRFor Fitness Studio Founders3 apps11 steps~22 min to set up

You hired a new front-desk person or instructor and now you have two weeks of chaos ahead of you. Your onboarding 'process' is a folder of Google Docs nobody updates, a Slack message thread you'll have to dig out, and an afternoon of you sitting next to them walking through how to pull attendance from Mindbody, how to handle a late cancellation in ClassPass, what the studio's class-fill target is, and where the cleaning schedule lives. Every answer still runs through you. You lose billable hours, they lose confidence, and three weeks later they're still asking where to find the member churn report you built in that one spreadsheet.

Build this on Starch → See the apps used

People & HRFor Fitness Studio Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A searchable studio wiki where SOPs for Mindbody, ClassPass, and your studio's daily routines live in one place — so new hires find answers without asking you

An automated task checklist that assigns day-one through day-thirty onboarding tasks with due dates, priority levels, and overdue alerts — so nothing gets missed

An onboarding email sequence that drafts and sends the right welcome messages, system-access requests, and check-ins at the right times — so you're not manually following up

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

Knowledge Management Task Manager Email Agent

Data sources & config

Knowledge Management connects to Notion (Starch syncs your Notion data on a schedule) so existing SOPs and pages flow into the wiki automatically. Task Manager runs standalone with no external integrations needed. Email Agent connects to Gmail (Starch syncs your Gmail data on a schedule) to send welcome emails, draft check-in messages, and set follow-up reminders. Any internal tools your studio uses that are web-accessible — like your Mindbody admin portal or a ClassPass partner dashboard — can be automated through your browser with no API required.

Prompts to copy

Build me a studio wiki with sections for: daily opening and closing checklist, how to process late cancellations in Mindbody, our class-fill target (75%) and what to do when a class drops below 50%, instructor sub-request process, and member churn escalation steps. Auto-detect when a page hasn't been updated in 90 days and flag it for review.

Create a new-hire onboarding task list for a front-desk role. P1 tasks in week one: complete Mindbody login setup, shadow two morning classes, read the class-fill SOP. P2 tasks in weeks two and three: handle first solo shift, complete member check-in simulation, review churn dashboard. Set due dates relative to their start date and send me an overdue alert if anything slips.

Draft a welcome email to send to our new hire on day one. Include their first-week schedule, a link to the studio wiki, and who to contact for IT access. Also set a reminder for me to check in with them at the end of day three and day seven.

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

Walkthrough

Step-by-step

1 Open the Knowledge Management app in Starch and type: 'Build me a studio wiki with sections for our daily opening checklist, Mindbody late-cancellation process, class-fill targets, instructor sub process, and member churn escalation.' Starch drafts the structure and pulls in any existing Notion docs automatically.

2 Review and fill in the studio-specific details — your 75% class-fill target, your specific Mindbody cancellation window, the name of your lead instructor for sub requests. These are things only you know; Starch handles the formatting and findability.

3 Set the wiki's stale-content alert: tell Starch 'flag any page that hasn't been edited in 90 days.' New hires will always hit current information, not last season's schedule.

4 Open Task Manager and type: 'Create an onboarding checklist for a new front-desk hire. Week one P1 tasks: Mindbody login, shadow two classes, read class-fill SOP. Weeks two and three P2 tasks: solo shift, member check-in simulation, review churn dashboard. Start date is [date].' Starch builds the list with due dates calculated from that start date.

5 Enable overdue alerts so you get a notification — not another calendar reminder you'll ignore — if the new hire's tasks slip past their due date.

6 Open Email Agent and type: 'Draft a day-one welcome email for our new front-desk hire. Include their week-one schedule, a link to the studio wiki, and a note to reach out to me for any system access questions.' Review and send with one click.

7 Set a follow-up sequence in Email Agent: 'Remind me to check in with the new hire at end of day three and end of day seven. Draft a short check-in message each time asking how their shifts are going and whether they have any questions about Mindbody or class scheduling.'

8 If your studio uses a Mindbody admin portal or a ClassPass partner portal for reporting, tell Starch: 'Pull my weekly class attendance report from Mindbody every Monday morning and add it to my wiki under Class Fill Reporting.' Starch automates this through your browser — no API needed.

9 One week before the new hire's start date, run through the wiki and task list with Starch: 'Review my onboarding wiki and task checklist — are there any gaps for a front-desk role at a boutique fitness studio?' Starch flags missing sections like member dispute handling or emergency contact protocol.

10 On day one, share the wiki link and confirm the task list is visible to the new hire. Their entire first month is mapped: what to learn, when to learn it, and who to ask if the wiki doesn't have the answer.

11 After the first hire goes through the process, ask Starch: 'Update the onboarding wiki based on any tasks that ran over deadline or questions the new hire asked me this month.' Use their experience to close the gaps before your next hire.

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

New Front-Desk Hire — April 2026, Pilates Studio (12 instructors, 340 active members)

Sample numbers from a real run

Owner hours spent on onboarding (before Starch)	14
Owner hours spent on onboarding (with Starch)	4
Onboarding tasks assigned with due dates	23
Tasks completed on time in week one	21
Days until new hire could independently pull a Mindbody attendance report	5

Maya runs a 12-instructor Pilates studio with 340 active members. She hired a new front-desk coordinator in April and used Starch to build the onboarding setup in an afternoon. The Knowledge Management app pulled in her existing Notion docs — class scheduling rules, sub-request process, late-cancel policy — and Starch organized them into a searchable wiki with a stale-content alert set for 90 days. Task Manager assigned 23 tasks across the new hire's first four weeks, with P1 tasks in week one focused on Mindbody login and class observation, and P2 tasks in weeks two through four covering solo shifts and the member churn dashboard. Email Agent drafted and sent the day-one welcome email and triggered check-in reminders on day three and day seven. Maya spent 4 hours total on onboarding instead of her usual 14. By day five, the new hire could independently pull the weekly class attendance report from Mindbody — Starch automated the browser navigation through the Mindbody admin portal on a Monday morning schedule, no API required. Two tasks slipped past their due date; Starch surfaced both as overdue alerts before Maya would have noticed.

Measurement

How you'll know it's working

Hours owner spends on onboarding per new hire (target: under 5 hours)

Percentage of onboarding tasks completed on time in the first 30 days

Days until new hire can independently run a Mindbody attendance or billing report

Number of 'where does X live?' questions routed to the owner after week two (target: zero)

Wiki pages flagged as stale within the first quarter after publishing

Comparison

What this replaces

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

Google Docs + Notion ad hoc

Free and familiar, but there's no stale-content detection, no onboarding task automation, and the owner still has to manually share the right links with each new hire — which is the bottleneck Starch removes.

Trainual or Notion-based SOPs

Purpose-built for SOPs and onboarding paths, but doesn't connect to your Gmail for automated welcome emails or to browser-reachable tools like your Mindbody admin portal for live data, so you still manually update everything.

Gusto or Rippling onboarding flows

Good for HR paperwork and payroll onboarding, but they don't know what a ClassPass partner dashboard is or what your 75% class-fill target means — so operational onboarding still happens in a Google Doc.

ClickUp or Asana onboarding templates

Solid task tracking, but building a fitness-studio-specific checklist from scratch takes hours, and there's no wiki search or email automation in the same tool — so you're still managing three separate platforms.

On Starch RECOMMENDED

One platform — knowledge management, task manager, email agent 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

Does Starch work with Mindbody or MarianaTek for pulling class data into the wiki?

Mindbody and MarianaTek don't offer open APIs for independent studio owners, but Starch automates them through your browser — no API needed. You can tell Starch to pull your weekly attendance or class fill report from your Mindbody admin portal on a schedule and drop it into a wiki page or dashboard. It navigates the portal the same way you would.

Can the new hire access the wiki directly, or is it only visible to me?

The Knowledge Management app is designed for your team. You control what's shared and what stays private. Your new hire can search the wiki for the late-cancel policy or the sub-request process without pinging you — that's the whole point.

What if my studio's onboarding process is different for instructors versus front-desk staff?

Just tell Starch. 'Build me two onboarding task lists — one for front-desk hires focused on Mindbody, ClassPass, and member check-in, and one for instructors focused on the sub-request process, class-fill expectations, and our music policy.' Starch builds both. You're not picking from a fixed template.

Is my studio's member data or billing information stored in Starch when I use browser automation?

Starch uses browser automation to pull specific reports or data you've asked for — like a weekly class attendance export — and surfaces it in your app or dashboard. It's not archiving your entire Mindbody database. Worth knowing: Starch is not SOC 2 Type II certified yet, so if your studio handles particularly sensitive member health information, factor that into your decision.

What happens when a task is overdue? Does Starch chase the new hire or just tell me?

Right now, overdue alerts go to you. Task Manager flags when a task has passed its due date so you can follow up. You can also ask Email Agent to draft a check-in message to the new hire at that point — but the nudge starts with you, not an automated message sent directly to them.

We already have some SOPs in Notion. Do I have to rebuild everything from scratch?

No. Starch syncs your Notion data on a schedule, so your existing pages flow into the Knowledge Management app automatically. You'd tell Starch which pages to pull in and how to organize them — it doesn't replace what you've already written, it makes it searchable and surfaces gaps you might not have noticed.