About five of our 18 financial services contacts said they already had something in place: a commercial tool, an in-house build, or a GRC provider their team already runs. That is about 28% of the list, and it’s the objection reps dread most. The instinct is to defend the product and recite features. That usually loses the call.

Treat “we already have it” as information. The incumbent is the baseline you have to beat, and the team using it knows exactly where it breaks.

Take a managing partner who runs about 100 entities on CSC at roughly $200 per entity. The pitch leaned on speed. He said speed wasn’t a priority, their process was efficient, and his real concern was the “brain damage” of switching providers and the stability of a startup. He declined a meeting. When the incumbent works, the switching risk is the objection. The feature gap comes second.

An engineering lead at a 70-person company told us their internal AI spend was well controlled through their developer portal. Nothing to replace there. But he was interested in the gateway for resale to large clients. The gap wasn’t internal spend. It was the client-facing layer his current setup didn’t cover. We booked a meeting on that.

A staff engineer whose team runs OpenAI and Anthropic had a different gap. Access to the models was fine. Visibility into spend and token usage was not. Email delivery problems got in the way, but he agreed to a 20-minute intro on a Thursday at 5:00 PM UK time, with a Calendly invite and a text or call follow-up if email kept failing.

Our process before the pitch:

  1. Ask what the current setup does well, and get them to say it. This lowers defensiveness and tells you what not to attack.
  1. Find the workaround. Look for spreadsheet exports, manual reconciliation, or a question their tool can’t answer. Workarounds mark the gap.
  1. Position against the gap, not the category. “You don’t need to replace your platform. You need to see the one thing it doesn’t show you.”
  1. Price the switch honestly: retraining time, migration effort, and whether the audit trail survives. Don’t invent commercial terms to make the switch look cheaper.
  1. Book the smallest next step. Twenty minutes to test one specific gap beats a full demo nobody asked for.

Compliance teams don’t reject a tool because it’s bad. They reject it because switching looks like more work than the pain they already tolerate. Make the pain specific, and the incumbent starts to look like the expensive option.