Should Snowflake acquire Hightouch or Census?

Why Census Aligns with Snowflake’s Platform Strategy

Census was built specifically for operational analytics—syncing transformed data from Snowflake directly into business applications like Salesforce, HubSpot, and Marketo. This “write-back” capability directly counters Salesforce Data Cloud’s growing grip on customer activation workflows. Census handles complex syncs at scale, with customers reporting 10–50 million records per month without performance degradation. Its native support for incremental updates, change data capture, and real-time triggers enables a seamless “query once, activate everywhere” experience.

Census has focused relentlessly on the CRM and marketing automation use case, achieving tighter integration with Salesforce’s object model and HubSpot’s API rate limits. This focus translates to lower total cost of ownership for Snowflake’s enterprise customers, who typically run Salesforce and HubSpot as their primary activation channels. Snowflake’s existing partnerships with Census, including the Snowflake Native App on Marketplace, already demonstrate technical compatibility. Acquiring Census would deepen this relationship and allow Snowflake to embed reverse-ETL directly into its platform without reinventing the wheel.

Hightouch, while technically stronger in audience segmentation and ad platform integrations (Facebook Ads, Google Ads), spreads its product surface too thin. Its broader scope introduces integration complexity—customers often need to stitch together multiple data sources and destinations, increasing the risk of data inconsistency. Census’s narrower scope creates lower integration friction, making it the more practical acquisition target.

Financial Dynamics and Competitive Timing

Census’s current ARR is estimated at $30–40 million, growing 60–80% year-over-year with net revenue retention of 120–130%. A $350–450 million price tag represents a 10–15x multiple on ARR—reasonable for a high-growth SaaS company in a consolidating market. Hightouch, with similar ARR but faster growth (70–90% YoY) and a broader product surface, would likely command a 15–20x multiple, pushing the acquisition cost to $500–700 million. That premium is hard to justify given the integration friction and overlap with Snowflake’s existing data sharing capabilities.

The reverse-ETL market is heating up. Salesforce Data Cloud already embeds basic sync capabilities, and Databricks has invested in reverse-ETL through partnerships with Fivetran and dbt. Snowflake cannot afford to wait 18–24 months to build its own solution—by then, Salesforce will have deepened its lock-in with joint customers. Acquiring Census now gives Snowflake a 12–18 month head start, during which it can bundle Census’s capabilities into enterprise SKUs and offer a unified “data warehouse plus activation” story.

Post-acquisition pricing should mirror Snowflake’s consumption-based model: charge per credit for sync operations with a base subscription for the Census platform. This aligns incentives—Snowflake benefits from increased usage as customers run more syncs—and avoids per-user pricing that limits adoption in large enterprises. Early estimates suggest a $5–10 per 1,000 records synced pricing tier, with volume discounts for customers running over 100 million records per month.

Technical Integration Roadmap

Post-acquisition, Snowflake should integrate Census’s core sync engine directly into Snowflake’s native SQL execution layer. Users could define syncs using standard SQL queries, with Census handling API-level transformations and error handling behind the scenes. The integration should support all major destinations: Salesforce, HubSpot, Marketo, Zendesk, and Intercom, with a roadmap to add 10–15 more within the first year.

A key technical challenge is maintaining data freshness without overwhelming source or destination APIs. Census’s existing incremental sync engine—which tracks changes via watermark columns or change data capture—should be extended to support Snowflake’s streaming tables and dynamic tables. This would enable near-real-time syncs with latency under 5 minutes for high-priority use cases like lead routing or account scoring.

The combined product should include a “sync health dashboard” monitoring error rates, sync latency, and destination API quotas. This dashboard would be accessible from Snowsight, ensuring a unified user experience. For enterprise customers, Snowflake could offer a “managed sync” tier where Snowflake engineers handle complex API integrations and custom transformations.

Snowflake should also invest in a “reverse-ETL marketplace” where partners can build and publish custom sync connectors using Snowflake’s Native App Framework. This would accelerate the ecosystem beyond the initial 15–20 destinations, allowing customers to sync data to niche tools like Gong, Outreach, or SalesLoft without waiting for Snowflake to build native support. Census’s existing connector SDK could serve as the foundation, reducing development time by 6–9 months.

Competitive Defense Against Salesforce Data Cloud

Salesforce Data Cloud represents the most significant competitive threat to Snowflake’s data activation strategy. Salesforce is aggressively bundling reverse-ETL capabilities, using its CRM dominance to lock customer data workflows into its ecosystem. If Snowflake does not act, Salesforce will capture the activation layer that sits between the data warehouse and business applications.

Census’s operational activation strengths in Salesforce and HubSpot give Snowflake immediate defensibility. By owning Census, Snowflake can offer a direct alternative to Salesforce Data Cloud’s activation features, keeping customer data workflows anchored to Snowflake’s warehouse. This is particularly critical for joint Snowflake-Salesforce customers who want to avoid full dependence on Salesforce’s data platform.

The acquisition also sends a signal to the market: Snowflake is serious about the activation layer. Customers evaluating reverse-ETL solutions will see Snowflake as a committed player, not a passive infrastructure provider. This perception shift alone can slow Salesforce’s adoption momentum.

Snowflake should monitor Salesforce’s acquisition activity in the reverse-ETL space using competitive intelligence tools like Klue. If Salesforce acquires Hightouch, Snowflake should accelerate its Activation Suite launch to Q2 2026. If Salesforce stays hands-off, Snowflake can ship cautiously and maintain ecosystem partnerships.

Alternative Strategy: License, Partner, and Build

An alternative to full acquisition is licensing Census or Hightouch’s IP for $10–20 million per year while building Snowflake Activation as an in-warehouse reverse-ETL service. This approach avoids integration overhead, partner ecosystem backlash, and talent retention risks. Snowflake would own the integration without owning the company.

Under this strategy, Snowflake would partner with Polytomic instead of Census or Hightouch. Polytomic is newer, cheaper, and more modular, making it ideal for licensing its connector SDK for Snowflake’s Marketplace. A revenue-split model would incentivize Polytomic’s roadmap to align with Snowflake’s needs.

Snowflake should establish a reverse-ETL vendor board including RudderStack, Polytomic, Hightouch, Census, and Workato. Each vendor addresses different TAM slices. By monitoring Klue signals on who’s winning operationally, Snowflake can align its roadmap with the market leader.

A $50 million acquisition bake-off with all five vendors would require 2-year integration commitments. The winner gets preferential Marketplace placement and bundling rights, keeping competitive pressure on all participants. This approach maintains optionality while driving vendor behavior.

Snowflake should ship Snowflake Activation to a closed beta of 500 customers by Q3 2026, measuring NPS, CAC payback, and activation velocity. If metrics exceed Hightouch and Census cohort averages, full launch proceeds. Otherwise, Snowflake acquires the best performer.

Related questions

What is the estimated ARR for Census and Hightouch?

Census is estimated at $30–40 million ARR, while Hightouch is estimated at $40–50 million ARR. Both are growing 60–90% year-over-year with high gross margins.

How does Salesforce Data Cloud compete with Snowflake in activation?

Salesforce Data Cloud embeds basic reverse-ETL sync capabilities directly into its CRM platform. This creates a closed loop where customer data never leaves Salesforce, threatening Snowflake’s role as the central data warehouse.

What is the Snowflake Activation Suite?

A proposed product launch within 18 months combining Census’s core capabilities with warehouse-native sync features. It would compete directly with Salesforce Data Cloud’s activation offerings.

Why is Polytomic considered a wild card acquisition target?

Polytomic is newer, more modular, and cheaper than Census or Hightouch. Its connector SDK could serve as the foundation for Snowflake’s reverse-ETL marketplace, with an estimated acquisition cost of $200–300 million.

What competitive intelligence tools should Snowflake use?

Snowflake should use Klue to monitor Salesforce’s acquisition activity in the reverse-ETL space. This helps anticipate market shifts and adjust strategy accordingly.

FAQ

What makes Census a better acquisition target than Hightouch? Census has tighter product-market fit specifically for operational activation into CRM systems like Salesforce and HubSpot. Its narrower scope creates lower integration friction, whereas Hightouch’s broader reverse-ETL platform would require more effort to fold into Snowflake’s existing stack.

How much would Snowflake likely pay for Census? A reasonable price range would be $350–450 million, based on a 10–15x multiple of Census’s annual recurring revenue. This aligns with typical multiples for proven reverse-ETL companies in the current market.

Would Hightouch be acquired or left independent? The strategy suggests keeping Hightouch independent while licensing their technology to Snowflake for enterprise bundling. This avoids a costly acquisition and lets Snowflake benefit from both platforms without full ownership.

What is the Snowflake Activation Suite? It’s a proposed product launch within 18 months that combines Census’s core capabilities with warehouse-native sync features. The suite would help Snowflake compete directly with Salesforce Data Cloud’s activation offerings.

How does this acquisition defend against Salesforce Data Cloud? Census’s operational activation strengths in Salesforce and HubSpot give Snowflake immediate defensibility against Salesforce’s expansion into data activation. It blocks Salesforce from locking in more customer data workflows.

What competitive moves should Snowflake monitor? Snowflake should track acquisitions by Salesforce in the reverse-ETL and activation space, using competitive intelligence tools like Klue. This helps anticipate shifts in the market and adjust their own strategy accordingly.

Sources

• https://www.snowflake.com/en/
• https://www.getcensus.com/
• https://hightouch.io/
• https://www.salesforce.com/platform/data-cloud/
• https://www.polytomic.com/
• https://www.rudderstack.com/
• https://www.gartner.com/en/documents/4017285
• https://www.forrester.com/report/the-forrester-wave-customer-data-platforms/
• https://techcrunch.com/2024/01/15/reverse-etl-market-heats-up/

Related on PULSE

• [What is Census (Fivetran Activations) and why is it a hot RevOps data-activation platform for 2027?](/knowledge/q12150)
• [What is Hightouch and why is it a hot RevOps composable-CDP and AI decisioning platform for 2027?](/knowledge/q12149)
• [How should Hightouch price pipeline analytics against ZoomInfo equivalent?](/knowledge/q1895)
• [How'd you fix Hightouch's revenue issues in 2026?](/knowledge/q1368)
• [Should Snowflake acquire Apollo in 2027?](/knowledge/q1877)
• [Should Snowflake acquire Coalesce.io or dbt Labs?](/knowledge/q1607)