Investor relations
Anticipating LP diligence on the research stack
Sophisticated LPs stopped asking only about track record—they ask how you know what you think you know. The diligence window favors teams who treat questions as repeatable product: evidence pre-staged, demos rehearsed, denials provable, vendors quantified, and AI policies written in plain English. The win is not theatre; it is opening folders your COO understands while counsel nods.
The modern allocator checklist
Controls attestation, SSAE reports where relevant, pen test summaries, incident history with lessons, subprocessor list, and research tool inventory with owners.
Expect ‘show, don’t tell’ on access: matrix demos, not policy PDFs alone.
Lineage story arc
Walk from vendor pull to published thesis in ten minutes with real (sanitized) examples—LPs pattern-match to other managers.
Prepare three difficulty tiers: trivial replay, medium archaeology, forensic edge case—with explicit boundaries on what you will not claim.
Business continuity
Document RTO/RPO for feeds, pricing, risk, and books; run tabletop with vendor brownouts quarterly.
Have a believable degraded mode: read-only risk, spreadsheet with explicit non-canonical watermark—prove you rehearsed it.
Access and segregation
Demonstrate least privilege with live demo accounts; show denial paths, not only happy paths.
If marketing hosts exist, explain host split and allowlists without revealing tenant topology.
Vendor and counterparty concentration
Heat map by spend and criticality; show failover or honest absence of failover.
Single-vendor dependencies deserve risk language in the PPM-style narrative—surprise erodes fee negotiations faster than underperformance.
AI usage disclosure
Policy on model use, human review gates, retention of prompts if any—blank slides here look evasive.
Separate ‘internal drafting assistance’ from ‘client-facing generation’ controls; conflation invites skeptical questions.
Incident narrative template
What broke, who noticed, how customers affected, how you proved correction—use anonymized past examples if allowed.
End each story with one structural improvement shipped—maturity signal allocators overweight.
Data room hygiene
Version filenames with dates; kill stale PDFs; link to canonical policy URLs on your own domain.
Appoint a single ‘room janitor’ owner; rotational chaos shows up as duplicate contradictions LPs love to catch.
Public desk routes referenced above
Same URL discipline applies after you authenticate—bookmarkable paths, no tenant data on these pages.
- Platform framing How tenancy and public chrome split when SEO and auth walls must coexist.
- Terms of use Stable legal URL when client-facing calculator links depart the marketing host.
- Privacy policy Maps subprocessors and flows; keep language consistent with how you split marketing and tenancy.
- Service status Public narrative around uptime; align its claims with what engineering will defend in postmortems.
- Readiness JSON Coarse liveness contract—use it to rehearse what is safe to expose anonymously vs behind auth.
- Guides Pair public guides with internal SOPs so training points at one narrative spine.
- Sitemap XML Canonical index of what you intend to be crawled—diff it when generators change.
Operator toolkits
Checklists and scripts you can lift into runbooks, vendor RFPs, or board appendices.
IR preparedness patterns; not a guide for specific securities offerings.