Salesforce is a remarkable platform. It can model almost any business object, automate almost any workflow, and report on almost any data shape. The problem is that the words "almost any" have to be paid for. When the IT steering group looks at a CAFM procurement and asks why we cannot just use Salesforce, the answer needs to be honest about both directions: when the generalist is the right call, and when it absolutely is not.
Why it is tempting
The case for Service Cloud writes itself. There is one vendor relationship instead of two. Identity and access are already sorted. Reporting tooling is shared. Sales, service, and operations live on one data spine. Your IT team already knows the platform. Your existing licence pool may extend to cover the new use case.
On paper, all of that is true. The question is whether the build cost to get from generic Service Cloud to a competent CAFM is smaller than the cost of a specialist that ships with that capability already.
Where it falls short for FM
Service Cloud has cases. CAFM has assets, locations, work orders, planned maintenance schedules, permits, compliance certificates, and contracts. None of those are first-class Salesforce objects. You can model them, but every CAFM deployment built on Service Cloud has to invent them, and each invention is a maintenance burden in perpetuity.
Asset hierarchy is the worst of it. A real estate has assets that contain assets that contain assets, with location relationships that move when buildings are reorganised. CAFM platforms model this natively. Service Cloud needs custom objects, junction objects, lookup chains, and a sharing model that handles tenant separation. By the time it works, it has cost a senior consultant six months.
Permit-to-work is similar. HSG250 expects separation of duties, isolation tracking, hazard identification, and a forensic audit trail. None of these are Service Cloud primitives. You can build them. You will spend a long time doing so. And the result will be a permit system that is less tested than a specialist's, with a smaller user base providing feedback.
Mobile work for engineers is a third gap. Salesforce Field Service exists and is competent, but it is a separate product, separately priced, and built for a different operational model than reactive FM repair work. Most teams end up with a third tool bolted on.
The hidden cost of configuration
Service Cloud licensing is per-user, per-month, and the Service Cloud Enterprise tier sits in the £125 to £150 per user per month range, with Unlimited and Einstein add-ons climbing from there. Multiply by your operator count, add the implementation partner's SOW, and the first-year cost typically lands well above six figures for any meaningful FM deployment. The per-seat tax is the part that quietly destroys the maths over a five-year window.
The implementation cost is the more uncomfortable number. Building a competent CAFM on Service Cloud is not a two-month project. It is a year of work to get the data model right, another year of polishing edge cases, and a permanent ongoing cost as Salesforce's release cycle breaks integrations or deprecates objects. None of that ongoing cost is in the original business case.
When Salesforce actually wins
There are situations where Service Cloud is the right call. If you have already built 80% of a CAFM on Salesforce, the marginal cost of finishing it is genuinely lower than migrating to a specialist. If your operation is light on physical asset management and heavy on customer interaction, a Service Cloud-led model can work. If your IT strategy is explicitly "everything on Salesforce" and the strategic value of consolidation outweighs the operational friction, that is a defensible position.
None of those describes the average UK FM provider, council, housing association, or NHS estates team.
When a specialist wins
If you need PPM scheduling, asset hierarchy, permit-to-work, compliance certificate tracking, or a tenant-facing self service portal that does not feel like a Salesforce Experience Cloud bolt-on, a specialist platform will deliver in weeks what Service Cloud would deliver in years. The operational difference is also visible: engineers, tenants, and admins use a tool built for them rather than a tool configured to approximate one.
The honest framing for a procurement panel is this. If your people will use Salesforce for non-FM work anyway, keep Salesforce for that. Run a specialist CAFM next to it, with clean data sharing where it matters. You will spend less, get more, and stop forcing a generalist platform into a shape it was not designed for.
See what a specialist looks like
Book a demo. We will run the use cases your Salesforce build is being asked to cover, and you can judge how comparable the experience is.