We scan new podcasts and send you the top 5 insights daily.
Instead of responding 'no' to RFP requirements your product can't meet, secure internal commitment from leadership to build it if you win. Position the gap as a 'custom development deliverable' with a timeline, turning a weakness into a sign of partnership.
In complex deals, frame your solution as part of a larger strategic "approach" that aligns with the buyer's existing initiatives. First, gain consensus on this shared approach, then position your offering as the foundational technology that enables it. This avoids commoditization.
When a prospect gets bogged down in niche technical requirements, ask how they accomplish that task today. Often, they'll admit they don't have a solution, which reframes their "must-have" requirement into a "nice-to-have." This prevents you from getting sidetracked defending a non-critical feature.
Product managers frequently receive solutions, not problems, from stakeholders. Instead of saying no, the effective approach is to reframe the solution as a set of assumptions and build a discovery backlog to systematically test them. This builds alignment and leads to better outcomes.
When facing a major technical unknown or skill gap, don't just push forward. Give the engineering team a dedicated timebox, like a full sprint, to research, prototype, and recommend a path forward. This empowers the team, improves the solution, and provides clear data for build-vs-buy decisions.
Don't view high-pressure sales requests as roadmap disruptions. Instead, see them as opportunities to pull forward planned features, co-design them with a committed customer, and provide the team with a motivating, tangible deadline. This turns external pressure into an accelerator for validated product development.
Don't just solve the problem a customer tells you about. Research their public strategic objectives for the year and identify where they are failing. Frame your solution as the critical tool to close that specific, high-level performance gap, creating urgency and executive buy-in.
When blocked from an RFP, focus on persuading both the buyer and their consultant. Use arguments based on their specific business needs, such as global presence and customer demographics, and reinforce with third-party validation like Gartner to make your inclusion seem essential.
By proactively asking about potential deal-killers like budget or partner approval early in the sales process, you transform them from adversarial objections into collaborative obstacles. This disarms the buyer's defensiveness and makes them easier to solve together, preventing them from being used as excuses later.
Avoid the trap of building features for a single customer, which grinds products to a halt. When a high-stakes customer makes a specific request, the goal is to reframe and build it in a way that benefits the entire customer base, turning a one-off demand into a strategic win-win.
Executives often see "discovery" as a slow, academic exercise. To overcome this, reframe the process as "derisking" the initiative. By referencing past projects that failed due to unvetted assumptions, you can position research not as a delay, but as a crucial step to prevent costly mistakes.