RelationshipsIQ
Evidence + strategic reading
Relationship history
Objective relevance
Opportunity Radar
Companies & Paths
Network Runway
Relationship Capital
Uncertainty
Recommended next move
GoHighLevel execution architecture
RelationshipsIQ decides who matters and why.GoHighLevel is where the approved move gets operationalized.
The integration is being built around a strict separation of responsibilities. RelationshipsIQ owns the relationship graph, objective-aware intelligence, evidence and recommendation. GoHighLevel owns contacts, opportunities, workflows, conversations, calendar and other supported execution surfaces.
Human approval
GoHighLevel
Operational execution
ContactsOperational CRM identity and contact context.
OpportunitiesApproved commercial or strategic actions.
WorkflowsExecution after the relationship decision.
Conversations + calendarFollow-through tied back to the reason the move mattered.
Why the boundary matters
A CRM event is not automatically relationship truth.
The integration will not let external execution events rewrite RelationshipsIQ intelligence directly. A CRM contact is not automatically reachable. An open is not advocacy. A pipeline stage is not Relationship Capital. Outbound activity is not inbound Pull.
Identity before writes
CRM identity resolution distinguishes confirmed, probable, ambiguous, unmatched and conflict states. Name-only merging is not acceptable.
Human approval
An Act Now relationship is still not permission to auto-send. Analysis, recommendation, draft, approval, execution and outcome remain separate.
Idempotent execution
Writes must be safe to retry without duplicating contacts, opportunities or actions blindly.
Normalized outcomes
Provider events return as evidence facts with provenance rather than becoming direct score mutations.
Server-side secrets
OAuth tokens and integration credentials belong behind the server-side provider boundary, never in the browser UI.
Tenant isolation
One user is not assumed to equal one GoHighLevel location. Tenant and location boundaries remain explicit.
Closed-loop model
The relationship decision stays explainable all the way through execution.
The target loop is evidence → intelligence → recommendation → approval → provider execution → outcome evidence → refreshed intelligence. External systems add facts; they do not become the new scoring engine.
Before execution
Reconnect before making the ask.
Example recommendation: a strong prior relationship now sits inside a named target company, but the current buying need is still unknown.
01 · Evidence
Prior relationship · current employer · objective context
FACT02 · Reading
Credible route exists; current intent remains unknown
RIQ03 · Approval
User chooses to reconnect before any commercial ask
YOU04 · Execution
GoHighLevel carries the approved operational step
GHLCurrent status
Core intelligence is certified. GoHighLevel execution is the next integration layer.
The website now reflects that distinction explicitly. The current product already delivers the relationship graph, cloud restore, objective workspaces, Radar, Runway, Companies & Paths and the broader intelligence layer. The GoHighLevel connector should be represented as integration architecture until the closed loop is fully certified.
Design-partner conversations
Have a GoHighLevel workflow where relationship context changes the move?
That is the right use case to evaluate while the execution layer is being productized.