Tixoo Ticketing Platform

Tixoo is an event ticketing platform for India, built against a signed launch date. Most of the job was deciding what not to build, and writing down every change that moved money or time.

The problem

Tixoo is a ticketing and live experiences platform for India. The agreement fixed an MVP launch date, and the scope behind it was everything a marketplace needs at once: a customer app on both stores, a promoter dashboard with a drag and drop seat map, an admin console, payments, QR entry at the gate, subscriptions.

Then a founding member marketing site was added on top, with three working days before its own launch. A weekend and a public holiday sat inside that window. Nothing about the date was negotiable, so everything about the scope had to be.

What I did

I cut the marketing site down to the one flow that had to work

The brief had five steps, a district level counter, an app preview and an interests picker. With only three working days, I took the funnel down to state, district, member, success, and got that signed off before anyone opened a file. The cut sections came back after launch, not before it.

I made the counter fake on purpose and put it in writing

The founding member count had to look alive on day one with nobody in it, and a real backend for that would have eaten the window. So I shipped a seeded front end counter with deterministic time based growth, which means it holds its value on refresh, and I wrote the decision into the shared document rather than leaving it to be discovered.

I held subscriptions out of the first store submission

Tixoo Plus runs on subscriptions, which have to be tested and released on Android and iOS together, and their Apple account was still migrating from personal to business. Submitting with it risked the review on both platforms, so it came out of the build and went back in as a paired release once the migration cleared.

I priced the post launch change list in developer days

When the change requests arrived, I split them into web bugs, web copy, web features, app bugs and the payment layer, put an effort figure on each, and showed the calendar estimate at two developers and at three. The conversation then stopped being about whether the list was reasonable and started being about how many people were on it.

What shipped

The founding member site went out on its date, and tixoo.in went on to carry the public site, with the events listing, individual event pages with real seat pricing, how it works, the perks and the policy set. The customer app was built to the signed scope with discovery, booking, QR tickets, Razorpay payments and Tixoo Cash, and the change list shipped as one tested build together with the payment layer rather than in pieces, so payments and the app changes were validated against each other. The store release sat with them.