structuring-investor-segmentation
Designs LP segmentation with tiered communication, access differentiation, and relationship management frameworks. Use when segmenting investor base, designing communication strategies, or managing LP relationships.
Best use case
structuring-investor-segmentation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Designs LP segmentation with tiered communication, access differentiation, and relationship management frameworks. Use when segmenting investor base, designing communication strategies, or managing LP relationships.
Teams using structuring-investor-segmentation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/structuring-investor-segmentation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How structuring-investor-segmentation Compares
| Feature / Agent | structuring-investor-segmentation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Designs LP segmentation with tiered communication, access differentiation, and relationship management frameworks. Use when segmenting investor base, designing communication strategies, or managing LP relationships.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Structuring Investor Segmentation Designs LP segmentation frameworks with tiered communication cadences, differentiated access levels, and relationship management protocols for fund managers and investor relations teams. ## When To Use - Launching a new fund and establishing LP tiers before first close - Restructuring IR approach after significant growth in LP count or AUM - Onboarding a new class of investors (e.g., sovereign wealth, family offices) that requires distinct treatment - Designing communication strategies that balance transparency obligations with operational efficiency - Building or refining an LP relationship management playbook for the IR team ## Inputs To Gather - **LP roster**: Names, commitment amounts, entity types (pension, endowment, family office, fund-of-funds, sovereign wealth, HNWI) - **Commitment data**: Capital committed, capital called, remaining unfunded, vintage year - **Relationship history**: Tenure with the GP, co-investment participation, re-up history, advisory committee seats - **Regulatory/structural constraints**: Side letter provisions, MFN rights, reporting obligations specific to LP type [VERIFY] - **Current communication inventory**: Existing reports, call cadences, portal access, event invitations - **GP strategic priorities**: Which LPs are targets for re-up, co-invest pipeline, or new fund seeding ## Workflow 1. **Profile each LP** — Classify by entity type, commitment size, strategic value, and engagement level. Assign quantitative scores where possible (e.g., commitment as % of fund, re-up likelihood rating). 2. **Define tier structure** — Establish 3-4 tiers with clear thresholds: - **Tier 1 (Strategic)**: Anchor LPs, advisory committee members, top decile by commitment. Typically 5-10% of LP count, 40-60% of AUM. - **Tier 2 (Priority)**: Significant commitments, active co-investors, strong re-up track record. - **Tier 3 (Core)**: Standard LPs meeting minimum commitment, consistent but lower engagement. - **Tier 4 (Monitoring)**: Small or legacy commitments, infrequent engagement, potential attrition candidates. 3. **Map communication cadences per tier**: - Tier 1: Quarterly 1-on-1 calls with senior partners, early access to deal pipeline updates, in-person annual review, custom reporting packages - Tier 2: Quarterly group calls, standard-plus reporting with portfolio-level commentary, annual meeting priority seating - Tier 3: Standard quarterly reports, semi-annual LP letters, annual meeting invitation - Tier 4: Standard quarterly reports, annual LP letter, digital-only engagement 4. **Design access differentiation** — Define what each tier receives beyond standard reporting: - Co-investment allocation priority and minimum notice periods - Portal features (real-time dashboards vs. static quarterly uploads) - Event access (advisory committee meetings, GP offsites, deal team introductions) - Custom analytics or benchmarking on request 5. **Address side letter and MFN implications** — Cross-reference tier benefits against side letter commitments. Confirm that tiered access does not conflict with MFN clauses granting equivalent rights to other LPs. [VERIFY specific side letter terms and MFN triggers] 6. **Build relationship management protocols** — Assign IR coverage by tier: - Tier 1: Named relationship manager at partner level, CRM tracking of all touchpoints - Tier 2: Senior IR professional with defined outreach calendar - Tier 3-4: Pooled IR coverage with automated communication triggers 7. **Document escalation paths** — Define when an LP's behavior or requests should trigger a tier reassessment (e.g., commitment increase, redemption signals, regulatory inquiry, co-invest decline pattern). ## Output Deliver a structured segmentation report containing: - **Tier definition matrix**: Thresholds, criteria weights, and LP assignments per tier - **Communication plan**: Cadence calendar by tier with responsible parties and content types - **Access differentiation schedule**: Tier-by-tier feature/benefit grid - **MFN/side letter cross-reference**: Flagged conflicts or required accommodations - **Coverage model**: IR team assignments and escalation triggers - **Reassessment criteria**: Quantitative and qualitative triggers for tier migration (up or down) ## Quality Checks - Every LP in the roster is assigned to exactly one tier with documented rationale - Tier thresholds are objective and defensible — no LP placement based solely on subjective preference - Communication cadences are operationally feasible given IR team capacity - Side letter and MFN provisions are cross-checked; any potential conflicts flagged with [VERIFY] - Tier benefits do not inadvertently create material non-public information access issues [VERIFY regulatory framework] - The segmentation framework includes a review cycle (recommend quarterly or semi-annual reassessment) - Output is formatted for direct use by IR team without requiring additional interpretation