🚀 AI-Powered Mock Interviews Launching Soon - Join the Waitlist for Early Access

situationalhigh

A prospect, a CTO of a mid-sized tech company, expresses strong skepticism about the ROI of our solution, stating they've invested heavily in custom-built internal tools that they believe are superior. How do you strategically challenge this assumption, gather data to quantify the hidden costs of their current approach, and position our solution as a more efficient and scalable alternative without directly disparaging their existing investment?

final round · 3-4 minutes

How to structure your answer

MECE Framework:

  1. Acknowledge & Validate: Express understanding of their significant investment and perceived value of custom tools.
  2. Probe for Gaps & Hidden Costs: Ask open-ended questions about maintenance, scalability, security updates, feature parity with market, developer bandwidth allocation, and opportunity cost of internal resources.
  3. Quantify & Compare: Introduce industry benchmarks for TCO of custom vs. COTS. Offer to conduct a joint ROI analysis focusing on operational overhead, future-proofing, and innovation velocity.
  4. Position as Strategic Partner: Frame our solution as an accelerator for their core business, freeing up internal teams for differentiating work, rather than a replacement for all custom tools.
  5. Call to Action: Propose a discovery session to map their current challenges against our solution's capabilities, focusing on specific pain points identified.

Sample answer

I'd approach this using a consultative, data-driven strategy. First, I'd acknowledge their significant investment and the perceived value of their custom tools, validating their expertise. Then, I'd pivot to asking strategic, open-ended questions designed to uncover potential hidden costs and resource drains: 'How do you manage ongoing maintenance, security updates, and feature enhancements? What's the opportunity cost of your engineering team building and maintaining these tools versus focusing on core product innovation? How quickly can you adapt to new market demands with your current setup?'

This line of questioning helps them self-identify potential inefficiencies. I'd then offer to collaborate on a 'Total Cost of Ownership (TCO) Discovery Session,' where we can jointly quantify the true cost of their current approach, including developer salaries, infrastructure, and lost innovation time. I'd present anonymized industry data on the long-term scalability, security, and feature velocity advantages of specialized solutions. My goal isn't to disparage, but to position our solution as a strategic accelerator that frees their internal teams to focus on their unique competitive differentiators, rather than commodity infrastructure, ultimately driving greater ROI and scalability for their core business.

Key points to mention

  • • Validate their existing investment.
  • • Focus on 'hidden' or 'opportunity' costs (maintenance, upgrades, security, scalability, developer bandwidth, technical debt).
  • • Emphasize TCO (Total Cost of Ownership) over initial development cost.
  • • Position solution as complementary or an accelerant, not a direct replacement.
  • • Highlight core competencies: allowing their team to focus on strategic, revenue-generating work.
  • • Use discovery questions to uncover pain points related to their custom tools.
  • • Reference industry trends regarding build vs. buy decisions for non-core functionalities.

Common mistakes to avoid

  • ✗ Directly criticizing or disparaging their custom tools.
  • ✗ Assuming their custom tools are inherently inferior without discovery.
  • ✗ Over-focusing on features of your solution before understanding their pain points.
  • ✗ Failing to quantify the potential savings or benefits in their context.
  • ✗ Being overly aggressive or dismissive of their past efforts.
  • ✗ Not asking enough open-ended questions.