Cybersecurity students in India abandon demo bookings at M Cyber Academy due to a 12-field form requiring manual follow-ups, causing 62% drop-off before enrollment (source: Q2 funnel analytics). Each lost student represents ₹12,000 in lost LTV (source: finance model, validated placement outcomes). Our ops team spends 15 minutes per lead on manual reminders (n=47 time-study), diverting resources from placement support.
Business case: 120 demos/month × 35% drop-off rate (Q2 funnel) × ₹12,000 LTV = ₹6,048,000/year recoverable. If adoption is 40% of estimate: ₹2,419,200/year. Implementation cost: ₹1.2M (source: regional eng benchmarks). This feature IS an integrated demo-to-enrollment pipeline with automated SMS/email nudges and placement tracking. It is NOT a CRM replacement or payment processor.
Calendly solves booking simplicity for time slots but lacks education-specific workflows. LeadSquared automates follow-ups but requires custom dev for placement tracking. Zoho CRM tracks leads but overwhelms with enterprise features.
| Capability | Calendly | LeadSquared | This Product |
|---|---|---|---|
| 3-field demo booking | ❌ | ✅ | ✅ (unique) |
| Auto-SMS reminders | ❌ | ✅ | ✅ |
| Placement tracking | ❌ | ❌ | ✅ (unique) |
| WHERE WE LOSE | Superior calendar UX | Enterprise scalability | ❌ vs ✅ |
Our wedge is mandatory placement tracking because hiring partners require auditable outcome data — a gap in all generic tools.
WHO / JTBD: When a cybersecurity student in India explores upskilling options, they want to book a course demo in <2 minutes and receive timely follow-ups — so they can evaluate programs without form fatigue or chasing admins.
WHERE IT BREAKS: Current flow forces students through 12 fields (including redundant academic history), offers no confirmation visibility, and relies on manual WhatsApp/email follow-ups. Admins track leads in spreadsheets, losing 27% of placement records (source: audit of 89 Q3 enrollments).
WHAT IT COSTS:
| Symptom | Frequency | Impact |
|---|---|---|
| Demo form abandonment | 62% of starts (Q2 funnel) | 120 lost leads/month |
| Manual follow-up time | 15 min/lead (ops time-study) | 90 admin hrs/month |
| Lost placement records | 27% of enrollments (Q3 audit) | ₹3.24M/year partner penalties |
Aggregate: ₹6.05M/year recoverable + ₹3.24M partner penalties.
Core mechanic: System captures demo intent in 3 fields, triggers time-based nudges via SMS/email, and surfaces placement status to partners via authenticated portal.
-
User flow:
- Student enters name/phone/course → books instantly
- Receives auto-SMS with demo link & prep PDF
- Post-demo: Enrollment link + placement opt-in
- Admin sees pipeline in dashboard (wireframe below)
-
Key decisions:
- 3 fields only (vs 12): Rejected comprehensive forms to reduce cognitive load. Validation: 78% faster completion in prototype test (n=32).
- SMS primary channel (vs email): 94% open rate in India (source: Twilio 2024). Rejected WhatsApp-first due to API costs.
- Placement portal MVP (vs full CRM): Partners need only "placed/not placed" status. Detailed analytics deferred to Phase 2.
-
Integration points:
- Twilio API for SMS
- Existing student DB for enrollment sync
- Placement cell Google Sheets → auto-export
┌───────────────────────────────────────┐
│ DASHBOARD: Enrollment Pipeline │
├───────────┬────────────┬──────┬───────┤
│ Name │ Course │ Demo │ Next │
├───────────┼────────────┼──────┼───────┤
│ Raj Sharma│ Black Hat │ ✅ │ [SMS] │
│ Priya Mehta│Cyber Foren│ ❌ │ [Call]│
└───────────┴────────────┴──────┴───────┘
┌───────────────────────────────┐
│ DEMO BOOKING (Student View) │
├───────────────────────────────┤
│ [Name] __________ │
│ [Phone] _________ │
│ [Course] ▾ Dropdown │
│ │
│ [BOOK DEMO NOW] │
└───────────────────────────────┘
Phase 1 — MVP (10 weeks)
US#1 — 3-field demo booking
- Given student accesses booking page
- When they submit name/phone/course
- Then system books demo & sends SMS in <5s with 100% consistency (P0)
- If fails: Manual backup form triggers. Validated by QA against 50 submissions.
US#2 — Automated SMS reminders
- Given demo booked 24hrs prior
- When reminder trigger time hits
- Then system sends SMS with link & PDF (≥99.5% deliverability)
- If fails: Admin dashboard alert. Validated by Ops with 20 test numbers.
Out of Scope (Phase 1):
| Feature | Why Not Phase 1 |
|---|---|
| WhatsApp integration | High per-message cost; SMS covers 92% users |
| Salary reporting | Requires partner legal agreements |
| Multi-course comparisons | Low incidence (<7% requests) |
Phase 1.1 — Placement Portal (4 weeks post-MVP)
- Partner login with student placement status
- Export placed-student resumes (PDF)
Primary Metrics:
| Metric | Baseline | Target (D90) | Kill Threshold | Method |
|---|---|---|---|---|
| Demo form drop-off | 62% | ≤30% | >45% | Funnel analytics |
| Demo→enrollment | 23% | ≥40% | <25% | Enrollment DB |
| Placement records | 73% | ≥95% | <80% | Partner audit |
Guardrail Metrics:
| Guardrail | Threshold | Action |
|---|---|---|
| Admin time/lead | 15 min | ≤5 min |
| SMS delivery cost | - | <₹2.50/lead |
What We Are NOT Measuring:
- Total demos booked (incentivizes spammy acquisition)
- Portal logins (doesn’t correlate with partner value)
- Feature usage frequency (students are one-time users)
TECHNICAL: SMS delivery failures at peak volume
Probability: Medium Impact: High
Mitigation: Multi-carrier failover (Twilio + Msg91). Owner: Eng lead (Dec 15)
ADOPTION: Students ignore SMS links
Probability: High Impact: Medium
Mitigation: Add 1-click calendar event. Owner: PM (D30 post-launch)
COMPETITIVE: Calendly adds education templates
Probability: Low Impact: High
Mitigation: Accelerate placement portal. Owner: Product Dir (monitor)
LEGAL: PDPA non-compliance for SMS
Probability: Medium Impact: Critical
Mitigation: Explicit opt-in flow + legal review. Owner: Compliance (Nov 30). Consequence: If not cleared, disable SMS.
Kill Criteria (within 90 days):
- Demo drop-off >45% after 30% traffic exposure
- Placement partner adoption <2 of top 5 partners
- SMS cost >₹5/lead at 500 leads/month
Decision: Field reduction strategy
Choice: 3 fields only (name/phone/course)
Rationale: Prototype showed 78% faster completion vs 5-field alternative. Rejected "gradual profiling" due to drop-off risk.
────────────────────────────────────────
Decision: Compliance ownership
Choice: Legal owns PDPA consent flows
Rationale: Student phone data requires explicit opt-in. Rejected engineering self-serve due to RBI penalties.
────────────────────────────────────────
Decision: Placement tracking depth
Choice: MVP: Partner-facing "placed/not placed" only
Rationale: Full analytics delayed to validate partner engagement first. Rejected salary tracking (Phase 2).
────────────────────────────────────────
Decision: Channel priority
Choice: SMS primary, email fallback
Rationale: 94% SMS open rates in India. Rejected WhatsApp due to $0.0082/message cost at scale.
Before/After Narrative:
Before: Raj (24, Gurugram) abandons demo form after 8 fields. He never receives the WhatsApp reminder lost in admin backlog. He enrolls elsewhere.
After: Raj books demo in 55 seconds, gets instant SMS with prep guide. Post-demo, he enrolls via link. His placement status auto-updates for Tata’s hiring team.
Pre-Mortem:
It is 6 months from now and this feature has failed. The 3 most likely reasons are:
- Students ignored SMS links due to carrier filtering (not validated with Airtel/Jio)
- Placement partners rejected the portal because it lacked resume exports (deferred to Phase 1.1)
- Admin reverted to spreadsheets after 2 SMS delivery failures eroded trust
Success looks like: Placement partners proactively request student batches. Admins reallocate 70% of follow-up time to interview prep. The CEO cites "enrollment velocity" as Q1’s top growth lever.