Advisors & Portfolio Support
How to Coordinate Co-Investor Support During a Portfolio Raise
Coordinate practical support from existing investors without duplicating asks, mixing confidential contexts or implying investment commitments.
What you will learn
- Separate support tasks from investment and legal decisions
- Assign one owner for each co-investor contribution
- Reconcile completed work, open dependencies and sharing permissions
Coordinate co-investor support through a founder-approved plan that names the job, contributing person, sharing boundary and next action. Keep support separate from decisions about investing, terms or allocation. A co-investor offering to review a deck has not committed money or authorized anyone to speak for the company.
This is operational coordination, not advice about syndication, placement activity or legal duties. The SEC's broker-dealer guide makes actual securities-related activities relevant to regulatory analysis. Have qualified counsel review the arrangement where needed; this worksheet creates no exemption.
1. Separate three conversations
The company may ask existing investors for operating help. Separately, an investor may consider a new investment. Separately again, legal questions may concern rights, documents or authority. Do not collapse these into one “co-investor support” status.
Name a founder-side coordinator. They can gather offers of help and keep company context consistent, but they do not automatically gain authority to make investment decisions or disclose sensitive documents. Confirm the actual role and permissions of each participant.
Do not assume every existing investor has the same information rights, relationship access or ability to help. Ask what they can contribute and what they need to do it. Route questions about agreements or rights to counsel rather than interpreting them in the support queue.
2. Build one practical plan with separate permissions
Fields for a co-investor support task
| Field | Purpose | Example |
|---|---|---|
| Founder job | Explains why the task matters | Review the industrial-customer story |
| Useful return | Defines completion | Three prioritized comments tied to evidence |
| Contributor and accepted role | Prevents an assumed obligation | Investor operating partner confirms review |
| Approved context | Limits disclosure | Named deck version, restricted customer detail |
| Company coordinator | Reconciles duplication | Founder or authorized operator |
| Next check and state | Makes follow-through visible | Accepted, in review, returned, held or closed |
For introduction-related help, keep the detailed lifecycle in the existing connector coordination process. Double opt-in remains a permission norm; a support plan does not substitute for either person's choice.
3. Worked example: use three offers without creating three conflicting campaigns
Illustrative example: Harbor Sensor is preparing a raise. Existing investor A offers narrative feedback, investor B offers to review the target criteria and investor C offers possible relationships. The founder wants help but does not want three people independently circulating different materials.
The founder approves one deck version for A's private review. B receives a company brief and fit criteria, not unrelated customer contracts. C receives no permission to contact anyone yet; the first return is a list of possible relationship owners for founder consideration.
Harbor's completed coordination plan
| Contributor | Accepted task | Boundary | Return |
|---|---|---|---|
| A | Review customer story | Named deck, no forwarding | Three comments, founder evaluates |
| B | Review investor-fit criteria | Approved company brief only | Evidence gaps and exclusions |
| C | Identify plausible relationship owners | No outreach authorized | Paths for separate permission review |
A and B both suggest the same potential investor. The coordinator merges the context and chooses a single next permission review. They do not ask both people to approach the investor independently. C's offer remains an offer of help, not a new financing commitment.
When A returns comments, the founder accepts two and asks for evidence behind the third. The plan records the actual return. It does not mark the narrative “investor-approved” or claim that all existing investors endorse the new raise.
4. Close tasks with the appropriate level of information
- Confirm that the promised work was received and understood.
- Record what the founder accepted, deferred or rejected.
- Thank the contributor and provide a concise outcome where appropriate.
- Do not share another investor's private comments or company documents merely to prove progress.
- Keep unresolved decisions with the authorized owner and professional adviser.
Use a separate, evidence-based record for any financing commitments. Neither an introduction, a meeting nor supportive wording is money received.
5. Copy the support map
Company / founder coordinator:
Operating job:
Useful return:
Contributor / accepted role:
Approved evidence and version:
Sharing and forwarding permission:
Duplicate request check:
Action owner / next review:
Actual returned work:
Founder acceptance or correction:
Separate investment/legal workstream:
Close-the-loop update:
What remains unapproved:Common failures
- Everyone uses a different deck: Name the approved version and stop circulation of unreviewed changes.
- An offer of help becomes a presumed duty: Confirm the task and timing before assigning it.
- Confidential investor context crosses workstreams: Limit access and obtain appropriate permission.
- Support is reported as investment intent: Correct the record and keep the two states separate.
Completion check: Each contribution has a useful return, one owner and a sharing boundary. The founder can explain what happened without implying a new investment or unauthorized endorsement.
Informational disclaimer
We are not lawyers. This article is for general education only and is not legal, tax, accounting or investment advice. Check with your attorney or accountant before acting on it.