Business Growth

The Post-Platform Risk: Platform Dependence Research and the Case for Protocol-Native Businesses

The pattern repeats with uncomfortable regularity. Facebook page reach fell from roughly 16% of followers in 2012 to low single digits within years as paid amplification became the toll (Ogilvy, 2014). Google's results page now resolves most queries without a click, 58.5% of U.S. searches ended clickless in 2024, and by 2026 fewer than one-third sent a click to the open web (SparkToro, 2024; SparkToro, 2026). Now AI platforms are consuming content at crawl-to-referral ratios reaching tens of thousands to one (Cloudflare, 2025). The lesson is structural: distribution rented from an aggregator gets repriced once dependence sets in. This article reviews the evidence and makes the case for protocol-native businesses, built on open standards no single company can revoke.

Joshua Agonya Pi'Rwot

By Joshua Agonya Pi'Rwot

Founder, Business Growth Accelerator

Executive summary

Every platform that aggregated attention eventually taxed it: Facebook reach fell from 16% to under 2%, and most Google searches now end without a click. The research case for rebuilding distribution on open protocols you own.

Section 1

The five challenges at a glance

Platform dependence fails businesses through five recurring mechanisms. Algorithmic reach decay quietly devalues audiences you spent years building; zero-click interfaces absorb the demand your content generates; AI assistants threaten to repeat both patterns at greater speed and concentration; rented customer relationships mean the platform, not you, owns the graph and the data; and single-channel concentration turns any policy change into an existential event. The table pairs each mechanism with its root cause, the most exposed firms, and the evidence. The unifying insight: none of these are scandals or accidents, they are the predictable economics of aggregation, which means they can be planned for rather than merely resented.

Section 2

Challenge one: the platform taxation pattern is documented, not anecdotal

Treat platform decay as a studied phenomenon. The canonical case is Facebook organic reach. Industry measurement in 2012 put average page reach around 16% of followers; by February 2014, Ogilvy's widely cited analysis measured roughly 6%, with large pages near 2%, and projected the trajectory toward zero, a projection that essentially came true, with current industry benchmarks placing unpaid page reach in the low single digits (Ogilvy, 2014). The mechanism was not malice but business model: once businesses had built audiences inside the walled garden, converting free distribution into paid distribution was the rational monetization step. Search followed a softer version of the same arc. SparkToro's clickstream research with Datos found 58.5% of U.S. Google searches ended without any click in 2024 (SparkToro, 2024), and its 2026 follow-up found fewer than one-third of searches now send a click to the open web (SparkToro, 2026). Pew's independent panel work confirmed the AI-specific acceleration: clicks to traditional results nearly halve when an AI summary appears (Pew Research Center, 2025). The pattern generalizes: aggregate demand, become indispensable, then internalize the value that previously flowed through. No platform has ever durably reversed a deliberate reach reduction. A service firm's planning assumption should therefore be that any rented channel's economics will worsen over its life, the only question is the schedule.

Section 3

Challenge two: AI platforms are repeating the pattern at higher intensity

The emerging AI layer does not break the aggregation pattern; it intensifies it. Cloudflare's network data quantifies the asymmetry: by mid-2025 nearly 80% of AI crawling served model training, and crawl-to-referral ratios were extreme, Anthropic's systems fetched roughly 38,000 pages per human visitor referred in July 2025, with OpenAI's ratio in the hundreds-to-one (Cloudflare, 2025). Content flows in; visitors largely do not flow back. Meanwhile the new gatekeepers are accumulating audiences at historic speed, ChatGPT surpassed 800 million weekly users by late 2025 (OpenAI, 2025), and adding transaction rails: Instant Checkout and the Agentic Commerce Protocol moved purchasing itself inside the chat interface (OpenAI, 2025; Stripe, 2025). For service firms the seduction is familiar: optimize hard for citation in one dominant assistant, enjoy the early-adopter arbitrage, and quietly rebuild the same single-point dependence that burned a decade of Facebook-first and Google-first businesses. The concentration risk may exceed search-era levels, because an assistant that answers, recommends, and transacts holds more of the journey than a results page ever did. The honest counterweight: this market is younger and more contested than 2014-era social, multiple assistants compete, and open standards are emerging alongside the platforms. Which future dominates is genuinely undecided. Prudent strategy participates in AI distribution aggressively while refusing to let any single assistant become structurally load-bearing.

Section 4

Challenge three: protocols are the alternative the platforms cannot revoke

The strategic alternative to platform dependence is not abstinence, it is protocols: open standards no single company owns, prices, or revokes. The distinction is concrete. Email runs on SMTP; no company can throttle your list's 'reach' to your own subscribers. The web runs on HTTP and HTML; schema.org gives machines a shared vocabulary maintained as an open project rather than a proprietary API (Schema.org, 2024). And the agent era is, unusually, and encouragingly, being built with protocol-shaped foundations. Anthropic released the Model Context Protocol as an open standard in November 2024; OpenAI adopted it across its products in March 2025; and in December 2025 Anthropic donated MCP to the Agentic AI Foundation under the Linux Foundation, co-founded with Block and OpenAI, with thousands of public MCP servers already running (Anthropic, 2024; Anthropic, 2025). The Agentic Commerce Protocol was likewise open-sourced rather than held proprietary (Stripe, 2025). A protocol-native business orients its distribution around these revocation-resistant layers: an owned email list rather than a rented social audience; structured data on owned domains rather than content fed exclusively into walled gardens; and, prospectively, MCP-exposed services that any compliant agent can discover and interact with rather than integrations bound to one assistant's marketplace. Label the forward part honestly, agent-to-business protocol commerce for services is early and unproven. But the architecture choice exists now, and it compounds.

Section 5

Innovative solutions

Five moves convert the analysis into operating posture. First, run a dependence audit: classify every acquisition and delivery channel as owned (email list, website, proprietary data), earned (citations, referrals, press), or rented (social reach, marketplace placement, assistant visibility), and calculate the revenue share flowing through each rented channel. Most firms discover one rented channel above 50%, that number is the risk. Second, build the owned-audience engine deliberately: email remains the protocol-native distribution workhorse, and every platform surface, social, podcasts, assistant citations, should be engineered to convert borrowed attention into owned subscribers. Third, become machine-legible on your own domain: schema markup, extractable claims, llms.txt, so that AI visibility accrues to an asset you control rather than exclusively to content posted natively inside platforms (Schema.org, 2024; Answer.AI, 2024). Fourth, place a small protocol bet: a basic MCP server exposing your scheduling, service catalog, or published benchmarks costs days of developer time and positions you for agent-mediated discovery as the standard matures, a labeled experiment, not a revenue projection (Anthropic, 2025). Fifth, set concentration tripwires: a standing rule that no rented channel exceeds an agreed share of pipeline, 40% is a defensible heuristic, though it is a judgment call, not a researched constant, with budget automatically reallocated toward owned assets when a tripwire fires. Platforms then become what they should have always been: amplifiers, not foundations.

Section 6

Solution framework

Govern the transition with a four-quadrant resilience model, reviewed quarterly. Quadrant one, exposure: the dependence audit refreshed, channel shares, terms-of-service changes, and reach economics per rented channel, with the Facebook and zero-click histories as the base-rate prior for where each channel is headed (Ogilvy, 2014; SparkToro, 2026). Quadrant two, conversion: the rate at which rented attention becomes owned relationships, subscriber growth from each platform, email capture per thousand impressions, community joins. This is the single most diagnostic metric in the model, because it measures whether platform participation is building your asset or only the platform's. Quadrant three, protocol surface: the machine-readable, standards-based footprint on owned property, schema coverage, structured content depth, MCP experiments, agentic-commerce readiness, tracked as leading indicators for the agent era (Anthropic, 2025; Stripe, 2025). Quadrant four, shock tolerance: the scenario test, if our largest rented channel repriced to zero tomorrow, how many months of pipeline survive? Score it honestly; the Facebook-era businesses that died were not warned less, they were diversified less. The framework's discipline is allocation: every quarter, some budget moves from the strongest rented channel toward the weakest owned quadrant. Not because platforms are villains, they are often the best short-term ROI available, but because the documented life cycle of rented distribution says the terms you enjoy today are the best terms you will ever get.

Section 7

Evidence-based action plan

Days 1-30: measure the dependence. Run the owned/earned/rented audit across every channel, calculate concentration percentages, and run the shock test on your largest rented channel. Inventory your owned assets honestly: list size, engagement, site authority, proprietary data. Most firms find the owned column thinner than their confidence suggested. Days 31-60: start the conversion engine. Install email capture on your highest-traffic owned pages, create one genuinely valuable subscription asset, a benchmark report, a monthly teardown, and route every platform presence toward it. Deploy schema markup and llms.txt so machine-mediated discovery accrues to your domain (Schema.org, 2024; Answer.AI, 2024). Days 61-90: place the protocol bets. Scope an MCP experiment exposing one service surface; document your agentic-commerce readiness against the ACP spec as it applies to services (Anthropic, 2025; Stripe, 2025). Set your concentration tripwires in writing and assign quarterly review ownership. Ongoing: track the four quadrants quarterly, shift budget per the allocation rule, and revisit the AI-platform landscape every six months, this market is young, and the open-versus-walled outcome is still being decided. The goal is not to predict which platform wins. It is to build a firm whose distribution survives any of them losing interest in you, which, the evidence says, they eventually will. For adjacent evidence in this pillar, see [The Agentic Economy: How to Grow a Business When AI Agents Do the Buying](/blog/growth-agentic-economy-playbook) and [Selling to Machine Customers: How Service Businesses Stay Discoverable to AI Agents](/blog/growth-selling-to-machine-customers).

FAQ

Direct answers for operators.

What is platform dependence risk for a service business?

It is the exposure created when acquisition or delivery runs through channels another company owns, prices, and can reprice. The documented pattern: Facebook organic reach fell from roughly 16% of followers in 2012 to low single digits (Ogilvy, 2014), and fewer than one-third of Google searches now send a click to the open web (SparkToro, 2026). Rented distribution historically worsens once dependence sets in.

What does protocol-native mean in practice?

Building distribution on open standards no single company can revoke: email (SMTP) for owned audiences, the open web and schema.org for machine-legible presence, and emerging agent standards like the Model Context Protocol, donated to the Linux Foundation's Agentic AI Foundation in 2025, and the open-sourced Agentic Commerce Protocol (Anthropic, 2025; Stripe, 2025). Platforms become amplifiers feeding owned assets rather than foundations you rent.

Are AI assistants just the next platform dependence trap?

The risk is real: Cloudflare measured crawl-to-referral ratios in the tens of thousands to one, and assistants are adding transaction rails that hold more of the buyer journey than search ever did (Cloudflare, 2025; OpenAI, 2025). But the market is young, multiple assistants compete, and key infrastructure is launching as open standards. The prudent posture is aggressive participation without letting any single assistant become structurally load-bearing.

How much of my pipeline can safely depend on one rented channel?

There is no researched constant, but a working heuristic is to treat any rented channel above roughly 40% of pipeline as a strategic risk requiring active mitigation, and to run the shock test: if that channel repriced to zero tomorrow, how many months of revenue survive? The historical base rate from social reach decay and zero-click search says rented terms deteriorate; diversification timing is the only variable you control (SparkToro, 2024).

Joshua Agonya Pi'Rwot

Written by

Joshua Agonya Pi'Rwot

Founder, Business Growth Accelerator · Country Director, AVODA Group Uganda · EMBA

Joshua helps service-business operators turn scattered marketing into a clear path from first attention to booked call. He is Founder of Business Growth Accelerator and Country Director of AVODA Group Uganda.