Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
The decision is rarely reversible cheaply. A Salesforce programme runs for years, and switching consultant halfway means paying a new team to learn what the old one built. Choose on the pitch and you find out in the second phase whether the people, the method and the accountability were real. By then the budget is committed.
Start with the work you need done
Choosing a Salesforce consultant starts with the job you need done, because the label on the business card rarely tells you which job a consultant does. A functional consultant translates your processes into configuration. A technical consultant or architect designs data models and integrations. A developer writes the code the platform cannot do out of the box. Most programmes need all three, in proportions that change as the work moves from design to build.
Where most of the work is custom code, the questions shift towards engineering practice, which our piece on choosing a Salesforce development company covers. Where the work is mostly configuration and change, a functional team with strong process knowledge matters more than raw development capacity.
Specialism matters as much as size
Sales Cloud, Service Cloud, Marketing Cloud and Commerce Cloud (Agentforce Commerce) are different disciplines with different specialists. A partner strong in one is not automatically strong in the others. Ask which clouds the proposed team has delivered together, not which clouds the company lists on its website.
Partners come in several shapes, from global integrators to regional specialists and independent consultants. Each shape has a place, and the types of Salesforce implementation partners differ mostly in who carries the risk.
Check who actually does the work
The team that sells the project is often not the team that builds it. Ask for the names of the people who will work on your project, their roles and how long they stay. Rotation is expensive. Every new face costs you weeks of context and reopens decisions you thought were closed.
We assign fixed teams from start to finish at FORWARD, with no rotations. That choice has a cost: a person on your project is not free for the next one. We also turn down projects that are not the right fit, and we have done so.
Ask references the uncomfortable questions
References tell you more than case studies, provided you ask the right things. A reference will always say the project went well. Ask instead what went wrong, how the partner told them and what it cost to fix. The answer shows whether mistakes get owned or explained away.
Time and budget are the other honest test. Carrefour gave us their internal award for the only project delivered on time and on budget. Whichever partner you consider, ask their references the same question: did it land on time and on budget, and if not, who absorbed the difference?
