GTM OpsSaaStr — Jason Lemkin

How Databricks Sells to Dozens of Industries Without Building a Single Vertical Product

Read original
back-to-basics-gtmrevenue-platform-consolidationhuman-first-sales

“Personas and ICP are about you — your product's fit, your market opportunity. Neither forces you to speak the language of the human sitting across the table from you. That human doesn't care about your TAM model. They care about the strategic priorities their CEO just laid out on the last earnings call.”

Key takeaways

  • Databricks uses 'imperatives' framework instead of traditional personas/ICP to sell horizontal platform across dozens of verticals without building vertical-specific products
  • Imperatives sit at intersection of three elements: customer priorities (OKRs/accountability), industry trends (market movements), and your product capabilities (differentiated value)
  • Traditional personas focus on buyer characteristics and ICP focuses on account fit, but neither forces you to speak the customer's strategic language or connect to their CEO's priorities
  • Framework is 'worth stealing' for any B2B horizontal platform selling into multiple industries - shifts from product-centric to customer-priority-centric positioning
  • Databricks retail example shows three imperative themes: personalization/monetization of customer experience, employee improvement, and supply chain optimization

Why this matters for operators: Horizontal platforms selling into multiple verticals; companies struggling with vertical GTM without building vertical products; enterprise sales teams needing better industry positioning

I cover AI×GTM intelligence like this every Wednesday.

Get STEEPWORKS Weekly

More picks

AI DevelopmentLenny's Podcast

Humans will keep inventing new reasons why we must stay in the loop with agents

  • Human resistance to full AI autonomy is not purely technical—it's psychological and organizational; companies will rationalize keeping humans in decision loops even when agents are capable
  • The 'human-in-the-loop' requirement may become a self-perpetuating narrative rather than a genuine necessity, driven by organizational risk aversion and change resistance
  • Product leaders at scale (Notion) are observing this pattern, suggesting it's a widespread phenomenon across enterprise AI adoption, not isolated to specific use cases
ai-agent-adoptionhuman-in-the-loopai-governance
Read original Full analysis →
GTM Ops**RevOps Impact (Jeff Ignacio)

Comp plans for consumption pricing

  • Consumption pricing fundamentally breaks traditional SaaS comp models—requires rethinking sales incentive structures around usage vs. contract value
  • Four distinct contract structures exist (pay-as-you-go, uncommitted, committed, hybrid), each requiring different compensation mechanics and sales behaviors
  • Enterprise consumption-based deals create tension: customers want flexibility, sales teams need predictability for quota attainment—comp design must bridge this gap
revenue-platform-consolidationconsumption-pricing-modelssales-comp-design
Read original Full analysis →
AI×GTMGTM OS: The Future GTM Operator

3 revenue motions your AI is only half wired into

  • Model parity has arrived: OpenAI/Claude now trade evenly on core tasks, making 'better AI' a non-differentiator—the edge shifts to integration depth into existing revenue motions
  • Waste is quantified: teams paying $17K-$37K/month for AI seats that never touch pipeline generation; real cost is opportunity cost of unused capacity, not subscription fees
  • Lean teams have a structural advantage: cannot out-buy larger competitors on model access, but can out-embed them by wiring AI 1 revenue motion deep (pipeline → content → deals) with proprietary deal context competitors haven't seen
ai-sdr-adoptionrevenue-platform-consolidationback-to-basics-gtm
Read original Full analysis →

This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.