Competitive gap analysis: Dive/Untis/Edupage/STA vs ReliefCher

[guangshinhaha]

Competitive Gap Analysis — ReliefCher

Date: 2026-04-09
Branch: research-synthesis-westwood

Synthesis of (a) the Westwood Secondary interview with HOD PE/CCA Eric Foo, (b) Adeline Chng's network sweep across DXD ex-KPs and partner schools, and (c) a desk review of competitor product pages and user guides.

---

1. Market context

ReliefCher is entering a market where most schools already use a paid vendor, not manual processes. Adeline's sweep found only 2/9 contacts without a vendor system.

System	Schools mentioned	Notes
Dive / Roster Analytics	Westwood Sec, Tampines Pri, Poi Ching, Edgefield Sec, Admiralty Sec	~S$5.9k/yr basic; founder-led; ~10% of MOE schools per their site
Edupage + aSc	Geylang Methodist Sec	Bundled with timetabling
STA (School Timetable App) by ESTL	200+ schools, Rosyth	Has relief module BUT frozen — under SCAC/ESTL review, no new dev, no new onboarding
aSc only	(Stanley's ex-school)	MOE's primary timetabling tool
MS Access / vibe-coded	Mee Toh, Beatty Sec	One-off internal builds
Manual (WhatsApp+Excel / whiteboard+HODs)	Canossa Pri, Bukit Batok Sec	Increasingly rare

---

2. Westwood / Dive deep-dive

What the incumbent does well

• Auto-assignment at fixed time (7:20 AM) using Hearts (workload, weekly reset) + Stars (role/subject priority)
• Customisable priority order (Westwood: SRE → untrained → FAJT → EO)
• Multi-channel notifications: email + Telegram + WhatsApp
• HBL-aware (auto-disables)
• Leadership dashboard with stats + Excel export
• Direct line to founder; responsive setup

Pain points even Dive users have (= ReliefCher opportunities)

1. Algorithm gap — splits relief across two teachers when one could cover consecutive periods for the same class. Eric raised this with Dive; not fixed.
2. Double logging — absence in Dive + sick leave in WorkPal. No integration.
3. Trust gap on auto-assign — 5–15 min daily manual correction because teacher inputs are wrong (e.g., relief requested when not actually needed).
4. Wishlist: AI to read teacher notes and validate/revise relief requests automatically.
5. In-class comms gap — relief teachers hit issues mid-lesson (e.g., student SLS login). HOD relays via WhatsApp ad-hoc.
6. Data privacy unease — Eric uncomfortable sending teacher emails to vendor.
7. Timetabling lock-in — schools won't switch from aSc/MOE; any relief tool must ingest external ROS.

---

3. Competitor feature matrix

Feature	Dive/Roster	Untis (intl. leader)	aSc / Edupage	STA (ESTL)	ReliefCher (today)
Auto-assignment	✅ <30s, Hearts+Stars, customisable	✅ One-click, considers history	⚠️ Suggests candidates (semi-auto)	⚠️ Lists available (manual pick)	❌ Manual only
Subject/dept matching	✅	✅	✅	❓	❌
Workload balancing (weekly reset)	✅ Hearts	✅ Counts subs/cancellations	⚠️ Limited	❓	❌
Consecutive-period optimisation	❌ (Eric's complaint)	⚠️ Not explicit	✅ Edupage bulk multi-day → single sub	❓	❌
Email notifications	✅	✅	✅	❓	❌ (stub)
Telegram	✅	❌	❌	❌	❌
WhatsApp	✅	❌	❌	❌	❌
Mobile push (native app)	⚠️ Web/mobile site	✅ Untis Mobile	✅ EduPage app	❌	❌
Relief teacher acknowledgement	✅	✅	✅	❓	❌
Self-report partial day, stack reasons	✅ <1 min	✅	✅	❓	⚠️ Full-day, single reason
Lesson plan / instructions handover	✅	✅	✅ Notes	❓	❌
Exam invigilation scheduling	✅ Dedicated module	⚠️ Via supervision	⚠️	❓	❌
Break / duty supervision relief	❌	✅ Module	⚠️	❓	❌
Real-time dashboards	✅	✅ WebUntis	✅	❓	⚠️ Basic
Historical analytics / trends	✅	✅	✅	❓	❌
Excel / CSV export	✅	✅	✅	❓	❌
Daily summary to EXCO/SLT	✅	⚠️	⚠️	❓	❌
aSc XML import	✅	N/A	✅ Native	❓	✅
STA timetable import	✅	❌	❌	✅ Native	❌
Multi-user simultaneous editing	❓	✅	✅	❓	⚠️ No locks
Mid-year timetable updates	⚠️	✅	✅ Auto	❓	⚠️ Replace mode
HR / payroll integration (WorkPal etc.)	❌	⚠️ Some EU HR	❌	❌	❌
AI absence-note validation	❌ (wishlist)	❌	❌	❌	❌
In-class issue reporting loop	❌	❌	❌	❌	❌
Find common meeting time	✅	✅	⚠️	❓	❌
Gov-hosted / data residency	❌ Vendor cloud	❌	❌	✅ ESTL/MOE	✅ string.sg
Pricing	~S$5.9k/yr basic	License	License	Free-ish (frozen)	Free (MOE-funded)

---

4. Table-stakes gaps to close (must-have parity)

Sorted by frequency across competitors + Westwood interview:

1. Auto-assignment algorithm — every serious competitor has one. Implement Hearts (workload, weekly reset) + Stars (role priority + subject match). Eric's interview gives a ready-made config schema.
2. Email notifications — only stubbed today. Use string.sg notification service or Postmark/Resend.
3. Telegram + WhatsApp — Dive's biggest UX edge. Telegram bot is cheap.
4. Relief teacher acknowledgement — covered teacher must confirm receipt. One-tap link in notification.
5. Partial-day absences + stackable reasons + lesson-plan attachment.
6. Daily SLT summary email — auto-send ~8 AM.
7. Excel export of relief assignments — for school records and payroll.
8. Historical dashboards — absences per teacher, relief load distribution.
9. Mid-year timetable updates without nuking existing data.
10. Exam invigilation scheduling — Dive bundles this; same data model, big stickiness.

---

5. Differentiation wedges (where we beat Dive, not just match)

1. Consecutive-period optimisation — Eric's explicit Dive complaint. Greedy post-pass: for each (class, day), prefer the same relief teacher across adjacent periods. Cheap, demoable, immediately credible.
2. AI validation of teacher absence notes — Eric's literal wishlist. Use Claude to parse freetext absence reason + lesson notes, flag "relief not actually needed" cases (e.g., "I'll be out but my class is on excursion"). Eliminates the daily 5–15 min manual correction.
3. WorkPal / HR double-logging killer — even one-way CSV export to WorkPal-compatible format solves the feat: multi-tenancy, auth, superadmin dashboard, onboarding, and test suite #1 daily friction. Full API integration is the moat.
4. In-class issue reporting loop — relief teacher hits SLS login problem → one-tap mobile report → routed to HOD AND auto-attached to absent teacher's return-to-work view. Nobody has this.
5. Gov-hosted data residency — only ReliefCher (string.sg) and STA can credibly say "teacher PII never leaves MOE infra." Eric flagged discomfort sending teacher emails to Dive. Lead with this in SLT pitches.
6. Free / MOE-funded — Dive is ~S$5.9k/yr. If ReliefCher is free, that's a cluster-level decision win even against happy Dive customers.
7. STA migration path — STA has 200+ schools and is frozen. A STA-format importer = an instant addressable market with no incumbent salesforce defending it.

---

6. Recommended sequencing

Sprint 1 — table-stakes: auto-assign (Hearts+Stars) · email notifications · relief acknowledgement · partial-day absences. Without these we cannot credibly demo to Tampines Pri.

Sprint 2 — wedges: consecutive-period pass · AI absence-note validator · Telegram bot.

Sprint 3 — moat: STA importer · WorkPal export · in-class issue reporting.

Defer: exam invigilation, break duty, native mobile app.

---

7. Validation plan

Adeline's prioritised contacts to interview, ranked by intent:

1. (1) Tampines Primary (Rahmah) — just onboarded Roster Analytics, "teething problems," open to deeper convo. Highest intent.
2. (4) Beatty Secondary — principal vibe-coded an internal tool → already validates "build-your-own" demand.
3. (7) Bukit Batok Sec (Darren) — no vendor; HOD-per-dept manual planning → greenfield.
4. (2)/(3) Poi Ching, Geylang Methodist — secondary.

Process note: schools require formal write-in via P/VP. Start with DXD ex-KPs (Penelope, Stanley, Darren, Keng Yong, Adeline) — internal and fastest.

Open questions to take into interviews

• Confirm Dive pricing (~S$5.9k/yr) and what extensions cost.
• Does STA's relief module actually work, or is it vestigial?
• What does WorkPal expose via API? (kills double-logging only if integration is feasible)
• Is data-residency a real wedge with school leaders, or just Eric's personal concern?

---

Sources

• Dive Analytics — Roster
• Dive — Smarter Relief Planning blog
• Untis — Substitution planning
• Untis — Online substitution planning
• Edupage — Specifying substitutions
• aSc Substitutions help
• ESTL — School Timetable Application

[guangshinhaha]

Completed — doc at docs/research/competitive-gap-analysis.md