
Captures user interactions with no code to generate analytics.
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Heap (W13).
Heap made a technical bet that became a product-analytics category: capture interactions first and let teams decide what they meant later. Founded by Matin Movassate and Ravi Parikh in 2013, the YC W13 company replaced preplanned event instrumentation with Autocapture, retroactive event definitions, and eventually warehouse and customer-data connections.[1]
Heap reached a strategic acquisition, not a shutdown. It raised $205 million, approached a $1 billion private valuation, reached roughly 10,000 customers, and was acquired by Contentsquare in 2023.[2] The sharper lesson is that a category-defining wedge can lose strategic scarcity. As autocapture spread, the larger prize became an integrated system connecting quantitative journeys, qualitative sessions, and business outcomes. Contentsquare bought Heap to assemble that system.
Movassate found the problem inside Facebook, not in a market-sizing spreadsheet. As a product manager, he had access to sophisticated internal analytics but still depended on engineers to add tracking code, wait for releases, accumulate data, and enlist a data scientist. He recalled asking, “if Facebook couldn’t even get this right at their level of sophistication, what hope did any other online business have?”[1]
He and Parikh built the first prototype in a basement. Movassate later described the pair ignoring a Google staff engineer who said the idea was impossible.[3] The technical audacity was the business insight: the analytics bottleneck lived upstream of the chart. In the founders’ formulation, “Analytics is a problem rooted in data collection, not visualizations.”[1]
Heap entered Y Combinator’s Winter 2013 batch with that original thesis and did not pivot away from it. The company would automate the tedious parts of analytics, preserve raw interaction history, and let a product manager answer a new question without first predicting it. The founders also learned a commercial lesson early. Movassate advised founders to “Ask customers for money earlier,” because polite feedback could masquerade as demand while a purchase exposed the real objection.[1]
Heap’s first move was Autocapture. One client-side snippet recorded clicks, taps, swipes, page views, and form interactions. Its second move, Virtualization, separated collection from meaning. A team could later define a useful business event, such as activation or checkout completion, against already collected history. That removed the “data blackout” created when a team forgot to instrument a new feature before release.[8]
The product expanded in both directions. Sources pulled customer context from systems such as Salesforce, Marketo, and payment providers. Connect pushed curated behavioral data and revised event definitions into Redshift, BigQuery, Snowflake, S3, and other warehouse destinations. Illuminate attempted to move from query tools toward proactive recommendations. This arc turned Heap from a clever capture layer into a broader digital-insights platform.
The design carried a real tradeoff. Capturing broadly accelerated discovery but created governance, privacy, cost, and semantic-cleanup work. Heap added automatic PII detection, deletion tools, selective capture, and support for manual instrumentation alongside Autocapture.[8] The hybrid model mattered because a raw click stream is not a shared business language by itself.
Read the complete post-mortem, the rebuild playbook, and the exact reasons Heap is still worth studying now.