Platform Dependence Risk Checklist for Commerce Founders
This checklist gauges precisely how exposed a commerce business is to a single platform's continued cooperation, and identifies which specific first-party assets deserve deliberate, early investment so that a policy or fee change on any one platform genuinely can't end the business outright.
The 10-Item Checklist
- What percentage of total revenue currently flows through your single largest sales channel?
- Do you have direct, owned contact information (email, phone) for customers, independent of any platform?
- Could you contact your customer base directly if your largest platform disappeared tomorrow?
- Have you confirmed your specific platform's current policies on customer data and communication access?
- What percentage of your total customer acquisition depends on that platform's own algorithm or search visibility?
- Do you have a genuine, functioning direct sales channel generating at least some real revenue independently?
- Have you modeled your unit economics under a scenario where your primary platform's fees increase meaningfully?
- Is your brand identity genuinely distinct and portable, or entirely tied to your presence on one specific platform?
- Do you have a specific, actionable plan for reducing channel concentration over time?
- Have you set explicit kill criteria tied to platform dependence risk specifically?
Quick Answer: This checklist maps channel concentration, customer data ownership, and policy exposure across ten specific items. The red line for channel concentration isn't a single universal percentage, but rather whether you've honestly confirmed you could survive a sudden, negative change on your largest single channel — if the honest answer is no, that concentration level represents genuine, unmanaged risk regardless of how comfortable current performance on that channel feels.
Item-by-Item Rationale
Items 1, 5, and 8 map your channel concentration — how much of your business depends on a single platform's continued traffic, algorithm favor, and brand presence. Items 2, 3, and 4 map your customer ownership — whether you have genuine, direct access to your own customer base independent of platform intermediation. Items 6 and 7 map your resilience — whether you have a genuine, functioning alternative channel and have honestly modeled your economics under adverse platform conditions. Items 9 and 10 map your response readiness — whether you have an actual, specific plan and pre-committed thresholds for addressing platform dependence, rather than only a vague, unexamined awareness that the risk exists in the abstract.
Ownership Table: Data, Audience, and Payment Relationships
| Asset category | Fully owned | Partially platform-dependent | Fully platform-controlled |
|---|---|---|---|
| Customer contact data | Direct email list you built | Platform messaging with limits | No access beyond the platform itself |
| Payment relationship | Your own payment processor | Platform-processed with some visibility | Entirely platform-managed |
| Brand and product presentation | Your own site and materials | Customized platform storefront | Generic platform listing template |
Failure Modes Each Item Prevents
| Item group | Failure mode prevented |
|---|---|
| Channel concentration (1, 5, 8) | Discovering total dependence only once a platform disruption actually occurs |
| Customer ownership (2, 3, 4) | Having no way to reach your own customer base if a platform relationship ends |
| Resilience (6, 7) | Lacking any functioning alternative or understanding of adverse-scenario economics |
| Response readiness (9, 10) | Having no actual plan or pre-committed threshold, only vague, unexamined awareness |
What to Build First to De-Risk
If you're starting from genuine, high platform dependence, prioritize building a direct email list first — the single highest-leverage, most broadly applicable first-party asset across nearly any commerce business model, following the first-party-asset discipline covered in the rented-land trap — before investing in a full independent sales channel, since even a modest, genuine direct communication channel with your existing customer base provides real optionality a fully platform-dependent business lacks entirely.
A Closer Look: Running This Checklist Honestly, Not Optimistically
The genuine value of this checklist depends entirely on answering each item honestly, based on your actual current situation, rather than on an optimistic read of what you intend to eventually build. It's a common, understandable failure mode to answer item 6 — whether you have a genuine, functioning direct channel — based on a channel that technically exists but generates negligible real revenue, effectively marking a real risk as mitigated when it genuinely isn't yet. A more disciplined practice: answer each item using a specific, current number wherever the item allows for one, rather than a qualitative impression, since qualitative impressions are considerably easier to answer optimistically than a specific figure honestly confronted.
For item 1 specifically, calculate your actual current revenue concentration by channel directly from real transaction data, not from a general sense of "we sell in a few different places." Founders are often genuinely surprised by how concentrated their actual revenue distribution is once they calculate the real number precisely, having underestimated it based on a vaguer, more optimistic general impression. The same discipline applies to item 5 — actually pulling your specific traffic source data rather than assuming a diversified traffic mix based on general impression alone.
Consider running this checklist not just once at launch, but at specific, pre-committed intervals as your business grows, treating a meaningfully worsening trend in your channel concentration numbers over time as an explicit trigger for action, even if the absolute current numbers don't yet feel alarming in isolation. A concentration level that was genuinely fine at your current, smaller revenue scale can become a considerably more serious risk once a larger share of your total business, and the capital or team commitments built around it, depend on that same single channel's continued cooperation.
Consider also involving someone other than yourself in scoring this checklist honestly, particularly for items where founder optimism bias is most likely to creep in — a co-founder, an advisor, or even a candid outside perspective can catch an overly generous self-assessment on items like brand portability or acquisition channel diversity that a founder deeply immersed in the day-to-day comfort of a currently working platform relationship might genuinely struggle to evaluate with full objectivity. This isn't a criticism of founder judgment generally, but a recognition that the same closeness to a business that makes a founder's judgment valuable elsewhere can make honest self-assessment of this specific risk category genuinely harder from the inside than it looks from a slight outside distance.
Key Takeaways
- This checklist maps channel concentration, customer ownership, resilience, and response readiness across ten specific, actionable items.
- There's no single universal concentration threshold — the honest test is whether you could survive a sudden, negative change on your largest channel.
- Customer contact data is the most broadly valuable first-party asset to prioritize building, given how directly it enables reaching your own customer base independent of any platform.
- Model your unit economics under an adverse platform scenario explicitly, not just your current, favorable conditions.
- Set explicit kill criteria tied to platform dependence specifically, turning abstract awareness of this risk into an actionable, pre-committed threshold.
Frequently Asked Questions
How often should I re-run this checklist as my business evolves?
Re-run it at least annually, and immediately upon any signal that your primary platform's policies, fees, or algorithm may be shifting — following the periodic-review discipline covered throughout this site's broader risk-assessment content, platform dependence risk isn't static, and a checklist run once at launch without subsequent review can miss meaningful changes in your actual exposure level as your business and the platform's own policies both continue to evolve.
Is some degree of platform dependence always going to be part of a commerce business?
Yes, generally — very few commerce businesses achieve zero platform dependence entirely, and this checklist's goal isn't eliminating dependence completely but rather understanding its specific shape and building genuine, deliberate resilience alongside it, following the general risk-management discipline covered throughout this site's broader content rather than pursuing an unrealistic goal of total platform independence.
How does this checklist relate to the broader rented-land trap essay, covered elsewhere on this site?
The rented-land trap covers the broader strategic argument and reasoning behind why platform dependence deserves deliberate attention, while this checklist provides the specific, actionable diagnostic tool for assessing your own particular business's exposure level — read that essay for the fuller reasoning, and use this checklist as the practical, periodic assessment tool that operationalizes its core argument into a concrete, repeatable practice.
What should I do if this checklist reveals genuinely high platform dependence I can't quickly fix?
Start with the single highest-leverage item first, generally direct customer contact data, following the prioritization guidance covered above, rather than attempting to address every identified gap simultaneously — a partial, honest improvement made deliberately and consistently is genuinely more valuable than an ambitious plan to fix everything at once that stalls under its own scope and never actually reduces real exposure. Set a specific, modest target for the next review cycle rather than an open-ended intention, since a concrete, time-bound goal is considerably more likely to produce genuine progress than a general commitment to "diversify eventually."