> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/the-podplay-system/why-podplay.md). # Why PodPlay? ### Why Clubs Choose PodPlay PodPlay was built by players, for players. The platform began as the technology that powers PingPod, a network of autonomous table tennis Clubs in New York City. After running 20+ venues and fielding constant inbound interest from other operators, PodPlay spun off as a standalone company in October 2025, backed by an $8 million Series A led by Frontier Growth. Every feature in the platform is stress-tested in a working Club before it reaches yours. #### Where PodPlay stands today PodPlay powers many of the country's most tech-forward Clubs, including Pickleball Kingdom, CityPickle, Performance Pickleball, SPF, and St. Pete Athletic, with strong footholds in New York City, Boston, Austin, Chicago, and beyond. Clubs that run a full side-by-side evaluation against PlayByPoint and CourtReserve consistently choose PodPlay. Clubs running on PodPlay have reduced labor costs by up to 66% while opening new digital revenue streams through Replays, digital scoreboards, and on-court sponsorships. PodPlay supports Per Spot, Per Court, and Court+ pricing. The strongest setup we've seen pairs court pricing for Reservations with Membership benefits focused on Open Play, which avoids the free-rider problem pure Per Spot pricing creates. #### Where PodPlay is going Three principles shape the roadmap: autonomy, technology, and accessibility. Autonomy: PodPlay is not a simple front-desk check-in App. The platform is designed so a Club can run with minimal staff onsite. Reservations, payments, door access, and Customer support all flow through the App without requiring someone behind a counter. Technology: PodPlay combines software, hardware, and automation in a single integrated stack. Customers stay in the App to chat with friends, capture and share Replays, track scores on digital scoreboards, and unlock the door to the venue. Social and marketing integrations let your Club focus on engaging Customers and building community. Accessibility: Every feature is built around a motto, "use technology to put technology down and be present in life." New features ship continuously, and the PodPlay Customer Success team has never missed an SLA. #### What this means for your Club If you're looking for a **high-tech, high-touch** club operating system, you've found it. The combination of an owner-operator perspective, flexible pricing, autonomy-first design, hardware-enabled experiences, and an active product team is what differentiates PodPlay from any other Club management software. Each piece on its own is replicable. The combination, refined across 20+ live venues, is what gives Clubs running on PodPlay a track record of staying on PodPlay. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/owners-playbook/the-podplay-system/why-podplay.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.