The whole picture in one place: the thesis, the funnel, the four surfaces, how the audience is acquired (SEO/GEO across every surface), the data layer, the roadmap, the build (portal now, app later), and the ask. Reconciled from the strategy, concept, scoping and gameplan work to date.
This is the candid version — it keeps the open decisions, the honest starting point, and the TBDs visible, because those are what the plan is built to resolve. The polished investor cut is a separate pass.
ShePlayz has a real, proven audience on YouTube. But YouTube is rented reach — Google owns the identities, so ShePlayz can't market to them, retarget them, or build owned data on them. A proven audience on rented land is a strong start and a fragile business.
The whole plan is one move: convert that reach into an owned, unified first-party intelligence stack — a known audience and what it does. Two owned channels do two different jobs — the newsletter captures identity (an email), and the portal is the vehicle that captures behaviour (the first-party data) and fills the stack. The portal is the vehicle we build now; the native app is the upgrade it earns, and the stack is the asset either fills — it carries over if the vehicle later becomes a native app or a personal agent. Every other surface points toward them. Own your source. Own your intelligence.
The honest starting point (why this is candid): the 111.8K is real demand. The app that exists today has ~20 users — a website replica with no reason to open it and no instrumentation. It didn't fail as a bet; it was never built as one. And the YouTube audience geography has never been pulled, so the "MENA-native" claim is a strong assumption, not yet a measured fact. The plan below is built to resolve exactly these gaps.
The funnel isn't a single destination — it's a filter. Each channel does a different job, and only the people who clear each stage move to the next, higher-commitment one. The portal is where the deepest engagement and richest data live, so everything drives toward it — but the newsletter exists to capture the people not yet ready to sign in, so they're nurtured rather than lost.
First touch — someone finding ShePlayz — routes to the site.
Interested but not ready to commit → routes to the newsletter.
Already converted, coming back → the portal. The bet.
Money is made across the whole funnel — B2B-first, no fan paywall. The portal isn't where revenue comes in directly; it's where the highest-quality behavioural data gets produced, which is what eventually makes the intelligence product sellable.
Detailed visual concepts for the site, portal, data and newsletter live in the companion ShePlayz — Concepts deck. Summarised here as the roles they play in the plan.
Thinner than before: one curated lead, not a video dump. Information stays fully open (scores, news, fixtures — free). What's behind the portal sign-in is the depth: follows, your feed, reminders (by email + add-to-calendar), shown as in-context teasers. Feature-gated, not paywalled. Two equal asks — email for the not-yet-ready, the free portal sign-in for the "I want the depth." The site is a custom front-end on Cloudflare Pages (exit Wix → Cloudflare); Ghost is the newsletter engine only.
v1: personalised feed, fixtures, follows, and email / add-to-calendar reminders — not a live-scores clone. Home / Fixtures / You, Arabic-first, Gulf-time, regional lead above the European one. The surface that owns behaviour — a known account and what it does — on the web, behind one sign-in. Free — one sign-in is the only ask. Instrumented from day one. No PWA or push; the native app comes later for those.
The cheap capture layer: converts anonymous reach into a known email. A genuinely good weekly read with a regional lead and a "Bubs's take" slot — not a form dressed up as content. Hermes-produced from licensed wires. Ships light-themed, single-column, on Ghost. It builds the warm base — and it's the portal's sign-in, so the portal doesn't cold-launch.
Fixtures is the visible surface (owned widgets, Nielsen retired); the capture layer underneath is the real prize — the instrumented first-party MENA dataset that becomes the B2B product. Covered in full below.
The capture mechanisms only matter if traffic arrives. Every surface is optimised both for how it's found and for driving the free sign-in. Some channels are immediate; SEO and GEO compound over time into a durable, owned advantage a competitor outside the region has to work hard to match — a first-mover, not structural, moat.
| Surface | How it's found / grown | Its job toward the portal |
|---|---|---|
| YouTube + Shorts | Title / tag / thumbnail SEO on athlete & rivalry names; consistent Gulf-time posting; clips point back to long-form. | The proven engine. Sign-up push tied to marquee fixtures + link in every description and end-card. |
| Site — SEO | Wire-fed breaking news published fast via Hermes, optimised on the names people search right after a headline breaks. | A compounding, near-zero-cost channel feeding the thin-site funnel — join CTA on every page. |
| Site — GEO | Regional + Arabic-language queries global outlets ignore; and generative-engine citability — being the source AI answer engines cite on MENA women's sport. | The MENA moat — hardest to displace once built. Same funnel: open info → email or the free portal. |
| Instagram — Reels + Stories | Athlete-led Reels and rivalry moments from the library; Stories for fixture-day urgency; link-in-bio + Story links to sign-up. Arabic-first captions for regional discovery. | Visual-first reach into a younger, female-skewing Gulf audience. Sign-up pushes tied to marquee fixtures; the platform where women's-sport fandom is most native. |
| TikTok | Short, high-velocity clips optimised for the For-You algorithm; trend and sound participation; regional hashtags global outlets ignore. | The highest-ceiling discovery channel for net-new reach beyond the existing YouTube base — but the least owned. Drive sign-ups hard, hold nothing here. |
| X / Threads | Real-time match reactions, results, and breaking-news posts fast via Hermes; reply-and-quote into live conversation. | Timely, low-production reach around live moments — a cheap complement, not a primary engine. Every post carries the sign-up / newsletter CTA. |
| Newsletter | Signup in every video description, end-card and on-site; referral forwards. | Owned identity + the on-ramp: "get alerts by email" on every issue, tied to specific matches. |
Honest calibration: immediate engines (YouTube, Instagram, TikTok) drive sign-ins now; SEO and GEO compound over 6–12 months into the moat. The organising principle across all of them: diversify the reach, concentrate the relationship. Spreading acquisition across several rented channels means no single platform is a chokepoint — the same anti-concentration logic that drives the whole plan — while every one of them funnels into the one owned stack. The channels are reach vehicles we don't trust to hold the audience; that's exactly why we drive sign-ups off them rather than living on them.
The data business isn't a new product line — it's the audience business monetised a second way. The no-paywall, free model maximises audience, which maximises behavioural signal. Each stage is a hard prerequisite for the next.
The dependency spine: Instrument → Audience → Attribution → Intelligence → Market data. Skip the early stages and there's nothing worth selling — you can't sell data you never collected.
| Stage | What it is | Status |
|---|---|---|
| Fixtures | Owned widgets off free/low-cost feeds (TheSportsDB, API-Football, ESPN). Nielsen retired. | Live |
| Event schema | The named events, properties and identity model — signed off before engineering. The one irreversible pre-engineering decision. | Open |
| Capture pipeline | Logs taps, dwell, shares, reminders. No PII beyond agreed. PDPL residency built in. | Scopable |
| Owned store | Under ShePlayz credentials, exportable anytime. All data/schema/derived graph = ShePlayz IP. | Scopable |
| Reporting view | "See the audience" — volumes, top cuts by sport / region / language / surface. | Scopable |
| Intelligence product | The sellable B2B layer — sponsor dashboards, licensable cuts. Currently parked / out of scope. | Unscoped |
| Open decision | Why it blocks scope |
|---|---|
| 1 · Event taxonomy | The schema IS the build — "instrument everything" can't be costed until events, properties and consent flags are named. |
| 2 · Name the buyer | "Brands / federations / rights holders" is a category, not a customer. No named buyer = no revenue to size. |
| 3 · Audience geography | Never pulled from YouTube. Gates the value, not just the cost — if it skews non-MENA the whole thesis weakens. |
| 4 · Identity model | One owned record — the passwordless magic-link account — ties email + portal + behaviour. Without it the newsletter and portal each own a fragment, not the whole person. |
| 5 · Reporting vs. product | "See the audience" is near-term & cheap; sponsor dashboards / licensable cuts are a separate, larger build. |
Gates, not dates. Each stage clears a numeric bar before the next is funded — nothing scales on vibes. Live scores are deliberately tabled for v1: the thinnest, most expensive feed shouldn't carry the launch.
| Stage | What ships | Gate to unlock next |
|---|---|---|
| v0 · Newsletter | "The Rundown" — Hermes-produced weekly, regional lead, Bubs's take. | 5,000 subscribers @ 35%+ open |
| v1 · Fan portal (awareness home) | Personalised feed, fixtures, follows, email / add-to-calendar reminders. Arabic-first, on the web. The MVP. | 25% of list activate · 20%+ D30 |
| v2 · Portal depth | Deeper personalisation, saved, sharper alerts, live moments — built on v1's real behavioural data. | 60% of actives follow + first data pilot signed |
| v3 · Native app — the upgrade | Push, offline, home-screen — the native-only adds, once the portal proves the features and the audience justifies the build. | Portal engagement justifies the native build |
Data compounding underneath the whole time: implicit signal (taps, dwell, reminders) → declared preference (v1 follows) → live behaviour at scale → a saleable audience-intelligence product.
Media & audience
Intelligence begins if a buyer is signed
Intelligence ~19% — buyer-dependent
These are a benchmarked model, not a forecast — read them as illustrative. Media & audience carries the business today; the intelligence line is the compounding upside but it is contingent on two still-open decisions — naming a B2B buyer and confirming the audience geography (below). Until the buyer is named, treat every intelligence-derived figure as directional. B2B-first, no fan paywall.
The v1 build is the fan portal, on the owned Cloudflare stack — weeks, not quarters, with no offshore dependency and no store review. The native app comes later, resourced from the India bench, and reuses the same seam. The discipline is not treating these as one timeline.
Scope, write the data seam, stand up the API + store + magic-link identity + consent, and build the portal front-end on Cloudflare Pages. This is v1 — it ships in weeks, no bench, no push.
The RN client, reusing the seam the portal already runs on. Starts only when the portal has proved the features and the native-only adds (push, offline) are justified.
The hinge is the data seam — event schema, API contract, identity model. The portal is built on it now; the later offshore app inherits it intact. Offshore execution is fast and cheap only when the spec is tight — so getting the seam right for the portal is exactly what later makes a ~90-day app build realistic. "90 days from scoping done" isn't real; "~90 days from a ready starting line" is.
Close the five data decisions (audience pull first), lock the portal surface, draft the event schema + taxonomy.
Our side stands up the owned store + pipeline (Cloudflare D1), the API, the passwordless magic-link identity, the consent/PDPL flow, and the portal front-end on Cloudflare Pages. Reminders are scheduled email + add-to-calendar — no device push. Ships in weeks.
The portal is an instrumented experiment to find the adoption drivers. Drive sign-ups from every surface, monitor the v1 gate, let the behavioural data — not a fixed roadmap — decide what v2 prioritises.
Once the portal has earned it: resource a mid–senior React Native / Expo pod off the India bench, name the integration owner who protects the seam across the time-zone gap, and run the ~90-day build reusing the proven seam. It adds only the native-only layer — push (iOS permissions, certificates, timezone scheduling), offline, and store presence. Budget for RTL on every screen and real App-Store review time.
The owned intelligence stack is the long-term asset; the portal is the vehicle we build now to fill it, and the native app is the upgrade its proof earns. The plan: build the v1 portal, instrument it against a portable schema, iterate on what the data proves drives adoption — de-risked by shipping the newsletter first (a warm base that doubles as the portal's sign-in), one web surface for v1, staged gates so capital releases against proof, and a free sign-in so there's no price friction on the way in.
The investment figure is deliberately TBD. The build can't be honestly costed until Phase 0 closes — the MVP surface locked and the data seam scoped. That's not a gap in the plan; it's the plan's discipline. Scope first, then the number has something to stand on.
Immediate next step: a working session on the open decisions, and the v0 newsletter live within the near term as the cheap proof-of-crossover and the list the portal launch depends on.