CRM sync
Your CRM already knows the account.Now it knows the reason to call.
Connect once. Intelligence X matches every account on domain, writes nine intelligence fields onto the record, and keeps them current — so the pitch is assembled before the rep opens the tab, and the close date rests on a renewal window rather than a feeling.
The CRM layer
It connects to your CRM and fills in the reason to call.
Intelligence X sits on top of the CRM you already run. It matches every account, writes nine intelligence fields back onto the record, and keeps them current — so the rep opens a familiar screen and finds the pitch already assembled, with the evidence attached.
Everything here is true and none of it tells a rep whether to call today. The three fields that would are the three that are empty.
The rep opens the same record they always did. What changed is that it now answers why this account, why this week — before the call.
How the sync runs
Connect
OAuth into Salesforce, HubSpot, Dynamics or Pipedrive. Read-only until you approve a write scope, and you choose which objects are in play.
Match
Records resolve on domain and corporate hierarchy rather than company name, so subsidiaries and rebrands don’t fracture into duplicates.
Enrich
Nine intelligence fields land on the account and contact, each carrying the source that produced it and the date it was found.
Write back
Everything writes to a namespaced field set. Rep-entered values are never overwritten, and every change is logged for audit.
Act
Score changes fire a Slack alert, create a task, or re-rank the queue — so the pitch is ready before the rep opens the record.
Better pitch
The opener arrives with the record.
Trigger, competing vendors and the buyer’s own measured KPIs sit on the account page, so the first line references something that actually happened at the company rather than a job title.
Better closure
Timing and committee coverage stop being guesses.
Renewal windows and an explicit map of who is still unmet turn forecast conversations into a checklist. Two of four contacts covered is a gap you can work this week.
The field map
Nine fields, each settling one question a rep would otherwise guess at.
Everything writes into a namespaced set. Nothing your team typed is touched, and every value carries the source that produced it and the date it was found.
Why this account
- IX_SIGNAL_SCORE__c
- Composite intent, 0–100, plus 13-week direction
- IX_TRIGGER__c
- The event that opened the window, with its date
- IX_COMPETITORS__c
- Vendors already detected in the evaluation
Why this week
- IX_BUYING_STAGE__c
- Unaware through to decision
- IX_RENEWAL__c
- Contract window and days remaining
Who to work
- IX_ECON_BUYER__c
- Named economic buyer and their measured KPIs
- IX_COMMITTEE__c
- Full committee with roles, and coverage gaps
What to say
- IX_TECH_STACK__c
- Detected systems with confidence and method
- IX_OPENER__c
- Recommended opening line, tied to the trigger
Where it connects
Connect the system your team already lives in.
Control
A write-back you can audit, scope, and switch off.
Scoped writes
Choose the objects and fields in play. Read-only until you approve a write scope.
Never destructive
Rep-entered values are left alone. Mappings can be set to fill-if-empty.
Full audit trail
Actor, value, source and timestamp on every write. Roll back any sync run.
Yours on exit
Disconnect and the fields stay, frozen at their last timestamp. Export as CSV.
Questions
Sync, matching and control
No. Every value Intelligence X produces lands in its own namespaced field set, prefixed IX_. Standard and custom fields your team owns are never written to unless you explicitly map them, and any mapping you do create can be set to fill-if-empty rather than overwrite.