Juniro Schools Product Strategy (India-First)
Purpose: Define the product strategy for Juniro's expansion into the schools vertical Last Updated: January 2026 Status: Future Phase Planning Market: India-First
Product Thesis
Juniro for Schools = the digital front door for private schools
- Discovery + trust + admissions info + fee collection
- NOT bookings, NOT programs, NOT a two-sided marketplace
This is B2B2C infrastructure, not a marketplace in the classic sense.
Why India First
India is uniquely well-suited because:
| Factor | Why It Matters |
|---|---|
| ~70%+ schools are private | Large addressable market |
| Fast, relationship-driven admissions | Less bureaucracy than Western markets |
| Fragmented digital presence | Many schools lack websites or have outdated ones |
| Tool chaos | Schools use Google Forms, Excel, WhatsApp, Razorpay links |
| Parent behavior | Already search online, compare informally, pay digitally |
Key insight: We're not changing behavior — we're consolidating chaos.
Product Scope
For Parents
| Capability | Description |
|---|---|
| Discover schools | Search, browse, filter by location/board/grades |
| Compare & review | Read reviews, compare facilities |
| Understand admissions | Clear timelines, requirements, fees |
| Pay fees safely | Secure, transparent transactions |
For Schools
| Capability | Description |
|---|---|
| Branded presence | Their "website" on Juniro |
| Admissions information | Showcase offerings, timelines |
| Inquiry capture | Lead generation and management |
| Fee collection | Digital payments with tracking |
| Basic communication | Updates to parents |
Explicitly NOT in Scope
| Not Building | Why |
|---|---|
| ❌ Seat allocation / admissions decisions | Schools own this decision |
| ❌ Academic management | Not an LMS |
| ❌ ERP replacement | Not competing with school management systems |
Product Phases (India Rollout)
Phase 1: Discovery + Trust (MVP Launch)
Goal: Validate parent demand, school willingness, and trust perception.
Parent Experience
"Explore Schools" — separate from Activities:
| Feature | Details |
|---|---|
| Filters | Location, Board (CBSE/ICSE/State/IB), Grades offered |
| School profile pages | Overview, Photos, Board & grades, Facilities, Admissions timeline, Fees (range), Reviews |
| CTAs | "View Admissions Info", "Contact School" |
No payments yet — keep friction low.
School Experience
| Feature | Details |
|---|---|
| Claim or create profile | Self-serve onboarding |
| Upload content | Logo, Photos, Admissions info, Fee structure (optional ranges) |
| Dashboard | None yet — keep it light |
Why This Works
- Low trust risk
- Low ops burden
- High parent value
- Schools see visibility immediately
Launch market: 1–2 cities only (e.g., Bangalore, Hyderabad)
Phase 2: Admissions Inquiry Layer
Goal: Become the default inquiry channel for schools.
What We Add
| Feature | Details |
|---|---|
| Inquiry forms | Child age, Grade, Contact info |
| Notifications | Email / WhatsApp to schools |
| Lead dashboard | Simple view for schools to manage inquiries |
What Stays Out
| Not Yet | Why |
|---|---|
| ❌ No payments | Build trust first |
| ❌ No seat commitments | Schools own decisions |
This is where schools start depending on Juniro.
Phase 3: Fee Collection (Big Value Unlock)
Goal: Turn Juniro into financial infrastructure for schools.
What We Enable
| Fee Type | Description |
|---|---|
| Admission fees | One-time application/admission fees |
| Term fees | Quarterly/semester payments |
| Annual fees | Full year payments |
| Receipts | Automatic confirmations and records |
Critical Design Principles
| Actor | Controls |
|---|---|
| Schools | Fee schedules, Refund policies |
| Juniro | Payment UX, Transparency, Dispute handling |
Parent perception: "The safe way to pay school fees"
This is where monetization begins.
Phase 4: Platformization (Later)
Prerequisites:
- Trust is high
- Ops are stable
- Schools rely on Juniro
What We Add
| Feature | Description |
|---|---|
| Student rosters | Basic enrollment tracking |
| Communication | Messages, announcements |
| Reports | Fee collection reports, inquiry analytics |
| Annual contracts | SaaS agreements with schools |
This is SaaS, not marketplace.
Data Model (Future-Proof)
Model schools differently from activities:
Institution
├── Has profile
├── Has admissions cycles
├── Has fee structures
├── Has inquiries
└── Has payments
Activities remain:
- Session-based
- Time-bound
- Bookable
Do NOT reuse activity schemas for schools.
Monetization Strategy (India)
Phase 1-2: Build Trust
| Who | Cost |
|---|---|
| Schools | Free |
| Parents | Free |
Phase 3+: Monetize
| Model | Description |
|---|---|
| Fee collection commission | Small % of fees processed |
| Flat SaaS fee | Monthly/annual subscription for schools |
| Hybrid | Base fee + transaction commission |
Important: Do NOT charge schools before fees flow through Juniro.
Trust & Compliance (India-Specific)
Define these early:
| Area | What to Define |
|---|---|
| Refund handling | Clear policies, dispute resolution |
| Dispute escalation | Support process, SLAs |
| Receipts & GST | Tax compliance, proper documentation |
| Support SLAs | Response times, resolution guarantees |
This is where parents will judge Juniro hardest.
Signals It's Working
Proceed Indicators
| Signal | What It Means |
|---|---|
| Parents spend time on school profiles | Discovery value is real |
| Parents submit inquiries | Intent is strong |
| Schools respond quickly | They value the leads |
| Schools ask about fee payments | Ready for Phase 3 |
| Schools ask about visibility & branding | They see Juniro as their digital presence |
The Winning Signal
If schools ask: "Can parents pay fees here?" You've won.
What NOT to Do (India Context)
| Don't | Why |
|---|---|
| ❌ Don't mix schools with activities | Different mental models, different UX |
| ❌ Don't promise admissions outcomes | We don't control school decisions |
| ❌ Don't onboard public schools early | Different dynamics, slower decisions |
| ❌ Don't rush payments without ops readiness | Trust takes time |
| ❌ Don't compete with ERPs | Stay focused, don't bloat scope |
Architecture Principles
Separate Surfaces
Schools will be a separate surface, not mixed into activity search:
| Activities | Schools |
|---|---|
| "Find a class" | "Find a school" |
| Class cards | School cards |
| Book Now | Inquire / Apply |
| Session times | Grade levels, terms |
| Price per class | Tuition / fees |
Provider Type Extension
type ProviderType =
| 'individual' // Phase 1 (Activities)
| 'business' // Phase 1 (Activities)
| 'institution' // Schools (Future)
Enrollment Flow Separation
| Activities | Schools |
|---|---|
| Search → View → Book → Confirm | Search → View → Inquire → Apply → Accept/Decline |
Timeline & Entry Signals
When to Enter Schools Vertical
| Signal | Threshold |
|---|---|
| Activity provider liquidity | 100+ active providers per market |
| Booking volume | Consistent repeat bookings |
| Inbound demand | Schools asking to join |
| Team capacity | Dedicated enterprise/sales resource |
| Compliance readiness | Legal review of school data requirements |
Leading Indicators
- Parents asking "do you have schools?"
- Franchise education centers asking for multi-location tools
- Providers with "academy" or "school" in name signing up
Summary
| Aspect | Schools Approach |
|---|---|
| Product type | Infrastructure, not marketplace |
| Business model | B2B2C |
| First market | India (private schools) |
| Core value | Trust layer + payments rail |
| Competition | Fragmentation, not other platforms |
| Phase 1 focus | Discovery + Trust |
| Monetization trigger | Fee collection (Phase 3) |
References
Decision Log
| Date | Decision | Rationale |
|---|---|---|
| Jan 2026 | India-first for schools | Higher private school %, more fragmentation |
| Jan 2026 | Separate from activities UX | Different mental model, don't pollute search |
| Jan 2026 | No ERP features | Stay focused, avoid scope creep |
| Jan 2026 | Free until fee collection | Build trust before monetizing |