We scan new podcasts and send you the top 5 insights daily.
A pilot or Proof of Concept (POC) is not a core cause of a purchase. Instead, it is an extra step in the sales process that adds time and complexity, placing it in the category of things that can prevent a deal. It should be avoided or minimized, not encouraged.
Before committing resources to a proof-of-concept (POC), build a preliminary ROI case. If the potential return isn't substantial enough for the customer to reallocate budget or personnel, the deal is unlikely to close. This step prevents wasting both your and your customer's time on unwinnable evaluations.
When a prospect asks for a free pilot, treat it as a sign that you failed to build enough confidence in the outcome. Instead of agreeing, diagnose their uncertainty by asking what they still need help predicting. This shifts the conversation back to value and avoids deploying your best resources on your least committed customers.
If a large customer drags out a pilot indefinitely, it's a sign that your solution isn't solving a visceral, high-priority pain. When the need is urgent, enterprises will "bulldoze" through internal bureaucracy to get the product into production quickly.
When a sale closes after a pilot, founders mistakenly credit the pilot as the cause, leading them to bake it into their sales process. The reality is that customers with strong pull might have bought anyway, and the pilot was an unnecessary hurdle they overcame, not a catalyst for the purchase.
When a clunky sales process fails, founders often incorrectly conclude their product isn't good enough and retreat to building more features. The real problem is typically the sales motion itself, which isn't aligned with customer demand. This leads to a cycle of building instead of fixing the sales process.
A successful sales process isn't just about identifying customer pull and fit (the causes). It's also about systematically designing out the things that prevent a purchase. This means minimizing steps like security reviews or long pilots, treating them as checkboxes to clear as efficiently as possible.
Contrary to the belief that top-tier products sell themselves, even OpenAI—the hottest company on Earth—uses pilots for major deals. If your pilots aren't converting, the issue is your product's value proposition, not the pilot process itself.
A customer's request for a pilot can signal many things: a bureaucratic necessity, genuine skepticism about your claims, or a polite way to delay saying no. You must first diagnose the reason behind the request to determine if a pilot is appropriate and how to structure it.
Labeling an ABM initiative a "pilot" signals a lack of long-term commitment and sets unrealistic expectations for quick results, especially when dealing with long sales cycles. To succeed, ABM must be positioned from the outset as a core, long-term go-to-market strategy that requires sustained investment.
Don't ask a customer, 'What do you need to see for this pilot to be a success?' This frames the pilot as an audition. Instead, ask, 'Under what conditions would you *not* buy as a result of the pilot?' This correctly positions the pilot as a final verification step before a confirmed purchase.