Customer Support

How to run customer qbrs as Educators, Coaches, and Course Creators

Customer SupportFor Educators, Coaches, and Course Creators2 apps12 steps~24 min to set up

Every six weeks you finish a cohort and tell yourself you'll do proper check-ins with students before the next one. Instead, you spend three hours manually pulling who paid what from Stripe, cross-referencing Notion for module completion, scrolling through Calendly to see who's booked a call, and reading Gmail threads to remember what each person said last time. You build a Google Sheet that's out of date by Thursday. The QBR never happens, or it's a fifteen-minute call where you wing it because the prep took longer than the meeting. Enterprise customer success tools assume you have a CS team. You have yourself.

Build this on Starch → See the apps used

Customer SupportFor Educators, Coaches, and Course Creators2 apps12 steps~24 min to set up

Outcome

What you'll set up

A per-student review dashboard that pulls payment history from Stripe, module progress notes from Notion, and calendar touchpoints from Calendly into one place — ready before every call

A meeting notes workflow that transcribes each QBR, extracts action items, and writes a follow-up email draft so nothing falls through after the call ends

A recurring automation that builds your QBR prep doc each week without you touching a spreadsheet

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 Meeting Notes

Data sources & config

Starch syncs your Stripe data on a schedule (charges, invoices, subscription status) and syncs your Notion databases on a schedule (curriculum pages, student progress records). Calendly bookings are synced on a schedule. Gmail is synced on a schedule for email thread history. Zoom is connected from Starch's integration catalog; the agent queries it live when pulling call records. The weekly prep-brief automation runs on a Monday morning schedule and writes output back to Notion.

Prompts to copy

Build me a student CRM where each contact has fields for: cohort name, enrollment date, Stripe payment status, modules completed (pulled from Notion), last Calendly call date, and a notes field I can update after each QBR. I want to be able to filter by 'haven't had a call in 60+ days' and 'completed less than 50% of the curriculum'.

After each student QBR call on Zoom, transcribe the conversation, write a 5-bullet summary with the student's main wins and blockers, extract any action items with owner and due date, and draft a follow-up email I can send within 24 hours.

Every Monday morning, pull next week's Calendly bookings tagged as QBR calls, look up each student in my CRM, and generate a one-page prep brief per student showing their payment history, module progress, and notes from our last session.

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

Walkthrough

Step-by-step

1 Connect Stripe — Starch syncs your charges, invoices, and subscription data on a schedule so you always have a current picture of who has paid, who is on a payment plan, and who has a failed charge before you get on a call.

2 Connect your Notion workspace — Starch syncs your curriculum databases on a schedule, so module completion data and any student notes you keep in Notion are available to the CRM without manual copying.

3 Connect Calendly — Starch syncs your bookings on a schedule, giving you a timestamped record of every student touchpoint so you can see exactly how long it's been since anyone spoke to a given person.

4 Connect Gmail — Starch syncs your messages on a schedule and the CRM surfaces the relevant email thread history for each student so you're reading their last message, not guessing what you talked about.

5 Open the CRM starter app and tell Starch how your student relationships actually work: cohort names, milestone fields, payment plan status, whatever you track. The CRM shapes itself to your schema, not the other way around.

6 Set up the Monday morning prep-brief automation: Starch pulls next week's QBR bookings from Calendly, looks each student up in the CRM, and assembles a one-page brief per person — Stripe status, Notion module progress, last call date, open action items from previous meetings.

7 Start each QBR call with the prep brief already in front of you. You're opening with 'I see you finished module 6 last week and you mentioned cash flow was tight — how's that looking now?' instead of 'so, remind me where we left off.'

8 Run Meeting Notes during the call. It transcribes in real time; you stay in the conversation instead of typing.

9 After the call ends, Meeting Notes generates a summary with key decisions and blockers, extracts action items with owners, and drafts a follow-up email you can send or lightly edit.

10 Action items and session notes are written back to the student's CRM record automatically, so the next prep brief six weeks from now includes what was agreed today.

11 At the end of each cohort, ask Starch: 'Which students had no QBR call in the last 60 days, completed less than 60% of the curriculum, and have a Stripe charge that failed in the last 30 days?' — you get a real list, not a canned report, and you can act on it before the refund request arrives.

12 For students who consistently re-enroll or refer others, use the CRM's filter to build a list and hand it to your ConvertKit or Mailchimp sequence — connect either from Starch's integration catalog and the agent queries it live when the automation runs.

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

Spring 2026 Cohort QBR Week — 18 students, 6-week course

Sample numbers from a real run

Students with QBR calls booked (Calendly)	12
Students with 0 QBR calls in 45+ days (CRM filter)	6
Students below 50% module completion at week 4 (Notion sync)	4
Students with a failed Stripe charge in last 30 days	2
Action items extracted by Meeting Notes across all calls	31
Follow-up emails drafted automatically (sent same day)	12

It's Thursday of week 4 in your spring cohort. Starch's Monday prep brief already told you that 6 of your 18 students haven't had a call since week 1, and 4 of those 6 are below 50% on the curriculum — two of whom also had a Stripe payment fail last week. You've already sent a personal check-in email to those two before they even thought about a refund. For the 12 students with QBRs booked this week, each call starts with a brief that shows their Stripe status (paid up or on plan), which Notion modules they've finished, what was discussed last session, and any open action items from that call. After a 30-minute call with a student named Priya, Meeting Notes surfaces that her main blocker is finding time to implement lesson 7, she wants an accountability partner, and she asked for a worksheet template. The follow-up email draft is ready in under two minutes: it thanks her, names the accountability partner idea as a next step, and links the worksheet. Priya replies the same afternoon saying it's the most useful coaching call she's had. You ran 12 calls this week and sent 12 follow-ups. Last cohort you sent 3, two days late.

Measurement

How you'll know it's working

QBR completion rate per cohort — percentage of enrolled students who had at least one live check-in call before the cohort ends

Days since last touchpoint — median and worst-case across active students, tracked in the CRM

Module completion rate at midpoint — percentage of students past 50% of curriculum by week 3 or 4, as a leading indicator of refund risk

Action item close rate — percentage of action items extracted by Meeting Notes that are marked resolved by the next call

Cohort renewal or upsell rate — percentage of students who re-enroll in the next cohort or buy a follow-on offer, tracked in Stripe and CRM

Comparison

What this replaces

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

Google Sheets + manual copy-paste from Stripe and Notion

Free and familiar, but the sheet is outdated within 48 hours, you build it from scratch every cohort, and it tells you nothing you didn't already type in.

HubSpot Starter

Real CRM with good pipelines, but the schema is built for B2B sales deals, not student journeys — you'll spend more time configuring it to fit your cohort model than running QBRs.

Notion CRM template

Lives where your curriculum already lives, which is convenient, but there's no automation, no Stripe sync, and no meeting notes — you're still doing the prep work by hand before every call.

Kajabi or Teachable's built-in student tracking

Shows you login frequency and lesson completion inside the platform, but it has no awareness of your Calendly calls, your Gmail threads, or your Stripe payment plans — it can't tell you who to call this week.

Otter.ai or Fireflies for meeting notes alone

Good transcription, but the notes live in a separate tool with no connection to your student records — you still have to manually move action items somewhere useful after every call.

On Starch RECOMMENDED

One platform — crm, meeting notes 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

My course platform is Kajabi — can Starch pull student data from it?

Kajabi isn't in the scheduled-sync provider list today. The practical path is to keep Stripe as your payment source of truth (Starch syncs it on a schedule) and Notion or Google Sheets as your progress tracker (both sync on a schedule). If you want to pull data directly from Kajabi's dashboard, Starch can automate that through your browser — no Kajabi API needed. For most solo operators, Stripe plus Notion covers 90% of what you actually need for a QBR.

I use Teachable or Thinkific instead of Kajabi — same answer?

Same answer. Stripe is the cleaner source of payment truth regardless of which course platform you use. For completion data, whatever you track in Notion, Airtable, or Google Sheets — all reachable. Starch connects Airtable and Google Sheets from its integration catalog; the agent queries them live when your CRM or automation needs the data.

Does Starch store all my student call transcripts? Is that a privacy issue?

Meeting Notes transcripts are stored in Starch. Starch is not SOC 2 Type II certified today — that's worth knowing if you have enterprise clients or handle sensitive personal information. For most coaches and course creators running personal-development or skills-based programs, this is the same posture as using Otter.ai or Zoom's built-in transcription. If your program deals with health, therapy, or legally protected information, flag that before proceeding.

Can Starch send the QBR follow-up emails automatically, or do I have to review them first?

Both options are buildable. You can tell Starch to draft the email and hold it for your approval before sending — most operators prefer this for personal coaching relationships. Or you can tell Starch to send automatically for lower-stakes follow-ups like 'here's the worksheet we discussed.' Just describe which you want when you set up the workflow: 'After each QBR, draft a follow-up email and add it to my Gmail drafts folder' versus 'send it directly.'

I don't do formal QBRs — I do Voxer check-ins or async Loom videos. Does any of this still apply?

The prep brief and student dashboard work regardless of your call format — knowing who's behind on modules and who hasn't paid is useful before any touchpoint. For the meeting notes piece specifically, Meeting Notes is designed for live calls on Zoom or similar. Async Voxer or Loom workflows would need a custom automation; describe what you want Starch to do with incoming Looms or Voxer messages and it can be built, but it won't be a one-click setup from the App Store.

My cohorts are 200 students — will the CRM get slow or messy at that size?

200 contacts is well within normal range. The CRM is a custom app, not a spreadsheet — filtering for 'hasn't had a call in 60 days and is below 50% completion' runs as a query, not a scroll. The honest limit to name: Starch is not a long-horizon data warehouse. If you need archived cohort-over-cohort analytics going back three years with complex drill-downs, a dedicated analytics tool would serve you better. For running current cohort QBRs, it's the right fit.