SMB CRM in 2026: what a 30-person team actually needs

The 20-person line is where CRM buying changes shape

Almost everything published on this blog about buying a CRM stops at about twenty people, and that is not an accident. It is roughly where our own product stops being the right answer. But a large share of the people searching for CRM advice are not five-person teams. They are thirty-person teams, fifty-person teams, a hundred-person company with three business units and a partner channel, and they are asking a question we have never answered here: what does a CRM need to do once you are past the point where one person can hold it in their head?

The visible cost of that question is per-seat pricing, and it multiplies faster than most teams expect. The headline per-user number on a vendor pricing page is the least useful figure on it, because the number that decides the purchase is the total, and the total is a function of one variable: how many seats actually need to be licensed.

Read the last column again, using the seat prices checked on 3 November 2026. For the same hundred seats, the gap between the cheapest line and the most expensive is $8,000 a month, or roughly $96,000 a year. At thirty seats the same spread is $2,400 a month. At that size the vendor choice stops being a feature decision and becomes a decision about admin tax, which is the hours per week somebody spends keeping the system honest and correctly configured.

That last point deserves more attention than it usually gets, because the seat price is the only number vendors quote and the only number most buyers compare. The seat bill is the part of the cost you can forecast. The admin tax is the part you cannot, and it is the part that gets discovered two months in, by which point the CRM is already wired into everyone else's workflow.

What breaks first above 20 people

The bill is what you can plan for. The operational strain is what actually arrives, and it arrives in a predictable order. Here is roughly what stops working, in the order teams hit it.

• —Territory and account assignment. At five reps you round by hand. At thirty, one person leaving a region strands every deal attached to it, and you need assignment rules and permissions nobody configured because nobody needed them.
• —Reporting that survives contact with the business. One dashboard served five people comfortably. At thirty it has to roll up by segment, territory and team, and the dashboard becomes the thing you argue about in the forecast meeting rather than the thing that settles it.
• —Data hygiene as a system problem. At five people a duplicate contact is a small embarrassment. At thirty it distorts every forecast you run, and somebody has to own the merge rules and the field list.
• —Onboarding as a repeatable process. At thirty people, hiring two reps a month means the CRM has to onboard people, not merely hold them. We covered that separately in our onboarding playbook.
• —The spreadsheet sitting next to the CRM. Five people can reconcile a sheet by hand. At thirty the sheet is where the real pipeline goes to hide, and the CRM ends up reporting a version of reality that nobody is working.

None of that requires an enterprise platform. It requires a CRM that has teams and permissions that are actually configured, a pipeline that matches how your team really sells rather than how a template says it sells, and automations doing the work that would otherwise turn into admin. What it does require is a budget line for the admin hours, which vendors do not quote and most buyers never cost.

When flat pricing stops being an advantage

There is a third option on the table, and this blog has a bias towards it, so it is worth being precise about where that bias stops being useful. Flat per-company pricing, with no per-seat meter and every feature on every plan, is genuinely better for most teams up to about twenty people. It is worse in two specific ways as you grow, and pretending otherwise would be dishonest.

First, the shape of the product. A flat-price vendor builds for a band. If your band is five to twenty people, the product will have exactly the features that band needs and few of the ones you are about to need. You will not get territory hierarchy, sandbox environments, custom objects at scale, field-level audit trails, or partner visibility, because nobody inside that band asks for them. The absence is not a bug, it is the design.

Second, the incentives, which are structural rather than personal. A per-seat vendor earns more when your company grows. A flat-price vendor does not. That is not a criticism of any particular company, it is how the two models work, and it is fair to ask what a flat-price product is optimised for when it carries no per-seat upside. In practice the answer is the small-team default: fewer fields per record, less configuration, simpler permissions, and the working assumption that one person owns the data.

So the question for a thirty-person team is not flat versus per-seat on price. It is whether the features your band needs are the features the product was built for. We are on the record about where our own answer ends. Our pricing is flat because our product is built for teams of two to twenty people, and past that we would rather you read the Salesforce comparison and the monday comparison and make the call on the merits.

The vendors at the cheaper end of that table are not obviously better products. Zoho CRMPlus from $20 per user and Salesforce Starter Suite at $25 per user are capable, widely used platforms with real depth. What they are is priced and shaped for a company that grows by adding seats. That is a different bet, not a better one. If you have got that far and you are still weighing products side by side, our Freshsales comparison and the Pipedrive comparison are worth reading too, because the shapes differ more than the price tags suggest.

Honest caveats: when an SMB team should buy something else

There are four cases where the honest answer is that a thirty-person team should buy something other than what we sell, or other than any SMB-shaped CRM at all.

• —You need governance, not seats. Multiple business units, territories that deliberately overlap, a partner or reseller channel you cannot see into, and audit requirements mean you need an enterprise tier. We cannot serve that, and we would rather say so than take the money and disappoint you in month four.
• —You need to bill people differently. If you charge business units separately, pass costs through to clients, or need per-seat entitlements to match what each team actually bought, flat pricing does not fit how you bill. Price the per-seat model here and it does.
• —Your real problem is the funnel, not the software. If there is no territory model, no forecast discipline and no owner for the data, a CRM will not create any of them. Buying one at thirty people makes the failure harder to see, because you end up with dashboards that show a pipeline nobody believes.
• —Your revenue is not tied to tracked opportunities. If you bill by hour or by project, a CRM is a contact list with extra steps, and the real cost of your sales tool stack is better spent on something that moves the work.

What to actually do at thirty people

If you are the person doing this, the order of operations matters more than the vendor. Four steps, in this order.

• —Run the seat math on your real headcount and your real billing cadence. Work out what each option costs at thirty, fifty and a hundred seats, then put two numbers side by side: the vendor bill and the admin hours it will consume. The cost calculator does the first half of that in a minute.
• —Count admins separately from sellers. Two people who live inside the CRM keeping it clean are a cost line, not overhead to be absorbed quietly. Vendors will not model them for you.
• —Decide the permission model before the territory model. Permissions are what you cannot retrofit cheaply at thirty people; territories can be redrawn in an afternoon.
• —Price the migration once, properly. The second month of a new CRM is always worse than the first, and we have written about what that transition actually involves in our pricing landscape for sales-led teams.

Then pick your band. If your team will sit at thirty people for the next two years and the work is selling, a flat-price product built for that band will usually serve you better than a per-seat platform you are paying to under-use. If your team will be a hundred people within a year, buy for the hundred. At a hundred seats the price gap is the smallest part of what changes, because the features you need have changed completely.

One last number, because it is the one that settles most of these. Take your vendor bill per head and set it against what one seller costs you in a year. The month those two numbers cross, the CRM conversation stops being about features and becomes a question about whether your margin can carry the tooling. That is the month to read what affordable actually means for a small team and compare it against what you have, rather than the month somebody in admin first complains.