Product purpose
Consulta exists to make consulting bookings feel complete instead of fragmented across chat, payment links, calendar notes, and video links.
- Clients see active consultants, rates, availability, and booking policies before choosing a time.
- Free intro sessions and paid sessions share the same confirmation and Beam handoff pattern.
- Consultants keep slot, policy, and notification visibility in the operator dashboard.
Platform boundaries
Consulta owns the consulting workflow. Beam is the reusable video component behind it, with product-agnostic room and join-token behavior.
- Consulta handles profile pages, availability, bookings, holds, policy windows, and payment state.
- Beam handles browser pre-join, room links, and video lifecycle without consulting-specific data.
- Provider integrations stay behind adapters so payments, video, and notifications can evolve cleanly.
Multi-consultant path
The first production customer is Cristian Silva. The public directory and admin flow are built for more consultants, but self-serve publishing is intentionally controlled during MVP.
- Active consultants appear in the consultant directory.
- New consultant requests enter an intake queue instead of instantly publishing a profile.
- Cristian's default rates and availability are configuration, not hardcoded product behavior.
Current launch posture
The MVP avoids card handling and per-minute video SaaS. Paid bookings confirm only from a verified payment webhook; free intros confirm without a payment record.
- SMTP and WOP are live; approved workshop messages are active while optional workers keep separate gates.
- Final legal/trust copy still needs Cristian's approval before it is treated as final policy.
- Real-device and 30-minute Beam media proof remain tracked separately in acceptance evidence.
