Launch Implementation Gaps
What's needed to go from current state to MVP launch.
Last Updated: January 17, 2026
Executive Summary
| Layer | Status | Notes |
|---|---|---|
| Pre-Launch Tools | ✅ Done | Waitlists, CRM, email marketing, analytics |
| Backend API | ✅ MVP Done | 11 routes, 16 tables, auth ready |
| Frontend UIs | ✅ Done | All 4 portals deployed |
| Frontend↔API Wiring | ❌ Gap | Frontends use mock data |
| Payments | 🟡 Partial | Config ready, webhooks TODO |
| Communications | 🟡 Partial | Email ready, WhatsApp TODO |
Critical Path: Wire frontends to existing API (3-4 weeks)
What's Done ✅
Pre-Launch Infrastructure
| Component | Status | Notes |
|---|---|---|
| Parent waitlist (juniro.com) | ✅ Done | Collecting signups |
| Provider waitlist (juniro.com/providers) | ✅ Done | Collecting signups |
| Viral Loops referral | ✅ Done | K-factor tracking |
| Loops email marketing | ✅ Done | Welcome sequences |
| Posthog analytics | ✅ Done | Events tracking |
| Attio CRM | ✅ Done | Provider pipeline |
| Resend transactional email | ✅ Done | Templates ready |
Backend API (juniro-api)
| Component | Status | Notes |
|---|---|---|
| Supabase Auth integration | ✅ Done | JWT validation |
| PostgreSQL + Prisma | ✅ Done | 16 tables deployed |
| User/Parent/Child APIs | ✅ Done | CRUD operations |
| Provider/Location APIs | ✅ Done | Multi-staff support |
| Activity/Offering/Session APIs | ✅ Done | Full lifecycle |
| Booking APIs | ✅ Done | Status transitions |
| Review APIs | ✅ Done | Ratings + responses |
| Category/Geography APIs | ✅ Done | Hierarchical data |
| OpenAPI documentation | ✅ Done | /docs endpoint |
Frontend UIs
| Portal | Status | Deployment |
|---|---|---|
| Public Website | ✅ UI Complete | juniro.com |
| Parents Portal | ✅ UI Complete | juniro-web-parents.vercel.app |
| Providers Portal | ✅ UI Complete | juniro-web-providers.vercel.app |
| Admin Portal | ✅ UI Complete | juniro-web-admin.vercel.app |
Design System
| Component | Status | Notes |
|---|---|---|
| Core components | ✅ 409 components | Button, Input, Modal, etc. |
| Storybook docs | ✅ 349 stories | Full documentation |
| Dark mode | ✅ Done | All components |
| Accessibility | ✅ Done | ARIA, keyboard nav |
What's Missing ❌
P0: Critical for MVP Launch
1. Wire Frontends to API
Status: Not started Effort: 2-3 weeks Impact: Enables real user data
| Task | Effort | Notes |
|---|---|---|
| Add Supabase Auth to all frontends | 3 days | Replace mock auth |
| Create API client library | 2 days | Shared fetch wrapper |
| Wire public site search | 2 days | GET /activities |
| Wire activity detail | 1 day | GET /activities/:id |
| Wire booking flow | 3 days | POST /bookings |
| Wire parent profile | 2 days | GET/PUT /me/profile |
| Wire children management | 2 days | CRUD /me/children |
| Wire provider dashboard | 3 days | Multiple endpoints |
2. Payment Webhooks
Status: Config ready, logic TODO Effort: 1 week Impact: Enables paid bookings
| Task | Effort | Notes |
|---|---|---|
| Stripe webhook handler | 3 days | payment_intent.succeeded |
| Razorpay webhook handler | 3 days | payment.captured |
| Update booking status on payment | 1 day | pending_payment → confirmed |
| Wire payment UI to API | 2 days | Create payment intent |
3. Booking Confirmation Emails
Status: Resend ready, templates TODO Effort: 3 days Impact: User experience
| Task | Effort | Notes |
|---|---|---|
| Create email templates | 1 day | Booking confirmed, reminder |
| Integrate with booking flow | 1 day | Trigger on status change |
| Provider notification email | 1 day | New booking alert |
P1: Should Have at Launch
4. WhatsApp Notifications (India)
Status: Not started Effort: 1 week Impact: India market engagement
| Task | Effort | Notes |
|---|---|---|
| Apply for Gupshup WhatsApp Business API | 1 day | Approval takes 1-3 days |
| Create message templates | 2 days | Meta approval needed |
| Integrate API in backend | 3 days | Booking notifications |
5. Admin API Endpoints
Status: Partial Effort: 1 week Impact: Operations capability
| Task | Effort | Notes |
|---|---|---|
| Provider verification endpoint | 2 days | Approve/reject |
| Market launch control | 2 days | City activation |
| Admin dashboard metrics | 2 days | Aggregated stats |
| Wire admin portal to API | 3 days | Replace mock data |
P2: Nice to Have
| Feature | Status | Notes |
|---|---|---|
| AI-powered search | Config ready | Groq + Together AI |
| Advanced analytics | Planned | Provider/parent insights |
| Real-time notifications | Planned | WebSocket support |
| Mobile apps | Planned | React Native |
Implementation Roadmap
Week 1-2: Core Wiring
| Day | Focus | Deliverables |
|---|---|---|
| 1-2 | Auth setup | Supabase Auth in all frontends |
| 3-4 | API client | Shared fetch library, error handling |
| 5-6 | Public site | Search + activity detail wired |
| 7-8 | Booking flow | Create booking → payment |
| 9-10 | Parent portal | Profile, children, bookings |
Week 3: Payments
| Day | Focus | Deliverables |
|---|---|---|
| 1-2 | Stripe webhooks | Payment status updates |
| 3-4 | Razorpay webhooks | India payment flow |
| 5 | Testing | End-to-end booking with payment |
Week 4: Communications + Polish
| Day | Focus | Deliverables |
|---|---|---|
| 1-2 | Email notifications | Booking confirmations |
| 3-4 | Provider portal wiring | Dashboard, classes, bookings |
| 5 | Testing + fixes | Bug fixes, edge cases |
Week 5-6: Launch Prep
| Day | Focus | Deliverables |
|---|---|---|
| 1-3 | Admin portal | Wire to API |
| 4-5 | WhatsApp setup | Gupshup integration |
| 6-7 | End-to-end testing | Full user journeys |
| 8-10 | Soft launch | Waitlist users invited |
Quick Reference
What's Live Now
juniro.com → Waitlist (collecting signups)
juniro-web-parents.vercel.app → Demo mode (mock data)
juniro-web-providers.vercel.app → Demo mode (mock data)
juniro-web-admin.vercel.app → Password protected (mock data)
api.us.juniro.com → API ready (not connected)
api.us.juniro.com/docs → API documentation
Environment URLs
| Environment | Public | Parents | Providers | Admin | API |
|---|---|---|---|---|---|
| Production | juniro.com | parents.juniro.com | providers.juniro.com | admin.juniro.com | api.us.juniro.com |
| Staging | TBD | TBD | TBD | TBD | TBD |
| Local | localhost:4000 | localhost:4001 | localhost:4002 | localhost:4003 | localhost:5001 |
Key Repositories
| Repo | Purpose | Status |
|---|---|---|
| juniro-design | Design system | ✅ 409 components |
| juniro-web-public | Public website | ✅ UI done, needs API |
| juniro-web-parents | Parents portal | ✅ UI done, needs API |
| juniro-web-providers | Providers portal | ✅ UI done, needs API |
| juniro-web-admin | Admin portal | ✅ UI done, needs API |
| juniro-api | Backend API | ✅ MVP done |
| juniro-docs | Documentation | ✅ Maintained |
Decision Log
| Decision | Choice | Date | Notes |
|---|---|---|---|
| Auth provider | Supabase Auth | Jan 2026 | Already integrated in API |
| Database | PostgreSQL + Prisma | Jan 2026 | Schema deployed |
| API framework | Hono | Jan 2026 | Lightweight, type-safe |
| Payments (US) | Stripe | Jan 2026 | Config ready |
| Payments (India) | Razorpay | Jan 2026 | Config ready |
| Hosting | Vercel | Jan 2026 | All apps deployed |
| Resend | Jan 2026 | Templates ready | |
| Gupshup | Planned | India market |
Success Criteria for MVP Launch
- Users can sign up/login with real accounts
- Parents can search and view real activities
- Parents can book and pay for sessions
- Providers can see their bookings
- Booking confirmation emails are sent
- Admin can verify providers
- Analytics tracking real events
See Product Status for detailed feature-by-feature breakdown.