A second relationship on the same connection
Northstar's connection stays the same. A second approved relationship, CloudAxis, activates on top of it with its own trigger, permissions, and action. Because CloudAxis also uses Salesforce, the destination side is configuration too.
Regulatory compliance and licensing
CRM: Salesforce
Cloud infrastructure
CRM: Salesforce
Cybersecurity
CRM: HubSpot
New opportunity from the same partner data
Approved signals reveal a separate need/opportunity, matched to an existing relationship; fit and action authority remain separate.
Meridian Manufacturing
Existing Northstar customer · Industrial manufacturing
Cloud infrastructure modernization
- Delivery / PSA — Recurring remediation work items against two end-of-life on-premises clusters.
- Document workspace — Deliverable metadata references a target-state architecture assessment.
- Billing and time — Unplanned infrastructure support hours well above baseline.
- Northstar CRM — New VP Technology contact added and engaged on two workstreams.
Reseller
Request quote
CloudAxis configuration
Activating the relationship on the existing connection.
What is reused
- Northstar's existing customer-signal access.
- The same signal, opportunity, existing relationship, permission, action, and outcome logic.
- Some or all of the existing Salesforce destination connection.
New work is limited to the relationship itself: trigger, rules, economics, and action.
Can one connection make Relationship #2 easier to activate?
Northstar's partner-side connection is already set up in this simulated example. The next test is whether another approved relationship can reuse it with its own state, permissions, economics, and action—making Relationship #2 materially easier to activate than Relationship #1.
Each relationship has its own trigger, eligibility, permissions, economics, action, and destination. A shared destination system such as Salesforce is a secondary benefit.