Investor one-pager · Draft v0 (faithful capture, not yet edited)
PavilionDraft v0

Pavilion is a cricket fan app built for the way the next generation of fans actually consume the sport.

01The Why

Why cricket?

Cricket is hard, a high entry barrier and a real product design problem. I've been following the sport since 2004 and used every cricket app on the market, so I know the user pain points first-hand.

Why now?

02Product

Team

Mudassir Ali (full-time, engineering + product + ops). Advised part-time by Suganth (principal product designer).

03Napkin math

Stream Est. ARR
$16M
$106M
$52M
$19M
$15M
$19M – ???
Total$227M+
On the $500M question. Cricket-only ceiling lands around $250-300M ARR at our current assumptions (ads and affiliate dominate, not subs). $500M needs one of two moves: live broadcast rights at scale (future, not pre-seed scope), or reusing our technology to recreate the model across other sports (football, tennis, F1). Cricket is the wedge; horizontal expansion is the venture-scale path.

04Handwavy roadmap

The consumer base is the engine for everything below. Scale fans first, the rest unlocks downstream. Rough sequencing at pre-seed depth, ordered by dependency, not timing.

Phase 0 Launch
MLC 2026

Enter the market.

Stretch goal: soft launch in the final week of IPL 2026. Tight given the build timeline, so realistically the soft launch lands just after IPL. First proper public GTM is MLC (mid-June to mid-July 2026): low risk, SENA+US-aligned, perfect fit for the early traction story.

Every subsequent league becomes its own GTM moment: The Hundred, CPL, Asia Cup, BBL, SA20. Layered launches, not a single bet.

Phase 1 Growth flywheel
B2C

Become the app cricket fans open every day.

Personalisation (the "this app gets me" graph) plus a stack of consumer-cricket USPs that don't exist anywhere today: live watch-along rooms, influencer-hosted match companions (creators run rooms fans join, monetised via tips and paid messages), AI watch companion that narrates context and history as play unfolds, private friend rooms, post-match highlight reaction rooms. The flywheel: better content + better community + better ambient experience compound into daily-driver behaviour.

The hardest test in Phase 1 is off-season retention: how do we keep cricket fans on the app between tournaments? Building Pavilion into the cricket subset of social media, not just a match-time utility, is the answer we are designing toward.

Subject to traction, in parallel: early agreements with players begin (setting up Phase 2), cultural-icon partnerships line up (Harsha Bhogle and similar tech-evangelist commentators as visible champions of the app), and we dogfood our own social media + content automation using internal tools that productise into Franchise OS in Phase 3.

Phase 2 Monetisation + Player Economy
B2C revenue, P2P

Turn audience into revenue, players into the moat.

Ads + Pavilion Pro ship. The personalisation graph built in Phase 1 lifts ad CPMs and affiliate conversion from day one. A few marquee players go live with claimable verified profiles and match-moment drop programs. Player presence credentials the ask: monetisation is easier to sell to fans when the players are visibly there.

Phase 3 Franchise OS
B2B2C

Productise the internal stack as enterprise SaaS.

The social automation and content workflows Pavilion has been dogfooding since Phase 1 productise into Franchise OS for non-IPL leagues, women's franchises, and smaller boards. Inverse pricing: marquee partners (IPL, top boards) sign for free in exchange for IP rights; aspirants and the long tail pay for the tools they actually need. Dogfooding continues for what becomes Cricket OS.

Phase 4 Cricket OS
B2B + Data

Bloomberg-style terminal for cricket professionals.

Search, AI authoring, alerts, analytics, and contextual intelligence sold to journalists, agents, scouts, broadcasters, federations, and tech partners. Long-term play, gated by data rights with ICC and member boards. Sportradar-class opportunity once unlocked.

05Moats

M1
Cricket is hard.
Needs a rare combination: consumer-tech speciality, product taste, engineering prowess, and the right partnerships. Generalists miss cricket; cricket-only teams miss product.
M2
Player + franchise economy.
Players build their audience and earnings on Pavilion (drops, threads, paid messages, status). Franchises run content, automation, and sponsor measurement on Pavilion. The cost of leaving is the audience and operations built here.
M3
User preference.
Pavilion learns each user's cricket taste over seasons: teams, players, formats, match-ups they actually care about. That memory cannot be ad-bought. Once earned, no incumbent matches the relevance.
M4
Cricket lives here culturally.
Match threads, hot takes, fan art, debates: cricket's cultural discussion happens on Pavilion. Layered with first-party signal on preferences and cricket-adjacent shopping patterns, every cricket intent is observable. Product moat and advertiser moat in one.
M5
Hand-built cultural graph of cricket.
A dedicated team builds Pavilion's structured cultural graph: storylines, rivalries, iconic moments, player arcs, memes. Nobody has this today. With AI in the loop, every model trained on it is sharper, every product built on top is smarter. The deepest moat here because it's the slowest to copy.

06The thesis we are testing

Pavilion is trying to prove that consumer sports tech can be built at scale without gambling. Every dominant sports data and media company today has betting exposure (Sportradar, Stats Perform, and most subcontinent cricket apps). We think the category-defining cricket business is waiting to be built outside that loop, and we want Pavilion to be it.

That also makes Pavilion the only brand-safe cricket layer for big tech (Apple, Google), sponsors after family audiences, and partners that cannot touch betting.