Salesforce implementation costs: the five factors that decide the number

Salesforce implementation cost is decided by five things: the editions you licence, how much you customise, how many systems you integrate, the size and shape of your organisation, and the state of your data. Everything else is a consequence of those five.

The licence is the part everyone looks at, because Salesforce publishes it. The implementation is where budgets actually move, and it moves for reasons that are knowable in advance. Ignyto scopes every engagement as user stories with effort against each one, so the number is assembled from the work rather than presented as a package price — and so change is a conversation about numbers rather than goodwill.

1. Salesforce edition

Edition sets the ceiling on what you can configure without custom development. Professional Edition covers straightforward sales and service processes. Enterprise Edition adds the automation, record types, API access and sharing controls most organisations need within a year or two of going live. Choosing Professional to save on licence cost, then paying for workarounds the edition cannot support, is the most common false economy in Salesforce budgeting.

• Count the automation and API requirements before choosing the edition, not after.
• Buy licences for the people who will use the system in the first month. Additional licences can be added quickly.
• Model the cost across three years — edition upgrades mid-contract are more expensive than starting correctly.

2. Customisation

Standard Salesforce functionality is free of implementation cost beyond configuration. Custom objects, Apex, Lightning Web Components and complex flows all carry build and, more importantly, maintenance cost — every custom element is something that must be tested against three Salesforce releases a year.

The practical test is whether the custom build changes a business outcome or only preserves a habit. Ignyto will recommend the standard product where it does the job, and say so before you buy a licence or fund a build.

3. Integration

Integration is usually the largest single variable, and it is the one most often missing from a quote. A CRM is judged on whether the order reaches the ERP, whether the invoice reconciles, and whether the customer record matches in both systems at four in the afternoon.

• A supported connector or AppExchange package — Breadwinner for Xero, for example — is the cheapest route where volumes allow it.
• Native APIs and Platform Events cost more to build but avoid middleware licensing.
• MuleSoft is warranted where the systems will keep changing, because the second integration then costs less than the first.

Ask any partner how many integrations are in scope, who builds them, and what the testing effort is. Integration defects surface after go-live, when they are most expensive.

4. Size of the organisation

User numbers affect licence cost linearly and implementation cost non-linearly. More users means more roles, more sharing rules, more training cohorts and more change management. A fifty-user rollout across three departments is a bigger implementation than a fifty-user rollout in one team.

Multi-entity and multi-country organisations add data residency, currency, tax and language considerations that belong in the scope from the start rather than in a phase two.

5. Data

Data is the cost nobody forecasts. Migration effort depends on the number of source systems, the quality of the records in them, and how many duplicates have accumulated. Profiling, cleansing and validation before anything moves is cheaper than fixing a migrated mess, and it is the difference between a platform people trust and one they work around.

• Profile the data before scoping the migration — the record count matters less than the field completeness.
• Decide what not to migrate. Historic records nobody uses cost money to move and slow reporting afterwards.
• Budget for a second pass. First migrations reveal problems the profiling did not.

Work with an experienced Salesforce partner

The cheapest quote is rarely the cheapest project. A partner who has delivered the same problem before will scope the integration and data effort accurately, and will tell you where the return is not there. Ignyto is a Salesforce Summit partner with 115 certifications in-house and over 1,000 projects delivered since 2016, working from London, Manchester and Dublin — and every engagement is scoped against a measurable return, baselined before the build so the change can be evidenced afterwards.

Common questions

Ignyto delivers Salesforce Sales Cloud for organisations across the UK and Ireland, as a Salesforce Summit partner with 115 certifications.