When a compliance lead says they build it in-house, most reps hear a no. The same sentence has come back with very different outcomes recently, so we now treat it as a question about scope.
One compliance officer at a fintech told us the team builds much of its technology internally. They still agreed to a 15-minute call. A second fintech had spent 18 months on its own regulatory system and declined outright. On the surface both said the same thing, and only one of them was closed.
The difference is whether the build is bounded or finished. A bounded internal build has a clear owner, a defined scope, and a team that can name what it has not done yet. They talk about gaps the way an engineering manager talks about a backlog. A finished system is different. Leadership is proud of it, it has usually been on the roadmap for years, and people describe what it does rather than what it lacks.
Three questions separate the two quickly without sounding like an audit. Which part of the process still runs on spreadsheets or manual review? When the next rule change lands, who builds the update and how long does it take? What did the last audit or examiner comment ask for that the system still cannot do? A bounded build answers with specifics and often admits the gap. A finished system answers with a short explanation and a change of subject.
If the build is bounded, do not pitch replacement. Pitch the gap. Offer to take one slice of the work they have not finished, and suggest a short call to compare their gap list against what you can cover. You are not asking them to switch. You are asking them to check their own backlog against an outside option. That is an easy call to say yes to.
If the system is finished and leadership is proud of it, stop selling. Ask what it does best, listen, and make a note. Arguing with something a team spent 18 months on will cost you the relationship and any future referral. If you follow up at all, tie it to a dated event they have already told you matters, and only with their agreement.
Length tells you less than you think. In a recent batch of technical and fintech calls, the three that produced a next step ran 936, 944 and 996 seconds, roughly 15 to 17 minutes. Each ended with a booked meeting or a clear follow-up. The longest call in the batch ran 1,500 seconds, or 25 minutes, and ended with no follow-up at all. A long call is not a qualified call. The duration does not give you the answer. The gap list does.
Our rule now: when you hear “we build it,” ask for the gap list before you decide it is a no.