Disclosure: I work at Conduyt, a CRM with flat pricing.
Most founders budget for a CRM the way they budget for laptops: one more hire, one more unit. That's close enough at five people. It stops working somewhere around the point where the team needs a feature the current plan doesn't have, and the upgrade applies to everyone at once.
This post writes the bill down as a formula, runs it through published list prices I pulled from five vendors' own pricing pages on November 5, 2026, and ends with a short Python script you can point at your own hiring plan. Prices change often, so treat every number below as a snapshot from that day and check the linked page before you use it.
The formula
For a per-seat CRM, the monthly bill at headcount n is roughly:
bill(n) = n × price(tier(n)) + n × per_user_addons + per_org_addons + usage The term that matters is tier(n). The tier isn't really chosen by headcount. It's chosen by the features a team of that size ends up needing, such as automation, permissions, or a sandbox. But since those needs show up as the team grows, in practice the tier follows headcount, and each time it moves, price changes for all n seats, not just the new one.
That makes the cost of one hire at a tier boundary:
step = n × p_new − (n − 1) × p_old That's the new seat at the new price, plus every existing seat's price difference.
Five ways the bill compounds
1. Seat price times users. Every vendor I checked prices this way. Salesforce's FAQ says you pay a monthly fee for each user who needs access. Pipedrive lists every plan per seat per month, HubSpot says paid Sales Hub plans are priced per seat, Close says pricing is based on seats for your team, and Zoho lists each edition per user per month.
2. Tier jumps at user limits. Free and solo plans have hard caps. HubSpot's free plan covers up to 2 users. Zoho CRM's free edition supports up to 3. Close's Solo plan is limited to 1 user, so the second person moves you from $9 to $35 a seat on annual billing (Essentials).
3. Tier jumps at feature limits. These are the bigger steps. On Close, workflows aren't included on Essentials. Automated workflows and the power dialer start at Growth, $99 a seat on annual billing. On Pipedrive, automations and nurturing sequences start at Growth, and group-level permissions appear at Premium. On Zoho, AI agents start at Professional, and the reporting hierarchy that gives managers a team-only view is on Enterprise.
4. Add-ons that scale with users. Salesforce's page says AI can be added to Core and above, and its feature table lists Agentforce for Sales as "available for purchase" without a price, so you'd need a quote. HubSpot's AI agents draw on monthly credits instead: Sales Hub Starter includes 500, Professional 3,000 and Enterprise 5,000, and extra credits are $0.010 each. Close includes AI credits per user in a shared pool that tops out at 10,000 a month on Essentials. Not everything scales with seats, though. Close's call recording add-on is $50 per org per month plus $0.02 a minute, so ask which unit each add-on uses.
5. Annual billing and one-time fees. Salesforce lists Pro Suite, Core, Advanced and Max as billed annually, at $100, $195, $395 and $550 per user per month. Only Starter Suite ($25) shows monthly billing. HubSpot's Professional card shows "Commit annually" even under the monthly payment option, and a required one-time $1,500 onboarding fee ($3,500 on Enterprise). Pipedrive's annual price is one payment per seat per year, $468 on Growth. On Close, annual-plan downgrades only take effect at the end of the term.
One thing I couldn't find was a minimum seat count. None of the five pricing pages I read that day lists one. That doesn't mean your order form won't, so ask.
A worked table: 5, 12, 25 and 50 users
To make the steps visible, I picked a growth path and the tier that matches it at each vendor:
- 5 users: pipeline, email and calling.
- 12 users: automated workflows or sequences (Close Growth, Pipedrive Growth, Zoho Professional).
- 25 users: managers need restricted views or role permissions (Close Scale, Pipedrive Premium, Zoho Enterprise).
- 50 users: sandbox and tighter security (Pipedrive Ultimate; Zoho Enterprise already lists a developer sandbox, and Scale is Close's top self-serve plan).
Matching the tiers to headcount is my assumption. The prices are the annual-billing list prices on each pricing page (Close, Pipedrive, Zoho CRM), per month, before tax and add-ons.
| Users | Close | Pipedrive | Zoho CRM |
|---|---|---|---|
| 5 | Essentials $35 -> $175 | Lite $14 -> $70 | Standard $14 -> $70 |
| 12 | Growth $99 -> $1,188 | Growth $39 -> $468 | Professional $23 -> $276 |
| 25 | Scale $139 -> $3,475 | Premium $59 -> $1,475 | Enterprise $40 -> $1,000 |
| 50 | Scale $139 -> $6,950 | Ultimate $79 -> $3,950 | Enterprise $40 -> $2,000 |
The interesting numbers are the boundary steps, meaning what the one hire who triggers the upgrade adds to the monthly bill:
| Boundary | Close | Pipedrive | Zoho CRM |
|---|---|---|---|
| 11 -> 12 users | $385 -> $1,188 (+$803) | $154 -> $468 (+$314) | $154 -> $276 (+$122) |
| 24 -> 25 users | $2,376 -> $3,475 (+$1,099) | $936 -> $1,475 (+$539) | $552 -> $1,000 (+$448) |
| 49 -> 50 users | +$139 (no tier change) | $2,891 -> $3,950 (+$1,059) | +$40 (no tier change) |
On Close, the twelfth hire adds about 23 times the $35 Essentials seat they would have cost if nothing else changed. That's the step. It never appears in a "price per user" comparison, because a comparison like that only lists the slope.
Monthly billing raises the slope as well. Close Growth is $109, Pipedrive Growth is $49 and Zoho Professional is $35 on monthly plans.
The seats nobody budgets for
The headcount in your hiring plan is the sales team. The headcount on your CRM invoice is everyone who needs a login, and that number is usually larger.
- Viewers. Founders, finance, and the board member who wants the pipeline dashboard. HubSpot offers view-only seats at no extra cost. On the other four pricing pages I didn't see a free viewer tier, so ask before you assume.
- Contractors. An outsourced SDR or a three-month implementation consultant who edits records is a user like any other under a "per user who needs access" definition.
- Operations staff. RevOps, the person who builds reports, support staff who look up account history. These roles show up late and almost never appear in the sales hiring plan.
- AI agents. This is the newest one. HubSpot and Close charge AI through credits. But if your own agent or automation works through a named user login, my reading is that it's a user who needs access like anyone else. Ask the vendor how they classify it before you connect one, not after the invoice arrives.
Add these to the plan before you run the model. They often move you over a tier boundary sooner than hiring does.
Model your own 24 months
The script below takes one headcount per month and prints the month when a per-seat bill first passes a flat quote, and the month when cumulative per-seat spend passes cumulative flat spend. The tiers use Pipedrive's monthly-billing list prices from November 5 as an example. The flat figure is a placeholder, so put in whatever quote you're comparing against.
# (minimum headcount for this tier, price per seat per month) TIERS = [(1, 24), (12, 49), (25, 79), (50, 99)] ADDON_PER_SEAT = 0 # e.g. an AI or dialer add-on priced per user FLAT_MONTHLY = 600 # the flat-priced quote you're comparing against def per_seat_bill(seats): price = max(p for floor, p in TIERS if seats >= floor) return seats * (price + ADDON_PER_SEAT) def compare(headcounts, flat=FLAT_MONTHLY): seat_total = flat_total = 0 first_month = cum_month = None for month, seats in enumerate(headcounts, start=1): bill = per_seat_bill(seats) seat_total += bill flat_total += flat if first_month is None and bill > flat: first_month = month if cum_month is None and seat_total > flat_total: cum_month = month print(f"{month:>2} {seats:>3} seats ${bill:>6,} " f"cum ${seat_total:>7,} vs ${flat_total:>7,}") print("Monthly bill passes flat in month:", first_month) print("Cumulative spend passes flat in month:", cum_month) plan = [5]*3 + [8]*3 + [12]*6 + [18]*6 + [25]*6 compare(plan) With that plan, the per-seat bill passes $600 a month in month 13, at 18 seats on the $49 tier. Cumulative per-seat spend passes cumulative flat spend in month 19, when the team reaches 25 and moves to the $79 tier. For the first year, per-seat is clearly the cheaper option, which is exactly why a first-year comparison can mislead you. Change ADDON_PER_SEAT to see how quickly an AI add-on moves both months earlier.
What to ask before you sign
Get these answers in writing:
- What counts as a seat? Is it every login, every active user, or every license you bought? Are API users, integration users and agents counted?
- Is there a seat minimum, and does it reset to your peak count at renewal?
- How do true-ups work? If you add seats mid-term, are they prorated to the renewal date or billed for a full year from the day you add them?
- Can seats go down mid-term, or only at renewal?
- Which features would force a tier change for the whole account, and can a single team be upgraded on its own?
- What unit is AI priced in: seats, the whole org, or credits? What does an extra unit cost, and do unused credits roll over? HubSpot's don't.
- What one-time fees apply at each tier, such as onboarding or implementation?
- What's the renewal price protection? Is the per-seat price capped at renewal, and does it hold if you renew with fewer seats?
The flat-price alternative
The other way to price a CRM is a fixed monthly fee that doesn't depend on headcount, so bill(n) is a constant and there's no step to plan around. That's not automatically cheaper. A team that stays small can come out ahead on per-seat pricing, and the script above will show it when that's the case. But if your hiring plan crosses a tier boundary within the contract term, it's worth putting a flat quote next to the per-seat one. We make one of those at Conduyt, and our ROI calculator runs the comparison against a team size you enter.
Jordan Tate is VP of Customer Relations at Conduyt, a flat-price CRM for small sales teams. Jordan writes about what CRM pricing and CRM data actually cost teams as they grow.