We booked a meeting with a general counsel managing compliance across six entities in California, Nevada, and Delaware. On paper, he fit perfectly. He handles regulatory work himself, no dedicated compliance person on staff, and when we asked about the role, he said it was “kind of a pain in the ass.” This sounded like a decision maker ready to solve a problem.
Then the disqualification came during the call.
He told us that his niche—franchise and title law—operates in a low-change regulatory environment. His compliance motion is minimal. He’s already got Practical Law as a baseline and uses AI tools when he needs them. Adding regulatory automation didn’t move the needle. He wasn’t rejecting the product. He was rejecting the premise that his business needed what we were selling.
This was the moment we realized something important about our targeting. We were fishing in the wrong pond.
Regulatory automation makes sense for compliance teams that spend their week tracking cross-jurisdictional changes, managing headline feeds across dozens of regulatory bodies, and responding to constant shifts in enforcement priorities. It makes sense for fintech teams managing multiple states’ lending rules or insurance firms tracking state insurance commissioner guidance. It does not make sense for a general counsel in a stable regulatory vertical that already has tooling in place and a fundamentally lower frequency of critical changes.
The problem is that low-change regulatory environments don’t look obviously different from the outside. We saw six entities across three states and a compliance pain point. We didn’t see the underlying rate of change. We didn’t factor in vertical stability.
What we learned in that call applies across at least two other sub-segments we’ve targeted. Legacy REI operators managing entities across multiple states, for instance, deal with tax compliance and entity formation changes, not regulatory motion. Compliance roles in smaller wealth advisory shops rarely track headline risks the way fintech firms do. The compliance work is real and ongoing, but the change frequency is low enough that existing solutions suffice.
The insight changes how we think about ICP. When we’re selling regulatory automation, the right target isn’t just “compliance professional managing multiple entities.” It’s “compliance professional managing multiple entities in a high-motion regulatory environment.” That’s specific. That’s defensible. That’s worth time.
We’re still validating this in the field. The calls we’ve booked with compliance teams managing cross-jurisdictional risks—asset servicing, financial services, insurance operations—show higher product resonance. The ones in stable verticals show interest in the conversation but quick disqualification once they assess their own regulatory velocity.
If you’re selling compliance automation, audit your pipeline against this lens. Strip out the segments where regulatory change is genuinely low frequency, even if the compliance work itself is real and annoying. You’re not losing deals to competition. You’re losing them because the problem you solve isn’t acute enough in those verticals.
Some pain points aren’t automation opportunities. They’re just the cost of doing business in a stable environment.