If you've asked two or three Salesforce partners for a quote on what feels like the same project, you've probably seen numbers that don't seem to be describing the same thing. One firm comes back at $8,000. Another comes back at $60,000. Both claim to be quoting "a standard Sales Cloud setup." Neither is necessarily lying — but only one of them has actually scoped the work.
The real cost bands, roughly
Across the market in 2026, the pattern looks something like this: a small team running a basic Sales Cloud setup — one cloud, standard objects, a handful of users — tends to land somewhere between $5,000 and $25,000 with a competent partner. Mid-market projects involving multiple clouds, real integrations, and meaningful data migration usually run $25,000–$75,000. Enterprise rollouts with custom development, multi-department coordination, and compliance requirements can clear $150,000 without much trouble.
The spread isn't random. It tracks almost entirely with four variables: how many users need access, how many Salesforce Clouds are being configured, how much existing data has to move cleanly, and whether the work is integrating with other systems you already run.
Why two "identical" quotes aren't identical
A few patterns show up over and over in quotes that look similar on the surface but aren't:
- Hourly vs. fixed-fee. An hourly quote rewards a slower consultant. A fixed-fee quote — scoped properly — protects you from that incentive entirely. If a quote is hourly with no cap, ask why.
- Blended rates. A "$200/hour" quote sometimes means a partner bills $500/hour and staffs two junior developers at $100/hour each, blended down to look reasonable. Ask who's actually doing the work, not just the average rate.
- What's excluded. Training, documentation, and post-launch support are sometimes priced as "add-ons" after the fact. A quote that doesn't mention a data dictionary, an admin runbook, or user training isn't necessarily cheaper — it's just hiding cost for later.
- No discovery phase. If a partner is proposing a solution before spending real time understanding how your team actually works today, the price they've quoted is a guess, not a scope.
Solo architect vs. team model
A large consulting firm often staffs a project with a solutions architect, a developer, a business analyst, and a project manager — four to six people, each adding coordination overhead that shows up in both timeline and price. A solo, senior architect handling the same project end-to-end frequently delivers faster (weeks rather than months) and at a meaningfully lower cost, simply because there's no handoff tax between roles. The tradeoff is capacity — a solo model has a ceiling on how much custom development it can absorb at once.
What we'd ask, if we were buying
Three questions cut through almost every bad quote: Is this price fixed or hourly, and if hourly, is there a cap? Who specifically is doing the configuration work, and is it the same person I'm talking to now? What deliverables, beyond a working org, do I actually receive — documentation, training, a runbook? A partner who answers all three clearly, without hedging, is usually one worth hiring. A partner who gets vague on any of them is telling you something too.