Salesforce Data 360
Salesforce Data 360 — formerly Data Cloud — set up as a real data spine: ingested, resolved into one profile per customer, and activated where it changes a decision.
01
The problem
Why people call us about this.
A
The same customer exists four times and every team trusts a different record.
B
You bought Data Cloud credits and nobody can point at what they bought you.
C
Your agents give confident answers from incomplete profiles.
02
What’s covered
The Salesforce we actually configure.
Agents and personalisation are only as good as the profile underneath them. This is the unglamorous work that makes the rest of it true.
03
How it runs
Five phases, and what you see at the end of each.
01 · Week 1
Inventory
What exists, who owns it, and which system is really the source of truth. Almost always surfaces something nobody knew was live.
A written map
02 · Weeks 2–3
Contract
The design in writing, with each decision and its reversal cost named. This is where we argue with the brief — before money is spent.
A signed scope
03 · Middle
Build
Built against the contract and reviewed against it. You see working software every two weeks, in your own sandbox.
Fortnightly demos
04 · Late
Prove
Volume testing at twice expected load, deliberate failure injection, and a replay run with your team watching.
A test evidence pack
05 · Final week
Hand over
Runbook, monitoring, escalation path and a named owner on your side — then a month watching it together before we step back.
Runbook and owner
04
First call
Thirty minutes. Three answers.
You speak to a certified architect, not a sales engineer. No deck, no discovery fee, and no obligation to go further — you leave the call with three things whether you hire us or not.
Whether this is even the right line
About a third of the time it is not, and we say so. Usually the ask is custom development when the real problem sits in the data model underneath.
A shape and a range
Roughly how long, roughly how many people, and the band it falls in. The firm number follows discovery about two weeks later, and it holds.
The two risks we would flag
The things most likely to blow the timeline on a project like yours — named on the call, before anyone has signed anything.
Book it for this week.
Pick a slot directly in the calendar — most questions get answered inside the thirty minutes.
05
FAQ
Asked on nearly every call.
Is Data Cloud the same thing as Data 360?
Yes. Salesforce renamed it Data 360 in 2025, and unlike Sales Cloud and Service Cloud — which got their old names back in September 2026 — this one kept the new one. Setup screens and contracts still say Data Cloud in places. The product, the data and the pricing did not change with the label.
How do you decide identity resolution rules?
From your actual duplicate patterns, tested against a sample you review before we commit them. Match rules built from assumptions produce confident nonsense at scale.
What does it cost to run?
Credit consumption, driven mostly by ingestion and query volume. We model it before ingesting anything and monitor it afterwards, because this is the bill that catches people out.
Do we need it for Agentforce?
For anything beyond a knowledge-only agent, effectively yes. An agent that cannot see a unified profile cannot resolve anything — it can only talk about resolving things.
Other lines