Salesforce consulting.
So that Salesforce works the way you sell.
Whether you are rolling Salesforce out for the first time or taking over an organisation that has grown unwieldy over the years, we shape it around the way you work rather than around the standard. For over 10 years, with certified colleagues in the team.
First the processes, then the configuration.
Salesforce rarely fails on the technology. It fails because a standard configuration forces the sales team to work differently from the way it sells, or because data from the neighbouring systems is missing and spreadsheets keep being maintained instead. Both are work on the process rather than on the interface.
So we start with the processes: how a lead comes about, who qualifies it, what has to be in a quote, which data comes from which system, and which reports the management really needs. Configuration comes after that, and development only where configuration is not enough.
Salesforce clouds for sales, service, marketing and portals
Which cloud makes sense is decided by the use case and not by the licence model. In most projects the Sales Cloud comes first, because that is where deals are made, and everything else follows as soon as there is a process for it to carry. Where the standard ends we build on the platform and keep the extensions as small as we can, so that a Salesforce release never becomes a risk to your changes.
- Sales Cloud for leads, opportunities, quotes and forecast
- Service Cloud for enquiries, cases and service levels
- Marketing Cloud and Account Engagement for campaigns and lead nurturing
- Experience Cloud for customer, partner and dealer portals
- Salesforce Platform with flows, Apex and Lightning Web Components
A rollout on a clean sheet
We take down the sales and service processes before anything is configured: how a lead comes about, who qualifies it, what has to be in a quote and which data comes from which system. After that come configuration, data migration with cleaning beforehand, the permission and role model, reports and training for the departments.
Clearing up an existing organisation
Often Salesforce has been running for years already and has grown hard to follow. It starts with a review: which fields and automations are really used, where do flows and triggers contradict each other, which reports does the department still trust. Out of that comes an order of work that clears things up without stopping the sales team.
Operation, training and further development
After that we take on operation, or your team does. Because as much as possible sits in configuration and flows and as little as necessary in code, your own organisation can make changes itself. What we did develop is documented and does not live as knowledge with one single person.
What we take on in Salesforce.
From the first look at your processes to daily operation, as a complete rollout or as reinforcement for a team that already runs Salesforce. Whether an interface comes into it at all is decided by your project and not by our portfolio. The unpopular parts belong to it too: cleaning data before the migration, permission and role models, and the question of who is allowed to change things after the project.
Rollout
Process analysis
Migration
Data cleaning
Customising
Flows and automation
Apex and Lightning Web Components
Permission and role models
Reports and dashboards
Interfaces
Training
Operation and support
Licence advice
Salesforce review
Connecting Salesforce to whatever else you run
Some projects are Salesforce projects and nothing else: roll out, configure, develop, done. But as soon as data from other systems is needed in the customer record, the work does not stop at the system boundary. Orders from the ERP, purchases from the shop, articles from the PIM, readings from an app or from devices in the field. Over 100 systems are ready to connect and we build whatever else is needed. That is the difference to a pure Salesforce consultancy: the far side of the interface is our daily work.
Frequently asked questions about Salesforce
Which Salesforce services does ebiscon offer?
The whole stretch: gathering processes, rollout, data migration and data cleaning, configuration and automation with flows, development with Apex and Lightning Web Components, permission and role models, reports and dashboards, training as well as operation and support. Reinforcing a team that already runs Salesforce works just as well.
How much Salesforce experience does ebiscon have?
Over 10 years of Salesforce in real projects, with certified colleagues in the team. On top of that comes the thing that usually holds a CRM project up in practice: the systems on the other side of the interface. ERP, shop and PIM have been daily work at ebiscon since 2011.
Which Salesforce clouds do you work with?
Sales Cloud for leads, opportunities, quotes and forecast, Service Cloud for enquiries, cases and service levels, Marketing Cloud and Account Engagement for campaigns and lead nurturing, Experience Cloud for customer, partner and dealer portals, and the Salesforce Platform where logic of your own is needed. Which of them makes sense is decided by the use case and not by the licence model.
When does Salesforce pay off, and when does it not?
Salesforce pays off when several people work on the same customer, when quotes and forecast have to be traceable and when data from ERP, shop or marketing is needed in the customer record. It does not pay off as a substitute for a decision nobody wants to take. If it stays open who qualifies a lead and what belongs in a quote, even the best CRM only reflects that lack of clarity. For a small team with few deals a year, licence and upkeep often outweigh the benefit. We say that before the project rather than after it.
Salesforce or Microsoft Dynamics 365?
Both are grown up CRM systems, and the choice is rarely settled by a feature list. What usually decides it are the systems around them. A company already deep in Microsoft 365 and Azure has shorter routes with Dynamics. A company that wants sales, service, marketing and partner portals on one platform gets there faster with Salesforce. We are a Microsoft Solutions Partner for Azure and have worked with Salesforce for over 10 years, so we take the decision from the use case rather than from our own portfolio.
What can you connect to Salesforce?
Anything that has an interface or can be given one. Most often ERP, shop and PIM, as well as marketing, payment and shipping services, your own apps and devices in the field. Customers and accounts travel both ways, quotes and orders go from Salesforce into the ERP, purchases from the shop into the customer record. It is built over the ebiscon integration platform with over 100 systems ready to connect or as a purpose built interface.
Do you take on an existing Salesforce organisation?
Yes. That happens more often than a rollout on a clean sheet. It starts with a review: which fields and automations are really used, where do flows and triggers contradict each other, which reports do the departments still trust. Out of that comes an order of work that clears things up without stopping the sales team.
Configuration or development?
As much configuration as possible, as little code as necessary. Everything that can be expressed in flows and settings stays there, because your own organisation can change it afterwards. We develop where the standard ends, and then as little as possible, so that a Salesforce release never becomes a risk to your extensions.
Do you also do Salesforce projects with no integration at all?
Yes, and it is an entirely normal case. Rollout, configuration, flows, development with Apex and Lightning Web Components, the permission and role model, reports, training and operation, without a single interface coming into it. Whether anything gets connected is decided by your project and not by our portfolio. We bring the integration experience along in case it is needed and we do not sell it when it is not.
How long does a Salesforce rollout take?
The scope decides that, not the product. A Sales Cloud for one sales team with usable data and one interface stands within weeks. As soon as several clouds, years of accumulated data and several connected systems come into it, it becomes a project over months that is delivered in stages. So we first cut it down to a version the sales team can really work with and build on from there.
What does a Salesforce project cost?
The price depends on the number of processes, on the state of the data being migrated, on the connected systems and on how much your team takes on itself. Licences come on top and are settled directly with Salesforce. After a conversation about processes and systems you get a quote with a fixed scope.