Stage 1 · Setup

What Vinculo is connected to, and what it is allowed to do

Northstar Consulting already works across these systems. Vinculo uses only approved information that is already available in the partner's workflow. It does not ask the partner to enter anything new and it does not contact the customer. Vinculo works across these systems rather than replacing the partner's CRM, PRM, or existing workflow. This composite-signal example uses scoped approved context; a bounded source-derived state is also a valid input for opportunity recognition.

Scenario used in this demo

Labrynth is a real Infinity Constellation portfolio company used here as the illustrative destination company. Northstar Consulting, Atlas Energy, CloudAxis, and ShieldWorks are fictional. This scenario does not represent an actual Labrynth customer, partner, or opportunity.

This relationship requires human approval. Other Vinculo relationships may execute automatically or require customer consent instead.

Product model

Signal→Opportunity→Relationship→Permission→Action→Outcome

Behavior model

Observe›Interpret›Match›Check›Permission›Prepare›Approve›Execute›Learn

Partner-side integrations

Northstar Consulting · illustrative consulting and implementation partner — These simulated integrations provide scoped approved signals for opportunity recognition. Bounded source-derived states are also valid; Vinculo does not replace the source systems.

Northstar CRM
Customer records · Account context and existing commercial activity
Simulated
Account dataCustomer/account historyExisting opportunitiesAccount structure
Delivery / PSA
Project and workflow · What the partner is actually doing for the customer
Simulated
ProjectsWork itemsDelivery activityService categoriesScope changes
Document workspace
Approved documents · Metadata-first read of approved working material
Read-only
Approved working documentsAssessmentsScope metadataProject plans
Billing and time
Commercial · Where effort and spend are moving
Simulated
Billed-hour categoriesChanges in service mixUnusual support effortScope expansion
Slack / Teams
Communication (optional) · Supporting evidence only
Optional
Opt-in onlyApproved channels only
Not required for the Atlas workflow. Communication data can corroborate evidence but cannot independently trigger a commercial recommendation.

Destination-side integrations

Used for the pipeline check, for writing the approved action, and for returning outcomes.

Labrynth

Salesforce

Illustrative first destination integration

· Check whether the account or opportunity already exists
· Create or update the approved partner-sourced action
· Return enough outcome information to track what happened

Illustrative first destination-system integration.

CloudAxis

Salesforce

Reuse example

· Uses the same destination system as Labrynth
· Requires its own access, fields, permissions, and workflow setup
· Shows the reuse question

If another destination also uses Salesforce, how much of the work can carry over?

ShieldWorks

HubSpot

Different system example

· Uses HubSpot instead of Salesforce
· May require additional integration work
· Shows what changes when the destination system is different

This example shows a second destination system and the possibility that more work may be required.

The reuse hypothesis: additional destinations on the same systems can reuse approved signal access, opportunity logic, and connector work, with their own authentication, mapping, permissions, and workflow setup.

Approved commercial relationships

Declared by the partner. No action exists outside these.

Labrynth
Referral
Regulatory compliance and licensing
Warm introductionDestination CRM: Salesforce
CloudAxis
Reseller
Cloud infrastructure
Request quoteDestination CRM: Salesforce
ShieldWorks
Referral
Cybersecurity
Warm introductionDestination CRM: HubSpot

Where each person works

Vinculo is a console for partner admins. Everyone else stays in the system they already use.

Partner admin / ops
Vinculo
IntegrationsRelationship setupPermissionsAuditSuppressionOutcomes
Partner employee
Their existing workflow
CRMTeamsEmailOther existing workflow
Vinculo surfaces the action there. They do not monitor a Vinculo inbox.
Destination employee
Their existing sales or partner workflow
SalesforceHubSpotPRMAnother existing workflow
The approved action arrives there.

Integration sequence for the Atlas Energy action

Exactly which system does what, in order, for the scenario in this demo.

1
Northstar CRM
Read Atlas account structure and existing opportunities
2
Delivery / PSA
Read changes in licensing-related work
3
Document workspace
Read approved scope and jurisdiction information
4
Billing and time
Read increases in manual regulatory work
5
Vinculo
Combine the approved Atlas signals
6
Vinculo
Recognize a regulatory compliance and licensing need — a potential commercial opportunity
7
Vinculo
Match that opportunity to an existing approved relationship and destination capability
8
Relationship rules
Check eligibility, permission, authority, and required approval; confidence is not authorization
9
Destination system
Check whether an Atlas opportunity already exists
10
Partner workflow
Show the prepared action to the account owner
11
Partner approval
Review, edit, and choose what may be shared
12
Destination workflow
Create or record the approved partner-sourced action
13
Destination → Vinculo
Return enough outcome information to track what happened

Permission posture

This relationship requires explicit human approval before external disclosure. Detection and a strong match are not permission. The partner decides what may be shared. CRM notes, project details, source documents, and communications stay with the partner unless a relationship rule allows otherwise.

Demo scope

Everything shown here is simulated in the browser. There is no real authentication, database, live AI, or CRM connection in this demo.

Next: four indirect signals from Atlas Energy, none of which state a need.

Detect customer signals