Quick answer
Published ranges for a Salesforce implementation run from about $10K for a small, services-only project to $500K or more for an enterprise programme. The sources disagree widely, so the honest answer is that it depends on scope: the processes you automate, the systems you connect, the state of your data and how many Salesforce clouds you roll out.
Published implementation ranges
These are the ranges two published guides give for a Salesforce implementation, by company or project size. They are third-party estimates, not Techila prices.
| Item | Range | Source | Caveat |
|---|---|---|---|
| Small project, US and EU partner | $50K to $100K | Savvycom: Salesforce implementation cost guideVendor · Updated | Vendor estimate with no stated method. |
| Medium project, US and EU partner | $100K to $200K | Savvycom: Salesforce implementation cost guideVendor · Updated | Vendor estimate with no stated method. |
| Large project, US and EU partner | $200K to $500K | Savvycom: Salesforce implementation cost guideVendor · Updated | Vendor estimate with no stated method. |
| Small business, services only | $10K to $30K | Codleo: Salesforce implementation costPartner · Dated | Partner estimate. The same source's FAQ widens the small-business range to $10K to $200K. |
| Mid-market, services only | $40K to $150K | Codleo: Salesforce implementation costPartner · Dated | Partner estimate with no stated method. |
| Enterprise, services only | $150K to $500K+ | Codleo: Salesforce implementation costPartner · Dated | Partner estimate with no stated method. |
Why the sources disagree
At first glance the two sources look contradictory: one puts a small project at $10K to $30K and the other at $50K to $100K. Most of the gap comes from three differences.
What is included
One source quotes services only. A figure that also covers licences, training or post-launch support will be higher for the same project.
Region
The higher ranges are for US and EU partners. Delivery from other regions, or a blended onshore and offshore team, changes the day rates behind the total.
Project type
“Small” can mean a single Sales Cloud set-up for a few users or a focused rollout for a large company. The labels are not defined the same way.
Sources can also disagree with themselves: the same partner guide that gives $10K to $30K for a small business widens that range to $10K to $200K in its FAQ. Use the ranges to sense-check a budget, not to set one.
What drives the cost
Whatever the starting range, these are the factors that move a quote up or down. When you compare quotes, check how each partner has assumed each one.
Business processes
The number of processes you want in Salesforce, and how far they differ from standard behaviour, sets the size of the design and configuration work. Adopting standard processes is cheaper than reproducing every existing workaround.
Integrations
Each connected system (ERP, billing, marketing tools, data warehouses) needs mapping, build, testing and monitoring. Older systems without modern APIs, or integrations that must run in real time, cost more.
Customisation
Configuration with standard tools is faster to build and cheaper to maintain than custom code. Custom components, Apex and complex automation add build and testing effort, and ongoing maintenance.
Data migration and data quality
Moving records from old systems means cleansing, de-duplicating, mapping and validating them. Poor-quality data can add a lot of unplanned effort, so assess it before you fix the budget.
Number of clouds
A Sales Cloud project is smaller than one that also covers Service Cloud, Marketing Cloud, Experience Cloud or an industry cloud. Each cloud adds design, build and training work, and the joins between them add more.
Compliance
Regulated industries such as healthcare and financial services add security design, audit requirements and extra testing.
Timeline and rollout scope
A tight deadline means a larger team working in parallel. Rolling out to several regions, business units or languages adds configuration, testing and training for each one.
Licences versus services
An implementation budget has two separate parts. Licences are paid to Salesforce, usually per user per year, and depend on the edition and clouds you choose. Services are paid to the partner who designs and builds the solution. The ranges on this page are about services. For licence prices, use Salesforce's own pricing pages, and for Agentforce read how Agentforce is priced.
Timelines and contingency
Timelines follow the same drivers as cost: a simple CRM set-up takes weeks, while multi-cloud programmes with integrations and data migration take months. Ask each partner for a phased plan with the assumptions behind it, so you can see which decisions on your side affect the schedule.
Set aside a contingency reserve for scope that only becomes clear during the project, such as data issues or a missed integration. Agree with your partner how changes are estimated and approved before the project starts.
How to compare partner quotes
- Check that every quote covers the same scope: processes, clouds, integrations, data migration and users.
- Ask whether licences, training, testing and post-launch support are included or separate.
- Ask for the team mix behind the price: roles, seniority, location and time allocated.
- Check what is fixed and what is estimated, and how change requests are priced.
- Ask how data quality has been assessed, and who does the cleansing.
- Look for assumptions that move risk to you, such as “client provides clean data”.
- Ask for comparable projects you can check, such as published case studies.
Related reading
- Salesforce consulting cost: how consulting is priced and what the published rates are.
- Salesforce developer hourly rates: published US and India rates by seniority.
- Techila case studies and Agentforce use cases: examples of the kind of work these ranges cover.
- Salesforce services: what Techila delivers.
[ Method ]
How these numbers were compiled
The ranges below come from two cost guides: one published by Savvycom, a software vendor, and one by Codleo, a Salesforce partner. Each row shows its source and the date recorded for it. Neither source states how it arrived at its figures, and both have a commercial interest in them.
We show both rather than averaging them, because they measure different things. Salesforce licence prices are not quoted here: edition names and prices differ between sources, so we point you to Salesforce's own pages instead.
[ Evidence ]
Sources
- Savvycom: Salesforce implementation cost guideVendor, updated 13 Oct 2026
- Codleo: Salesforce implementation costPartner, dated 1 Oct 2026
[ FAQ ]
Frequently asked questions
Published ranges run from about $10K for a small, services-only project to $500K or more for an enterprise programme. The sources disagree widely, so treat any single number with care: the real figure depends on your processes, integrations, data and the number of clouds in scope.
Not necessarily. One source labels its ranges as services only; the other gives ranges for US and EU partners. Check what any range or quote includes. Licences are paid to Salesforce separately, so budget for them as their own line and check Salesforce's pricing pages for current figures.
Published ranges assume a typical project. Integrations with older systems, poor-quality data, regulated industries, several clouds or a tight deadline all push the cost up. Ask the partner to show which of these drivers the quote assumes.
No. These are third-party published ranges. Techila quotes each project after a scoping conversation.
[ Next step ]
Get an estimate for your implementation.
Share your processes, systems and timeline, and we will come back with an estimate based on your scope rather than a published average.