Library/Elements/Annotated review
Decision-making · Document review · Internal

Margin notes, severity tagged.

A document with annotations pinned to the exact words they're about. Each note is tagged must-fix / should-discuss / nit. Click a highlight in the doc to focus its note; click a note to jump back. Beats tracked-changes hell for deck reviews, contract redlines, content reviews, proposal reviews.

Pitch deck draft · Aspen Wealth

v2 · in review · 7 annotations

Slide 1 — Cover

"Aqua: the modern operating system for alts." Subtitle: A new chapter for Aspen Wealth's investment platform.

Slide 2 — The problem

Wealth managers are losing share to advisors who can offer alternatives at scale. The bottleneck isn't access — it's manual ops. Sub docs, K-1s, capital calls, statements: every alt fund adds a permanent ops tax.

Slide 3 — Aspen's current state

Aspen runs $1.4B AUM across 38 advisors. Today, alts are ~6% of book — limited by operational drag. Average new-position onboarding takes 14 business days end-to-end, with five hand-offs between client, advisor, ops, and admin.

Slide 4 — Aqua's three-part fix

One: AIX connects your custodian + admin + reporting into one operating layer. Two: Access Vehicles provides feeders and SPVs you don't have to build yourself. Three: Document Intelligence auto-extracts every doc that hits the inbox. Result: 42% ops time saved, 14-day onboarding compressed to 36 hours.

Slide 5 — What Aspen sees on Day 1

Branded advisor portal. Investor statements in Aspen's voice. Allocation drift alerts. A live alts patchwork audit of your current book. Plus access to our Marketplace of 12 sponsor partners with negotiated terms.

Slide 6 — Numbers

Aqua-served advisors at firms your size see 2.4× alts share growth in year one. Median ops cost falls 38%. We expect Aspen to reach 14% alts allocation by end of Year 1, 22% by end of Year 3.

Annotations

Must fix2
Should discuss3
Nits2

Fork & ship

Each annotation in the doc is a <span class="anno"> wrapping the relevant words, with severity classes (must / default should / nit) and a data-id. The right panel reads NOTES array and binds clicks both ways.

const NOTES = {
  n1: { severity: "must", who: "Appa",
        text: "Headline too generic. Lead with the AAS-specific framing." },
  // ... etc
};

When to use this

Deck review, content review, contract redlines, copy review, proposal feedback. Anywhere a Google Docs comment thread is more friction than help. Especially useful for design + copy crits where the structure of the doc matters as much as the words.

Reuse ideas

Legal redline of MSA, customer-deck feedback round, RFP-response review, blog post copy-review, press-release approval flow.