A pool per company, each one theirs
Every client needed its own players and its own table, isolated from the rest, and its own brand in front of its own staff. HR does not buy a tool that shows a vendor's logo to the team.
CASE STUDY · 2026
A white-label prediction platform
with a pool per company.
A white-label prediction pool for the World Cup, sold to HR teams across Latin America: one platform holding every company at once, each on its own subdomain, under its own brand, and run by its own people.
104
Matches loaded and scored on their own
24h
From the brief to a pool that is live
4
Special predictions that can turn the table
2
Tables: individual and by department
What a pool carries and what the onboarding commits to. Adoption figures from the tournament are reported separately.
- Client
- ProdeClub
- Industry
- Corporate engagement / SaaS
- Year
- 2026
THE CHALLENGE
The date could not move.
A World Cup does not wait. If it was not live before the first match, there was no product and no season to sell it in.
A prediction pool is the oldest office ritual there is: everyone picks the scores, the table settles the argument, and for a month people who never speak have something to say to each other. It is also, every four years, a spreadsheet somebody in HR maintains by hand. ProdeClub was built to be the product that replaces the spreadsheet, and to be sold not to the players but to the company paying for the culture program behind them.
A wrong result breaks everything
The table is the whole game. One score entered wrong recalculates every player's points and the trust goes with it.
Nobody has a month to set it up
The sale happens weeks before kickoff and HR has a day, not a quarter. Onboarding had to be something the operation could finish between meetings.
THE SOLUTION
One deployment. A pool per company.
Multi-tenant from the first line, so selling to another company is a record in a table, not a release, and everything that makes a pool feel like theirs is configuration.
The brand, and the page that sells it
ProdeClub as a product brand from scratch: name, logotype, palette and a visual system loud enough for a game and sober enough to survive an HR committee. On top of it, the one-page site that has to do the whole sale, because the buying window is the few weeks before a tournament starts.
- Two readers, one voice The same page is read by the person who wants the fun and by the person who signs for it. Neither should feel it was written for the other.
- Built for a deadline, not a funnel A countdown to kickoff, the plans in the open and a form that asks headcount: there is no time for a nurture sequence when the tournament has a start date.
- The brand it does not use Everything here is the only place ProdeClub shows itself. Inside a pool, the brand is the client's.
The pool people play, and the panel HR runs
Two products with the same spine. Players get predictions, the fixture, the table and the prizes. The company gets a panel that owns the whole thing: branding, players, prizes, questions, emails and which modules are even switched on.
- Ranked individually and by department The second table is the one HR actually wants: it turns a personal game into an argument between floors.
- Players in from a spreadsheet Added by hand, imported from Excel or let in by an invitation link, because that is the shape the list arrives in.
- A guided setup, in five steps Logo and banner, prizes, players, modules, automated emails. The panel walks the operation through it and shows how far along it is.
Live results, and the campaigns on top
A sports data feed brings in the fixture and the results, scoring and standings recalculate on their own, and scheduled jobs keep every pool current without anybody watching. Alongside it we ran the Google Ads campaigns through the selling window.
- Exact and close, scored differently A player gets more for the exact score than for the right winner, which is what keeps the table moving to the last match.
- Specials that can turn it around Champion, runner-up, third place and top-scoring country, locked the moment the tournament starts and settled at the end.
- Acquisition against a closing window The campaigns had to land in the weeks when a company could still say yes and be live before kickoff.
How it is wired Next.js and TypeScript on Vercel, with Supabase and Prisma behind it. Tenancy is resolved per subdomain in middleware, so one deployment serves every company. Scheduled jobs sync the fixture and the results and recalculate standings; transactional mail goes out through Resend, and acquisition is measured in GA4.
A LOOK AT THE WORK
EXPLORE
THE MISSION.
STACK & TOOLS
WHAT IT IS
BUILT ON.
Only what this project actually runs on.
LET'S TALK ABOUT YOURS
THE RESULTS
Live before the first whistle.
ProdeClub shipped ahead of the tournament and held through it, including the minutes before predictions close, which is when a prediction game gets all of its traffic at once. Because tenancy was built in from the first line, every company that bought in after launch joined without a deployment, and the panel meant the operation set up its own pool instead of booking us.
- Brand and one-page site
- Multi-tenant, one subdomain per company
- White label with the client's brand
- Predictions, fixture, leaderboards and prizes
- Admin panel and player import
- Live results with automatic scoring
READY WHEN YOU ARE
YOUR CASE STUDY
IS THE NEXT ONE.
Tell us what you are building and where it is stuck. We answer within one business day.