The Playbook · Chapter 3: Demo calls · Lesson 2 of 2

How to answer “does it work with our stack?”

Does it work with what we already run?

If this means a migration, I'm out.

Answer the fear, not just the question. The question is integrations; the fear is disruption. Say what stays exactly the same first, then what changes, in that order. The order is the reassurance.

The read

Why they say it

Behind the integration question sits a migration that went badly once, and a person calculating how much of their team's quarter your product could consume.

That's why a feature-list answer misses. They didn't ask what you connect to; they asked, in stack vocabulary, whether saying yes to you means pain.

The move

Answer the fear, not just the question, in practice

In practice the order runs: what stays exactly the same on day one, then what changes, then what's optional later. Most reps open with everything the product could do, and to this buyer a list of possibilities is a list of work.

Be concrete about their core systems, not your whole catalog. Knowing their stack better than they expected is worth more than a wall of logos on a slide.

If something genuinely doesn't connect, say so and name the workaround plainly. An honest gap with its cost attached builds more trust than a stretched yes that surfaces during rollout.

Same exit, other doors

Variations you'll hear

We're locked into one vendor's ecosystem. They're telling you who they are, not just what they run. Answer with that vendor's native integration points, not a generic API answer.

Who else runs this with our setup? A reference request in disguise. Have one story ready, or say plainly that you'll connect them with a customer on a similar stack.

How long does implementation take? What they're really pricing is their team's time. Answer in their hours, not your project plan.

Hear this objection handled

A sample call against an AI buyer who leads with it, scored and broken down

Charles Whitaker
9

The caller successfully secured the meeting by closely adhering to the structured reassurance strategy, first confirming that existing hardware and dispatch workflows would remain unchanged before introducing the optimization layer.

0:00/0:00

Your turn against the same buyer

Same persona, same objection, same scorecard

Charles Whitaker

Cold Call to Apex Logistics Group

Your objective is to secure a 15-minute product demonstration with Charles. When he inevitably asks if your system integrates with his existing setup, you must address the deeper fear of operational disruption, not just the technical integration. Frame your answer by stating what stays exactly the same first (their dispatch workflow, their existing hardware terminals), and only then explain what changes (the automated background route optimization). Strictly follow this order of reassurance to disarm his skepticism and earn the meeting.

Uses your mic. Hang up anytime. Scorecard at the end.

Practice it until it stops working on you.

Start practicing