Library/Deal Strategy & Stakeholder Management/Objection Handling & Risk Reduction/Respond to In-House-Build Objection
TestedDeal Strategy & Stakeholder ManagementQuick Win (under 10 min)
About this prompt
This prompt helps AEs and Sales Engineers respond when a technical buyer says they've already built something in-house that handles the problem. It produces a four-part response framework: an acknowledgment that respects the engineering investment, curious questions to understand the actual scope of what they built, subtle wedge questions that surface maintenance burden and opportunity cost, and a bridge to your value only if a genuine gap exists. Use it in technical evaluations where an engineering team is in the room and dismissing their work would end the conversation.The in-house-build objection is one of the hardest to handle because the person raising it has ownership and pride in what they built — pushing back directly creates defensiveness rather than dialogue. This prompt generates a response framework that starts by acknowledging their investment before exploring whether a real gap exists, which is the correct sequence. Populate [YOUR PRODUCT] to ground the comparison, [SIZE] because the maintenance burden argument lands differently for a 10-person engineering team than a 500-person one, [WHAT YOU THINK THEY BUILT] based on what you know about their technical stack and the scope they've described, and [WHAT MAKES YOU BETTER] with specific differentiators — not feature lists, but the capabilities they are most likely missing based on what they told you. The goal the prompt sets — understand if there's a real opportunity, not to win the objection — is the right mental model here; if their in-house solution genuinely covers the use case, this prompt will help you figure that out early rather than spending cycles on a deal that isn't real. Use this in evaluation-stage calls with technical buyers; if you're in an introductory call and they mention in-house tools in passing, note it and return to it later rather than engaging immediately.The prompt
Help me respond to this objection from a technical buyer: "We've already built something in-house that does this." Context: ● My product: [YOUR PRODUCT] ● Their company size: [SIZE] ● Their likely in-
The rest of this prompt is Pro.Copying the full text is Pro. Browsing stays free, and 100 prompts are free in full.
Copying the full text is Pro.
Variables to replace
YOUR PRODUCT | SIZE | WHAT YOU THINK THEY BUILT | WHAT MAKES YOU BETTER
How to run it
- Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot — it's tuned to run in any of them.
- Replace the variables — swap each bracketed token for your deal's specifics. The variables list above explains every field.
- Make it yours — run it, keep what's strong, and tighten your inputs on the next pass. The prompt improves with your context.
What good output looks like
Make it yours
Promptifi ProFull text of all 2,900+ prompts, every workflow, unlimited saves.Start Pro — $4.99/moor $99 once, lifetime
You're ProFull library open. Copy, save, and chain anything.