Key Takeaways

  • ClickHouse scaled beyond $350 million in ARR by copying Datadog's self-serve product-led growth motion instead of Snowflake's expensive upfront sales model.
  • Aaron Katz spent 12 years working under Marc Benioff at Salesforce, learning how a contact manager competing with ACT and GoldMine expanded to take on Siebel, SAP, Oracle, and Microsoft.
  • Enterprise sales motions cannot replace developer distribution early; they must be layered on top of proven bottom-up product adoption once volume exists.
  • ClickHouse buys instead of builds when founders build categories on top of ClickHouse, leading to the acquisition of Berlin-based agent observability startup Langfuse.

The Two Infrastructure Playbooks

Infrastructure startups face an early fork in the road. Katz looked at the two defining infrastructure software companies of the last decade: Datadog and Snowflake.

Snowflake chose heavy enterprise sales from the start, burning capital on large enterprise quotas and field marketing. Datadog chose self-service developer adoption. Developers deployed an agent, instrumented code, and ran queries without talking to a sales rep.

“I just thought it was going to be a lot easier to follow the Datadog playbook than the Snowflake playbook,” Katz said. “And it proved to be the case, but at some point you need to layer in an enterprise sales motion on top of some sort of PLG distribution.”

Starting with self-serve gave ClickHouse distribution velocity without massive customer acquisition costs. Developers adopted the database for real-time analytics quietly inside companies. Once developer usage created accounts with meaningful query volume, enterprise sales teams stepped in to negotiate company-wide contracts.

The Salesforce Expansion Formula

Layering enterprise sales onto an early product requires matching the sales ambition to the product trajectory. When Katz joined Salesforce early in his career, the company was a three-year-old startup selling basic sales automation.

“When I started, it was a three-year-old startup and it was basically a glorified contact manager,” Katz noted. “We essentially said what you're traditionally using ACT or GoldMine or using a spreadsheet, you can use Salesforce for. But Marc had this bigger vision and he said we're going after Siebel, SAP, Oracle, Microsoft.”

Salesforce did not wait for the software to match SAP before selling upmarket. Benioff defined the enterprise target early while the sales force targeted displacement of simple desktop tools. At ClickHouse, Katz applied the same sequencing: win developer workloads first, then build enterprise security, governance, and multi-product capabilities to close seven-figure commitments.

When to Build vs. Buy on Developer Demand

As developer adoption expands, customers demand adjacent tools. Founders often debate whether to build those tools internally or acquire them. Katz uses a simple filter based on what developers build on ClickHouse.

“If I think that our product and engineering teams can innovate in a specific area that we're not in today, then I'll let that play out organically,” Katz explained. “If I see a founder or group of founders that are building on top of ClickHouse that are getting into a category that I think is going to be a future component of what we build as an ultimate data platform, then I think about doing something inorganically.”

That logic drove ClickHouse to acquire Langfuse, an agent observability startup founded by three engineers in Berlin. Rather than building LLM agent monitoring from scratch, ClickHouse bought an existing team building on top of its engine.

What to Do With This

Audit your active pipeline to identify bottom-up usage inside enterprise accounts. Pull your top 20 self-serve accounts by usage volume this week, and assign an account executive to map the organizational chart behind the engineering team using your tool.