Sales & CRM

How to build an outbound email sequence as Educators, Coaches, and Course Creators

Sales & CRMFor Educators, Coaches, and Course Creators3 apps11 steps~22 min to set up

You write a new launch email sequence every six weeks for each cohort — from scratch, every time. You're copying last quarter's ConvertKit automation, editing the dates, swapping in the new course name, and hoping you didn't break a conditional trigger. Your welcome sequence, nurture drip, and cart-abandonment follow-up all live in separate ConvertKit or Mailchimp automations that have no idea what's happening in Calendly, Stripe, or your Notion enrollment tracker. Someone books a discovery call but never pays — nobody follows up. Someone pays but never opens lesson 1 — nobody notices. You're doing this manually, between teaching sessions, at 11pm.

Build this on Starch → See the apps used

Sales & CRMFor Educators, Coaches, and Course Creators3 apps11 steps~22 min to set up

Outcome

What you'll set up

An outbound enrollment sequence that automatically identifies warm leads — people who clicked your sales page, booked a call, or asked a question — and sends them a timed email series without you writing each one from scratch

A CRM that tracks each prospective student from first contact to enrolled, with their conversation history, call booking status, and payment status visible in one place so nothing falls through

A follow-up automation that catches the people who ghosted after a discovery call or abandoned checkout and sends a personalized nudge without you manually combing through Stripe and Calendly every Friday

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 Email Agent LinkedIn Automation

Data sources & config

Starch syncs your Gmail data on a schedule so the CRM captures email thread history automatically. Starch connects directly to Stripe so payment status updates in the CRM the moment someone pays. Connect Calendly from Starch's integration catalog — the agent queries it live when the automation checks whether a discovery call was completed. LinkedIn outreach runs through browser automation on your behalf — no LinkedIn API needed. ConvertKit or Mailchimp can be connected from Starch's integration catalog if you want to trigger sequences in your existing email tool rather than send through Starch directly.

Prompts to copy

Build me a CRM for my cohort-based course business. Pipeline stages are: Inquiry, Discovery Call Booked, Discovery Call Completed, Proposal Sent, Enrolled, Ghosted. I want to track each contact's course interest, which cohort they're considering, whether they've paid, and the last time I emailed them. Flag anyone who hasn't moved stages in 7 days.

Build an outbound email sequence for people who booked a discovery call but haven't enrolled yet. Send email 1 the day after the call (recap + next step), email 2 three days later (student success story + FAQ), email 3 five days later (closing deadline reminder). Pull their name and course interest from my CRM. Stop the sequence the moment they pay.

Every Monday morning, pull contacts from my CRM who are in the 'Discovery Call Completed' or 'Proposal Sent' stage and haven't moved in 5+ days. Draft a short personal follow-up email for each one based on their last conversation note. Show me the drafts for approval before sending.

Connect to LinkedIn and send connection requests to high school teachers, corporate trainers, and instructional designers who follow accounts like mine. Use this message: 'Hi [name], I run a cohort on [topic] for educators — thought it might be relevant to your work. Happy to share more if useful.'

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

Walkthrough

Step-by-step

1 Connect Gmail — Starch syncs your Gmail data on a schedule, pulling in sent/received threads so every email to a prospective student shows up automatically in the CRM contact record.

2 Connect Stripe — Starch connects directly to Stripe so enrollment payment status syncs into the CRM. When someone pays, their stage moves to Enrolled and any active follow-up sequence stops.

3 Connect Calendly from Starch's integration catalog. The agent queries it live when checking whether a contact completed their discovery call, so the automation knows which stage to put them in.

4 Describe your CRM to Starch in plain language — include your pipeline stages (Inquiry through Enrolled), the fields you actually track (cohort interest, payment status, last contact date), and the flag rule for stale deals.

5 Start with the CRM app from the Starch App Store as your base. Fork it to match your stage names and add the course-specific fields — cohort date, module access granted, referral source.

6 Write the outbound sequence prompt: tell Starch which stage triggers the sequence, the timing between emails, the tone you want, and the stop condition (payment received). Starch drafts the sequence and shows you the copy before anything sends.

7 Review and edit the email drafts inside Starch. You're approving the logic and the voice — not writing from scratch. This is where your 11pm rewrite ritual ends.

8 Set up the Monday morning stale-deal automation: Starch queries the CRM for contacts stuck in 'Discovery Call Completed' or 'Proposal Sent' for 5+ days, drafts a short personalized follow-up for each, and surfaces them for one-click approval before sending.

9 If LinkedIn is part of your top-of-funnel, set up the LinkedIn Automation app. Describe your ICP — job title, industry, what they post about — and Starch sends connection requests and optional follow-up messages through your browser at human-paced intervals.

10 Set an enrollment deadline automation: the week before cohort close, Starch identifies everyone still in 'Proposal Sent' and triggers a deadline-reminder email with your early-bird or last-call framing.

11 After each cohort launch, ask Starch: 'How many people entered the discovery-call stage in the last 6 weeks, and what percentage enrolled?' Use that conversion rate to adjust your sequence timing or copy for the next cohort.

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

May 2026 Cohort Launch — Curriculum Design for Educators Course

Sample numbers from a real run

Discovery calls booked (Calendly, 3-week window)	34
Calls completed	27
Enrolled within 72 hours of call	11
Enrolled after follow-up sequence (emails 2–3)	8
Ghosted — no response after sequence	8
Revenue enrolled (at $1,200/seat)	22,800

Before Starch, the May cohort looked like this: 27 completed calls, a Google Sheet with color-coded rows, and a ConvertKit automation you rebuilt from February's version at midnight on April 28th. Eight people who completed calls never heard from you again because they slipped off the sheet. This time: Starch's CRM ingested all 34 Calendly bookings automatically. When a call was marked completed, the 3-email follow-up sequence triggered the same day. Of the 27 who completed calls, 11 enrolled within 72 hours — that's your normal close rate. But 8 more enrolled after email 2 or email 3, people who previously would have gone cold. The Monday morning automation flagged 9 contacts still sitting in 'Proposal Sent' by day 5; Starch drafted personalized follow-ups based on their call notes ('you mentioned you're building this for your district's PD program — here's how another curriculum director used the course'). Total enrolled: 19 out of 27 completed calls, a conversion rate of 70% versus your historical 40%. You didn't write a single sequence email from scratch.

Measurement

How you'll know it's working

Discovery-call-to-enrollment conversion rate per cohort (target: know the number, improve it each launch)

Days to enrollment after discovery call (shorter = sequence is working)

Percentage of booked calls that ghosted before the call happened (signals a pre-call nurture gap)

Number of seats filled before the early-bird deadline vs. last-call scramble

Sequence open rate on email 2 and email 3 (the ones that used to never get sent)

Comparison

What this replaces

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

ConvertKit automations + manual CRM spreadsheet

ConvertKit handles the email sequencing reasonably well, but it has no idea what's in your Calendly, Stripe, or Google Sheet — so the trigger logic is manual and the follow-up gaps happen every launch.

HubSpot Starter

HubSpot gives you a real CRM and sequence builder, but you'll spend a weekend configuring it to your cohort model, and the 'sequences' feature requires Sales Hub at a price point that hurts on a solo course business.

Mailchimp + Calendly + Stripe (no CRM)

Three separate tools that don't share data — you're the integration layer, which means the follow-up logic only runs when you remember to run it.

ActiveCampaign

Powerful automation and tagging, but the learning curve is steep and you'll need to rebuild your sequence logic every cohort unless you invest serious time in the template architecture — time you're spending teaching.

Notion CRM template + manual email

Free and flexible, but Notion doesn't send emails, has no Stripe sync, and 'automation' means a reminder to yourself to do the thing.

On Starch RECOMMENDED

One platform — crm, email agent, linkedin automation 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 actually write the emails or do I still have to write them?

Starch drafts the sequence copy based on the context you give it — your course topic, the stage the contact is in, the tone you describe, and any notes from previous conversations. You review and edit before anything sends. Think of it as getting a strong first draft for every email in the sequence rather than starting from a blank page at midnight.

I use ConvertKit for my list. Do I have to switch my entire email setup to Starch?

No. You can connect ConvertKit from Starch's integration catalog and trigger sequences in ConvertKit from Starch automations. Starch handles the logic — who gets what, when, based on what they did — and ConvertKit handles the actual sending. Or you can run sequences directly through Starch using your Gmail connection. Either way works; pick whichever keeps your list hygiene simpler.

What about Kajabi or Teachable — can Starch see who's enrolled or completed a module?

Kajabi and Teachable are reachable through browser automation — Starch automates them through your browser, no API needed. For pulling structured enrollment or completion data on a schedule, the cleanest path is usually to export that data from Kajabi/Teachable into a Google Sheet (which Starch can query live from its integration catalog) and use that as your enrollment source of truth alongside Stripe payment data.

Is my student email data secure? I'm nervous about an AI tool reading my inbox.

Honest answer: Starch is not SOC 2 Type II certified yet. Gmail syncs are read and used to populate your CRM and draft follow-ups — Starch does read thread content to do that job. If you're handling sensitive student information or operating under institutional data policies (a district partnership, for example), that's worth factoring in before connecting your inbox.

I do a new cohort every 6–8 weeks. Do I have to rebuild the sequence every time?

No — that's exactly the problem Starch is designed to end. You build the sequence once, tied to pipeline stages and trigger conditions (call completed, not yet paid, 72 hours elapsed). When the next cohort opens, the same logic runs against the new contacts. You update the cohort dates and any course-specific details; the sequence structure and follow-up timing stay the same.

Can I use this for a lower-ticket product like a $97 self-paced course, not just high-touch cohorts?

Yes, though the workflow looks a bit different. For low-ticket self-paced, the sequence is typically triggered by a Stripe payment not completing (cart abandonment) or by someone opting into your lead magnet without buying. You'd describe that trigger to Starch — 'someone signed up for my free masterclass but hasn't bought the course within 5 days, send them this sequence' — and it builds the automation around that logic instead of around discovery calls.