TCG085: Enterprise Salescraft with Drew Meli

William and Drew explore the often-misunderstood world of enterprise sales, specifically in infrastructure and cloud technology. Drew begins by sharing his background in sales, starting at a family-owned value-added reseller and progressing through various enterprise roles, highlighting his 16-year partnership with solutions engineer Justin Madison as an example of effective sales-SE collaboration.

The core of their discussion centers on what Drew calls the 'deal follow' - how a purchase evolves from initial interest to signed contract. Drew emphasizes that the first critical step is determining whether a genuine problem actually exists and whether stakeholders truly care about solving it. He argues against the stereotype that salespeople use smoke and mirrors, instead advocating for transparent conversations about challenges, solutions, and organizational alignment from the beginning.

A major theme throughout is the importance of identifying all relevant stakeholders before investing time in a deal. Drew explains that different people hold different types of authority - technical evaluators, budget holders, security gatekeepers, and executive sponsors all play distinct roles. He advocates for proactively bringing all these parties into discussions rather than having them obstruct deals late in the process. This approach prevents what he calls 'wedging in' solutions without proper organizational buy-in.

The conversation addresses the specific challenge of replacing existing systems. Drew notes that even if a new solution is technically superior, the migration costs, operational risk, and organizational effort required create legitimate reasons to maintain status quo. Good salespeople, he argues, need the discipline to acknowledge when change might not be worth it for a customer and know when to say no to a deal.

Regarding proof of concept (POC) and proof of value (POV) exercises, Drew stresses that these must be scoped, time-bound, and clearly connected to business justification. He emphasizes 'planning for success' - understanding what comes after a successful POC, including budget justification, which often requires working with finance teams to demonstrate ROI or identify cost savings from other areas.

The discussion then moves to post-evaluation gatekeepers: security review boards, compliance teams, legal, and procurement. Drew argues these aren't obstacles to work around but essential parts of ensuring organizational readiness. He notes that bringing these stakeholders in early prevents surprises and that companies sometimes must repeat security reviews if procurement takes too long, creating a cascading delay.

On generative AI's impact on sales and enterprise purchasing, Drew observes that AI tools are normalizing sales language and documentation, which paradoxically makes all vendors look similar. He notes the emergence of new stakeholders - AI councils and AI-focused roles within organizations - who now have input on purchasing decisions. Security and compliance questionnaires increasingly include AI-specific questions about data usage, model training, and organizational risk.

The final discussion explores how IT and infrastructure teams traditionally positioned themselves as cost centers but are now becoming closer to revenue-generating functions through cloud and AI initiatives. Drew argues this shift allows these teams to tell better stories about business impact rather than just operational necessity.