Direct answer: A permissioned introduction queue that matches founder needs to plausible mentors or investors without treating a visible connection as consent.
Who this workflow is for
Accelerator teams, VC platform teams, Founder support teams. Use it when relationship context is spread across approved records, communication, meetings, and documents, but the final judgment still belongs to a person.
Execution mode and prerequisites
Permission-gated cohort support recipe. Finta can organize founder requests and relationship evidence, but every introduction remains a sequence of human decisions.
- Founder-approved company briefs and requests
- Permissioned mentor and investor relationship records
- A conflict and confidentiality policy
- A named owner for every introduction request
Inputs, review boundary, and outcome
| Input | What a person verifies | Reviewed output |
|---|---|---|
| Founder request | Goal, timing, exclusions, and approved positioning | Cohort support brief |
| Mentor and investor records | Fit, relationship evidence, conflicts, and owner | Plausible introduction paths |
| Program policy | Consent, confidentiality, fairness, and tracking rules | Approved request process |
Run the workflow
- Collect a concise, founder-approved request with the desired outcome and exclusions.
- Find possible mentors, investors, and relationship owners using permitted evidence.
- Check fit, conflicts, confidentiality, cohort fairness, and whether the relationship is current.
- Ask the relationship owner whether a connector request is appropriate.
- Prepare a short request and forwardable context for human review.
- Track consent, introduction status, outcome, and a close-the-loop update without pressuring either side.
Human approval boundary
The founder approves the positioning, the relationship owner decides whether to ask, the prospective connector chooses whether to introduce, and the recipient remains free to decline. Finta prepares context but does not grant permission on anyone's behalf.
Worked example
A founder requests an introduction to a healthcare operator before a hospital pilot. The platform team identifies two mentors with relevant experience, removes one because of a portfolio conflict, and asks the remaining relationship owner for permission. The owner approves a forwardable note, the mentor accepts, and the platform team records the outcome for the founder.
Expected review receipt
- The founder brief and fit rationale are visible
- Conflict and confidentiality checks are recorded
- Relationship-owner and connector consent are explicit
- The introduction outcome and close-the-loop owner are tracked
Decision checklist
- The founder approved the request and positioning
- The proposed person fits the stated need
- Conflicts and confidential relationships are excluded
- The relationship owner has not been bypassed
- A decline is easy and recorded without penalty
Failure states and safe stops
- A visible connection is mistaken for relationship strength or permission
- The founder brief is incomplete or not approved
- A conflict or confidential relationship is exposed
- The workflow favors access without a documented program rationale
Where Finta helps
In a supported, permissioned setup, Finta can organize the relevant CRM record, relationship history, connected or user-provided evidence, documents, and next-action workspace. Aurora can prepare a recommendation, summary, or draft. A person remains responsible for checking the evidence and approving consequential changes or communication.
Relevant Finta products: Networks, CRM, Aurora, Tasks. Relevant integrations: Gmail, Outlook, Google Calendar, LinkedIn.
What this workflow does not do
- Finta does not guarantee a response, meeting, introduction, or investment.
- LinkedIn context depends on supported imports or user-invoked browser context, not continuous sync.
- Program leaders remain responsible for fairness, conflicts, and confidentiality.
Sources and review notes
The Techstars Mentor Manifesto says mentors should hold information in confidence, guide rather than control, and commit clearly or decline. Those principles support a permission-first introduction process.
- Techstars Mentor Manifesto
- Finta Networks
- Warm introduction workflow
- Portfolio company fundraising workflow
Research reviewed: September 1, 2026. Recheck product behavior, permissions, professional standards, and the human approval boundary before publication and after any material workflow change.