Work/ Product & Operations/ Dublin Padel League
Period
Oct 2025 — Present
Role
Founder · Platform Director
Scope
Product · Ops · Build
Status
Live · 600+ players

From a WhatsApp idea to Dublin's largest padel league.

Built and now run the full platform — software, operations, comms, and community — for a competitive league spanning sixteen clubs and 600+ active players across the city.

Featured Project — 2026
600+
Active Players
16
Clubs
4mo
Launch Sprint
01The problem

Padel was exploding in Dublin. Nothing connected the players.

By late 2025, padel had become Ireland's fastest-growing racket sport, but the experience for serious recreational players was fragmented: pay-to-play tournament apps on one end, unstructured WhatsApp groups on the other. No proper ongoing league with rankings, no scheduling that respected players' time, no platform that treated padel as the community it was becoming.

I'd been playing competitively for months and kept hearing the same complaint from other players — "I'd commit to something regular if someone organised it properly." So I built it.

"The best community tool is the one your members already check daily — not another login they'll forget."
02Approach

Validate fast. Build the platform players actually need.

The instinct with any community problem is to over-engineer. I went the other way for week one — proved the demand was real, then invested in proper software once it was clear the league had legs.

A / 01
Validate before building
A single message in three Dublin padel WhatsApp groups: "Would you commit to a competitive league?" Sixty-plus committed responses in 48 hours. Brief confirmed.
A / 02
Build the platform properly
Custom Vue.js platform with Firebase backend — real-time match rankings, fixture scheduling across the venue network, automated standings, player profiles. Built lean but built to scale beyond the first season.
A / 03
Operationalise across clubs
Launched with eight Dublin venues and grew the network to sixteen clubs across the city. Negotiated court time, built the booking layer, and set up the comms infrastructure so players, clubs, and the platform stay in sync.
A / 04
Iterate weekly with players
Format, rules, and product decisions all shipped publicly. Players feel ownership of the league rather than being handed rules from above. Friction drops; retention climbs.
Built with
Vue.jsFirebase Realtime DatabaseCloud Functions WhatsApp BusinessStripe
03Outcomes

600+ players. Sixteen clubs. Live in four months.

Active players
600+
Sustained week-on-week activity, with new sign-ups exceeding churn every month since launch.
Club network
16
Clubs across Dublin running fixtures on the platform. Each handles its own bookings, the platform handles the rest.
Launch sprint
4mo
From zero to Dublin's largest competitive padel league. Built solo, no outside funding.

The league is now self-sustaining operationally. Player demand exceeds available slots most weeks. The platform has become the de facto home for serious padel in the city.

04What I'd take elsewhere

The pattern works for any community-first product.

Validate before you build. Use the channels your community already opens daily. Solve the operational problem properly before the tooling problem. And don't be precious about shipping a rough version one — players don't remember the platform, they remember the matches.

If you're launching a community, league, marketplace, or any recurring event with real stakes, the playbook generalises. I'd be happy to talk it through.

§ Next case study
Crisp Chilli — scaling a streetwear brand to €20k+
→