We just booked three demos in a single day. What connected them wasn’t the size of their companies or the revenue they manage. It was the geography they’re fighting.

One contact manages about 200 entities. Another oversees registered agent and UCC filing requirements across multiple states. A third just left his previous role to scale a new venture from scratch. On the surface, three different stories. But each one surfaced the same unspoken pressure: multi-state regulatory fragmentation is the real fintech buying trigger.

We talk about entity count. Daniel Schwartz, a controller at a mid-market firm, is shopping for accounting software because his previous company’s setup no longer fits his new role at a smaller operation running on QuickBooks. But here’s what matters: his pain isn’t that QuickBooks can’t do accounting. His pain is that NetSuite and Business Central are built for companies managing 50+ entities across 10+ states, overkill in feature set and implementation burden for where he sits today. He’s caught between tools built for complexity he doesn’t have yet and tools insufficient for the complexity he will have.

Robert Kim manages approximately 200 entities. He’d been using a hands-off, email-based workflow from vCorp. When we connected, Robert’s immediate question wasn’t about features. It was about whether we could handle the multi-state compliance work as smoothly as his current provider, just at lower cost. That tells us his decision framework is simple: give me the same operational model across 200 entities and 15+ states, but cheaper. The geographic scope is the constraint. The number of entities is just the consequence.

Matt Eager at OTRA Capital confirmed his team has light annual filing needs but is actively unhappy with his current registered agent and UCC filing provider. He’s managing compliance obligations across multiple states and multiple entity structures. He’s not shopping because his provider can’t file. He’s shopping because managing disparate state-specific requirements across a growing portfolio is eating time and creating blind spots. We booked him for a demo specifically to walk through how we handle the state-by-state variance.

The pattern is consistent. Giovani, who recently started his own business after leaving Banyan, was interested in our model but needs 30-60 days to evaluate budget. What drove his interest? He’s scaling from zero. He knows his entity count will grow. He knows his geographic footprint will expand. He’s pre-buying for complexity he’s about to face.

This is different from the narrative we usually hear in fintech selling. We talk about “scaling entities” or “managing compliance at scale.” But what we’re actually seeing is that the real pain point is geographic. Five states is manageable. Thirty-eight states is not without infrastructure. Thirteen entities in one state is a different problem than thirteen entities across thirteen states.

The buying signal isn’t when a company hits a certain entity count. It’s when they realize that geographic scope is going to require a different operational system than what they’re currently using. That realization drives urgency.

For us as sellers, the implication is straightforward. When we dig into a prospect’s compliance footprint, we need to ask about state count before we ask about entity count. A controller managing 50 entities in Delaware looks different from a controller managing 50 entities across all 50 states. One has a filing problem. The other has a systems problem.

That difference is worth three demos.