ComponentWhy it is unattributedcalls$ / run
Model · 32%Long-form synthesis (Claude Opus 4)The model ingests a stitched document context and produces a 4,000-8,000 token structured memo with section-level citations. Opus 4 is used for hallucination risk tolerance reasons.tokens in: 85,000 · tokens out: 6,500Visible on the invoice.3$1.76
Prompt · 10%IC memo template and section schemaA 12,000-token prompt encodes section headings, financial model hooks, risk taxonomy, and 4 full few-shot examples. Sent on every call without caching.tokens in: 36,000 · tokens out: 0Visible on the invoice.3$0.54
Orchestration · 10%Document ingestion and section routing agentsAn ingestion agent chunks and classifies source documents; a routing agent dispatches chunks to section-specific sub-calls; a merge agent assembles the output.tokens in: 22,000 · tokens out: 3,000Document ingestion and merge agents are instrumented as 'data pipeline' steps in engineering logs, not as LLM spend in the finance system.9$0.56
Retrieval · 4%Source document chunk retrievalEach section call retrieves the top-12 relevant chunks from the source document index. Re-embedding runs on every revision cycle even when source docs have not changed.tokens in: 42,000 · tokens out: 0Re-embedding unchanged source docs on revision runs is a known inefficiency; the cost is buried in the embedding vendor line rather than the deal P&L.18$0.20
History · 32%Prior memo draft re-injection on revisionsRevision runs prepend the full prior memo draft to the model call context so the model can diff its own output. A 5,000-token draft becomes 25,000 tokens re-billed across 5 revisions.tokens in: 48,000 · tokens out: 0Revision-cycle context is framed as 'draft history' by the application; it appears nowhere in the per-run cost breakdown visible to finance or risk.3$1.73
Connectors · 12%DealCloud, PitchBook, Box, and Salesforce connectorsThe run pulls source documents from the Box data room, comps from PitchBook, and sourcing context from Salesforce, then writes the completed memo and IC status back to the DealCloud deal record. Each external pull is normalized into memo-section inputs by an LLM mapping step, and revision runs re-pull unless cached.tokens in: 22,000 · tokens out: 1,600The PitchBook pull is on the data-vendor contract, the Box data-room reads on the storage tier, and the DealCloud write-back on the deal-CRM plan; none is attributed to the deal's memo P&L.10$0.66
An investment memo costs ~$5.45 to generate; revision cycles mean 58% of the $24.5k/yr total is prior-draft re-injection plus DealCloud/PitchBook/Box connector pulls repeated on every edit nobody is tracking.