R7 — Test defensibility with one question: would your competitor's version of this look exactly like yours? If yes, it's a commodity

Rule: Before any data-tool recommendation, ask this single test: would your competitor's version of this look exactly like yours? If yes → it's a commodity. Rent the cheapest decent version or use the free public one and move on. If no → if the edge comes from data only you have → that's worth building around.

Why: This is the operational form of the a16z position (Andreessen Horowitz, "The Empty Promise of Data Moats" (Casado & Lauten, 2019) — most "data network effects" are really scale effects that diminish) and the four-point defensibility synthesis (Synthesis: data is a defensible asset only when proprietary + hard to replicate + tightly coupled to a feedback loop + continuously refreshed — otherwise it is an operational byproduct any competitor can buy or collect). It is also the single sharpest client-facing framing in the brief — it cuts through the "data is the new oil" vendor frame in one question.

How to apply:

• Use the question explicitly in scoping conversations.
• Pair with R1 — Rent (or use free) for data ABOUT THE OUTSIDE WORLD; you will never out-collect the Census Bureau (for the commodity side) and R2 — Build only on data you already own — transaction history, CRM, scheduling, no-show patterns; that is the only category with native defensibility (for the defensible side).
• When the answer is "we don't know" — the right next step is exploration, not a build.