Salesforce SPoT
Status: Custom engagement. Account identity and governance.
What this is, and what it is not
SPoT is custom RevOps engineering, not one of the four Mixbound products and not a Data Enhancement pass. Enhancement runs as a scoped pass against a set of records you approve. SPoT resolved identity at the moment an account record would otherwise have been created, inside the customer's own Salesforce environment. This capability has been deployed in a customer environment; it is not a service you enable on a portal.
Single Point of Truth
SPoT designates Salesforce as the authoritative registry for Account records. HubSpot operates as the ABM discovery and engagement layer. Account authority resolves deterministically to Salesforce, so the question “which record is this account” has one answer rather than one per system.
Identity resolution before creation
The ordering is the whole design. Identity is resolved first; an account is created only if resolution finds no valid match. Duplicate prevention is therefore a property of the sequence rather than a cleanup step that runs afterwards.
Matching is hierarchical and deterministic: domain first, then external identifier, then normalised name. Each strategy is evaluated in order, and a match at a higher tier settles the question without falling through to a weaker signal.
Controlled account creation
Where no match exists, account creation is governed by eligibility rules rather than performed on demand. Records that resolve are linked; records that do not resolve and do not qualify are not silently created.
Stable linking
Resolved pairs are linked bidirectionally with stable identifiers, so the association survives later edits on either side and both systems can be reconciled against each other rather than compared by name.
It operates alongside native sync
SPoT does not override or replace the native HubSpot-Salesforce integration. It addresses the identity gaps that native sync does not resolve, and it leaves the existing sync rules in place.
Who it was built for
RevOps, SalesOps and GTM engineering teams running HubSpot as the primary ABM surface with Salesforce as the authoritative account registry. The result is that sales sees the same strategic accounts that marketing and SDR teams activate, and sync behaviour becomes predictable rather than conditional on the order in which contacts arrive.