People & HR

How to onboard a new hire as Educators, Coaches, and Course Creators

People & HRFor Educators, Coaches, and Course Creators3 apps12 steps~24 min to set up

Every six weeks you run a new cohort and every six weeks you onboard the same people the same broken way. You paste a welcome email from last time, manually add each student to Notion, chase down the Calendly link for orientation, and then spend the first week answering 'where do I find the Zoom link?' in Slack or Circle. Your stack — Stripe, Notion, Calendly, Zoom, ConvertKit or Mailchimp, and a community platform — doesn't talk to each other, so you're the connective tissue. Hiring even one part-time TA or ops assistant means rebuilding that tribal knowledge from scratch, because it's all in your head or buried in a Google Doc you haven't updated since cohort two.

Build this on Starch → See the apps used

People & HRFor Educators, Coaches, and Course Creators3 apps12 steps~24 min to set up

Outcome

What you'll set up

A repeatable new-hire and TA onboarding workflow that automatically surfaces the right Notion docs, Calendly orientation link, and Slack channels the moment someone joins — no copy-pasting from last cohort.

A knowledge base your team can actually search, so the next TA you hire isn't emailing you to ask where the lesson delivery checklist lives or what the refund policy is.

A task tracker that assigns onboarding milestones to you and your new hire with due dates and priority levels, so nothing slips between cohort prep and live teaching weeks.

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 Scheduling Task Manager

Data sources & config

Starch connects directly to Notion via scheduled sync, pulling your existing pages and databases so the knowledge base is seeded from what you've already written. Calendly is connected via scheduled sync for booking data and availability. Slack is connected via scheduled sync so the agent can surface the right channels during onboarding. For platforms like Kajabi, Teachable, or Thinkific that don't appear in the scheduled-sync list, Starch automates them through your browser — no API needed — to pull enrollment data or post welcome announcements. ConvertKit and Mailchimp are reachable from Starch's integration catalog; the agent queries them live when your onboarding workflow triggers a welcome email sequence.

Prompts to copy

Build me a knowledge base for onboarding new TAs and ops hires. It should include sections for: how we run each cohort (Zoom links, Calendly setup, lesson delivery checklist), where to find student records in Notion, our refund and deferral policy, and how to handle the fifteen most common student questions. Pull in our existing Notion pages and flag anything that looks more than 60 days out of date.

Create an orientation scheduling workflow. When I add a new hire in Notion, automatically send them a Calendly link for a 45-minute onboarding call, block two slots on my calendar this week labeled 'TA Orientation,' and add a follow-up reminder in five days if they haven't booked.

Set up an onboarding task list for a new cohort TA. Tasks should include: complete knowledge base walkthrough (P1, due Day 1), shadow one live session (P1, due Day 3), send first solo reply in the student Slack (P2, due Day 5), submit first weekly check-in (P2, due Day 7). Alert me if anything goes overdue.

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

Walkthrough

Step-by-step

1 Connect Notion via Starch's scheduled sync. Starch pulls your existing pages and databases on a schedule — curriculum docs, lesson delivery checklists, refund policies, past cohort retrospectives — and uses them to seed your knowledge base.

2 Connect Calendly via Starch's scheduled sync so the agent knows your real-time availability and can generate orientation booking links automatically without you touching the app.

3 Connect Slack via Starch's scheduled sync so the agent can identify the right channels (student support, TA team, announcements) and include them in the onboarding path it builds.

4 Tell Starch to build your knowledge base: describe what a new TA needs to know in plain language. Starch pulls from your connected Notion content, organizes it into searchable sections, and flags pages that look stale.

5 For any content that lives in Kajabi, Teachable, or your course platform, Starch automates the browser to retrieve enrollment data or course structure — no API required — and incorporates it into the onboarding docs.

6 Set up the orientation scheduling automation. Tell Starch: 'When I mark someone as a new hire in Notion, send them a Calendly orientation link and block two slots on my Google Calendar this week.' Starch builds this as a triggered automation.

7 Build the onboarding task list in Task Manager. Describe the milestones and deadlines once; Starch creates a reusable template with P1–P4 priority levels you can clone for every new TA or ops hire.

8 Wire a welcome email trigger. Connect ConvertKit or Mailchimp from Starch's integration catalog and tell Starch: 'When a new hire is added, enroll them in the TA welcome sequence and send me a confirmation.' The agent queries your email platform live when the automation runs.

9 Run a dry-run with yourself as the test hire. Go through the knowledge base, check that the Calendly link works, confirm the task list looks right, and ask Starch to fill any gaps you notice during the walkthrough.

10 Publish the knowledge base link in your TA hiring offer email. New hires arrive already knowing where things live, so your orientation call becomes a Q&A rather than a screen-share tour.

11 Set a recurring Starch automation to check Notion for pages flagged as stale (older than 60 days with no edits) and send you a Slack message listing what needs updating before the next cohort launch.

12 After cohort one using this system, tell Starch: 'Show me which knowledge base articles were searched most in the last six weeks.' Use that to decide what to expand before you hire your next TA.

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 cohort — onboarding a first TA in 48 hours

Sample numbers from a real run

Notion pages pulled into knowledge base	34
Stale pages flagged for update before cohort launch	7
Onboarding tasks auto-created in Task Manager	8
Hours spent on TA orientation vs. prior cohort	2
Student 'where is X?' Slack messages in week 1 vs. prior cohort	4

You hired your first part-time TA for the April 2026 cohort — a former student who knows your content but has never run the back end. In the past you would have spent a full afternoon walking her through a screen share: here's Notion, here's the Zoom recurring link, here's what you say when someone asks for a refund. Instead, you told Starch: 'Build a TA onboarding knowledge base from my Notion workspace. Flag anything older than 60 days.' Starch pulled 34 pages, organized them into sections (lesson delivery, student support, tech setup, cohort operations), and flagged 7 pages that hadn't been touched since cohort two — including the refund policy, which had a wrong dollar amount in it. You fixed those 7 pages in about 20 minutes. Starch then created 8 onboarding tasks in Task Manager with priorities and due dates: complete knowledge base walkthrough by Day 1 (P1), shadow a live session by Day 3 (P1), send a solo student reply by Day 5 (P2). When you marked her as a new hire in Notion, the Calendly orientation link went out automatically and two 45-minute slots blocked on your calendar. The orientation call itself was 90 minutes shorter than usual because she'd already read everything. In week 1, you got 4 'where is X?' Slack messages from students — down from around 20 the prior cohort, because your TA could actually answer them.

Measurement

How you'll know it's working

Time from 'offer accepted' to new hire completing knowledge base walkthrough (target: under 48 hours)

Number of 'where do I find X?' messages from new hires in their first two weeks

Percentage of onboarding tasks completed on time vs. overdue at end of week 1

Number of stale knowledge base pages updated before each cohort launch

Student support response time in week 1 of cohort when a TA is onboarded vs. when you handle it solo

Comparison

What this replaces

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

Notion alone (as wiki + onboarding doc)

Notion stores the docs but doesn't surface them intelligently, flag stale content, assign tasks with deadlines, or connect to your Calendly and email platform — you're still doing all the coordination manually.

Trainual or Lessonly

Purpose-built onboarding platforms with structured paths and quizzes, but they don't connect to your course platform, Stripe, or calendar — so you're maintaining a separate tool that doesn't know anything about how your actual business runs.

ClickUp or Asana for onboarding tasks

Good task tracking with templates, but no AI that reads your Notion docs, flags what's outdated, or connects the task list to your Calendly booking flow — still separate tools you're stitching together yourself.

A Google Doc onboarding checklist you email each hire

Zero setup cost and total familiarity, but it's a static document that goes stale immediately, can't trigger Calendly links or welcome emails, and requires you to manually update and re-send every cohort.

On Starch RECOMMENDED

One platform — knowledge management, scheduling, task manager 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 content lives in Kajabi, not Notion. Can Starch still pull it in?

Yes. Kajabi doesn't appear in Starch's scheduled-sync list, but Starch automates it through your browser — no API needed. It can navigate your Kajabi admin, pull course structure or enrollment data, and incorporate that into the onboarding knowledge base. You describe what you want retrieved and Starch handles the rest.

I only hire a new TA every few months. Is this worth setting up for something that infrequent?

The setup pays off the first time because the same knowledge base and task template also serves you between cohorts — for answering student questions faster, keeping your docs current, and not rebuilding the checklist from memory every six weeks. The onboarding workflow is a byproduct of having your course operations documented in one searchable place.

Will Starch work with ConvertKit for the welcome email, or only Gmail?

Both. Gmail and Outlook are scheduled-sync providers, so Starch can read and send from those directly. ConvertKit is reachable from Starch's integration catalog — the agent queries it live when your onboarding automation triggers, so it can enroll your new hire in a sequence or send a one-off welcome email from ConvertKit without you logging in.

Is Starch SOC 2 certified? My new hire will have access to student payment data.

Not yet — Starch is not SOC 2 Type II certified today. If your TA needs to see Stripe transaction data or student PII, that's worth factoring into your decision. For most education operators, the knowledge base and task workflows don't touch payment records directly, but it's an honest limit worth knowing upfront.

What happens if the knowledge base articles get out of date after I publish them?

Starch can run a scheduled automation that checks your Notion pages for content older than a threshold you set — say, 60 days without an edit — and sends you a Slack message listing what to review before your next cohort launch. It doesn't auto-update the content (you know your curriculum better than the agent does), but it makes sure you're not handing a new hire a policy doc from two years ago.

The Task Manager is listed as 'currently in development.' Can I still use it?

You can request beta access. If you'd rather not wait, you can tell Starch to manage onboarding tasks through a Notion database instead — Starch syncs Notion on a schedule and can read and write task records there. Describe the onboarding milestone structure you want and Starch builds the view in Notion until Task Manager is fully live.