VVinculo
Northstar Consulting
Stage 3 · Decide

Vinculo decision and audit view

This is the partner admin view for reviewing what Vinculo surfaced, what it held back, and why. Employees do not need to monitor this screen.

Observe›Interpret›Match›Check›Permission›Prepare›Approve›Execute›Learn
AI suggests the need. Partner rules determine whether there is an allowed commercial action.
Surfaced · 2 open

Atlas Energy

Surfaced

Existing Northstar customer · Utilities and generation · Client since 2021

Need highFit strong
Inferred need

Energy regulatory compliance and licensing workflow

Need confidence

High

Destination fit

Strong

Evidence
  • Delivery / PSA · Primary evidence — Licensing and permit work items growing sharply across four engagements.
  • Billing and time · Primary evidence — A material block of billed hours categorized as 'manual regulatory tracking'.
  • Document workspace · Supporting evidence — Two SOW amendments add coverage for three additional jurisdictions.
  • Northstar CRM · Corroborating evidence — Two new regional operating entities added to the Atlas Energy account.
Why Atlas was surfaced
  • Need confidence: High
  • Destination fit: Strong
  • Existing opportunity: None found
  • Approved relationship: Yes
  • Allowed action: Warm introduction
  • Partner approval required: Yes
  • Result: Surfaced
Approved relationship

Northstar → Labrynth

Regulatory compliance and licensing

Commercial model

Referral (approved relationship)

Prepared action

Warm introduction

Delivery surface

Northstar CRM

This relationship is configured to deliver approved Vinculo actions inside Northstar's CRM workflow.

This relationship is set up to send approved actions into the partner's CRM. The same Vinculo logic could be delivered through another existing workflow.

Labrynth Salesforce checked — no existing Atlas Energy opportunity.

See action in Northstar workflow

Harbor Logistics

Surfaced

Customs and trade compliance workflow

Need highFit strongWarm introduction

Evaluated and not surfaced

Shown here for the demo. In production a partner sees a suppression log, not an inbox item.

Beacon Manufacturing
Plant maintenance scheduling and asset uptime
Need highFit weakNot surfaced

ReasonReal apparent need but destination mismatch.

Crescent Utilities
Regulatory filing automation
Need highFit strongSuppressed

ReasonExisting Labrynth opportunity already exists.

Nova Medical
Quality management documentation (weak inference)
Need lowNot surfaced

ReasonInsufficient evidence.

Decision logic

Three separate questions determine whether Vinculo should surface an action.

1
Is there enough evidence of a real need?
Customer signals
Approved signals from the systems the partner already uses, such as CRM, delivery, billing, account activity, and scope changes
Need inference
AI looks across approved customer signals and identifies a possible need, with the evidence kept so a person can understand why
Need confidence
How much independent evidence supports the need, using the partner's own rules
2
Is there an approved destination that fits?
Inferred need
Output of stage 1, independent of any destination
Approved destination relationships
Domain coverage, segment, geography, commercial model
Destination fit
Strong / Possible / Weak, based on the inferred need and configured destination criteria
3
Is there an allowed action, and should it be surfaced?
Destination fit
From stage 2
Permission rules
What may be shared, and who approves
Existing pipeline
Destination CRM check for a live opportunity
Relationship type
Referral, reseller, or no allowed action
Permitted commercial action
Surfaced with a prepared action — or suppressed, with a recorded reason
Why this matters

Most evaluated cases should result in no action. Beacon has a real need but a weak destination fit. Crescent already has an active opportunity. Nova does not have enough evidence. Harbor shows that even a strong recommendation can still be dismissed by someone who knows the customer better.

Next: see the same action inside the account owner's existing workflow.
DetectSee action in Northstar workflow