The minimum operating layer
Most of the target product can start out as a manual process. These six things cannot — they are what makes the pilot repeatable, safe, and easy to review.
Approved data access
A clear agreement on which systems, fields, and accounts can be used. Nothing is analyzed unless the partner has approved it.
Customer signal history
A simple record of what changed for each customer, when it changed, where the signal came from, and the supporting evidence.
AI interpretation
AI looks across approved customer signals and suggests a possible need, with the evidence shown so a person can review it.
Relationship and permission rules
A clear list of approved destination companies, what needs they can help with, what actions are allowed, what may be shared, and who must approve.
Action delivery
Send a reviewed recommendation into a workflow the employee already checks, such as email, Slack, Teams, CRM tasking, or another existing surface.
Action and outcome record
Keep a record of what was suggested, approved, dismissed, sent, and what happened afterward.
The minimum layer is not a smaller version of the full platform. It is the smallest loop needed to run the workflow repeatedly and safely.
Approved pilot data intake
How approved partner data reaches the pilot before production integrations exist
Before production integrations exist, partner data can arrive through an agreed export, a limited read-only connection, secure upload, or another approved method.
- Which systems can be used
- Which fields can be accessed
- Which accounts are in scope
- How often data can be refreshed
- What may be retained
- An agreed export
- A limited read-only connection
- Secure upload
- A secure shared folder created for the pilot
Only explicitly approved data enters the pilot.
Start with document metadata and only use specific approved files or excerpts when needed.
The pilot should not require broad access to a partner's document repository.
The Phase 1 loop
Batched or scheduled data is a fine starting point
- 01Approved partner data
Agreed export, secure upload, or limited read-only access
- 02Pilot intake
Check that the data is approved and in scope
- 03Customer signal history
Record what changed, when, source, and evidence
- 04AI interpretation
Suggest possible need and show why
- 05Vinculo operator review
Check evidence, fit, permissions, and suppression
- 06Partner action delivery
Email, Slack, Teams, CRM task, or another monitored workflow
- 07Human approval
Review, edit, approve, dismiss, or defer
- 08Send to destination
Structured referral or agreed intake process
- 09Outcome record
Accepted, declined, existing, meeting, opportunity, qualified, or other agreed outcome
Where AI sits
AI suggests; people and rules decide
AI suggests the need. People and partner rules decide whether anything happens.
The evidence is kept separately from the AI interpretation, so a person can always see what the suggestion was based on.
Illustrative employee delivery options
Delivery into a workflow the employee already uses
Vinculo should not require partner employees to monitor another inbox. The requirement is that a reviewed action reaches the employee in a workflow they already use.
The way the action is delivered can change over time. A pilot may start with email or Slack/Teams, while a later version may place the same action directly inside the partner's CRM.
Vinculo found a possible partner opportunity
- Account
- Atlas Energy
- Possible need
- Energy regulatory compliance and licensing
- Approved destination
- Labrynth
- Why now
- Atlas is expanding into additional jurisdictions while regulatory work remains manual.
Review opens a lightweight approval page.
Vinculo
Atlas Energy may have a need that fits an approved partner relationship.
Possible destination: Labrynth
- jurisdiction expansion
- growing regulatory workload
- manual tracking remains significant
The same action could be delivered through Teams, Slack, CRM tasking, or another monitored workflow.
The product requirement is delivery into an existing employee workflow. Email, Slack, Teams, CRM tasks, or other surfaces are implementation options that can vary by partner.
The employee does not need to monitor Vinculo.
Everything else can remain manual until repetition justifies automation.
Implementation examples in this demo are illustrative. The product requirements are the behaviors, constraints, permissions, and interfaces shown here. Specific technical choices remain open.