Skip to content
LAST REVIEWED 2026-10THREE RECORDED SESSIONS AND SUPPLEMENTAL WRITING

A deep tech investor emphasized differentiated data rather than competing with large model developers on algorithms or compute. The speaker’s example involved collecting historical trading discussions over several years and selling that dataset. The account illustrates the value the speaker placed on historical coverage; it does not independently establish the dataset’s exclusivity, predictive quality or commercial results.

Two repeatable sources of differentiated data, from a seed investor whose thesis is exactly this:

  1. Collect what nobody publishes. Do the unglamorous work of gathering data that exists in the world but not in any dataset.
  2. Domain experience. The investor emphasized knowing which data matters to a customer’s work. That experience informs collection and interpretation; the claim still needs evidence that the resulting product offers something customers value.

The roundtable cautioned against relying on commodity enrichment alone. Identify what you collect or learn beyond what competitors can obtain, then test its value on the intended task.

The mechanics that came out of the practitioner roundtable:

  • Make feedback pay instantly. Users label your data when doing so immediately improves their own experience: that instant reward, not goodwill, is what powers explicit feedback loops.
  • Interview your ICP about what’s missing. The people doing delivery and support know which context the dataset lacks; mine call recordings the way teams “study film.”
  • Back-test creative sources. Permit and remodel records against subsequent outcomes, demographic age-out data, web-scraped alternative data, satellite imagery: the roundtable’s real-estate examples all shared one property: a testable predictive claim.
  • Test a smaller dataset. The roundtable discussed finding early signals before collecting data at scale. Test performance on the intended task; the discussion does not establish a universal relationship between dataset size and useful results.

The first-customer playbook connects here: deep early discounts traded for utilization minimums and feedback obligations are how the flywheel gets its first turns: see First customer contracts.

For compliance-grade products, the roundtable’s reliability pattern: multiple models cross-checking with a tiebreaker, tasks decomposed into micro-steps with intermediate outputs as an audit trail, and human-in-the-loop encoded as a company value rather than a patch.

The session material connects a growing dataset, improved predictive models and customers staying because the product improves. Explain the evidence for each link. More records do not, by themselves, demonstrate better results or continued customer demand. State what you have measured and which part remains a hypothesis.

When the moat depends on a marketplace or physical operations

Section titled “When the moat depends on a marketplace or physical operations”

The October pitch review brought a marketplace question into the discussion: after you introduce a buyer and supplier, why do they keep transacting through you? A directory or introduction can lose its value once both sides know each other. The participating founder described services such as financing and insurance as potential reasons to stay. Those services were part of the proposed approach; the session did not establish that they had prevented buyers and suppliers from going direct.

Make the continuing value explicit, then test whether customers actually use it. The reviewer also asked whether an infrastructure business would remain needed after the market bottleneck that made it timely began to ease. A large problem today is not, by itself, proof of a durable business.

The discussion broadened beyond data to physical and operational advantages. For a business involving hardware, explain who owns the assets, who pays for them, and what advantage the company retains. The investor described financing structures in which other parties carry hardware costs; this session does not establish that such financing is available to every startup or that software companies need hardware to be defensible.

Editorial synthesis: a useful test is whether the advantage survives when competitors can access similar software, buyers know their suppliers, and the immediate bottleneck improves. That question combines the reviewer’s challenges; it was not a quoted checklist from the room.

Test what customers would still value after a copy

Section titled “Test what customers would still value after a copy”

A supplemental practitioner article considers whether easier software copying and migration could weaken an existing advantage. The writer distinguishes an initial lead in shipping from an advantage that persists. These are strategic questions to test, not findings that switching costs or specialized expertise have disappeared.

The article describes a proposed way to recreate a customer’s workflow in another product. It does not establish that the proposed feature completed those customer migrations. Use the example to ask which parts of your own offer a competitor could reproduce and what work the customer would still need to change suppliers.

VEN editorial worksheet. These questions combine the supplemental article’s argument with the existing session discussion of continued customer value. They are not a quoted speaker framework.

QuestionEvidence to record
What could a competitor reproduce?The capability or workflow, and an actual comparison if available
What would migration still require?Relevant data preparation, integrations, permissions, validation, training or support work; check which applies
Why does the customer stay?Observed use, measured benefit and the customer’s explanation
What improves through use?A tested change in results, with the task and comparison made explicit
What would an incumbent put at risk by copying the offer?The effect on existing revenue, costs or channel relationships, with evidence for the assumption
Can your own model support the offer?Delivery, compute, support and update costs alongside the proposed revenue
What would disprove the claimed advantage?A comparison or customer test, its owner and a review date

The article also proposes alternative licensing and distribution arrangements. Those were options under consideration, not validated business models. Compare the customer responsibilities and economics before selecting one; see Pricing in the AI era.

For the customer conversation behind continued use, see Customer feedback and early retention. A claim that customers would find it hard to leave needs different evidence from a claim that they receive value and choose to stay.

Three sessions: an AMA with the managing partner of a deep tech seed fund on defensibility (Apr 2026), an in-person member roundtable on proprietary data and flywheels (May 2026), and an October 2026 pitch-deck review with a venture investor and former founder on marketplace durability and physical or operational advantages. Roundtable material is presented without individual attribution. October material is paraphrased, with founder proposals distinguished from demonstrated outcomes.

Supplemental practitioner writing: an article considering software defensibility, migration work and business models in the AI era, supplied for editorial review without a publication date. Its claims and proposed products are not independently verified results. The final section and worksheet identify that separate perspective; they do not represent a consensus of the session participants. Personal, company and product names from the article are omitted.