When encountering a prospect who pushes back, the best strategy is not to argue or prove them wrong. Instead, give them the space to find their own way into your solution. Trying to force their conversion only increases resistance; allowing them autonomy can turn them into your strongest advocates.

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.

Instead of attacking a prospect's current approach (status quo), acknowledge its "redeeming reasons." This prevents an offense-defense dynamic where they feel compelled to protect their past decisions. It lowers their guard and makes them more receptive to hearing about negative consequences they hadn't considered.

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.

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.

Immediately attacking a prospect's current solution triggers a defensive reaction. A more effective strategy is to first empathize with why they made that choice, acknowledging its merits. This disarms them and creates an opening for a more collaborative discussion about its limitations, preventing an adversarial dynamic from the start.

Instead of waiting for prospects to raise concerns, proactively bring up potential issues and objections. This demonstrates fearlessness and courage, building trust and positioning you as a confident partner rather than a salesperson just trying to close a deal.