This teardown is for a 10-person team paying Sales Cloud seats for a contact list and a few stages. By the end you’ll know what the per-user bill, the add-ons, and the implementation actually add up to, and whether you are using the platform or storing names in it.
A 12-person installer in a solar operating system build was paying about $1,100 a month for eight Salesforce seats and using them as a contact list and an install-date log. That is the Salesforce-specific failure: enterprise seat math on workshop usage. Before you re-negotiate seats, run the Stack Sprawl Index.
01 · The sticker
What the pricing page wants you to remember
Salesforce sells per user, per month, billed annually for the “real” rate. Mid-market Sales Cloud editions commonly land in the ~$80–$165+/user/mo band depending on edition and promotions (2025–2026 public list ranges; always check current pricing). Multiply by ten seats and the page already looks serious.
What the page underplays:
- Editions that unlock automation, forecasting, and API limits you may never touch
- Add-ons (inbox, CPQ, marketing adjacency, sandboxes, Premier Support)
- Partner implementation: often a five-figure project before day-one usefulness
- Admin time: someone has to own fields, permissions, reports, and integrations
02 · A 10-seat loaded sketch
Illustrative monthly bill
Exact quotes vary by edition and discount. The point of this table is the shape of the invoice a 10-person team actually feels, not a binding quote.
| Sales Cloud seats × 10Mid-tier list band (~$100–$165/user/mo) | ~$1,000–$1,650 |
| Common add-ons / productsInbox, sandboxes, support tiers, often partial | ~$100–$400+ |
| Amortized implementationPartner project spread over year one | ~$200–$600 |
| Admin / ops labor (internal)0.2–0.5 FTE equivalent keeping fields & integrations alive | ~$800–$2,000+ |
| Loaded monthly (year one sketch) | ~$2,100–$4,650+ |
Even if you cut the labor line to zero on paper (you should not), software alone for ten seats is already a four-figure problem for a team that needed a pipeline, not a platform.
About 15% of the platform surface is what we see small teams actually touch. The rest is editions, sandboxes, and support tiers you still pay to have available.
03 · The cost that is not on Salesforce’s PDF
The labor line, in one sentence
The hours spent retyping form email into Salesforce are middleware, covered in You’re paying for middleware. What is specific here is the seat: you pay per user for a platform whose admin, fields, and permissions are a job of their own.
04 · Keep, consolidate, cut, or rebuild
How we score Salesforce on a small team
| Signal | Lean keep | Lean rebuild |
|---|---|---|
| Heavy use of automation, forecasting, complex sharing | Yes | - |
| Mostly contacts + stages + notes | - | Yes |
| Forms and email still outside the CRM | - | Yes |
| Admin is a part-time job with no product ROI | - | Yes |
| Switching cost is fear, not feature fit | - | Audit hard |
The keep-or-rebuild table above is the Salesforce pass: heavy forecasting and sharing can justify the seats, a contact list cannot. Finish the inventory before you cancel.
05 · What we put in its place
An owned pipeline, not a cheaper Salesforce
The replacement is not a cheaper CRM with the same per-user lease. It is leaving Sales Cloud’s object model, the partner implementation, and the edition you bought for forecasting you do not run. What we put in its place is a pipeline whose stages match how you sell and deliver, with the site form writing the record and the email sitting on it. You own the schema. You do not renew a seat to keep a contact.
Bring the edition, the seat count, and a screenshot of the objects you actually open. Do not cancel mid-quarter. Map what still writes into Salesforce first, using How to audit your SaaS stack before you rebuild.
Conclusion
Expensive infrastructure for a simple job is still expensive
A 10-person team can run a sharp pipeline without enterprise CRM rent. If Salesforce is earning its seats with automation and reporting you rely on daily, keep it, and cut the glue around it. If it is a contact list with a four-figure habit, the Index and a proper audit will say the same thing: own the system that moves the work.