Kommo for tutoring? Wrong tool — 8 real tutor alternatives

Bottom line: why Kommo mismatches tutoring workflow

Direct answer: A tutoring business's real workflow is a 6-stage student-lifecycle — enquiry (from parent typically) → initial assessment or consultation → lesson package purchase → recurring lesson delivery with progress tracking → parent updates + reports → retention through school year + rebook. Kommo's sales-pipeline model with deal stages + sales bots is wrong tool category — tutoring is professional-services with recurring lesson cadence, not sales-cycle conversion.

Why the mismatch is structural, not just cosmetic:

• Wrong buyer + acquisition model. Kommo optimized for teams where new clients acquired via WhatsApp/Instagram sales conversations, guided through deal stages, closed with sales bots. Tutoring parents come from referral (existing tutor client tells friend) + school partnerships + educational directory listings + local Google search — not sales-pipeline conversion.
• Per-user pricing model. Kommo per-user pricing scales linearly with team size. Tutoring agencies with 5-15 tutors + admin all needing access reach meaningful monthly cost quickly — for features not designed for tutoring workflow.
• No lesson scheduling with tutor availability. Tutoring requires matching tutor availability + student availability + subject expertise + level appropriateness. Vertical-native tutor tools (TutorCruncher, Tutorbird, Oases) handle this natively. Kommo has no lesson calendar concept.
• No student records with subject + level structure. Tutoring student records need subject (maths, English, physics, French), level (Year 7, GCSE, A-level, KS3, KS4, university), exam board, target grade, learning goals. Kommo has generic contact records.
• No parent portal. Parents need access to lesson history, invoices, progress reports, scheduling. Vertical-native tutor tools include parent portals; Kommo doesn't.
• No lesson-package billing model. Tutoring billing follows lesson-package (10-lesson block), monthly subscription (X lessons/month), or per-lesson patterns. Vertical-native tools handle all three; Kommo has generic invoice generation without lesson-package concept.

The practical outcome: no tutoring business should use Kommo as primary tool. The alternatives below split into vertical-native tutor management (scheduling + billing + parent portal + tutor management) and horizontal WhatsApp BSPs (for parent-facing chat channel that vertical tools handle differently).

The 8 alternatives: 6 tutor management + 2 WhatsApp Business Platform

Direct answer: 6 tutor/tutoring-centre management platforms — TutorCruncher, Oases Online, Tutorbird, MyEdu, Class4Kids, Bookwhen — combine scheduling + billing + tutor management + parent portal + progress notes. 2 WhatsApp BSPs — WATI, Callbell — for direct parent/student chat. Also relevant: Enrolmy, Sawyer (kids activities), Practice (specialized), TeacherKit.

Bucket 1 — Tutor/tutoring-centre management platforms (public pricing verified from vendor pricing pages August 2026):

• TutorCruncher (tutorcruncher.com/pricing): UK-founded, popular with tutoring agencies. Tiered pricing typically per active tutor + student count — from ~£30/mo tier for very small agencies scaling to enterprise. Full agency workflow — tutor management + student CRM + scheduling + invoicing + agency-tutor fee splitting.
• Oases Online (oaseslink.com): US-focused tutoring centre software. Scheduling + billing + parent portal + tutor management. Pricing quoted on request.
• Tutorbird (tutorbird.com/pricing): Independent-tutor + small-studio focus. ~$40-100+/mo tiers. Scheduling + billing + parent portal.
• MyEdu (myedumanager.com): Tutoring centre management. Pricing quoted.
• Class4Kids (class4kids.co.uk): UK-focused kids-activity booking + billing. Suits tutoring for kids activities + classes.
• Bookwhen (bookwhen.com/pricing): Simple class + lesson booking + payment. ~£12-59+/mo tiers.

Also worth naming: Enrolmy (NZ/AU-focused), Sawyer (US kids activities), Practice (specialized tutor tool), TeacherKit, Setmore (broader booking).

Bucket 2 — Horizontal WhatsApp Business Platform tools:

• WATI (wati.io/pricing): Growth ~$29/mo, Pro ~$79/mo. WhatsApp inbox for parent chat + lesson reminders.
• Callbell (callbell.eu/pricing): ~€30/user/mo. EU-hosted for UK GDPR-strict setups.

Practical stacking pattern for small UK tutoring business: TutorCruncher (~£30-100/mo depending on tutor + student count) + WATI Growth (~£23/mo). Combined ~£60-200+/mo covers all 6 student-lifecycle stages. Kommo at Base $15/user × 3 users = $45/mo (~£35) delivers chat + sales pipeline you don't need — additive without tutoring workflow value.

How Kommo's sales-pipeline model specifically breaks for tutoring

Direct answer: Kommo's core value proposition — 'lead → prospect → deal → won/lost pipeline stages with sales bot automation' — doesn't map to tutoring workflow where enquiries come from parents (not sales prospects), engagement letter is a signed agreement (not a deal close), and work happens on recurring weekly-lesson cadence across months + years. Sales pipeline is the wrong mental model.

Where Kommo's design specifically breaks for tutoring:

1. Deal stages don't fit. Typical Kommo pipeline: New lead → Contacted → Meeting scheduled → Proposal sent → Negotiation → Closed won. Tutoring client: Parent enquires → Assessment scheduled → Package purchased → Active student for months/years on weekly lessons. There's no 'deal stage' that maps to 'currently in Week 15 of GCSE prep' or 'awaiting parent feedback on progress' — those are workflow states.

2. Sales bots don't help tutoring. Kommo's sales bot automation ('lead didn't respond in 24h → auto-send follow-up message') fits sales cadence but not tutoring cadence. Tutoring student 'missed last lesson' needs pedagogically-appropriate follow-up ('Hope everything's OK — shall we reschedule?') not sales-cadence pressure.

3. WhatsApp inbox helps but isn't primary tool. Kommo's WhatsApp inbox is useful — but it's not the primary tool a tutoring business needs. Tutor management (TutorCruncher/Tutorbird/Oases) is primary; WhatsApp inbox is supporting communication channel. Buying Kommo for WhatsApp inbox means paying for sales pipeline + sales bots + deal management that don't apply.

4. No lesson scheduling integration. Kommo doesn't integrate with lesson scheduling systems + doesn't have native calendar management with tutor availability + subject-level matching.

Practical implication: if reason for evaluating Kommo is 'we need WhatsApp for parent comms,' get WATI Growth (~£23/mo) — dedicated WhatsApp BSP without unnecessary sales-CRM overhead. Fund tutor management separately for actual workflow.

Stage 1 — Enquiry + initial assessment (converting parent interest to first paid lesson)

Direct answer: Tutoring enquiries arrive via web form, phone, WhatsApp, or referral. Parent asks about specific academic need. Vertical-native tutor tools structure enquiry into student record; WhatsApp BSPs capture direct-chat channel.

Stage 1 scorecard:

TutorCruncher, Oases, Tutorbird, MyEdu: 🟢 web enquiry form with structured questions (student age, subject, level, availability, learning goals). Creates student prospect record.

WATI, Callbell: 🟢 for direct WhatsApp enquiry channel — parent messages 'Do you have GCSE maths tutors?' — chatbot flow captures student age + subject + level + preferred time.

Kommo: 🟡 web enquiry form + basic CRM but no tutor-matching capability + no lesson scheduling + no assessment booking workflow.

Winner for Stage 1: vertical-native tutor management for structured intake + tutor matching; WhatsApp BSP for parent-facing enquiry channel.

Stage 2 — Lesson scheduling + package management (the operational rhythm)

Direct answer: Tutoring requires matching student availability + tutor availability + subject match + lesson package tracking. Vertical-native tutor management handles natively; Kommo doesn't touch scheduling.

Stage 2 scorecard:

TutorCruncher, Oases, Tutorbird, MyEdu: 🟢 lesson scheduling with tutor calendar + student calendar overlay, package tracking (10-lesson block, credits remaining, expiry), rebooking automation, cancellation window enforcement.

Class4Kids, Bookwhen: 🟢 for class-based booking (group classes rather than 1:1).

WATI, Callbell: 🟢 for lesson reminder delivery — 24-hour + morning-of WhatsApp reminders drive fewer no-shows.

Kommo: 🔴 no lesson scheduling, no package tracking, no tutor-student calendar matching.

Winner for Stage 2: vertical-native for scheduling; WhatsApp BSP for reminder delivery.

Stage 3 — Progress tracking + parent reports (retention driver)

Direct answer: Parents pay for tutoring to see academic improvement. Per-lesson progress notes + monthly/termly parent reports demonstrate value + drive retention. Vertical-native tutor tools structure this; Kommo doesn't.

Stage 3 scorecard:

TutorCruncher, Oases, Tutorbird, MyEdu: 🟢 per-lesson notes structured (topics covered, exercises completed, homework assigned, next steps, tutor observations). Parent portal shows lesson history + notes.

Termly parent reports: vertical-native tools generate reports automatically from lesson notes + attendance + assessment scores.

WATI, Callbell: 🟢 for delivery of parent report notifications — 'Termly report for [student] ready — view in parent portal: [link]'.

Kommo: 🔴 no student record structure, no lesson notes, no parent reports.

Winner for Stage 3: vertical-native tutor management uniformly.

Stage 4 — Billing (lesson package / monthly / per-lesson) + tutor payroll

Direct answer: Tutoring billing follows one of three patterns — pre-paid lesson package (10-lesson block), monthly subscription with X lessons/month, per-lesson billed after completion. Vertical-native tutor management handles all three + tutor payroll (splitting fee between agency + tutor for agencies).

Stage 4 scorecard:

TutorCruncher, Oases, Tutorbird, MyEdu: 🟢 flexible billing model support. Auto-invoice generation. Integrated payment (Stripe/Square/GoCardless typical).

Tutor payroll for agencies: TutorCruncher + Oases handle agency-tutor fee splitting — typically 60-80% to tutor, 20-40% to agency. Auto-calculates + generates payment reports.

WATI, Callbell: 🟢 for billing reminder delivery — 'Your invoice for [month] is ready. Payment via [link]'.

Kommo: 🔴 no lesson-billing model, no tutor payroll.

Winner for Stage 4: vertical-native tutor management uniformly.

Stage 5-6 — Retention + school-year rhythm + rebook

Direct answer: Tutoring follows school-year rhythm — September start, half-term breaks, exam periods, summer break. Retention through natural break points (summer especially) is the retention challenge. Vertical-native tools track student history + trigger retention outreach.

Stage 5 scorecard (school-year retention):

TutorCruncher, Oases, Tutorbird, MyEdu: 🟢 student history + package tracking + at-risk-of-churn identification.

WATI, Callbell: 🟢 for retention outreach delivery.

Practical patterns:

End-of-term rebook: '[Student]'s current package ends this Friday. Renew for the next half-term: [link]'.

Summer break retention: 'Summer intensive packages — 5 or 10 sessions between July and August: [link]'.

Exam period intensity: 'GCSEs approaching for [student]. Exam prep packages start [date]: [link]'.

Stage 6 (referral + review):

WATI, Callbell: 🟢 for review request delivery + referral prompts.

Kommo: 🔴 no student history structure.

Winner for Stages 5-6: vertical-native for student history + retention triggers; WhatsApp BSP for outreach delivery.

Situational winners by tutoring business profile

Direct answer: Independent 1:1 tutor → Tutorbird + WATI. Small tutoring agency (2-10 tutors) → TutorCruncher + WATI. Tutoring centre (10+ tutors) → Oases or MyEdu + Callbell. Kids activity classes → Class4Kids + WATI. Never Kommo as primary for any tutoring profile.

Profile A — Independent 1:1 tutor (5-30 students, 1 tutor)

• Winner: Tutorbird (~$40/mo) + WATI Growth (~$29/mo) for WhatsApp parent chat.
• Total: ~$70/month.
• Don't buy Kommo: ~$15-45/user/mo delivers WhatsApp inbox + sales pipeline; standalone WATI provides better focused WhatsApp inbox at ~$29/mo without unnecessary sales-CRM overhead.

Profile B — Small tutoring agency (2-10 tutors, 30-200 students)

• Winner: TutorCruncher (from ~£30/mo scaling) + WATI Growth (~£23/mo).
• TutorCruncher is UK-founded with strong agency workflow — tutor management + payment splitting + student CRM + parent portal.
• Total spend: ~£75-250/month.

Profile C — Tutoring centre (10+ tutors, group + 1:1 lessons)

• Winner: Oases Online or MyEdu + Callbell (~£26/user/mo scaled).
• Total spend: ~£300-1,500/month.

Profile D — Kids activity provider (drama, music, sports, tutoring for kids)

• Winner: Class4Kids (UK-focused) or Sawyer (US) + WATI.

Profile E — Online-only tutor selling recorded courses + live sessions

• Winner: Teachable or Thinkific for course platform + Tutorbird or Zoom + Calendly for live + WATI for parent chat.

Common mismatch (avoid): buying Kommo because it appears in 'WhatsApp CRM for tutors' searches. Kommo is sales pipeline + WhatsApp inbox — you don't need sales pipeline (referral-driven tutoring), and standalone WATI provides better inbox at lower cost. Fund vertical-native tutor management first; add WhatsApp BSP for parent chat second.

Safeguarding disclaimer: UK tutoring businesses working with under-18s should follow appropriate safeguarding practices including DBS-checked tutors + safeguarding policy + supervision protocols. US: state-specific background check + child protection requirements. This teardown is editorial guidance on tool choice, not safeguarding compliance advice. No undisclosed commercial relationship with any vendor listed.