Claim and evidence
paying rent for the right to plug into someone else's database.Salesforce, HubSpot · a16z.com · 2026-05-14
Secondary
A reputable third party analysed it (Lenny's Newsletter, First Round Review, Reforge, an Ahrefs study).
a16z argues AI agents lower migration friction and shift lock-in to the AI layer.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Accumulated data and third-party apps depending on your database raise the cost of any decision to leave; extra modules on the same data deepen it.
How to run it
- Be the system of record for a workflow
- Open an integration marketplace
- Add modules on the same data
- Track integrations per account vs retention
Ways to run it
Design options to test, not promised results.
- Option AIntegration marketplace
Open a marketplace where other apps plug into your data, as Salesforce and HubSpot do.
- Option BModules on shared data
Add new products that reuse the same records, deepening what a move would cost.
- Option CIntegrations as a health signal
Track integrations per account against retention to see where lock-in is weak.
Dated examples
- 2026
Salesforce, HubSpot
a16z describes marketplace apps paying rent to plug into the CRM database and modules raising exit cost.
“paying rent for the right to plug into someone else's database.”
✓ quote checked word-for-word on the pagea16z.com · 2026-05-14
Does it still work?
Sources
- a16z.com
“paying rent for the right to plug into someone else's database.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (retention)