Direct answer: A small, prioritized set of dormant investors with a credible reason to re-engage and a reviewed, context-rich outreach draft.
Execution mode and verification status
Reviewed outreach recipe. Email, calendar, CRM, and user-invoked Chrome or imported LinkedIn Connections context may inform the review; Finta does not claim continuous LinkedIn sync or permission to contact someone.
The outcome this workflow produces
A small, prioritized set of dormant investors with a credible reason to re-engage and a reviewed, context-rich outreach draft.
| Input | What to verify | Output |
|---|---|---|
| Dormant contacts | Last meaningful interaction | Candidate relationship set |
| New evidence | Material milestone or changed fit | Reason to re-engage |
| Relationship path | Owner and introduction context | Best next approach |
Run the workflow
- Define dormancy by meaningful interaction rather than opens or list age alone.
- Limit the universe to investors who still fit the company, fund, stage, geography, and current raise.
- Find a material new reason to reconnect, such as traction, thesis change, timing, or a trusted path.
- Review the previous conversation, objections, promises, and contact preferences.
- Prepare a concise draft that acknowledges context and gives the recipient a clear reason to respond now.
Worked example
Example: an investor passed six months ago because the company was pre-revenue. The company now has paid customers and the investor still matches stage and thesis, so a contextual draft is prepared. A second investor is excluded because the record contains a do-not-contact note.
Expected review receipt
- Dormancy and eligibility rules are documented
- A material new reason to reconnect is visible
- Suppression and channel preferences are checked
- Each message remains individually approved
Decision checklist
- Investor fit is current
- The prior relationship is accurately summarized
- There is a real new reason to contact the person
- Frequency and channel preferences are respected
- The message is individually approved
Where Finta helps
In a supported, permissioned setup, Finta can organize the relevant CRM record, relationship history, user-provided or connected-source evidence, and next-action workspace for the same review. Aurora can prepare a recommendation or draft; a person remains responsible for checking the evidence and approving consequential changes or communication.
Human approval boundary
A person confirms fit, timing, prior context, and the right channel before outreach; dormancy must never trigger bulk automated messaging.
Failure states and safe stops
- No material change supports re-engagement
- The investor no longer fits
- The prior record includes a pass or suppression instruction
- Relationship or consent context is stale
Limitations
- Silence can be a decision, not a reminder problem.
- Old relationship data can be stale or incomplete.
- A new milestone does not automatically make every dormant investor relevant.
Sources and related Finta resources
Last reviewed: August 30, 2026. Re-verify product behavior, permissions, and the approval boundary before publication and after a material workflow change.