We scan new podcasts and send you the top 5 insights daily.
When highlighting the downsides of building in-house, avoid directly telling the prospect they will fail. Instead, frame potential pitfalls as lessons learned from other, similar companies ("One CMO I worked with found..."). This makes you a helpful advisor sharing industry wisdom, not a confrontational salesperson.
Instead of directly challenging an objection, reframe it by suggesting there's a deeper context. Using phrases like 'it sounds like there's a story behind that' encourages the prospect to volunteer the real root cause of their hesitation, transforming a confrontation into a collaborative discovery process.
Instead of promising a flawless implementation, build trust by telling prospects where issues commonly arise and what your process is to mitigate them. Acknowledging potential bumps in the road shows you have experience and a realistic plan, making you a more credible partner than a salesperson who promises perfection.
When a prospect says they'll build in-house, resist the urge to immediately counter. Instead, ask open-ended questions like "What led you to this decision?" to understand their core beliefs. This disarms them, reduces sales pressure, and uncovers weaknesses in their plan for you to address later.
When faced with the "we can build this ourselves" or "we can use ChatGPT" objection, don't argue about features. Simply ask, "If it's valuable and easy to build, why haven't you built it yet?" This forces the prospect to confront the real-world complexities and resource constraints, validating the need for your solution.
Tailor your innovation story to your company's risk culture. For risk-averse organizations, proactively acknowledging potential problems, barriers, and what could go wrong is more persuasive. For risk-tolerant cultures like Amazon's, leading with opportunity and the potential for learning is more effective.
After building trust and highlighting the risks of a DIY project, pivot to your solution using an "instead of" framework. Directly compare the negative outcomes you've discussed (e.g., "instead of pulling a developer to maintain this...") with the positive outcomes your product provides, letting the prospect self-convince.
Instead of directly criticizing a competitor, salespeople should share stories of why existing customers switched from that competitor. This reframes the critique as a customer's success story, making it more credible and less aggressive, while still highlighting the competitor's weaknesses.
To challenge a prospect's approach without making them feel attacked, use softening language and frame your point from experience. Saying, "We were working with another customer with a similar pain, but we discovered..." turns a direct confrontation into a helpful, experience-based insight that builds trust.
After a prospect decides to build in-house, don't fight them. Instead, offer genuine advice on how they can succeed, such as tips on resource allocation or success metrics. This counterintuitive move builds massive trust, lowers their defenses, and makes them more receptive to hearing the potential pitfalls later.
When discussing the downsides of a DIY approach, move beyond typical cost-benefit analysis. Highlight less obvious but critical risks, such as losing employee confidence with a failed internal rollout or the unforeseen complexity and delays caused by needing buy-in from privacy, compliance, and IT departments.