"Copilot is basically free in our MS bundle"

1. 1Concede the budget logic, fully and first. "You're right, the marginal cost of Copilot in your bundle is close to zero. That's real and I'm not going to argue you out of math that's true." Conceding disarms. Fighting price makes you look like you have nothing else.
2. 2Refuse to fight on price. Don't discount reflexively. Don't start a per-seat spreadsheet war you'll lose. Move the axis instead: "The question isn't what the seat costs. It's what an hour of senior engineering time costs and which tool returns more of it."
3. 3Propose a head-to-head on ONE real workflow. Skip the feature bake-off. Pick a painful, representative workflow they own: a legacy migration, a flaky test suite, a cross-repo refactor. Run it in both tools, with their engineers and their code, time-boxed. Box reports migration effort cut 80–90% (vendor-reported; verify before quoting). That's the kind of delta a real workflow exposes and a price sheet hides.
4. 4Differentiate on depth, governance and outcomes. When the head-to-head surfaces the IDE-to-cloud continuum (IDE → CLI → Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition.), the version-controlled Project RulesVersion-controlled instructions in the repo that every Cursor agent interaction inherits, so standards are encoded once. Press Enter for the full definition. and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition.'s independent review, then introduce the control plane: "Whatever you choose, here's the admin plane your security team will ask about: allowlists, audit, AI-code tracking, ZDRZero Data Retention. A contractual guarantee that the model provider won't store your code or train on it. Press Enter for the full definition.."

One discipline holds the whole script together: the head-to-head must be a workflow they already hate, never a demo you've rehearsed. Credibility comes from letting their reality make the argument, not your slide.