Firm Size Does Not Predict Compliance Software Fit. This Does. 

Uncategorized
Firm Size Does Not Predict Compliance Software Fit. This Does. 
Summary

Compliance officers comparing financial services compliance software vendors, whether at a registered investment adviser, broker-dealer, hedge fund, private fund, or wealth manager, usually measure fit in AUM, headcount, or revenue tier. Across more than 450 firms running compliance programs on Skematic, size turns out to be a poor predictor. What predicts fit is the distance between how complex a firm’s obligations are and how much capacity it has to carry them manually. That gap varies enormously across this market, which is why most platforms end up serving one end of it well and the other end poorly.

The question is fair, and the skepticism behind it is earned, because compliance technology has a long history of being designed around one type of firm and marketed to all of them. The more useful question is not which platform serves firms of a given size, but which one is calibrated to the distance between what a compliance program requires and what its team can absorb. 

Why Size Predicts Less Than Expected

A twelve-person registered investment adviser whose compliance officer is also the chief financial officer needs systematic oversight at least as much as a 300-person firm with a five-person compliance team, arguably more, because that person has no slack to absorb the manual work fragmented tooling creates. 

Across the customer base there is no clean size threshold. What recurs instead, at firms that otherwise look nothing alike, is compliance teams of one person or twenty spending a disproportionate share of the week on manual reconciliation that was not reducing risk in proportion to the hours it consumed. 

Growth is what moves a firm along that range, and it moves faster than anyone plans for. Manual processes that function acceptably at fifty employees tend to become unworkable somewhere between one hundred and two hundred, without any policy changing, because the volume of certifications, attestations, and account monitoring climbs faster than a team can process by hand. The recognition usually arrives attached to an SEC examination, a FINRA inquiry, an internal audit, or an accumulation of near-misses. 

Why Most Platforms Serve One End of the Range 

Because the gap looks so different at either end, platforms tend to be built for one version of it, and the vendors firms compare tend to sort the same way. 

The established platforms, including COMPLY, ACA Group, StarCompliance, and MCO, were built during the first wave of RegTech and have grown through a combination of internal development and acquisition. That history produces genuine breadth, and it assumes a compliance team with the capacity to configure and maintain the result. The assumption is reasonable about the firms those platforms were built for, and those firms are generally well served. For a compliance officer who is also the CFO, the configuration weight is the problem rather than the solution, and much of the capability goes unused because nobody has time to operate it. Pricing follows the capability rather than the usage, so a firm running a fraction of what it bought still pays for the whole platform, often alongside implementation fees scaled for an organization with a dedicated compliance department. 

The newer entrants reach a version of the same problem from the other direction. Hadrius and Greenboard both raised venture funding in 2026, both describe their platforms as AI-native, and both are shipping agentic modules and conversational layers quickly. The engineering is strong. Venture funding also rewards visible differentiation, which tends to produce capability faster than compliance teams can absorb it, and a firm that needs dependable certifications, preclearance, and trade surveillance can find itself evaluating features it has no near-term use for. Newer platforms are also earlier in meeting the structural complexity that arrives with a second legal entity, a second code of ethics covering an overlapping population, or an office subject to FCA rules. 

Overbuilt is the word smaller firms tend to use, and it is not only a legacy condition. It occurs at both ends of this market for different reasons: breadth accumulated through acquisition on one side, feature velocity funded by venture capital on the other. Either way it costs a firm twice, once in the subscription and again in the hours spent operating a system built for someone else’s circumstances. Both are rational strategies for the companies pursuing them, and neither is organized around the distance between a firm’s obligations and its capacity to meet them. 

Firms evaluating Skematic are usually comparing it against both groups at once, against COMPLY or ACA on one side and Hadrius or Greenboard on the other. That is the right comparison to run, once the range question is separated from the feature list. 

What Makes the Range Possible 

Covering both ends is an architectural decision, and it has to be made at the beginning. 

Skematic’s founders had seen the problem from both ends before they built anything. Brian Kesselman spent years as a compliance officer doing this work by hand at a firm without a compliance department to absorb it. Charles Steerman was employee #2 at Compliance Science, now COMPLY, where he spent two decades watching which firms the first generation of these systems served well and which ones it did not. The small end is usually the one left out, because it is least profitable to serve and hardest to serve without simplifying the product past the point of usefulness. 

That experience produced a specific design requirement. The engine has to carry the complexity that large, multi-entity programs actually contain, including layered account structures, overlapping codes of ethics, and obligations across more than one regulator. The surface has to stay simple enough that a one-person compliance function can run the program without a configuration specialist or a consultant on retainer. 

Building both at once is harder than building either alone, and it is close to impossible to retrofit. A platform that began as an enterprise product carries its configuration model forward, and a platform that began simple usually has to be rebuilt to handle real complexity. Designing for both from the start required knowing in advance what each end would need, which is the part that comes from having worked at both. 

That range is visible across the customer base. It runs from firms where one person handles compliance alongside the CFO role to firms with twenty-person compliance teams operating under several regulators at once, and it includes consultants and outsourced chief compliance officers who run a dozen client programs from one system rather than moving between whatever tool each client happens to prefer. Those look like three different problems. Structurally they are the same one. 

Measuring Your Own Gap 

How many hours each month does the compliance team spend moving information between systems, chasing submissions, or reconciling records by hand? How much of that work would be hard to reconstruct for an examiner without someone’s memory filling in what the tools did not capture? And what happens to those hours if headcount grows by half over the next two years? That last question is worth asking whether or not growth is planned, because it establishes how much margin the current approach has left. 

If the obligations have already moved past what manual process and scattered tools can reliably carry, the gap is real, and it widens rather than closes on its own. The question after that is not which platform serves firms of your size. It is which one will still fit when the gap changes shape.