Altitude 7
Investor RelationsWorkflow

LP Question Response

Last updated April 27, 2026

What it does

Connect Cowork to the folder of prior letters, due diligence questionnaires, and your own memos. Paste an LP's question. Cowork drafts the response in your house style, citing the specific language you've used in prior letters, and flags anything that needs the CIO's eye. Consistency across LP comms is a real compliance and reputational concern — Cowork referencing prior language directly is materially safer than rewriting from memory.

What you need first

  • ·A folder containing prior quarterly letters, DDQs, and any pre-approved IR talking points
  • ·A short house-style note in your global instructions or a Skill (e.g., “we use plain language, no superlatives, lead with the number”)

The prompt

An LP just sent the following question:

"{PASTE LP QUESTION HERE}"

Draft a response, following these rules:

1. Search this folder for any prior coverage of this topic in our quarterly letters, DDQs, or IR talking points. Quote the language we've used.

2. If we've answered a similar question before, reuse the language verbatim where it still applies. Don't paraphrase what we've already said publicly — that creates inconsistency.

3. If the question goes beyond what we've covered, draft a response in our house style and explicitly flag the new content with [NEW] markers so the CIO can review it.

4. Keep the response under 200 words unless the question genuinely requires more.

5. End the draft with a "Sources" block listing every prior document you pulled from, with quoted excerpts.

6. Save as "{date}-LP-response-{topic}.md" in this folder.

What good output looks like

  • ✓A draft that reads like you wrote it
  • ✓Clear [NEW] markers wherever Cowork went beyond your prior corpus
  • ✓A Sources block at the foot — names of letters and quoted excerpts
  • ✓Under 200 words unless genuinely required

Make it a Skill

Save as lp-question-response. Pair it with a separate “house style” Skill that captures your IR voice — Claude will pull both in automatically when this Skill runs.

Common pitfalls

  • Don't skip the [NEW] markers. They're what makes this safe — the CIO can scan for new positioning before it goes out.
  • Curate the source folder. If outdated talking points are in the folder, Cowork will cite them. Move stale content out.
  • Final eyes are still yours. Cowork drafts; the CIO and IR head approve. The point is to skip the blank-page step, not the review.