AI moat

Three PDFs the morning
after every event.

One for the organiser with attendance, revenue, NPS and no-show clusters plus an AI analyst read. One per speaker with per-session numbers and themed attendee feedback. One per sponsor with ranked leads and AI-drafted outreach emails. Auto-generated at 03:00 IST, auto-emailed by 03:30. The wrap-up work that used to steal your Monday now runs while you sleep.

Wrap-up · Auto
Post-event reports
1 organiser · 8 speakers · 12 sponsors sent
ORGANISER
TechSummit '26 — post-event
412 attended · ₹4.8L · NPS 62
SPEAKER
Priya Kumar — feedback themes
"clear examples · loved the demo"
SPONSOR
Razorpay — 128 scans · 22 hot leads
Top 12 leads + AI outreach drafts

A different story for each stakeholder.

🏛
Organiser report
Attendance, no-shows, turnout %, revenue and order count. NPS with promoter/passive/detractor split. No-show clusters by category and city. Plus a two-paragraph AI analyst read + 3-5 themes extracted from attendee comments.
🎤
Speaker report
Per-session check-ins vs capacity, direct attendee quotes mentioning the speaker or their session titles, and 2-3 AI-summarised themes covering both strengths and improvement areas. Sent to the speaker's email address.
💼
Sponsor ROI report
Booth scan totals, hot/warm/cold breakdown, top 12 leads ranked by seniority and engagement, plus an AI-drafted follow-up email per top lead. Delegated to the same engine that powers our standalone Sponsor ROI feature.

Two scheduled jobs. Zero manual work.

🌙
03:00 IST — sponsors
reports:sponsor-roi fires. For every event 24h+ past, every sponsor without a report yet gets one generated + emailed.
🌆
03:30 IST — organiser + speakers
reports:post-event --skip-sponsors fires 30 min later so shared work doesn't double-run. Organiser PDF + one PDF per speaker.
🔁
Idempotent
Both jobs check for existing generated_at timestamps and skip anything already done. Safe to re-run at 03:03 if the first attempt crashed.

Because the post-event report is where every event dies.

Ask any Indian event agency. Sunday night, event's done, everyone's celebrating. Monday morning the sponsor asks for their ROI report. Wednesday the client asks for the attendance summary. Thursday a speaker DMs you for their feedback. Now it's Friday and you're still building spreadsheets from the previous week's event instead of selling the next one.

This kills the flywheel. The clients you served best get worse follow-through than the ones you barely delivered to, because you're always one report behind. Sponsor renewal drops. Speaker rebooking drops. Client references dry up.

The AI post-event reports feature does that Monday-through-Friday drag in one background command. By the time the sponsor asks for the report, they already have it in their inbox. By the time the speaker follows up, their PDF is sitting there. You get to spend Monday on the next event, not last week's.

Where the wrap-up matters most.

The organiser report's NPS score and theme extraction feed directly off your feedback survey. One data pipeline, three outputs.
💼
The sponsor slice is the same engine, invoked from the same nightly job. Standalone if you want it, bundled with the post-event pack if you don't.
🎤
Speakers already have a portal for materials and bio. The post-event PDF closes the loop with their feedback in the same channel.

Questions we get

When do the reports fire?
Sponsor ROI runs at 03:00 IST the night after the event. Organiser + speaker reports run at 03:30 IST. Both are scheduled Laravel commands, idempotent, safe to re-run.
Where do NPS themes come from?
From your feedback survey's text questions. The AI provider chain reads up to 25 free-text comments per event and returns 3-5 themes with a one-line description each. Ratings feed the NPS score separately (1-5 or 0-10 scale, auto-detected).
How does the speaker report decide which comments are about that speaker?
Case-insensitive substring match on the speaker's name and their session titles across all free-text feedback. Not perfect, but catches most direct mentions. Themes are extracted by the AI from the matched comments.
What if I have no AI provider configured?
Reports still generate. The organiser report falls back to a hand-written narrative built from the raw numbers. Speaker theme extraction is skipped, but direct comments still appear in the PDF.
Can I regenerate + resend a report after the auto run?
Yes. The admin page has Regenerate and Email buttons on every report. The PDF is overwritten in place so links stay stable.
Stop chasing wrap-up work on Monday.
See all three post-event PDFs generate live in 5 minutes.