What you’ll find in this blog
- Why no two Salesforce implementations should be the same
- The risks of relying on a standard implementation approach
- What experienced Salesforce consultancies do differently
- How a tailored implementation creates long-term value
There isn’t a “perfect” Salesforce implementation
One of the questions we’re asked surprisingly often is whether there’s a best practice for implementing Salesforce.
It’s an understandable question.
If you’re investing in a new platform, you want to know there’s a proven approach that will give you the best chance of success.
The answer is… yes and no.
There are absolutely best practices when it comes to security, governance, user permissions and data structure.
Where things become more complicated is when people assume there’s a standard implementation that works for every organisation.
After delivering hundreds of Salesforce and Certinia projects, we’ve found the opposite is usually true.
The most successful implementations aren’t built around a template.
They’re built around the business.
Every organisation has its own way of working
Two businesses can operate in the same industry, sell similar products and even use the same Salesforce licences, yet still need completely different solutions.
Why?
Because Salesforce isn’t just supporting your sales team.
It’s supporting the way your organisation works.
That includes your customer journey, approval processes, reporting requirements, integrations and the way information flows between departments.
Those things are unique to your business.
Trying to fit them into a generic implementation often creates challenges that don’t become obvious until much later.
Templates aren’t the problem
Let’s be clear.
There’s nothing wrong with using templates.
In fact, they can be a brilliant starting point.
The problem is when they become the finish line.
We’ve seen organisations inherit Salesforce environments that looked perfectly reasonable on paper, but in reality:
- Sales teams were maintaining spreadsheets alongside Salesforce because the system didn’t reflect how they worked.
- Reporting no longer answered the questions leadership wanted to ask.
- Processes had gradually become more complicated as new requirements were bolted on.
- Integrations had been added over time without anyone stepping back to review the bigger picture.
None of those issues were caused by Salesforce.
They happened because the implementation was never fully aligned to the organisation in the first place.
Discovery is where successful implementations begin
When people think about Salesforce implementation, they often imagine configuration.
The fields.
The objects.
The automation.
In reality, the most valuable part of any implementation usually happens before any of that.
Good discovery is about understanding how the business operates.
What works well today?
Where are the frustrations?
Which processes genuinely create value?
Where does information come from and where does it need to go?
Only once those questions have been answered does it make sense to start configuring Salesforce.
That’s why we spend so much time understanding the business before building the technology.
A good implementation should still make sense three years from now
One of the easiest ways to judge an implementation isn’t to look at the day it went live.
It’s to look at it two or three years later.
Has it evolved alongside the business?
Are people still using it consistently?
Has reporting kept pace with changing requirements?
Have integrations been introduced in a structured way?
Can new functionality be added without creating unnecessary complexity?
Those are the questions that determine whether an implementation has really been successful.
That’s also why implementation shouldn’t be viewed as a one-off project.
It should be the beginning of an ongoing relationship with your Salesforce platform.
Where Xenogenix fits in
Every Salesforce consultancy has its own way of working.
Ours starts with understanding the organisation before recommending the solution.
That means looking beyond implementation alone and considering the wider picture, including Salesforce data migration, integrations, optimisation and long-term managed services.
It’s an approach that’s helped us deliver more than 400 successful Salesforce and Certinia projects across a wide range of industries.
Because in our experience, the best Salesforce implementations aren’t the ones that are delivered the fastest.
They’re the ones that continue delivering value long after the project has finished.
Frequently Asked Questions
What is a tailored Salesforce implementation?
A tailored Salesforce implementation is designed around your organisation’s processes, objectives and users rather than relying on a generic deployment approach.
Is a tailored implementation more expensive?
Not necessarily. Investing more time in discovery often reduces rework, improves adoption and creates a platform that’s easier to develop in the future.
How long does a Salesforce implementation take?
Every implementation is different. Timescales depend on the complexity of your processes, data migration requirements, integrations and business objectives.
Why is discovery so important?
Discovery helps ensure Salesforce supports the way your organisation actually operates. Without it, there’s a greater risk of unnecessary complexity, lower adoption and additional work after go-live.