Salesforce Consulting and Implementation
Salesforce consulting and implementation across Sales Cloud, Service Cloud, CPQ, Revenue Cloud Advanced, Field Service, Financial Services Cloud, Manufacturing Cloud, Data Cloud and Agentforce. We map the process first, configure standard features before custom code, and document what we build so your team can run it.
One customer platform, configured around how you sell and serve
Salesforce is a set of clouds on one platform and one data model. Most organisations license two or three of them and use a fraction of each. The value comes from connecting them properly: a quote that becomes an order, an order that becomes a service case, a case that dispatches a field engineer, with one customer record underneath all of it.
Most Salesforce orgs that underperform were not short of features. They were configured line by line from a requirements list, with custom code where a standard feature would have done, and nobody wrote down why. Two years later every release is a risk and nobody wants to touch the automation.
OMAV starts with the process, configures standard capability first, and records every customisation with the reason it exists. Where a requirement needs a different product, an AppExchange package or a change in how your team works, we say so before you buy licences.
The Salesforce clouds we implement and support
Nine products on one platform. Most engagements combine two or three of them, scoped as a single piece of work.
Sales Cloud
Leads, accounts, opportunities and forecasts configured around your real sales stages. Territory and pipeline rules, approval processes, Outlook and Gmail integration, and reports that sales and finance both accept.
Service Cloud
Case management, omni-channel routing, entitlements and SLAs, knowledge base and self-service portal. Email, web, chat and WhatsApp routed to the right queue, with escalation rules your support leads can maintain themselves.
Salesforce CPQ
Product bundles, price rules, discount schedules, approvals and quote templates for teams already running CPQ. Salesforce no longer sells CPQ to new customers, so we also advise whether an existing org should be cleaned up or moved to Revenue Cloud Advanced.
Revenue Cloud Advanced (RCA)
Quote-to-cash on the core platform: product catalogue, pricing, configuration, quotes, orders, contracts and billing. Implemented for new buyers, and as the migration target for existing CPQ and Billing orgs.
Field Service (FSL)
Work orders, service appointments, scheduling and optimisation, technician skills and capacity, the mobile app with offline access, and van stock. Linked to Service Cloud cases so the customer history travels with the job.
Financial Services Cloud (FSC)
Household and relationship models, client onboarding, financial accounts, referrals and compliant data sharing for banks, lenders, wealth managers and insurers. Built on the industry data model rather than rebuilt in custom objects.
Manufacturing Cloud
Sales agreements, account-based forecasting and rebate management, so commercial teams see run-rate business next to new opportunities. Integrated with ERP order and production data, including SAP, so forecasts match what the plant can build.
Data Cloud (Data 360)
Customer data from Salesforce, ERP, web and marketing systems unified into one profile, with identity resolution, calculated insights and segments. It is also the data layer Agentforce grounds its answers on.
Agentforce
AI agents for sales, service and internal teams, built with defined topics, actions and guardrails. Grounded in your Salesforce and Data Cloud records, tested on real past conversations, with a clear hand-off to a person.
How a Salesforce engagement runs
Map the process
Workshops with the people who sell, quote and serve, documenting how the process runs today and the decisions it depends on.
Design the org
Data model, security model, clouds and licences chosen against the fit-gap, with every customisation justified in writing.
Configure and build
Standard features first, then Flow, then Apex only where a requirement cannot be met declaratively. ERP integrations built and tested in a sandbox.
Migrate and train
Data cleansed, de-duplicated and loaded with reconciled record counts, then role-based training on your own records.
Go live and support
Cutover, hypercare through the first sales and service cycle, then support under a defined severity model.
Which Salesforce product fits the problem
A starting point. The right combination depends on how your revenue and service processes connect.
| If the problem is | Start with | Usually paired with |
|---|---|---|
| Pipeline and forecasts nobody trusts | Sales Cloud | Data Cloud |
| Slow or inconsistent customer support | Service Cloud | Agentforce |
| Complex quotes and discount approvals | Revenue Cloud Advanced | Sales Cloud |
| An existing CPQ org that is hard to change | CPQ clean-up or RCA migration | Revenue Cloud Advanced |
| Engineers scheduled by phone and spreadsheet | Field Service | Service Cloud |
| Client relationships split across advisers and systems | Financial Services Cloud | Data Cloud |
| Forecasts that ignore run-rate orders | Manufacturing Cloud | Sales Cloud and SAP integration |
| Customer data scattered across systems | Data Cloud | Agentforce |
| Repetitive enquiries tying up the team | Agentforce | Service Cloud |
Where Salesforce is the wrong answer
Salesforce is a CRM and customer platform, not an ERP. Finance, inventory valuation, production planning and statutory accounting belong in a system such as SAP S/4HANA or Business One, with Salesforce integrated to it. Rebuilding those processes in custom objects is expensive to maintain and hard to audit.
Agentforce and Data Cloud are priced on consumption. Before recommending either, we estimate the usage your volumes will generate, because a pilot that works can still be a cost surprise at full scale. Where clean customer data does not exist yet, the first job is fixing the data, not deploying an agent.
- Map the process before configuring the org.
- Standard features first, Flow second, Apex only where nothing else will do.
- New quote-to-cash buyers should start on Revenue Cloud Advanced, not CPQ.
- Agentforce is only as reliable as the data it is grounded in.
- Salesforce runs the customer side. Keep finance and production in your ERP.
Questions buyers ask about this
Should we buy Salesforce CPQ or Revenue Cloud Advanced?
If you are new to Salesforce quoting, Revenue Cloud Advanced. Salesforce stopped selling CPQ to new customers and new feature work now goes into Revenue Cloud Advanced. If you already run CPQ, it remains supported, so the decision is about timing. We review the org, estimate the migration effort, and tell you whether a clean-up now or a move to RCA is the better use of budget.
Can Salesforce integrate with SAP?
Yes. Accounts, products, prices, orders, invoices and delivery status are commonly synchronised between Salesforce and SAP S/4HANA or SAP Business One, through middleware such as MuleSoft or SAP Integration Suite, or through direct APIs. Because OMAV works on both SAP and Salesforce, the integration is designed from both ends rather than handed between two vendors.
Is Data Cloud the same as Data 360?
Yes. Salesforce renamed Data Cloud to Data 360 in 2025. It unifies records from Salesforce and other systems into one profile per customer, and makes that data available to flows, segments, analytics and Agentforce.
How do you make Agentforce safe to put in front of customers?
By narrowing what each agent can do. Every agent gets defined topics, specific actions and clear rules for handing over to a person. We test it against a set of real past conversations before launch and review transcripts afterwards, so changes are based on what customers actually asked.
Can you take over an existing Salesforce org?
Yes. We start with an org health check covering security, data quality, automation, technical debt and licence use, then agree a support scope with response targets. Undocumented customisations are documented as we find them.
How long does a Salesforce implementation take?
A single cloud such as Sales Cloud or Service Cloud for one business unit typically takes six to twelve weeks. Multi-cloud programmes that include Field Service, Revenue Cloud Advanced or an ERP integration usually run in phases of three to six months. Data quality and integration scope move the timeline more than configuration does.
Marked up as FAQPage structured data, matching the visible text exactly.
Still not sure this is the right service?
Answer four questions and we will tell you which one fits — or that none of them do.
Tell us what you are trying to fix.
A short conversation about the objective, the constraints and the timing. If we are not the right fit, we will say so.