
I’ve always been driven by the belief that technology should make systems fairer and more accessible, not more frustrating. After personally experiencing the frustration of ticket scalping, fake QR codes, and outrageous fees, I realized how many industries are built around inefficiency and exploitation. Entrepreneurship is my way to fix that—to create products that empower people instead of gatekeeping access. I’m inspired by the idea that with the right vision and plan of execution, we can build something that changes millions of people’s experiences.
One of my proudest moments was when we got our first pieces of MVP code working and saw parts of the blockchain logic function successfully. It was the first real proof that our technical approach is viable—and that FairTix can actually deliver secure, verifiable ticketing the way we envisioned. Even though the full MVP isn’t live yet, seeing our early code run gave us huge confidence that we can get everything working by next semester. It made the project feel tangible and showed that our vision for fair, transparent ticketing is absolutely achievable.
How Did You Come Up With The Idea For Your Business?
The idea for FairTix came directly from personal frustration and conversations with others. After losing money to a fake concert ticket and seeing friends priced out of shows by scalpers, we started asking why ticketing still felt rigged. Through talking to users, we discovered a lot of distrust and want for change. Combining our backgrounds in software and engineering, we realized we could rebuild ticketing from the ground up—making every ticket verifiable, fairly priced, and community-owned.
FairTix

Industry
Mission
Our mission is to restore fairness and trust to live experiences by giving control back to the people who create and attend them. FairTix empowers fans, artists, and organizers through transparent pricing, verified ownership, and equitable revenue sharing. We believe access to live events shouldn’t be controlled by scalpers or corporations—every ticket should allow for connection, not exploitation.