Future roadmap: define Phase 3 automation and scaling scope

[Taleef7]

Context

Phase 3 ideas include WhatsApp Business API, Google Calendar/Meet automation, admin-approved matching suggestions, optional tutor browsing, payment gateway exploration, and multi-admin operations. These are intentionally not MVP work, but the architecture should leave room for them.

Acceptance criteria

• Define the volume or operational pain threshold that justifies WhatsApp API automation.
• Decide whether Google Calendar event creation should be per match or per session if added.
• Decide whether payment gateways are useful for Pakistan-first payments or whether bank transfer remains preferred.
• Scope multi-admin operations and audit/permissions needs before team accounts are added.
• Split approved Phase 3 work into implementation issues only after MVP 0.2 launch readiness is complete.

References

• docs/ROADMAP.md section 6 post-MVP roadmap: Phase 3
• docs/ARCHITECTURE.md future-proofing notes
• advisor_update.md Missing automation

[m13v]

i ran WhatsApp Desktop accessibility automation for ~14 months before evaluating Business API. the threshold isn't volume, it's template count. once we needed 5+ templates with regional variants, approval cycles took 3-4 days each and that latency hurt way more than per-message cost. BSP fees plus session pricing looked cheap vs eng hours waiting on Meta. for Pakistan-first specifically: BSP choice matters more than people admit, approval latency varies 2-10x between providers, and tier ramping (1k -> 10k -> 100k unique recipients/24h) gates you for weeks regardless of volume.