Recently, I met David Krauza, VP of Enterprise Data Strategy and Products & Governance at Comcast, at the 2026 CDOIQ symposium, and after chatting for a bit, he agreed to come on the show to talk about how he, as an enterprise buyer, thinks about B2B software purchases in the age of AI. As vibe coding makes internal development more accessible, David explains why the buy-versus-build decision isn’t simply about whether a company can build a solution itself. Leaders need to weigh long-term roadmaps, maintenance, integrations, and whether they want to take on the responsibility of becoming a software company. The real question is not just what can be built, but what makes the most strategic sense to own.

David also highlights an important consideration vendors frequently overlook: the data their own products create and the possible importance of that to an enterprise data leader. This is particularly true when the product’s primary intended purpose is not analytics itself. In a complex sales environment, which may include a senior data leader as a champion or decision maker, product metadata, or what you might currently be thinking of as a byproduct, might actually be a primary decision point in an enterprise purchasing conversation. David then outlines the pre-implementation work required before any of this can be evaluated: establishing shared definitions, explicit success metrics, and a documented “before-picture” you can run at renewal time to understand the ROI of the product.

We also explored the hidden costs that can undermine an otherwise compelling product. A polished UI may still create UX friction if users have to constantly move between systems, while complex data integrations can introduce additional labor and operational burdens. This friction should be considered during the evaluation rather than discovered after development. David says vendors can stand out by demonstrating that they understand where a customer’s business is headed and how their roadmap supports that direction. He also dropped some real gold about the difference he sees as a buyer when being pitched by a founder vs. a B2B salesperson—and what the latter is missing when they pitch him.

Highlights / Skip to:

  • Why buy any products when AI allows you to build them yourself? (2:03)
  • Allowing use cases and goals to dictate the adoption of internal solutions (4:03)
  • Making data capture, accessibility, and ecosystem fit part of the buying decision (5:54)
  • Is data missing in sales conversations due to a lack of marketing or of results? (8:36)
  • Comcast’s method for deciding to renew when the intelligence is invisible (11:22)
  • The importance of pre-post analysis when making a renewal argument (14:02)
  • Where David sees the most time being wasted in the pitch process and why vendors who did _____ win more often (16:36)
  • The hidden costs that often go undiscussed during the sales process (20:07)
  • How Comcast evaluates UX friction (back-and-forth of switching between applications to accomplish work) (22:22)
  • Other hidden factors that can prevent your sale from closing (25:13)
  • Differences David sees between founder-led sales and sales-led sales (26:41)
  • David’s advice for founders selling in the analytics and data space right now (28:14)

Links

Rss Apple Podcaster
Podden och tillhörande omslagsbild på den här sidan tillhör Brian T. O’Neill from Designing for Analytics. Innehållet i podden är skapat av Brian T. O’Neill from Designing for Analytics och inte av, eller tillsammans med, Poddtoppen.