Your App Store Is a Single Point of Failure: What One Founder's Removal Taught Us About Platform Risk in Marketplaces

Yakov Filippenko, founder of Intch, had his app removed from the Apple App Store without clear explanation. Apple removed nearly 167,000 apps in 2025 and restored fewer than 500. During the removal, Apple froze three months of funds and disabled recurring subscriptions. Intch sur

·4 min read·Source: news.crunchbase.com

What Happened

Yakov Filippenko, founder of Intch, had his app removed from the Apple App Store without clear explanation. Apple removed nearly 167,000 apps in 2025 and restored fewer than 500. During the removal, Apple froze three months of funds and disabled recurring subscriptions. Intch survived because it had already built a web-based payment channel two years prior.

Why It Matters

This isn't an App Store story — it's a concentration risk story. Any marketplace that routes its supply, demand, or payments through a single platform it doesn't control is exposed to the same failure mode. The platform doesn't need to be malicious. It just needs to change its rules, have a glitch, or decide your category no longer fits. The deeper signal: founders who want to build a successful marketplace consistently underestimate infrastructure risk when it comes from a distribution channel rather than a server. But the effect on revenue is identical.

Marketplace Insight

SUPPLY: If your suppliers (service providers, sellers, creators) access the marketplace through a single channel — an app, a social platform, a directory — a disruption there removes their ability to transact. Supply doesn't just slow down; it disappears instantly. DEMAND: Buyers who can't find or access the marketplace don't wait. They find alternatives. A removal or de-listing doesn't pause demand — it redirects it, often permanently. LIQUIDITY: Marketplaces depend on the simultaneous availability of supply and demand. Any single-channel dependency creates a liquidity cliff: one decision by a third party can drop transaction volume to zero with no gradual warning. TRUST: When an app disappears, existing users question legitimacy before they question the platform. 'Is this a scam?' is the first reaction — not 'I wonder what happened.' Trust erodes faster than it was built. GROWTH: Every dollar spent acquiring users into a single-channel funnel is a dollar that increases your exposure to that channel's decisions. Growth without channel diversification is not de-risked growth — a reality that underscores why following marketplace launch best practices from the start matters. ONBOARDING: If new users can only onboard through one channel, a disruption means no new supply and no new demand — simultaneously. Web-based onboarding as a parallel path is not a backup plan; it is a continuity requirement. MONETIZATION: Payment processors and subscription engines tied to a single platform (e.g., Apple's in-app billing) are doubly exposed. A removal freezes not just access but revenue already earned. Diversifying payment infrastructure is as important as diversifying access channels.

What This Means for Marketplace Founders

Non-technical founders often treat the App Store, Google Play, Instagram, or any dominant aggregator as a growth channel. The more accurate framing is: these are gatekeepers with unilateral authority over your customer relationships. You don't need to understand code to act on this. The decision to build a web-based version of your marketplace, capture direct user contact details, or run payments outside a platform's native billing system is a business decision, not a technical one. The critical mistake is waiting until removal happens to build the alternative. By then, you are building under pressure, without revenue, and with users already questioning your credibility. The founder's job is to identify which single decisions — made by companies outside your control — could end your business, then reduce the blast radius before that decision is made — something worth considering early when structuring any community marketplace platform.

Actionable Takeaways

• Map every platform you do not own that sits between you and your users (app stores, social platforms, payment processors, aggregators) — these are your concentration risks.

• Ask yourself: if this platform removed us tomorrow, could our users still transact? If the answer is no, that is your highest-priority infrastructure problem.

• Build a direct web-based access point for both supply and demand before you need it — not as a backup, but as a parallel primary channel.

• Collect direct contact information (email, phone) for every user at onboarding, regardless of which channel they came through. This is your continuity asset.

• Route at least one payment method through a channel you control directly (Stripe, direct bank transfer) so that a platform suspension does not freeze earned revenue.

• Test your alternative channel while your primary channel is still live — verify that users can actually complete transactions through it before it becomes critical.

• Before raising or deploying capital into user acquisition, calculate what percentage of your MRR would survive a removal of your primary distribution channel. If the answer is below 50%, redistribution of spend is warranted.

• Frame platform dependency explicitly in investor conversations — sophisticated investors will ask, and having a clear answer signals operational maturity.

The Founder's Digest

Enjoying this? Get weekly signals for marketplace founders.

No summaries. No noise. Just the week's most useful marketplace insights, translated into strategy.

Source: news.crunchbase.com