More than 400,000 end customer accounts have moved onto PodPlay from another club management system.
This is a piece about why that line moves up and to the right, and about the objection that says it shouldn't.
When an existing operator tells us no, it is almost never because they think the system they are on is better.
It is because switching feels like a risk they have to absorb personally. Their staff know the current software. Their members know the current app. Programming, memberships, recurring billing, and years of accumulated custom logic all live inside it. The fear is not that PodPlay is worse. The fear is a bad six weeks — confused members, broken billing, staff learning software instead of running a club, and a handful of customers who use the disruption as an excuse to leave.
That is a real objection and it deserves a real answer.
The most honest answer we have is the number at the top of this post. Migration risk is highest for the people who have done it least. We have moved more than 400,000 customer accounts, and the clubs on the other side of that number are not fragile — they are the ones that grew.
The second answer is arithmetic, and we'll come back to it at the end. The cost of migrating is one-time, bounded, and knowable. The cost of not migrating is recurring, unbounded, and invisible — which is exactly why it never shows up on the list of things an operator is worried about.
When we founded PodPlay we thought the timing was good for two specific reasons. Pickleball was exploding, and we had a product with characteristics nobody else had — because it was initially built to run our own clubs which operated without a front desk. That gave us a right to win.
But there is a rule in vertical software that every founder learns eventually. When you start a vertical SaaS business, you want to align yourself with a fast-growing greenfield opportunity, because it is very hard to win migrations as the newest entrant. Even when your product is clearly better. Switching costs are real, incumbency is real, and "nobody got fired for staying" is a durable strategy for a busy operator.
So our expectation was straightforward. We would spend our first three years winning new builds and making the clubs we served successful. Migrations would be few, and they would come almost entirely from tech-forward operators — the ones who understood that being early meant helping shape the PodPlay roadmap.
Migrations came sooner, in greater volume, and at a faster pace than we modeled. And the pace is accelerating.
We attribute that to two things.
The first is that our product has become accepted as the standard at the premium end of the market. Operators do not read a feature matrix and switch. They play at another club, or their members do, and the difference is obvious in about ninety seconds. That is a slow way to build a pipeline and an extremely durable one.
The second is that the industry itself matured. We wrote about this in After the Gold Rush for The Dink: the build-first era is over, supply has caught up with demand, and the basis of competition has shifted from courts to experiences and community. When "being open" was the whole strategy, your software only had to take a booking. When experience is the strategy, your technology is the experience — before, during, and after the time a player spends at your club.
Clubs are not migrating because they discovered a better booking form. They are migrating because the job changed.
1. Mobile First From Inception
Ninety percent of your customers will book on their phone. That has been true for years and most club software still doesn't act like it.
We had no choice. PodPlay's technology was built to run PingPod, a network of autonomous table tennis clubs that operate 24/7 with nobody behind a desk. When there is no staff to bridge the gap between a confusing interface and a confused customer, the app has to be self-evident or the entire model collapses. Building for the unstaffed case forced a discipline on us that a staffed-first product never has to develop: no grid-based calendars, vertical scroll instead of horizontal, quick filters, anonymous browsing before account creation were all there from inception. I laid out the full set of principles in Your App Is Your Front Door.
The DNA matters too. Our engineering team is led by co-founder and CTO Ilya Rivkin, who worked on the Nike+ Running and Equinox mobile apps at R/GA before leading mobile development for Clarity Money, which was acquired by Goldman Sachs. The majority of our engineering, product, and design team worked on those projects with each other. That is a team whose instincts were formed building consumer mobile experiences at scale.
Other companies have made the transition from desktop to mobile, and some have made it well. But it is hard to escape a desktop heritage. We never had a desktop application that needed to be translated, retrofitted, or refactored. There was nothing to escape.
The scoreboard on that: as of the end of Q2 2026, PodPlay-powered apps carried more than 13,500 App Store ratings at an average of 4.91. When we published Your App Is Your Front Door in September 2025, that number was 5,200 ratings. The rating didn't move. The sample size nearly tripled.
2. Built With Taste
Taste is the ability to make product decisions that transcend pure utility — choices driven by aesthetic sensibility, cultural intuition, and a sharp point of view. It sounds soft. It is the hardest thing on this list to copy.
Ilya says it best: "the right way is faster than the fast way." Shortcuts, quick hacks, and hasty integrations are cheap on the day you ship them and expensive every day after. Restraint — shipping 90% of the functionality with none of the friction rather than 100% with all of it — is a decision you have to make over and over, and it only compounds if you make it consistently. We wrote the long version in Taste as a Moat in the Age of AI.
Operators and customers feel this before they can articulate it.
3. One Stack, Not Seven
PodPlay is the only platform in racquet sports that combines club and tournament management software, video capture hardware, and autonomous capabilities in a single integrated system. Everything else in the market is point solutions or loose integrations — which in practice means multiple logins, multiple apps, separate vendor relationships, and staff context-switching all day between systems that were never designed to talk to each other, resulting in more costs, compounded and covert, than what the baselines tell you.
Building the full stack is genuinely hard. Hardware is hard, software is hard, and the intersection is harder than either. But it is the only way to build the experiences that matter, because the interesting things happen at the seams.
A few that are simply not possible any other way:
Point solutions don't compound. They fragment. Integrated systems compound.
4. A Ticket Into the Content Ecosystem
This is the reason operators least expect and end up caring about most.
Most pickleball is played by amateurs. Almost all pickleball content is about professionals. PodPlay solved the first half of that gap — who has the camera — by putting capture in the club. The second half is harder: who has the audience.
So we built the distribution. PodPlay's replay content has been viewed more than 35 million times across Instagram, YouTube, and LinkedIn, from 572 trackable posts of amateur highlights captured at PodPlay-powered clubs. That runs through our own channels and through the biggest media names in the sport — ClipTHAT with The Dink, the Monthly Top 10 Amateur Highlights with The Kitchen, Highlight and Blooper of the Week with DUPR, Best of Pickleball with Kaitlyn Kerr, and the PodPlay Creator Collective. And this is just the posts and views we can track. There is a long tail of content based on PodPlay replays that doesn't run through our channels.
No other club platform has anything like it, because content is not a marketing department at PodPlay. It's infrastructure. (Content Is Infrastructure)
What that means for an operator: your club's courts become a source of content with a real audience attached. A member's best point at your club is one tap from a feed with millions of views on it — carrying your club's name. Being on PodPlay is a ticket to participate in the most robust ecosystem for amateur pickleball highlights that exists. Nothing about your booking software has ever done that for you before.
5. The Autonomous Category
For the subset of operators who want to run autonomously, we are the category leader, and we created the category with PingPod.
More than 70 autonomous clubs are now signed up on the platform. The model has done two things the industry did not expect. It made small-format clubs viable in dense urban markets where the rent math never worked for a big build. And it brought pickleball and other sports to smaller markets that cannot support a large club at all. Use technology to increase available hours and reduce overhead, and a whole class of previously impossible clubs becomes possible.
The proof is in the operating data, not the pitch. Pickleball 365 is a three-court unstaffed club in Fair Haven, Michigan. Trailing-twelve-month utilization: 46% - based on 24 hours. Most recent month at the time of writing: 57% — 13.7 court-hours booked per day, per court.
Autonomous is also a non-trivial model to execute. There are a hundred small operational decisions that determine whether it works, and every one of them is a thing we have already gotten wrong once. PingPod has run hundreds of thousands of reservations through this model across roughly 20 locations. We would never claim to have seen everything. We have seen a lot, and that accumulated wisdom is embedded in the product our autonomous operators use.
You could try to assemble it yourself. A QR code on the door, an outsourced monitoring vendor, PIN codes, a booking tool that has never heard of any of them. We know exactly what that stack is worth, because we ran one. When PingPod acquired Sharks Pool Club in 2023, it was operating on a patchwork of point solutions with a person in the loop for most of what the technology should have handled. Operators almost never get to see the counterfactual. We did. Nine months after moving Sharks onto the PodPlay stack, operating margin went from 4% to 37%, revenue was up 76%, and published hours went from 12 a day to 18. Read the case study.
6. Multi-Location Architecture, Built First
We built for a multi-location operator before we had a single external customer. That operator was PingPod, and it was running ~20 locations.
Multi-layer permissions and nested parent-child entity relationships are complex architecture. You either get them right at the foundation or you spend years bolting them on. Many systems in this category were designed to treat every location as its own island, with a separate account, separate reporting, and separate everything. That works fine until an operator opens a second club — and then it never works fine again.
We were multi-location from day one, and we have since added the architecture required to handle franchise operations: franchisor-level visibility, franchisee-level control, and roll-up reporting that doesn't require exporting six spreadsheets and doing the math yourself.
7. From System of Record to System of Action
Most club-management software is a system of record. It stores what happened. Some of it will draw you a chart of what happened.
That is table stakes, and it is not where this is going. The future belongs to systems that help you decide what to do next, and then do it for you. We shipped the first version of ours in July: PodPlay Insights puts KPIs, thematic deep dives, and an AI Assistant that reasons over your club's own data directly in the dashboard. No exporting to a chatbot. The read you need, where you work.
It's v1, which means it is the worst version of Insights you will ever use. That is the point. There is a ton of work ahead of us. The gap between a system of record and a system of action is going to widen every quarter from here, and which side of it your club is standing on is a decision you are making right now, whether or not you think of it as a decision.
Everything above is a reason to want to switch. None of it is a reason to accept six weeks of disruption. That case has to be made in dollars.
The best vertical software companies earn the right to compete on ROI rather than price. They do it by becoming an essential driver of profitability for the businesses they serve — not by being cheaper. I laid out the framework in Earning the Right to Compete on ROI: a premium system has to improve the customer experience, increase revenue, or decrease cost. Ideally all three.
Here's what that looks like against a migration.
Revenue. A venue's revenue is utilization times average hourly rate. Volume times price. At $50 per hour, a 10% increase in utilization is more than $200,000 a year for a ten-court club. Algorithmic court assignment alone can move utilization 10% or more during peak hours — and because it becomes the default, you can charge a premium to the players who want to lock a specific court. Technology-enabled courts let you price differentially against standard courts and open replay and sponsorship revenue on top. Coach Connect moves both variables at once: at one PodPlay club, the lifetime value of customers who take coaching ran 17x the average customer.
Cost. NAICS data puts labor at 32% of revenue for Fitness and Recreational Sports Centers. It is the largest controllable line in most clubs. Using PodPlay's autonomous capabilities, clubs have reduced labor cost by up to 66%. Even for clubs that never go autonomous, the efficiency case holds: fewer SaaS subscriptions, less context switching, more time spent building community.
Experience. Harder to put a number on and easier to feel. It shows up in the 4.91 rating, in the magic of scoreboards and instant replays, in repeat play, and in the members who tell their friends where they play.
Now run that against the switch. Six to eight weeks of structured project work, run by a team that has done it dozens of times, against a revenue and cost profile that changes permanently on the other side. Set the disruption at its worst honest estimate and the payback is still measured in months, not years.
Migration is a one-time expense. Staying is a recurring rate.
Every one of the seven reasons above is really the same reason: future-proofing your club.
If you want to win the next ten years, you have to win on experience and community. Courts are table stakes. The clubs that thrive will be the ones whose members feel something before they arrive, during the session, and after they leave — and that experience runs on software, or it doesn't run at all.
Migration is a finite project with a start date and an end date. Operating on a system built for the last era is a permanent drag, compounding quietly, every single day.
Clubs representing 400,000 customer accounts have already made that trade.
Curious what the move looks like for your club? Request a demo.
How one Las Vegas club owner sold court, wall and replay sponsorships to local businesses: what to sell, which verticals to call, and what to charge.
Oct 1, 2026
A case study of Premier Pickleball in Herriman, Utah, which became a magnet for local creators. The blog lays out a six-step playbook for building a creator strategy at your club.
Sep 23, 2026
We only use cookies for necessary navigation of our website, performance tracking, or third party vendors. Our cookie tracking is used to better serve our users and users' interests.