ebiscon rolls Salesforce out, tidies up orgs that have grown unwieldy, and connects your CRM to ERP, shop and PIM. For over ten years, with certified consultants on the team.
The difference
You know most of this already.
Salesforce rarely fails on the technology. It fails because the standard forces a sales team to work in a way it does not sell in. Or because data from the neighbouring systems is missing, so the spreadsheets stay in use.
- TodayThe number for Monday is built on Friday in a spreadsheet.
- After thatThe number is in the system as soon as the quote is.
- TodayThe price exists in three versions of one price list.
- After thatThe price comes out of the ERP, in one version.
- TodayWhat was promised to the customer sits in a colleague inbox.
- After thatIt hangs on the customer, and sales can see it.
- TodayA quote takes days because somebody collects the data for it.
- After thatA quote comes out of what was recorded long ago.
- TodayService hears about the sale when the customer calls.
- After thatThe case hangs on the order before the customer calls.
Clouds
You do not need all of it.
You need the part that carries the next deal. In most projects that is the Sales Cloud. Everything else follows once there is a process that really needs it.
Salesforce has renamed the product families and now lists them under Agentforce. We name both, because both are still spoken in projects.
Sales Cloud
today Agentforce Sales
Leads, opportunities, quotes, forecast. The place your sales team spends the working day.
Almost every project starts here.
Service Cloud
today Agentforce Service
Enquiries, cases and service levels in one place, visible to everyone who looks after the customer.
Once more than one person decides what happens to an enquiry.
Marketing Cloud
today Agentforce Marketing, in the Marketing Cloud Next Growth and Advanced editions
Campaigns and lead nurturing, in B2B through Account Engagement, formerly Pardot.
Once your sales team qualifies properly.
Experience Cloud
name unchanged
Portals for customers, partners and dealers, without access to the org itself.
Once somebody outside is to see your data.
Field Service
today Agentforce Field Service, formerly Field Service Lightning
Scheduling jobs, dispatching technicians, recording work, hours and spare parts on site, with no connection too.
Once your people work at the customer site rather than at a desk.
Underneath it lies the platform. Where the standard ends we build on with Flows, Apex and Lightning Web Components and keep the extensions small. That way a Salesforce release stays an update instead of turning into a project.
Approach
Four steps, in this order.
Processes first, the system after that. As much configuration as possible, as little code as necessary, so your team can change things later without us.
Processes
How does a lead come about, who qualifies it, what has to be in a quote, which number the management reads on Monday morning. We record that before anyone creates a field.
After that it is written down how your sales team really works.
Configuration
Objects, fields, flows, permissions, reports. We build as much as possible by clicking rather than by coding.
After that your team changes things itself, without waiting for a developer.
Development
Apex, Lightning Web Components, interfaces. Where configuration reaches its limit, and only there.
After that every extension survives the next Salesforce release, because it is small and documented.
Operation
We take it on, or your team does. What we built is written down.
After that your CRM no longer hangs on what one person happens to know.
Services
What we take on in Salesforce.
From the first look at your processes to running the system day to day. As a full rollout or as reinforcement for a team that already runs Salesforce. We do the unpopular parts too. Cleaning data, sorting out permissions, and settling who is allowed to change anything after the project.
- Process discovery and concept
- Rollout on a clean slate
- Review and clean up of existing orgs
- Data migration with cleaning beforehand
- Customising, flows and automation
- Development with Apex and Lightning Web Components
- Permission and role models
- Reports and dashboards
- Interfaces to ERP, PIM, shop and apps
- Training for the departments
- Operation, maintenance and support
- Licence advice
Integration
Connecting Salesforce to everything else you run.
Some projects stay entirely inside Salesforce. As soon as data from other systems is needed in the customer record, our work does not stop at the system boundary. Orders from the ERP, purchases from the shop, articles from the PIM, readings from devices in the field.
Over 100 systems are ready to connect, everything else we build. The far side of the interface is our daily work.
Go to system integrationFrequently 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?
The Sales Cloud for leads, opportunities, quotes and forecast, and almost every project starts there, because that is where the money happens. The Service Cloud pays off once more than one person decides what happens to an enquiry. The Marketing Cloud and Account Engagement show an effect once the sales team qualifies properly, before that they only produce more addresses. The Experience Cloud joins once customers or partners are to see your data themselves. And the Salesforce Platform underneath, where logic of your own is needed. Which of them makes sense is decided by the use case and not by the licence model.
How does a Salesforce project start?
With the processes, not with the system. How does a lead come about, who qualifies it, what has to be in a quote, which number the management reads on Monday morning. We record that before anyone creates a field. After that come the configuration with objects, fields, flows, permissions and reports, the development with Apex and Lightning Web Components where configuration reaches its limit, and finally the operation, which we take on or your team does.
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.
7 more questionsShow fewer
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.