I Was Wrong About Why Clubs Don't Segment Their Players
In March last year I wrote that most padel clubs treat all their regular players the same, without recognising that they have different needs. I filed it under common mistakes.
I owe those clubs a correction. It wasn't a mistake. It was a locked door.
Every operator knows the Tuesday-morning retiree and the Thursday-night competitor are different businesses. What they lacked was any way to tell one from the other at scale, because the record of who played, when, how often and how much sat inside a booking platform they could look at but not query.
That door opened this year, quietly, in a help-desk article.
What I left out
The piece laid out five stages a player moves through: attraction, initiation, retention, the fork between specialisation and stagnation, and dropout risk. For each I gave the mistake and the strategy — personalised follow-up after a first session, automated reminders when someone stops booking, reactivation offers, the right invitation to the right player.
Every one of those strategies shares an assumption I never examined: that the club knows which stage each player is in.
None did. Answering it meant somebody exporting spreadsheets on a Sunday and eyeballing three hundred names. I described a system that needed a data layer nobody had, then called its absence a mistake.
The life cycle was never the hard part. Knowing who is in which stage was.
The model already exists, and it isn't from padel
Playtomic's Club API now gives clubs programmatic access to their own booking data: booking IDs and timestamps, court information, player details including email and communication preferences, and payment information.
Look at what those fields actually are. When did this person last play. How often. How much do they spend.
Recency, frequency, monetary value. RFM — the segmentation model retail has used since the 1990s. It isn't clever and it isn't new; it is simply the most durable customer framework ever built. And until this year, no padel club in Europe could run it on its own members.
It maps onto the life cycle almost line for line. Recent first bookings with no frequency: initiation. High frequency, high recency: retention. Frequency falling while recency holds: the fork. Historically high frequency, low recency: dropout risk — and that player is worth more to you than any lead your next campaign will produce.
Where the API delivers, and where it doesn't
Life cycle stageSupported today?1. AttractionNo. Booking data begins after the player is already yours. This stage stays with your ads and community work.2. InitiationFully. A first booking is unambiguous. The follow-up message I described can now fire on its own.3. RetentionPartly. Frequency segmentation works. Lesson and class attendance doesn't — for clubs running Syltek, Playtomic warns schedule elements like classes may not sync.4. Specialisation vs stagnationWeakly. You can infer intent from patterns — the same slot every week reads differently from scattered weekend play. The real signals are tournaments, clinics and coaching, and that data is on the roadmap, not in the API.5. Dropout riskFully, and this is the strongest case. Recency is trivial to compute. A player who hasn't booked in thirty days can be flagged automatically, every night, forever.
Ninety days
Historical data reaches back ninety days. Access requires a Champion or Master subscription, and every location of a multi-site operator needs its own.
That ceiling will cost clubs more than the price does. Dropout is seasonal — the player you lost was lost over a winter, not a weekend. Ninety days lets you catch the lapse; it does not let you study the pattern. Start extracting nightly this month and you own a full season by spring. Query the API only when you want an answer, and you will have a ninety-day memory in perpetuity.
One way in, by design
The API is read-only. You can pull data out. You cannot create, modify or cancel a booking through it.
Read that as a strategic statement, not as something they haven't got round to building. The reservation is Playtomic's product. Open the write side and any competent developer could build a full club front-end on top of it, leaving Playtomic as a database with someone else's logo on the screen. Read-only draws the line precisely: the intelligence layer is yours, the transaction layer stays theirs. It also spares them every support ticket a third party would generate by creating double bookings and broken payment states in a live calendar.
So the flow runs one way, and the loop has to close somewhere else. Data leaves Playtomic and enters your system. Your system decides who needs to hear what. The message goes out by email, SMS or WhatsApp. The player books — back inside Playtomic, in the app they already use. Your next data pull shows the booking, and you attribute it yourself.
The loop closes through the player, not through the software.
There is an upside here that nobody selling you software will mention. Because no vendor can write to your calendar, no vendor can hold your operation hostage. Your switching cost stays low. Read-only is a ceiling on what any tool can do for you and, at the same time, a floor under how badly it can trap you.
Which is why the CRM stops being optional
A padel club's real asset was never the courts. Four courts are a commodity — anyone with capital can build them down the road and undercut you by two euros an hour. The asset is the list: twelve hundred players, and everything the club knows about each one.
Most operators believe they already have this, because they have a booking system. A booking system is not a CRM. It records transactions, not relationships. It knows a court was reserved at 19:00. It doesn't know the player is coming back from injury, wants to reach competitive level, always books with the same two friends, or complained twice about the lighting.
And if the only place your members exist is inside a platform that shows you ninety days, you don't own a database. You're renting a view of one.
The API is the pipe. The CRM is the tank. This is the year the tank stopped being a nice-to-have, because for the first time the pipe exists — one-way, on a clock, and everything flowing through it is yours to keep only if you actually keep it.
Playtomic is holding the key, and knows it
Playtomic reports more than 6,500 clubs on its management platform, over 18,000 courts and more than a million players. By a distance, the largest behavioural dataset in racket sports.
It made three moves this year that only make sense together. It opened the front door: clubs generate their own API credentials in Playtomic Manager, under Settings and Developer Tools. It closed the back one: a security update is disconnecting unauthorised automations, and the fix has to come from whoever built the integration, not from Playtomic support. And it built a gate between them — Playtomic Connect, certifying which external companies get structured access, with a verified badge and visibility inside Manager.
Read-only. Tier-gated. Certified partners only. Ninety days.
That is not a company casually publishing an API. It is a company deciding to become the platform layer of this industry, and to control who builds on top of it.
The roadmap tells you where the rest of the key sits: player data endpoints, enhanced payment history, and detailed event, activity and clinic data are all in development. Go back to the table — stages three and four, the ones barely supported today, are exactly what those three items unlock. Playtomic isn't withholding the next level of club management. It's releasing it in order, and it sets the order.
The category is already at the door
Evidence that this isn't theoretical arrived in my feed last week as a paid ad.
StackEleven, a US agency that markets racket-sport clubs and runs a CRM called GrowMyClub, is advertising that it has linked up with the biggest padel booking software, and that its integration with Playtomic will allow guest information to flow directly into its CRM.
Note the tense. Will allow. As of writing, the integrations listed on the product's own page are CourtReserve, PodPlay and Meta — American systems. Playtomic is not among them.
This is not a case against them. The product is credible and the direction of travel is one-way. The point is the timing: the first serious marketing platform is advertising into European padel before the connection has shipped, which tells you how valuable the position is.
When they call — and they will — you will be asked to hand over credentials giving a company outside the EU access to your members' emails, communication preferences and payment records. Your members booked a court. They did not consent to a marketing database in another jurisdiction. Ask who the controller is, who the processor is, what the legal basis for the messaging is, and where the data sits. I am not a lawyer and this is not legal advice, but no vendor will raise those questions for you.
The honest counter-argument
Most clubs losing money don't have a segmentation problem. They have a programming problem, a coaching problem or a pricing problem, and no CRM ever filled a Tuesday morning. A read-only API with a ninety-day window and a one-call-per-minute rate limit is plumbing, not transformation.
There is discomfort in the shape of it, too. The data describes your members, generated in your building, and your access to it now depends on your subscription tier and on which partners a platform chooses to certify.
Both true. Neither changes the sequence. The club that fixes its programming first still needs to know who stayed and who left.
Sixteen months ago I asked whether your club had a strategy for each stage of the player life cycle.
Here is the harder question. Open your booking system and name the twenty players who were regulars last season and haven't booked since. Not how many — name them.
If you can't, that is no longer a mistake. It's a decision.
Beyond Padel directs academies and advises club operators across Europe and the Middle East — Los Naranjos in Marbella, and Ocean Padel in Kuwait, which we designed and directed for over five years. We spend our time on the unglamorous layer: what your numbers actually say, and what your club does about them on Monday.
If you're being pitched software, or wondering what your own booking data is hiding, start here. A conversation, not a proposal.