Finta Core Workflow: Investor Relations
Overview
Post-fundraise investor management: send periodic updates, share metrics, manage cap table, and maintain relationships for future rounds.
Prerequisites
- Confirm the update audience, source-of-truth metrics, and internal approval owner.
- Verify that recipients are authorized for the selected content and documents.
- Prepare a redacted draft outside of production mailing lists for review.
Instructions
Investor Updates
- Go to Updates > New Update
- Select template (monthly, quarterly, or custom)
- Finta auto-populates metrics from connected financial tools:
- MRR/ARR from Stripe
- Cash and burn rate from Mercury/Brex
- Runway calculation
- Add qualitative updates (milestones, challenges, asks)
- Send to all investors or select groups
Update Template
Subject: [Company] Monthly Update - March 2026
Key Metrics:
- MRR: $X (up Y% MoM)
- ARR: $X
- Burn Rate: $X/month
- Runway: X months
- Headcount: X
Highlights:
- [Achievement 1]
- [Achievement 2]
Challenges:
- [Challenge and plan to address]
Asks:
- Introductions to [specific companies/people]
- Feedback on [specific topic]
Warm Introduction Network
Finta's network feature identifies 2nd-degree connections:
- Go to Network > Find Introductions
- Select target investor
- Finta shows mutual connections from your team, advisors, and existing investors
- Request introduction through the platform
Cap Table Tracking
- Import cap table from Carta, Pulley, or CSV
- Track ownership percentages after each round
- Model dilution for future rounds
- Export for legal and compliance
Output
Create an approved investor-update record containing the audience segment, source metric date, reviewer, send time, and any open follow-up requests. Keep cap-table exports and recipient-level details in their approved systems, not in local drafts or repository files.
Error Handling
- Stop a send when the recipient segment, attached document permissions, or source metrics cannot be verified.
- Treat bounced messages, unsubscribe requests, or audience mismatches as a review queue; do not automatically resend to an alternate address.
- If connected metrics are stale or incomplete, label the update as pending and obtain an owner’s decision before sending.
- Revoke access and document the correction if a restricted update or document is shared with the wrong audience.
Examples
Draft a monthly update with fictional metrics, have the designated reviewer approve the audience, and send it only to a test segment. Verify the activity record and document permissions, then use the same reviewed template for the authorized production segment.
Resources
Next Steps
For troubleshooting, see finta-common-errors.
1---2name: finta-core-workflow-b3description: Manage ongoing investor relations and updates with Finta. Use when sending investor updates, tracking cap table changes, or maintaining LP relationships post-close. Trigger with phrases like "finta investor updates", "finta LP management", "finta post-close", "finta investor relations".4license: MIT5---6# Finta Core Workflow: Investor Relations
7
8## Overview
9
10Post-fundraise investor management: send periodic updates, share metrics, manage cap table, and maintain relationships for future rounds.
11
12## Prerequisites
13
14- Confirm the update audience, source-of-truth metrics, and internal approval owner.
15- Verify that recipients are authorized for the selected content and documents.
16- Prepare a redacted draft outside of production mailing lists for review.
17
18## Instructions
19
20### Investor Updates
21
221. Go to **Updates** > **New Update**
232. Select template (monthly, quarterly, or custom)
243. Finta auto-populates metrics from connected financial tools:
25 - MRR/ARR from Stripe
26 - Cash and burn rate from Mercury/Brex
27 - Runway calculation
284. Add qualitative updates (milestones, challenges, asks)
295. Send to all investors or select groups
30
31### Update Template
32
33```
34Subject: [Company] Monthly Update - March 2026
35
36Key Metrics:
37- MRR: $X (up Y% MoM)
38- ARR: $X
39- Burn Rate: $X/month
40- Runway: X months
41- Headcount: X
42
43Highlights:
44- [Achievement 1]
45- [Achievement 2]
46
47Challenges:
48- [Challenge and plan to address]
49
50Asks:
51- Introductions to [specific companies/people]
52- Feedback on [specific topic]
53```
54
55### Warm Introduction Network
56
57Finta's network feature identifies 2nd-degree connections:
58
591. Go to **Network** > **Find Introductions**
602. Select target investor
613. Finta shows mutual connections from your team, advisors, and existing investors
624. Request introduction through the platform
63
64### Cap Table Tracking
65
66- Import cap table from Carta, Pulley, or CSV
67- Track ownership percentages after each round
68- Model dilution for future rounds
69- Export for legal and compliance
70
71## Output
72
73Create an approved investor-update record containing the audience segment, source metric date, reviewer, send time, and any open follow-up requests. Keep cap-table exports and recipient-level details in their approved systems, not in local drafts or repository files.
74
75## Error Handling
76
77- Stop a send when the recipient segment, attached document permissions, or source metrics cannot be verified.
78- Treat bounced messages, unsubscribe requests, or audience mismatches as a review queue; do not automatically resend to an alternate address.
79- If connected metrics are stale or incomplete, label the update as pending and obtain an owner’s decision before sending.
80- Revoke access and document the correction if a restricted update or document is shared with the wrong audience.
81
82## Examples
83
84Draft a monthly update with fictional metrics, have the designated reviewer approve the audience, and send it only to a test segment. Verify the activity record and document permissions, then use the same reviewed template for the authorized production segment.
85
86## Resources
87
88- [Finta for Fund Managers](https://www.trustfinta.com/blog/finta-for-fund-managers-venture-capital-crm)
89
90## Next Steps
91
92For troubleshooting, see `finta-common-errors`.