Five years of bookings and I couldn't answer a simple question.

The question was a simple one: how many of our customers had booked more than once in the last two seasons? We'd been running events for years, we had a ticketing platform, we had booking records going back further than I cared to think about. I said I'd have the answer in an hour.

I didn't have it in three days. And even then, I wasn't sure it was right.

The data was all there, in theory. Thousands of bookings, spread across a platform that worked fine for selling tickets and processing payments. What it wasn't built for — what it had never promised to do — was tell me anything useful about the people who'd bought those tickets over time. Not without a lot of manual work and a spreadsheet that got unwieldy fast.

That was the day I realised the platform wasn't really our tool. We were one of its inputs.

Ticketing platforms are built to process transactions. That's what they're good at. The event goes live, someone finds it, they pay, they get a confirmation email, they show up. Smooth, fast, works every time.

What they're not built for is you understanding your own customers. The customer record lives in their system. The email address is attached to their login, not yours. The purchase history sits in their database. You have access to it through their interface — but access isn't the same as ownership, and you find that out the moment you try to do something the platform didn't design for.

We wanted to identify loyal customers and give them early access before tickets went on general sale. Sensible — the kind of thing that costs nothing and earns a lot of goodwill. What we discovered was that 'loyal' meant something different to us than it did to the platform. Their view was a single event. Ours was three years of people coming back. Getting from their view to our view meant downloading CSVs, matching email addresses, deduplicating, and hoping nothing had changed in the meantime. Email addresses change. Accounts get remade. People book under different names.

Two people and a working afternoon for a list we should have had in thirty seconds.

When you raise this with a platform's support team, the answer is usually some version of 'you can export your data.' Which is true. You can download a spreadsheet. A very large spreadsheet.

But a spreadsheet is a snapshot. The moment you export it, it starts going out of date. It doesn't update when someone cancels a booking, rebooks under a different email, or buys for next season. It's not a database — it's a photograph of one.

We ran that way for longer than I'd like to admit. Exporting, merging, cross-referencing, swearing at VLOOKUP. The individual steps were manageable and the events kept going fine. The trouble with manageable is that it hides how much time it's taking, and it hides what you're quietly not doing because the data's too messy to trust.

A spreadsheet is fine when you're running one or two events a year and your repeat rate is low enough that it doesn't really matter. It stops being fine when the cumulative admin starts eating into time that should go somewhere else — or when you notice you've stopped trying. Not sending that loyalty email. Not checking which customers came last year but not this year. Not ringing the people worth ringing. Not because you don't want to, but because getting to a clean list takes a whole afternoon you don't have.

That's the line. Not when it breaks. When it makes you stop bothering.

The fix isn't necessarily complicated. It might mean pulling booking records into a place you actually control. It might mean asking a harder question before you sign with the next platform: where does the customer record actually live, and can I get at it the way I need to? Some platforms are better than others on this. Worth asking before you've put five years of data in someone else's house.

We've helped a few businesses sort this out — getting the customer record back onto the operator's terms rather than the platform's. If you're starting to feel that friction, it's probably worth a conversation.