Salesforce implementation with governance built-in
A Salesforce implementation by CRM Force starts with agreements on who decides and who may change what, and only then with building. That gives you a Salesforce org your own team understands and can maintain.
- Work out the cost up front
- One experienced consultant per project
- Sales Cloud and Service Cloud
Salesforce implementation at a glance
Updated on
- What it is
- Setting up Salesforce around your own process. There's nothing to install: Salesforce runs in the cloud.
- Who it's for
- SMEs choosing Sales Cloud, Service Cloud or both. If you're still deciding between Salesforce and your own CRM, read how to choose between the two first.
- What it costs
- That depends on your clouds, the number of users, your preparation and the number of integrations. The calculator on this page gives you a price range up front.
- How long it takes
- Agreed after the intro call. The pace mostly depends on how quickly decisions get made.
- Licenses
- Paid separately to Salesforce, per user per month.
Does this sound like your sales process?
- Requests come in through the website, forms, campaigns and the phone, and you want every one of them followed up the same way.
- You want to see where a customer stands, from request to contract.
- You already work in Salesforce, but the calculations and custom objects from back then no longer fit the way you sell now.
- Changing a price or a pricing tier only works with a developer involved.
How CRM Force sets up Salesforce
Building only starts after the agreements and the design, so the project doesn't change direction halfway.
1. Agreements on who decides
We record who owns Salesforce, who reviews changes and how decisions get made.
2. Data model and processes
We decide which data you record and how a lead, a customer question or an order moves through your business.
3. Building, Flow first
Automation goes into Salesforce Flow, which your own admin can read. Apex only where Flow falls short.
4. Handing over to your team
Your admins and key users learn during the work what has been built, so they can carry on afterwards.
After go-live you also keep a blueprint
A Salesforce implementation involves decisions you can't trace back from the system a year later: why a field is there, which system leads. CRM Force records those decisions along the way in a blueprint.
- Which systems there are and what data flows between them.
- How a record is created, from sign-up to placement.
- Which automation drives the process, and why.
How much does a Salesforce implementation cost?
You can work out what a Salesforce implementation with CRM Force costs in the calculator below. You answer a few questions about your organization and get a price range. These things make the price higher or lower:
- Sales Cloud, Service Cloud or both;
- the number of users;
- several legal entities in one Salesforce org;
- how clearly defined your data model is and whether your processes are documented;
- how willing your people are to change the way they work;
- how many of your own processes need to be automated;
- the number of integrations with other systems.
A clearly defined data model, documented processes and a team that's willing to change bring the result down. That result is a first estimate; after the intro call you get an estimate for your situation. Licenses are paid separately to Salesforce.
Investment estimate for your Salesforce implementation
With this calculator you get a price range for a Salesforce implementation with Sales Cloud and Service Cloud in a few steps, based on the choices you make.
Step 1 of 7
Do you want a realistic estimate?
The calculator works with what a Salesforce implementation costs in practice, even when that turns out higher than you hoped.
Frequently asked questions about a Salesforce implementation
What's the difference between a Salesforce installation and an implementation?
You don't install Salesforce: it runs in the cloud. Implementing means setting it up, so data, permissions, automation and reports match the way your business works.
Do we have to roll out Sales Cloud and Service Cloud at the same time?
No. You can start with one cloud and add the second later. See Sales Cloud implementation and Service Cloud implementation.
Can you fix an implementation that didn't go well?
Yes. CRM Force first maps what's there and what isn't being used, and then you decide what stays. More on the Salesforce optimization page.
Can we connect Salesforce to our other systems?
Yes. Each integration counts separately in the calculator, because the price depends on what the other system allows and how clean the data is. More on connecting Salesforce.
Is training part of the implementation?
The handover to your admins and key users is part of it. For all your users there's tailored Salesforce training.
Book an intro call about your implementation
Tell us briefly which clouds you want to use, for how many people, and what's already in place. Pascal van de Braak will get in touch to schedule a time.
Not sure Salesforce is the right fit?
A Salesforce implementation pays off when your organization needs the heavy standard features, faces requirements from outside, has people in-house who want to manage the system, or already runs on Salesforce. If your process is unusual and the features you need are light, a custom-built CRM often fits better. CRM Force does both; the trade-off is on Salesforce or your own CRM.
Why does a Salesforce implementation get stuck?
A Salesforce implementation gets stuck when nobody owns it, decisions are slow and the company's own people don't understand what's being built. Then building starts before it's clear what it should do, and the project changes direction halfway through.
The result is called technical debt: automations nobody understands anymore, flows that get in each other's way and a Salesforce org that gets harder to change with every edit. That's why CRM Force records who decides at the start, and builds automation in Flow that your own admin can read.
How long does a Salesforce implementation take?
CRM Force agrees on the schedule for a Salesforce implementation with you after the intro call. A fixed number of weeks can't be given up front, because the pace mostly depends on how quickly decisions get made on your side, how clean your data is and how many systems need to be connected.
How do you choose a Salesforce implementation partner?
Choose a Salesforce implementation partner in the Netherlands on who does the work and what you're left with after go-live, more than on the size of the firm. That's why you should ask these five questions in the first conversation, before you compare quotes:
- Who will you talk to during the project, and does that person also make the decisions?
- How many people work on it, and why?
- Can you read back the decisions after go-live?
- Who manages the org afterwards, and can your own team learn to?
- Which customers has the partner worked for, and can you see that work?
CRM Force works with one experienced functional consultant per Salesforce implementation, and a second when the work calls for it. Pascal van de Braak is your single point of contact, backed by a steady group of specialists. That's how CRM Force rebuilt the sales process in Salesforce for Lease-e and LeaseKlik, from lead to opportunity, quote and contract. Read the Lease-e and LeaseKlik customer story.
Which Salesforce products can you have implemented?
CRM Force implements Sales Cloud and Service Cloud; those are also what the calculator on this page works with. Salesforce also has products for portals, marketing, data and analytics. Whether you need them, and whether CRM Force is the right party for them, is something you'll hear in the intro call.
- Sales Cloud
- The CRM for the sales team: leads, opportunities, quotes and forecast.
- Service Cloud
- Customer questions and service processes in cases, across several channels.
- Experience Cloud
- A portal where customers or partners log in to data from Salesforce.
- Marketing Cloud
- Emails and customer journeys at scale.
- Data Cloud
- Customer data from several systems brought together into one view per customer.
- CRM Analytics
- Analysis and dashboards beyond the standard reports.
- Industry clouds
- Extensions for one sector, such as Manufacturing Cloud for manufacturers and Education Cloud for education.
What can you do yourself to lower the cost?
You lower the cost of a Salesforce implementation mostly by preparing before the start. The calculator reflects this: a clearly defined data model and documented processes bring the result down. Four things you can do yourself:
- Data model. Write down which data you record and how customers, contacts and orders relate to each other.
- Processes. Describe how things work now and what you want to change.
- Goals. Know what you want to achieve, so the project doesn't change direction halfway.
- Your team. People who already know the basics of Salesforce take over the new org faster.
How CRM Force builds: Flow first, Apex where needed
CRM Force builds automation in Salesforce Flow wherever possible, because Flow is visual and your own admin can read and change it without writing code. How that works in practice is explained in the article on automating with Salesforce Flow.
Apex, the programming language of Salesforce, is something CRM Force only uses when Flow falls short: for heavy calculations, integrations or logic Flow can't handle. Settings that change often, such as tiers and thresholds, go into Custom Metadata, so you can adjust them without code. Also read when to choose Apex and when Flow.
Updated on
