An event-ticketing platform, from an empty repo.
One platform, three sides — the fan who discovers and books, the producer who creates and markets, and the admin who keeps it trustworthy. I define all three.
A marketplace is really three products that have to agree — a producer's pricing choice shapes the fan's event page; an admin's approval flow decides how fast a producer goes live.
Discover and book · create and sell.
The consumer app leads with a city-aware discovery feed and event pages that carry the artist's energy straight into booking. The producer side makes going live self-serve: a zone-first event-creation flow, a revenue simulator that shows net payout before publish, discounts, multi-city tours, and embedded Meta/Google marketing tied to real ticket sales.
The calls that shaped it.
Zone-first, not seat-map-first
Most Indian events are GA/zone-based. Leading with zones cuts time-to-publish; reserved seating is the advanced path.
Simulate the money before publish
Showing net payout after fees & discounts converts pricing anxiety into confidence — and kills the #1 support ticket.
Admin controls are a designed surface
Onboarding, listing approval, payouts — spec'd as PRDs, because a marketplace is only as trustworthy as its slowest payout.
Proven on real, high-stakes events.
customer · producer · admin
on the platform
Tikiti demand capture
Tikiti is scaling toward public launch — numbers reflect real events run on it, not open-market GMV.