FAQ
Frequently asked questions
Clear answers about wallet credit, usage, subscriptions, and how Tycoon charges for work.
Luma already handles RSVPs, reminders, and check-in. What does this add?
Luma is a great RSVP + event-page tool. What it doesn't do: source venues, negotiate F&B, curate your guest list from your CRM, write invitation copy in your voice, coordinate vendors day-of, track ROI in your pipeline, follow up with segmented sequences. Tycoon orchestrates across Luma + your other tools. You keep using Luma for what it's best at (the event page); Tycoon handles the 80% of event planning that isn't the RSVP page.
What about bigger events — conferences with 500+ people, multiple tracks, sponsor booths?
Workflow scales up with added coordination layers. AI COO handles: sponsor outreach + contract management, speaker selection + logistics (flights, hotels, AV), track scheduling in Sched or similar, attendee segmentation (VIPs, general, press), sponsor ROI tracking. For conferences >500 attendees, you'll still want a human event coordinator for day-of floor management — but their job becomes 'execute the plan' rather than 'build the plan', and planning time drops from 6 months to 2 months.
International events — different currency, taxes, venue norms. Does it handle that?
Yes, with country-specific adaptations. For EU events: venue pricing in EUR with VAT clarity, catering that accounts for local dietary norms, data handling GDPR-compliant, invitations that comply with local marketing laws. For Asia: venue sourcing from local networks (Peerspace has less coverage; AI COO uses Lark/WeChat for outreach in China, Jimoti in Japan), F&B norms that differ from US standards. You set the country; the workflow adapts.
We host recurring events (monthly meetup). Does the workflow compound?
Yes — this is where it shines. After event 1, AI COO has: vendor relationships (preferred venue, trusted caterer, reliable photographer), audience data (who came, who RSVP'd and no-showed, who engaged), messaging that worked (subject lines, invite copy). Event 2 onward, planning time drops 60-70% because the decision tree is pre-populated. By event 5 you have a true playbook — same format, predictable turnout, known-good vendors.
What if I want the event to feel intimate and unscripted, not corporate?
Workflow adapts to vibe. For an intimate dinner: less structure (no formal talks, just dinner + curated seating), invitation copy that's personal not marketing-y, zero branded signage, no name tags unless you want them. The AI's default for small founder dinners is minimal-overhead curation — seat a great mix of people, feed them well, get out of the way. The automation is on logistics, not the social texture. You set the tone; the workflow removes friction.