Event Ticketing: Payments Rebuilt
Stripe wired without payment status tracking. Worked in demos. Would have failed on the first busy on-sale.
- 8 weeks
- audit to MVP
- ~30k
- tickets a year, first venue
- Nov 2026
- ticket sales launch
Eight systems I built or rebuilt since 2018. Four have the full story: what was broken, what I decided and why, and the proof. The other four get a row.
Stripe wired without payment status tracking. Worked in demos. Would have failed on the first busy on-sale.
A community organization with nothing digital. Membership, payments, store, events and delivery had to exist in three months.
Users load crypto and spend it through virtual cards. The backend had to exist first: KYC, compliance, transactions, card issuance.
About 80 agents ran the busiest agency in the city on ten Telegram groups and a set of spreadsheets.
Several farm locations logging shifts, fuel and GPS by hand, during a war in which GPS gets jammed.
Drivers used a Telegram bot: two taps to open and close a shift, field search by buttons, no login. When GPS was jammed the system fell back to driver input. Payroll and bonuses were calculated from the same data.
Find contractors linked to the companies ordering from them, across the national procurement history.
Every tender, auction and bid from the Prozorro API, cross-referenced. Storage grew from 1 TB to 16 TB. Built for a media investigation, used by media, NGOs and business.
Rank the top 400 universities on admission exam data and conversion into master's programs.
Full Python pipeline: collection, scoring, dashboards. Published by Forbes Ukraine.
From downloaders and game bots to lead funnels and daily digests for marketing teams.
Some of the first Telegram mini-apps. Survey bots, a tarot bot, a bot that put a client's site admin panels inside Telegram. Clients in Ukraine, UAE, Greece, Cyprus, France, Germany, Denmark, UK, US, Kazakhstan, Georgia and Azerbaijan.