Skip to content

PRODUCT_ROADMAP.md

Latest commit

 

History

History
206 lines (161 loc) · 9 KB

PRODUCT_ROADMAP.md

File metadata and controls

206 lines (161 loc) · 9 KB

Protocol Guide — Product Roadmap

Last updated: 2026-03-19 Status: Core app shipped. RAG accuracy fixed. Security hardened. Ready for growth.

Current State (Shipped)

Metric Value
Protocol chunks 64,397 (Gemini Embedding 2)
Agencies ~2,700
States with data CA (primary), partial TX, FL, NY, WA
Test suite 4,428 passing
Vulnerabilities 0
Deployment Netlify (frontend) + Railway (backend)

Core features complete: Jurisdiction-scoped RAG search, auth (Google/Apple/email), Stripe subscriptions, offline PWA, admin dashboard, voice input, tools (dosing calculator, arrest timer, ROSC checklist, quick reference, protocol comparison), bookmarks, push notifications, referral system.

Track A: Data Coverage Expansion (The Moat)

Goal: National protocol coverage. More states = more users = network effects.

A1: Automated Multi-State Ingestion Pipeline (10 steps)

Priority: HIGH | Effort: 2-3 days | Impact: 10x protocol coverage

  1. Refactor ingestion into generic state pipeline (scripts/parsers/generic-state-portal.ts exists)
  2. Build state protocol source registry (URLs, PDF patterns, update frequency)
  3. Automate PDF discovery per state (crawler patterns differ by state)
  4. Standardize text extraction across PDF formats (some are scanned images → OCR)
  5. Implement chunk quality validation (reject garbage extractions)
  6. Build embedding pipeline with progress tracking and resume support
  7. Create state coverage dashboard (admin) — chunks per agency, last updated, quality score
  8. Add automated monitoring for protocol updates (cron: check source URLs monthly)
  9. Build county-agency mapping tool for new states
  10. Deploy and ingest top 5 states by EMS population

Key files: scripts/parsers/, scripts/lib/lemsa-processor.ts, server/_core/embeddings/batch.ts

A2: Top 10 States by EMS Population (10 steps)

Priority: HIGH | Effort: 1-2 weeks | Depends on: A1

Target states (by active EMS providers):

  1. Texas (TX) — ~80K providers
  2. Florida (FL) — ~60K providers
  3. New York (NY) — ~55K providers
  4. Pennsylvania (PA) — ~45K providers
  5. Ohio (OH) — ~40K providers
  6. Illinois (IL) — ~35K providers
  7. North Carolina (NC) — ~30K providers
  8. Georgia (GA) — ~28K providers
  9. Virginia (VA) — ~25K providers
  10. Michigan (MI) — ~22K providers

Steps per state:

  1. Identify protocol sources (state EMS office, LEMSA websites)
  2. Map agencies and counties
  3. Run ingestion pipeline
  4. Validate search accuracy for that state
  5. Update coverage map in app

A3: National Coverage — All 50 States (10 steps)

Priority: MEDIUM | Effort: 1-2 months | Depends on: A2

  1. Batch-process remaining 35+ states through automated pipeline
  2. Handle edge cases: military bases, tribal lands, federal jurisdictions
  3. Build protocol version tracking (detect when agencies update protocols)
  4. Implement automated re-ingestion on update detection
  5. Create public coverage map page (SEO + social proof)
  6. Add "Request my agency" feature for uncovered agencies
  7. Build protocol freshness scoring (stale protocols get flagged)
  8. Add interstate protocol comparison feature
  9. Implement protocol change notifications (push to subscribed users)
  10. Publish national coverage milestone (press release, social media)

Track B: Growth & Marketing (User Acquisition)

Goal: 10K MAU within 6 months. EMS community is ~1.3M providers in the US.

B1: Referral & Email Activation (10 steps)

Priority: HIGH | Effort: 2-3 days | Impact: Viral coefficient

  1. Activate referral system (code exists in server/routers/referral/) — verify end-to-end flow
  2. Design referral reward structure (7 free Pro days exists; test higher incentives)
  3. Build referral tracking dashboard (admin) — codes generated, redeemed, conversion rate
  4. Implement email drip campaign activation (code exists in server/services/send-drip-emails.ts)
  5. Create Day 1 welcome email template (value prop + first search guide)
  6. Create Day 3 tips email (power user features: voice search, offline, tools)
  7. Create Day 7 Pro pitch email (show what they're missing + discount code)
  8. Build email analytics dashboard (sent, opened, clicked, converted)
  9. A/B test referral incentive amounts (3 vs 7 vs 14 Pro days)
  10. Add in-app referral prompt after 3rd successful search

Key files: server/routers/referral/, server/services/send-drip-emails.ts

B2: App Store Optimization + SEO (10 steps)

Priority: MEDIUM | Effort: 1 week | Depends on: B1

  1. Submit iOS app to App Store (eas build --profile production --platform ios)
  2. Submit Android app to Google Play (eas build --profile production --platform android)
  3. Write App Store listing copy (keywords: "EMS protocols", "paramedic reference", "LEMSA")
  4. Create App Store screenshots (search, results, tools, offline)
  5. Build keyword-optimized landing pages per state (/ems-protocols/california, etc.)
  6. Add structured data (JSON-LD) for MedicalBusiness schema
  7. Create blog content: "How to find your local EMS protocols" (SEO target)
  8. Configure Google Analytics with real tracking ID (placeholder exists)
  9. Build SEO sitemap with dynamic protocol coverage pages
  10. Submit sitemap to Google Search Console + Bing Webmaster

B3: Community & Social Proof (10 steps)

Priority: LOW | Effort: Ongoing | Depends on: B2

  1. Set up Reddit presence in r/ems, r/NewToEMS, r/Paramedics
  2. Create Twitter/X account for Protocol Guide
  3. Build testimonial collection system (in-app prompt after 10+ searches)
  4. Design "Used by X paramedics" social proof badge
  5. Contact EMS podcasts for guest appearances
  6. Create TikTok educational content strategy
  7. Partner with EMS training programs for early adoption
  8. Build EMS conference presence calendar
  9. Design referral landing page with social proof
  10. Implement NPS survey at Day 30

Track C: Enterprise / B2B (Revenue)

Goal: $10K MRR from department subscriptions within 6 months.

C1: Agency Admin Portal Polish (10 steps)

Priority: HIGH | Effort: 3-5 days | Impact: Revenue enabler

  1. Audit existing agency admin system (6+ router files exist, mostly complete)
  2. Fix any remaining gaps in staff management (invite, remove, role assignment)
  3. Build agency-level analytics dashboard (searches per provider, popular protocols)
  4. Implement seat-based billing for departments (Stripe quantity subscriptions)
  5. Create agency onboarding flow (sign up → invite team → upload protocols)
  6. Build custom protocol upload UI (PDF → extract → embed → serve)
  7. Add agency branding options (logo, color scheme in protocol viewer)
  8. Create department admin training documentation
  9. Build agency billing portal (invoices, seat management, upgrade/downgrade)
  10. Implement agency-level usage reports (exportable PDF/CSV)

Key files: server/routers/agency-admin/, app/admin/

C2: Advanced Enterprise Features (10 steps)

Priority: MEDIUM | Effort: 2-3 weeks | Depends on: C1

  1. Build custom protocol version management (draft → review → publish)
  2. Implement protocol approval workflows (admin review before publish)
  3. Add audit logging for all protocol changes (compliance requirement)
  4. Build ImageTrend/ESO integration for CAD dispatch data
  5. Create API access tier for enterprise (REST API keys, rate limits, docs)
  6. Build SSO integration (SAML/OIDC for large departments)
  7. Implement multi-agency comparison for medical directors
  8. Add compliance reporting (protocol adherence metrics)
  9. Build white-label deployment option (custom domain, branding)
  10. Create enterprise sales materials and pricing page

Execution Order (Recommended)

Month 1:  A1 (pipeline) + B1 (referral/email) + C1 (agency portal)
Month 2:  A2 (top 10 states) + B2 (App Store/SEO)
Month 3:  A3 (national) + C2 (enterprise features)
Month 4+: B3 (community) + iterate based on data

Each phase is a self-contained plan that can be executed with /agents-plan in a Claude Code session. Start any phase with:

/agents-plan [Track][Phase] - e.g., "Execute Track A1: Automated Multi-State Ingestion Pipeline"

Key Metrics to Track

Metric Current Month 1 Target Month 3 Target
States with data 5 10 50
Protocol chunks 64K 150K 500K+
MAU 0 500 5,000
Pro subscribers 0 50 500
Department accounts 0 5 25
MRR $0 $500 $5,000
App Store rating N/A 4.5+ 4.7+

Technical Debt to Address Along the Way

  • Fix 21 pre-existing test failures (rate-limit, drip-email, stripe, user-router)
  • Fix icon-symbol.web.tsx duplicate property TS errors
  • Replace Google Analytics placeholder with real tracking ID
  • Enable dark mode (currently intentionally disabled)
  • Add E2E tests for critical user journeys (Playwright)
  • Upgrade Expo when 55+ releases (for new APIs)
  • Consider migrating from Voyage fallback to Gemini-only — Done 2026-03-24 (Voyage fully removed)