SHEPLAYZ
◆ Internal · candid · decisions-focused · sourced · 2026

Where this
is going

A working read of the landscape ShePlayz is building into — written for us, not for the room. The correction this document makes to how we've been talking: the intelligence stack is the asset. The app is the vehicle we're building to fill it. Vehicles change — app today, personal agent tomorrow — but the owned, unified intelligence layer underneath persists across all of them. That's what we're actually betting on.

The one idea underneath everything: every layer that used to carry an audience to a brand for free — YouTube, search, social — is becoming metered, closed, or mediated by someone else's machine. So the asset can't be any single channel or surface. It has to be the intelligence layer beneath them, which we own and can point at whatever vehicle wins.

The stack
is the asset — owned, unified, portable across vehicles
the reframe · §The asset
100%
of the audience lives on YouTube today — one revocable vehicle we don't control
internal · §1
2.9×
value multiple on unified first-party data — what the stack accumulates
BCG & Google
0
owned identities in the stack right now — the number the plan exists to change
internal
The picture · in one idea

Don't bet on a vehicle.
Bet on the layer underneath it.

For twenty-five years, being found and owning the audience travelled together: publish, get discovered, earn the click, keep the visitor. That chain is breaking on every surface at once — which is exactly why the asset can't be any single surface.

The mechanism repeats everywhere. An intelligent layer — YouTube's recommender, a search engine's AI answer, a personal assistant — inserts itself between the audience and the source, reads the content, keeps the person inside its own walls, and decides whether the source is ever seen. Chasing the winning channel is a losing game because the channel keeps changing and someone else always owns it. The durable move is to own the thing every channel eventually needs: a unified, first-party understanding of a known audience. Sections 1–3 are three views of the same lesson — YouTube, web, agents — each showing why no vehicle is safe to depend on. "The asset" is what we build instead. Sections 4–5 are how the vehicle plugs into it, now and later.

The reframe, stated plainly for the team: the app is not the asset — the intelligence stack is. The app is the best available vehicle to fill that stack today. If the vehicle needs to change to a personal agent down the road, we change vehicles — the asset doesn't reset, because the data was ours all along.

◆ The real selling point · the intelligence stack

The asset is the intelligence stack

This is the part every other document treats as the by-product, and it's backwards. The behavioural data, the identity graph, the proprietary MENA-league coverage, and the intelligence derived from them — that is the business. Everything else is how we collect it and how we express it.

Building now
The app
React Native client — the proven first vehicle. Collects behaviour, expresses the intelligence back to the fan.
↑ vehicles are interchangeable — each one plugs into ↓ the asset that persists
◆ The intelligence stack — owned, unified, portable what compounds, and what a buyer pays for
Identity graph
One record tying newsletter email + app account + behaviour into a known person, across time and surface. Without it, every vehicle owns a fragment. This is what makes the asset portable between vehicles.
Behavioural record
Every follow, dwell, open, reminder — the first-party signal ladder: implicit → declared → live behaviour. Can't be collected retroactively; the reason instrumenting now is the one irreversible move.
Proprietary MENA data
Structured coverage of the Saudi WPL and regional leagues that no one else has built a clean feed for — data ShePlayz would produce and own. Honest scope: this is largely still a candidate to build, not a finished asset. And the moat is first-mover + effort, not structural — a league or a funded entrant could produce it too. The advantage is being first and embedded before they bother.
Derived intelligence
What AI turns the above into — audience segments, demand signals, predictive insight. The B2B product, and the fuel for personalisation and any future agent. The ceiling.
one owned system · collected once, sold twice — the audience business and the data business are the same business

Why this framing beats "the app is the asset"

"The app is the asset" invites the one question that can sink the pitch: what if the app doesn't win — a better one appears, or the form factor dies? The stack framing dissolves it. If the asset is the owned intelligence layer, the app is a replaceable collection instrument, and vehicle risk stops being existential. We're not betting on a form factor; we're betting on an accumulating, portable asset that whatever-wins plugs into. Far calmer, and far more defensible, to put money behind.

2.9×
What the stack is worth

BCG & Google measure a 2.9× value multiple on unified first-party data — and AI systems now favour owned first-party signal. The stack is the exact input the next era pays a premium for.

BCG & Google
Twice
How it monetises

The same captured data is sold twice: once as the audience (media/reach), again as the intelligence (B2B insight). The free-app model isn't giving product away — it maximises the signal the stack runs on.

the plan's own logic
Only us
Why it's a moat

The proprietary MENA-league layer is insight no competitor outside the region can produce — they don't have the source. This is what makes the stack defensible, not just valuable.

internal · Data & Intelligence
The precondition that makes all of this true — not optional

"The stack is a portable asset we can carry from vehicle to vehicle" is only true if the data is modelled to be portable and unified. A pile of app-specific logs welded to one app's structure is exactly the thing this framing is meant to escape — change vehicles and it resets to zero. So the identity model and event taxonomy (open decisions #2 and #4) aren't plumbing beneath the app — they are the architecture of the asset itself. External data backs this: 78% of firms collect first-party data, only 22% unify it; the rest is "expensive noise." Vehicle-independence is a goal the schema has to earn. This is the single most important build decision we make.

The decision this makes unavoidable Write the event taxonomy and identity model to serve the stack and its future vehicles — not just the v1 app feed. Sign them off before app engineering, because they're the asset's architecture and the one thing that can't be retrofitted. Every other open decision waits on this being done right.
1 · Why no vehicle is safe · YouTube

The vehicle we're on today is revocable

The plan says YouTube is "rented reach — Google owns the identities." True, but too gentle. In 2026 YouTube isn't a passive landlord withholding the tenant list — it's actively rewriting the lease, and 100% of our audience rides in that one vehicle. This is the clearest proof of why the asset can't be a channel.

What YouTube is doing to creators right now

16
One sweep, Jan 2026

Channels removed in a single enforcement wave — 4.7B lifetime views and ~$10M in annual creator revenue wiped off the platform at once. Not copyright. Quality control.

ScaleLab; MilX; Fliki
Channel
The unit of judgement changed

Enforcement shifted from scoring videos to evaluating whole channels — the stated test is interchangeability: if YouTube could swap your channel with a hundred others and no one noticed, you're at risk.

Fliki (creator↔YouTube comms); ScaleLab
Face
The algorithm moved too

As of June 2026, recommendations favour videos with a real human face on camera. Some faceless creators now hire on-camera hosts just to satisfy it. One company's ranking choice reshapes what even gets distributed.

Hollywood Reporter, Jun 13 2026

Why this is our problem, specifically

The plan names one dependency — we can't market to, retarget, or build data on the 111.8K. Real, but stacked underneath it is a more acute one: concentration risk. All demand rides one vehicle that is, this year, deleting channels overnight and moving the goalposts without warning. In stack terms: today we own no asset — we have an audience someone else holds for us, revocably. A rule change and there's no second surface holding the relationship.

The honest read — so this isn't fear-mongering

The demonetisation wave targets mass-produced "AI slop," not genuine editorial voice — YouTube has been explicit it isn't banning AI, only interchangeability. A real women's-sport channel with human judgement is not the target, so near-term monetisation risk is modest. But that's not the risk. We don't control the policy, can't appeal a rule that doesn't exist yet, and can't predict the next change. Being low-risk under today's rules isn't safety when the rule-maker rewrites them annually and 100% of the audience is concentrated in their vehicle. Safety comes from owning the asset, not from staying on the right side of someone else's policy.

The fair objection — and the honest answer

A sharp reader will catch a tension: if YouTube is this risky, why does the whole acquisition plan still run on YouTube driving installs? Fair. The answer is a deliberate split — we keep using YouTube for what it's good at (top-of-funnel reach) while we move the part that matters (the relationship and the data) off it and into the owned stack. We're not pretending we can stop using YouTube tomorrow; we're making sure that the day a YouTube shock lands, the relationship already lives somewhere we control. Continuing to draw reach from a risky channel is fine — depending on it to hold the relationship is what we're ending.

The reframe for how we sequence Building the app now is an insurance move as much as a growth one: it starts moving the relationship into an asset we own, off the single revocable vehicle. The newsletter (v0) and the install gate are the evacuation route. And pulling the YouTube geography (open decision #3) now has a third job on top of validating the MENA thesis and baselining the funnel: it baselines the audience we're racing to move into the stack — we can't measure how fast we're de-risking without it.
2 · Why no vehicle is safe · Web traffic

The free click is disappearing

Our second planned acquisition vehicle — the site, found through search — is being undercut by the same AI wave, more slowly than YouTube's acute risk but in the same direction. The click that delivered a visitor is being answered in place.

~60%
Zero-click

Of all Google searches now end without a click to any site — ~77% on mobile. Only ~360 of every 1,000 searches reach the open web.

SparkToro / Datos; Similarweb
−34→58%
And accelerating

AI Overviews cut clicks to the #1 result 34.5% (Apr 2025) → 58% (Dec 2025). The effect grows as the feature matures — a line steepening, not levelling.

Ahrefs
−38%
Publisher reality

US publisher referral traffic from Google fell 38% YoY; worst-case navigational queries at some outlets ~89%. Happening to real media businesses now.

Press Gazette; DMG Media

And the AI layer keeps the user in place by design. Google's generative AI Mode passed one billion monthly users at I/O 2026, volume more than doubling each quarter — while referring out on just 1.6–2.5% of queries vs 17–19% for traditional search.

The counterweight we keep in view

Gartner's "search drops 25% by 2026" did not land at that level, and Gartner later called it scenario modelling. Google still dominates; classic SEO still works. The real, measured shift is subtler: impressions hold while clicks per search fall — Ahrefs' "Great Decoupling." The takeaway isn't "search is dead"; it's that being visible no longer reliably becomes a visit.

What it means for the site & SEO/GEO plan The SEO/GEO engine still matters, but its job changed — it can't be counted on to deliver an install click. Its real job is being the cited source in the AI answer about MENA women's sport, and converting the smaller, higher-intent set of surviving clicks into the stack. Another reason the value can't sit in any channel: even the acquisition surfaces are being disintermediated.
3 · Why the vehicle will change · Personal agents

Soon the visitor won't be a person

The shift now underway: increasingly the thing that arrives to consume content isn't a human with a browser — it's an agent acting on a person's behalf. Early, but the infrastructure is already being built, and it's the clearest signal that the vehicle we reach fans through will change — which is exactly why the asset must not be the vehicle.

What's already concrete

The two futures — and which the stack lets us be ready for

The threat, if the asset is a vehicle

Disintermediation

A fan asks an assistant "what happened in women's football this weekend," the agent reads a source and answers directly, and the fan never reaches any ShePlayz surface. If our value lived in the app, we'd be invisible to the machine doing the choosing.

The opening, because the asset is the stack

Becoming the source — and the agent

Because we own a known relationship and — if we build it — the earliest clean MENA-league data, we can be a source the agent cites, and stand up our own agent acting for the fan. Not a pivot — the same stack expressed through a new vehicle.

Calibration — don't overbuild for this yet

Agent traffic is still a small share of the real world today; this is about readiness, not a v1 feature. The mistake would be building agent infrastructure before we have the stack that makes it worth anything. Right posture: make the choices now that keep the agent vehicle available later — own the MENA data, keep it machine-legible, and model the identity graph so a ShePlayz agent could one day act for a known fan. Cheap to preserve now; impossible to retrofit. Same precondition as the stack section: portability isn't free, it's designed in.

4 · The build · The vehicle that plugs in

Build the vehicle people want today.
Design it to swap tomorrow.

The app is the proven first vehicle — the right one to build now, because it's the only surface that turns a passive viewer into a known, instrumented user and starts filling the stack. The discipline: ship something a fan genuinely wants today, while making sure what it collects belongs to the stack, not to the app.

Why the app is the right vehicle to start with

Consumer reality in 2026: people don't download another news reader, and they abandon apps that give them nothing YouTube or a newsletter already give them. The v1 job is a genuine near-daily reason to open — smart alerts in Gulf time, follow-your-athlete moments, a curated feed tuned to real behaviour — not a live-scores clone and not the website replica the ~20-user current app was. The near-term AI (summaries, personalisation) earns the open; the data it generates fills the stack. Ship the want; feed the asset.

The risk we have to be honest about — retention

The plan calls the app "the daily home for women's sport" and gates v1 on 20% D30 — but a daily habit needs daily reasons to open, and women's sport in MENA is seasonal and fixture-sparse compared with the men's leagues fans are used to. The unexamined question a sharp reviewer will ask: on a dead Tuesday in the off-season, why does anyone open this? "Curated feed + push" is a thin answer on its own. This is the likeliest way the MVP underperforms, and it's not yet solved — the honest position is that finding the real daily hook is the thing the v1 experiment has to prove, and the D30 gate is deliberately the bar it must clear before more capital goes in. We're naming it as the open risk, not asserting it away.

The vehicle swap — plainly stated

Here is the part worth saying out loud, because it's the strongest thing about the strategy: we fully expect the vehicle to change, and that's fine. App → personalised app → personal agent is not three product pivots; it's one stack, expressed through whatever the fan uses to reach it. When personal agents become how a Gulf fan checks on women's sport — and the agent infrastructure shipping in 2026 says that's a when, not an if — we don't rebuild. We point the stack at a new vehicle. The 111.8K→known-audience relationship, the behavioural record, the MENA data all carry over intact.

To be clear about what this isn't: it is not "fund an app we plan to abandon." The app is the vehicle that does the collecting for years — it's how the stack gets built in the first place, and there is no stack without it. The swap is insurance against a form-factor shift we don't control, not a plan to walk away from the app. We build it to last and to earn; we design it so that if the world moves to agents, we move with it instead of starting over.

What we're NOT doing

Betting the company on the app winning

If the app were the asset, a form-factor shift to agents would be an existential threat — a rebuild from zero. That's the fragile bet the old framing implied, and the one we're deliberately not making.

What we ARE doing

Owning the asset the next vehicle needs

The app fills the stack; the stack outlives the app. Swapping to an agent is a vehicle change, not a reset — provided the data was modelled portable from day one. That proviso is the whole game.

The precondition, again — because it's the same one "We can swap the app for an agent without losing the asset" is only true if the event taxonomy and identity model are written for the stack, not welded to the app. This is the same open decision as the stack section — which is the point: nearly everything important routes back to getting the asset's architecture right before we build the first vehicle.

A word on acquisition — diversify the reach, concentrate the relationship

This is where the acquisition plan (YouTube + Instagram + TikTok + search driving installs) has to square with everything §2 and §3 just said about social platforms closing. The reconciliation is the same move as the whole document: these platforms are reach vehicles, not relationship homes. We use Instagram and TikTok precisely because we don't trust them to hold the audience — we drive installs off them into the owned stack, so a reach channel going hostile costs us reach, not the relationship. Spreading across several rented channels is the same anti-concentration logic that made single-platform YouTube dependence the headline risk: no one chokepoint. The discipline that keeps it from backfiring — repurpose one content core across platforms rather than producing natively for each, and add channels in sequence, not all at once. Diversify what's rented; concentrate what's owned.

5 · The synthesis · Potential future state

Why the stack is the only position that survives

Put the shifts on one page and the ShePlayz thesis stops looking like an app bet and starts looking like the one position left standing when every vehicle around it changes.

The shiftWhat it takes awayWhy the intelligence stack answers it
1 · YouTube Our entire audience relationship — held revocably by a platform deleting channels and rewriting rules this year. 16-channel Jan 2026 sweep Moving the relationship into an owned stack makes a YouTube shock survivable, not fatal. The asset isn't the channel we might lose.
2 · Web traffic The free click that delivered a visitor. ~60% of searches now end zero-click. SparkToro; Ahrefs The stack doesn't re-earn a click each time — it holds a known relationship reachable through whatever vehicle, by push or by agent.
3 · Personal agents The human visitor entirely — an agent may consume the content and the fan never arrives. Cloudflare Sep 2026 A known fan + owned, legible MENA data lets ShePlayz be the cited source and stand up its own agent. New vehicle, same stack.
The asset Nothing — this is the tailwind. But it rewards only unified first-party data, not scattered logs. BCG/Google; StackAdapt The stack is the only thing that compounds, is defensible (MENA data), monetises twice, and survives every vehicle change — if the schema is portable.

The plausible future state, five years out

Not a forecast — a direction the evidence points to. Discovery is agent-mediated: fans ask assistants, and the sources with owned, machine-legible data on under-covered leagues get surfaced. Rented reach on any single platform is a liability every media business has learned to hedge. Unified first-party behavioural data is the core traded asset of audience businesses, and the ones who unified early own a moat the late movers can't buy. In that world ShePlayz's value isn't the YouTube channel and isn't even the app — it's the owned MENA women's-sport intelligence stack, reachable directly and legible to agents, expressed through whatever vehicle fans use that year.

◆ Where the audience lives today
YouTube — rented · revocable · 100% · no owned asset

One vehicle, held on our behalf, that we don't control — and no stack underneath it yet. This is the risk the build buys down.

◆ Where it needs to live — vehicles on top, the owned stack underneath
YouTube reach
Site
Newsletter
App → agent (owned)

Vehicles stay useful — YouTube still drives reach — but the relationship and the data compound in the owned stack beneath them. The owned share is the part that can't be revoked and carries across vehicle changes.

The bet in one line for the team: ShePlayz has real demand on a rented, revocable vehicle (111.8K on YouTube) and zero owned intelligence today. Every shift widens the gap between those two numbers — and the fix isn't a better vehicle, it's owning the stack the demand can be moved into, while there's still time to build it calmly.

Two guardrails so we stay honest with ourselves

The receipts

Sources & calibration

Drawn from published 2025–2026 research. Where studies disagree, the range and method are noted rather than the most dramatic single number — built to survive our own scrutiny, not to win a slide.

The asset · first-party data value

BCG & Google (2.9× value on unified first-party data) · StackAdapt (78% collect / 22% unify; the rest "expensive noise") · Theodyx / 2025 creator-monetisation survey (56.8% fully own audience; 2.7× more likely to earn $31K+) · "collected once, sold twice" and the MENA-proprietary-data moat: ShePlayz internal Data & Intelligence and Technical Architecture docs.

1 · YouTube creator risk

ScaleLab, MilX, Fliki, TubeBuddy, AITuber (Jan 2026 removal wave: 16 channels, 4.7B lifetime views, ~$10M annual revenue; per-video → whole-channel enforcement; "inauthentic content" / interchangeability standard; AI targeted as slop, not banned) · The Hollywood Reporter, Jun 13 2026 (recommendations favour on-camera faces; faceless creators hiring hosts) · caution carried in the text: some viral "$250K/month lost" figures trace to copyright shutdowns, not the inauthentic-content policy.

2 · Web traffic & zero-click

SparkToro / Datos (~360 of 1,000 US searches reach the open web) · Similarweb (zero-click trend; AI Mode referral 1.6–2.5% vs 17–19%; AI Mode 1B+ MAU, Google I/O 2026) · Ahrefs ("Great Decoupling"; #1-result click loss 34.5%→58%, Apr–Dec 2025) · Pew Research Center (68,879-search study; 1% click within an AI Overview; 26% session abandonment) · Press Gazette (US publisher Google traffic −38% YoY) · Digital Content Next (19 publishers, −10% median) · DMG Media (up to −89% navigational) · Bain & Company, "Goodbye Clicks, Hello AI," Feb 2025 · Gartner "Predicts 2024," Feb 2024 (25%-by-2026 — unrealised / scenario modelling).

3 · Personal agents

Cloudflare (Search / Agent / Training traffic classes; agents blocked by default on ad pages from Sep 15 2026; Web Bot Auth cryptographic identity) · reporting on agentic browsers driving real browser sessions (Perplexity Comet, ChatGPT Atlas) · Meta / About.fb.com and reporting (Advantage+/Lattice AI ownership of targeting; outbound-link limit tests).

4 · Consumer behaviour & owned audience

Theodyx / 2025 survey (Substack $1.1B/$100M, beehiiv ~$30M ARR, Patreon $10B+ lifetime) · Hootsuite 2026 (Instagram organic reach 1–2%, down from 16% in 2012) · Goldman Sachs Research (creator economy $250B→~$480B by 2027; ~70% of creator revenue via algorithmic platforms) · email-vs-social ROI ($36–42 vs ~$2 search / ~$2.80 social per $1): Litmus, the DMA and Omnisend, via 2026 benchmark aggregations.

On the email-vs-social ROI figure: email's $36–42 per $1 (vs ~$2 paid search, ~$2.80 social) is attributed across 2026 benchmark reporting to Litmus, the DMA and Omnisend. One honest caveat we keep in view: the $36 (Litmus, USD) and $42 (DMA, originally £42, UK) are independent studies in different currencies and years — so we cite it as a cross-channel comparison, not as a single precise number or a trend line.

ShePlayz — Where This Is Going · internal · candid · confidential · 2026
A Pegasus Collective / Pegasus Source practice frame. Own your source. Own your intelligence.
The asset is the intelligence stack; the app is the first vehicle. Companion to The Plan, The App Is the Asset, the AI Ladder, and the Data & Intelligence picture.