Salesforce is excellent enterprise infrastructure. It is also one of the most expensive ways for a 10-person team to store contacts and move deals through a few stages. This teardown walks the sticker, the loaded bill, and the labor — then the owned alternative we actually ship.
If you only remember one number from Autonode’s solar teardown: a 12-person installer was paying ~$1,100/mo for eight Salesforce seats and using the product as a contact list and install-date log. That pattern is not rare. It is the default outcome when a small team buys a platform sized for a different company.
Before you re-negotiate seats, run the free Stack Sprawl Index and skim the tools hub. Sprawl score first; CRM decision second.
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.
03 · The cost that is not on Salesforce’s PDF
Middleware labor
The CRM only works if the rest of the stack feeds it. On a typical rented marketing stack that means:
- Website form → email notification → someone types into Salesforce
- Mail tool list ≠ CRM contacts
- Calendar / Zap layer that breaks quietly
That is the same “office manager as middleware” pattern as the solar operating system case study and the Webflow + Zapier + HubSpot cost piece. Salesforce becomes the expensive filing cabinet at the end of a brittle chain.
Score that chain with the Stack Sprawl Index. If Support + Manual dominate SaaS on the result screen, seats are not your real problem — ownership of the pipeline is.
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 |
A full framework lives in How to audit your SaaS stack before rebuilding. Do not rip out Salesforce mid-quarter without finishing inventory and data-flow mapping first.
05 · What we put in its place
An owned pipeline, not a cheaper Salesforce
The replacement is not “HubSpot instead.” That often recreates seat and contact-tier math. The replacement we build:
- Stages that match how you sell and deliver (not a generic enterprise object model)
- Site forms that write straight into the CRM — no email-and-retype
- Email next to the customer record
- You own the schema and the data
You pay for the build once; you do not rent the filing cabinet forever. For teams already on a sprawling stack, start at /tools, run the calculator, then bring the Salesforce line items to an audit.
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.