Clearbit's API-first platform strategy

Diving deeper into

Matt Sornson, co-founder & ex-CEO at Clearbit, on vertically integrated data and workflow tools in sales and marketing

Interview
we didn't want to lose the innovation edge, which was having so many amazing people building cool stuff on top of it.
Analyzed 4 sources

Keeping the API alive meant Clearbit could use its customers as an external R&D engine. Developers and technical marketers were wiring Clearbit data into Salesforce, HubSpot, Segment, Zapier, Drift, and custom workflows, which showed where the data created real value. The platform then turned the best of those patterns into packaged products, while new platform APIs let customers export combined CRM and Clearbit data back out into other tools.

  • Clearbit started as APIHub and reached $1M in about a year by selling raw company and person data primitives. That API first start gave it distribution with developer friendly buyers before it moved up into forms, audiences, website personalization, and routing workflows for marketers.
  • This is the core tradeoff in vertically integrated sales software. Apollo, ZoomInfo, and later HubSpot bundle data with the app where reps work, which is easier to buy and deploy. Clearbit kept the API because it preserved neutrality across customer stacks and surfaced use cases a single app team would miss.
  • The platform did more than wrap the API in a UI. It joined Salesforce, Marketo, Snowflake, website activity, and Clearbit enrichment into one customer graph, then exposed those computed audiences and segments through platform APIs so other products could trigger campaigns from them.

The category keeps moving toward bundles where the best data is built directly into the system of record, but the winning products will still expose that data outward. The next wave is not API or platform. It is tightly integrated workflows on top, with programmable access underneath, so the product can be both easier to use and harder to replace.