Why we chose to build small first: the UK-only decision
Three weeks before launch, our lead developer asked me a question I didn't want to answer: 'Why are we saying no to the US market?' We had interest from San Francisco. We had a working product. We had the infrastructure to scale globally in weeks. Instead, we chose to stay UK-only. That conversation shaped everything we've built since.
The temptation to go everywhere (and why we didn't)
Most app founders will tell you the dream. Launch, grow fast, raise money, expand globally. It's so obvious it barely feels like a choice. We spent a full quarter planning international expansion before we'd even launched FlashSeat to a single UK user.
Then we stopped and asked something harder: what does flash deals actually mean? Not 'deals on flights and tickets.' I mean the behaviour underneath. Someone sees a notification. They have maybe ninety seconds to decide. They check their calendar. They imagine the night. They book it. That decision-making is cultural. The urgency is cultural. The willingness to take a spontaneous trip to London for a gig on Saturday is a very particular thing.
We realised that expanding to ten countries at once meant watering down that insight into nothing. We'd be chasing 'deals' everywhere instead of understanding how Brits actually use time-limited travel and event bookings. So we stopped the expansion roadmap and doubled down on UK inventory. No apologies.
Building for one market means you actually talk to your users
Last month a user emailed to ask why she couldn't find Glastonbury re-sale deals in the app. Fair question. Turned out our event ticket partners didn't have reliable real-time access to festival secondary markets yet. Instead of building a feature that didn't work, we could tell her exactly why. We could tell her when we'd fix it. In person, almost.
That conversation would have been impossible at scale. At five markets, we'd have a support queue. At ten, we'd have a bot answering 'why is feature X missing' in seven languages. We'd lose the insight entirely.
Building for the UK meant we could call our flight partners directly. We could sit in on calls with the major event promoters. We could ask why Ticketmaster's API behaves differently at 9pm on a Thursday versus Sunday. We could find the 30% of deals that matter instead of chasing the 70% that don't. That's not scalable. It's the opposite of scalable. And that's the point.
The buyer fee tells the story
When we launched, our free tier came with an 8 to 10% buyer fee. I knew that would frustrate people. It did. But we kept it because it forced us to stay honest about unit economics in one market instead of pretending we'd figure it out later across fifteen.
The fee matters because it teaches us who actually books and who just browses. It taught us that Premium members (paying £7.99 a month or £59.99 a year to cut that fee to 4 to 5%) are genuinely engaged; they're not playing with the app, they're using it weekly. Pro subscribers with zero fees don't exist just as an ego play. They exist because we needed to understand the ceiling of what someone will pay to skip the fee entirely, in one market, with real behaviour.
If we'd launched globally, the fee structure would have been committee output. Instead it's data. It's a UK user telling us what they value, and us listening.
Why UK deals are harder than they look
People assume 'UK inventory' is easy. It's one country. Wrong. UK event ticketing and flight pricing are fragmented across dozens of partners, each with different APIs, update frequencies, and compliance requirements. Ryanair pricing moves every eight minutes. Ticketmaster and Live Nation don't always agree. Sports tickets from Ticket City behave differently from concert drops on AXS.
We spent weeks just mapping how deals actually propagate through UK booking systems. How fast? When? Who sees them first? The answer differs by event type, by season, by day of the week. That's not something you reverse-engineer while also managing Indian domestic flights or Australian festival bookings.
Staying UK-focused meant we could get ruthlessly good at one ecosystem instead of mediocre at many. Our saved searches and deal alerts work because we understand the rhythm of when deals actually drop here, not when some global model says they should.
The question we ask now
Eighteen months in, we've got regulars who open FlashSeat multiple times a week. The Premium and Pro tiers have real adoption. We know exactly why someone books a spontaneous trip or buys a ticket at 11pm on a Tuesday. We've built something people actually use, not something that works in theory.
Will we expand beyond the UK? Probably. But we'll do it properly. We'll pick one new market, spend three months understanding how deals actually flow there, talk to users until our ears hurt, and build something that feels native instead of transplanted.
The global expansion playbook will still be waiting. But by then we'll know what we're actually expanding.
Does your app need to be everywhere from day one, or is there value in being genuinely indispensable somewhere first?