Demo script — 5 minutes, end to end
Status: template — rehearsed and recorded on Day 4. Audience: Sriram, Rohan.
Pre-flight (10 minutes before)
-
docker compose -f deploy/compose.yml ps— all green - Gateway upstream warm (one throwaway chat through the chain)
- Demo phone + Telegram open on a phone; bot NOT already in contact-share state
- Manager DB seeded: no half-created bots; one fresh phone number reserved
- Density screen ready:
e2e/density.shoutput +docker stats --no-stream - Soak report printed (
docs/economics.mdfilled)
The script
- Homepage (30s) —
aquila.exaflair.com: "your number is your account" → type the demo number → lands on<phone>.aquila.exaflair.comwelcome page. - One Telegram tap (45s) — tap Verify → Telegram opens → Share Contact → OTP arrives → enter → workspace unlocked. "That was the entire signup — no password, no form."
- Build the team (60s) — create VEGA + NOVA + PULSAR; show each persona card; point at the pending 6am routine.
- The bots speak (60s) — Telegram: force-run the inbox digest → live message with the Hinglish summary + drafted reply. Reply in chat → bot responds in context.
- The boring miracle (45s) — manager dashboard: all bots green, per-bot ₹ spend this month, density meter. "X bots on one laptop slice; a mini PC runs more."
- The economics (45s) —
docs/economics.mdverdict table: cost/bot vs ₹250 at 10/15/20 per node. "This is the number you asked for." - Close (15s) — what's next: WhatsApp notifications (official API), Rohan's S3 for bot files, K8s mapping so this rides the platform.
Contingencies
- Telegram flaky → workspace chat panel (same core, web channel).
- Upstream 429 → gateway fallback chain kicks in; call it out as a feature.
- A routine misfires →
/routine/{name}/runfrom the admin panel; show the logs.