Respond to "We Can Build This In-House"

This template is for a late-stage discovery or evaluation call where an engineering-led buyer says they could build the capability themselves. It is designed for build-vs-buy objections, not for pricing-only pushback or generic objection handling. The goal is to help the learner compare in-house build effort against buying with a concrete, credible frame. It works best when the buyer is technical, confident, and skeptical of vendor claims.

Use it after the buyer has shown real interest in the problem and is now pressure-testing whether your product is worth purchasing. It fits late discovery, solution review, or pre-proposal conversations where implementation feasibility is being debated. It is less useful at the very top of funnel, where the buyer has not yet committed to the problem. The scenario helps reps practice moving from feature interest to business-case comparison.

This roleplay is ideal for account executives, sales engineers, founders selling technical products, and customer-facing leaders who need to handle technical skepticism. Managers can use it in coaching sessions to evaluate whether a rep can stay calm, quantify tradeoffs, and ask strong follow-up questions. It also works well for peer practice because the persona has a clear temperament and realistic pushback. The best facilitator is someone who can score the learner on specific behaviors, not just general polish.

The rep should show that they can acknowledge the buyer's ability to build, then compare the real cost of doing so against buying. That means naming likely build time, launch time, stabilization effort, and the ongoing maintenance burden. The rep should also connect engineering time to opportunity cost in business terms, such as delayed roadmap work or slower delivery of higher-value initiatives. A strong attempt ends with a concrete next step, not a vague promise to follow up.

Practice it whenever engineering-led buyers are a meaningful part of the pipeline, especially if reps regularly hear “we can build this ourselves.” It is also useful before major pipeline reviews, product launches, or enterprise deal cycles where technical buyers are likely to challenge buy-vs-build assumptions. Teams often revisit it after a lost deal to see whether the rep underplayed maintenance, overclaimed speed, or failed to quantify opportunity cost. Repeating the scenario helps reps build a more grounded, repeatable response.

The most common mistake is arguing with the buyer instead of acknowledging that they probably could build something. Another is giving vague claims like “it will take a lot longer” without breaking down build, launch, and support effort. Reps also often ignore hidden costs such as maintenance, bug fixes, documentation, and internal ownership after launch. The scenario exposes whether the rep can move the conversation from opinion to a realistic comparison.

Customize the scenario with your product's actual implementation shape, likely integration points, and the kinds of engineering resources required to replicate it. You can also tune the buyer persona to match your market, such as a startup CTO, a director of platform engineering, or an enterprise architect. The rubric can be adjusted to emphasize security review, data migration, or ongoing support if those are common objections in your deals. Keep the core structure focused on build time, opportunity cost, and maintenance burden.

Ad hoc responses often drift into feature defense or generic reassurance, which can make a technical buyer more skeptical. This template gives the rep a repeatable structure: acknowledge, quantify, compare, and close on a next step. That makes coaching easier because managers can score specific behaviors instead of subjective confidence. It also helps teams standardize the message across reps so the objection is handled consistently.

The best next step is usually a concrete comparison step, such as reviewing implementation assumptions, mapping the buyer's internal effort, or agreeing on success criteria for a pilot or evaluation. The rep should avoid ending with a soft “let me know what you think” close. Instead, they should guide the buyer toward a specific action that advances the deal and clarifies the build-vs-buy decision. That keeps the conversation grounded in evidence rather than debate.