studio / fund infrastructure

// studio

Studioforfunds

A HIPAA-compliant platform where fund teams build their own IC memos, LP decks, and portfolio dashboards in natural language, wired to live deal data.

Fund teams use Studio to assemble IC memos, LP decks, and portfolio notes from diligence files, claims, and model tables. Each artifact keeps its source, owner, audience, and approval state. Drafts update as deal facts change, and nothing leaves without a review trail.

Trace the work Talk to us

Healthcare systems

Human review

Workflow proof

Studio - fund infrastructure view

source map / task / review

Source and review

Evidence before the memo.

Review required

CIMs, QoEs, VDR files, CRM paths, model tables, IC drafts, LP decks, and portfolio updates show where claims came from, who reviewed them, and which audience can see the draft.

QoE variance

$3.8M

Adjusted EBITDA delta tied to reviewed addbacks.

Deal score

Healthcare services rubric with citations and owner notes.

Open items

Requests grouped by finance, operations, market, and legal owner.

IC deck

Slides rebuilt from approved claims and the fund template.

Deal boundary

Roles, audience, audit trail

Source intake

VDRs, CRMs, files, notes

Fund rubric

Evidence and overrides

Review record

IC, LP, portfolio updates

studio

Operating layer

Ask

Scoped deal room

Which diligence claims changed this week?

Score

Partner review

Apply the fund rubric with evidence.

Build

Versioned draft

Prepare IC, LP, and operating materials.

Approved

Export after audience checks.

Pipeline

CRM

Banker, founder, and advisor paths

Diligence

VDR

CIMs, QoE files, addenda

Process

Questions, notes, requests

Modeling

Sheets

Operating metrics and cases

How the fund work starts

The deal record comes before the IC memo.

Studio - fund source view

diligence / IC / portfolio

Deal record

Facts, claims, and open questions stay in one record.

Deal facts, diligence claims, draft memos, and review state stay connected.

Deal rooms

Active processes with scoped access.

Review state

Claims waiting for partner or operator review.

Pipeline

Live

Advisor notes and market context in one review list.

Diligence

In review

Claims, sources, and open requests attached.

Outputs

Draft

IC memo, LP note, and operating plan share facts.

01 / Fund record

Start with a single deal record.

Seller files, analyst notes, CRM paths, models, and draft decks land in one place. Each claim or table keeps its source link and reviewer. The IC memo starts from facts, not fragments.

Deal setup includes roles, sources, and audience boundaries up front.

Analysts and partners see every draft with its source and reviewer.

IC memos and LP decks show their evidence trail before export.

Studio - fund source layer

connectors / files / review

Source layer

Every source file stays mapped to its claims.

Seller materials, fund notes, market research, and financial files keep their source trail.

Scoped

CRM

Pipeline

Banker, founder, and advisor paths

Mapped

VDR

Diligence

CIMs, QoE files, addenda

Reviewed

Email

Process

Questions, notes, requests

Versioned

Sheets

Modeling

Operating metrics and cases

Cited

Market

Research

Comps, claims, context

Tracked

Portfolio

Post-close

KPI watchlists and initiatives

02 / Intake

Map every CIM, QoE file, CRM note, and spreadsheet.

VDR exports, CIMs, QoEs, CRM exports, spreadsheets, and notes land with their source and owner visible. No hidden handoffs. No pretending every file is clean. Every claim keeps its origin.

VDRs, CRMs, spreadsheets, and notes share a single intake.

Each claim shows its source file and owner.

Analysts see what is missing or provisional before review.

Studio - diligence room

claims / questions / evidence

Diligence room

Claims from CIMs and QoEs become a reviewable list.

The team sees which claims have evidence and which need more work before IC.

Claims

Diligence claims with source context.

Open asks

Requests grouped by owner.

Growth

Open

Referral expansion claim needs same-store support.

Margin

Matched

Labor bridge reconciles with staffing file.

Technology

Flagged

Scheduling workflow has three manual handoffs.

03 / Diligence room

Extract claims from CIMs and QoEs into a review list.

Analysts extract growth claims from CIMs and addbacks from QoEs. Each claim links to its page or file. Follow-ups are grouped by owner so nothing gets dropped before IC review.

Claims become a review list tied to original files.

Open questions are assigned by function: finance, operations, market, legal, and technology.

Every conclusion links back to the material that supports it.

Studio - deal scoring

rubric / evidence / override

Fund rubric

Scores show their supporting claims and overrides.

Weighted criteria link to evidence, and partner notes stay attached.

Durability

Recurring demand and payer exposure.

18 / 20

Workflow debt

Manual handoffs technology reduces.

16 / 20

AI fit

Administrative drag with inspectable outcomes.

14 / 20

Sensitivity

Provider, patient, and compliance sensitivity.

High review

04 / Deal scoring

Score each claim with evidence, never just a number.

Each score is an argument tied to claims and files. Partners can override with a note that stays in the record. The rubric improves as deals pass or close.

Scores are structured arguments with links to evidence.

Partners override with a note that remains part of the record.

The rubric improves as deals move through review.

Studio - IC builder

memo / deck / appendix

IC materials

IC memos assemble from reviewed claims and files.

A partner traces each claim to its source before signoff.

Draft artifact

Versioned

Memo

Investment thesis and key risks drafted.

Deck

Operating bridge and market page updated.

Appendix

Needs check

Sensitivity table linked to model assumptions.

05 / IC builder

Build IC memos from reviewed claims, not copy-paste.

The IC memo pulls from reviewed claims and files, not fragments copied between decks. Partners can challenge any fact, risk, or model assumption before distribution.

IC memos use approved claims, not scattered highlights.

Open questions stay visible through drafting.

Financial and operating claims keep source links until distribution.

Studio - LP presentation

audience-safe export

LP-ready materials

LP decks show approved summaries with a redaction log.

Every LP update records what was held back and who approved what left the room.

Draft artifact

Versioned

Internal

Restricted

Deal risk, diligence gaps, and partner notes.

LP draft

Review

Approved summary with sensitive details removed.

Export

Held

Presentation package with approval log.

06 / LP materials

Redact sensitive details before LP decks leave the room.

Internal risk notes stay inside. LP decks show approved summaries. Each export keeps a log of redactions and approvals before anything leaves the room.

Internal risk notes are held back; LP language is reviewed for audience.

Sensitive facts stay inside; summaries move out with approval.

Exports log redactions and reviewer signoff.

Studio - model router

frontier / private / cost

Model routing

Each extraction or draft run shows its route and reviewer.

No model run moves forward without sensitivity, reviewer, and approval state logged.

Frontier

Long context

CIM, QoE, contracts, notes.

Private

Extraction

Tables, schedules, fields, claims.

Reviewed

Drafting

IC memo and LP language.

Logged

Scoring

Rubric labels and confidence.

07 / Model routing

Route extraction and drafting by sensitivity and reviewer.

Extraction jobs for tables and claims follow stricter routes for sensitive material. Narrative drafts wait for partner review before they reach a deck or memo.

Extraction, drafting, and classification jobs use different routes.

Sensitive files stay inside stricter boundaries.

Model runs log provider, cost, and reviewer for each job.

Studio - browser run

portal / export / evidence

Portal bridge

Portal exports are logged with screenshots before use.

Screen work gets logged as evidence before it touches deal artifacts.

Open

Started

Data room export with stale folder structure.

Capture

Logged

Download, screenshot, file hash, and notes.

Hold

Waiting

Analyst approves before score or deck update.

08 / Portal work

Log every portal export or screen capture before use.

When data comes from a portal, stale VDR export, PDF, or admin screen with no API, the analyst logs screenshots or exports as evidence. No update hits a deck until someone reviews the run.

Every portal export or screenshot is logged as evidence.

Analysts approve before data affects any artifact.

No blind copy-paste from portals into memos or decks.

Studio - portfolio monitor

post-close tracking

Portfolio bridge

Portfolio KPIs trace back to original diligence claims.

Post-close tracking links each number back to its original assumption.

Revenue bridge

On plan

Referral capture and payer mix against base case.

Workflow

Compounding

Intake cleanup moved from pilot to weekly cadence.

LP note

Draft

Approved update assembled from operating evidence.

09 / Portfolio monitor

Track original diligence claims through post-close KPIs.

Revenue bridges and KPI watchlists start from original diligence assumptions, not a scramble after close. Portfolio updates show what changed since investment.

Operating plans start from the original investment case.

KPIs and owner notes keep source, owner, and version attached.

LP updates draw from approved progress, not last-minute assembly.

Studio - governance

logs / approvals / audience

Governance

Every artifact carries its reviewer log and version history.

No memo or deck leaves without source state, approvals, and audience boundaries visible.

Boundary

Scoped

Deal, audience, and user role checked.

Lineage

Cited

Claims trace back to original material.

Approval

Held

Partner signoff required before export.

10 / Governance

Every memo or deck carries its source trail and approval log.

Partners see who approved each claim or artifact. LP exports stay separate from internal notes. Every memo and deck carries its boundary, reviewer log, and version history.

Partners see who approved each memo or deck.

Internal notes stay inside; exports show their audience check.

Every artifact carries its reviewer log and version history.

01 / Fund record

Start with a single deal record.

Seller files, analyst notes, CRM paths, models, and draft decks land in one place. Each claim or table keeps its source link and reviewer. The IC memo starts from facts, not fragments.

Deal setup includes roles, sources, and audience boundaries up front.

Analysts and partners see every draft with its source and reviewer.

IC memos and LP decks show their evidence trail before export.

02 / Intake

Map every CIM, QoE file, CRM note, and spreadsheet.

VDR exports, CIMs, QoEs, CRM exports, spreadsheets, and notes land with their source and owner visible. No hidden handoffs. No pretending every file is clean. Every claim keeps its origin.

VDRs, CRMs, spreadsheets, and notes share a single intake.

Each claim shows its source file and owner.

Analysts see what is missing or provisional before review.

03 / Diligence room

Extract claims from CIMs and QoEs into a review list.

Analysts extract growth claims from CIMs and addbacks from QoEs. Each claim links to its page or file. Follow-ups are grouped by owner so nothing gets dropped before IC review.

Claims become a review list tied to original files.

Open questions are assigned by function: finance, operations, market, legal, and technology.

Every conclusion links back to the material that supports it.

04 / Deal scoring

Score each claim with evidence, never just a number.

Each score is an argument tied to claims and files. Partners can override with a note that stays in the record. The rubric improves as deals pass or close.

Scores are structured arguments with links to evidence.

Partners override with a note that remains part of the record.

The rubric improves as deals move through review.

05 / IC builder

Build IC memos from reviewed claims, not copy-paste.

The IC memo pulls from reviewed claims and files, not fragments copied between decks. Partners can challenge any fact, risk, or model assumption before distribution.

IC memos use approved claims, not scattered highlights.

Open questions stay visible through drafting.

Financial and operating claims keep source links until distribution.

06 / LP materials

Redact sensitive details before LP decks leave the room.

Internal risk notes stay inside. LP decks show approved summaries. Each export keeps a log of redactions and approvals before anything leaves the room.

Internal risk notes are held back; LP language is reviewed for audience.

Sensitive facts stay inside; summaries move out with approval.

Exports log redactions and reviewer signoff.

07 / Model routing

Route extraction and drafting by sensitivity and reviewer.

Extraction jobs for tables and claims follow stricter routes for sensitive material. Narrative drafts wait for partner review before they reach a deck or memo.

Extraction, drafting, and classification jobs use different routes.

Sensitive files stay inside stricter boundaries.

Model runs log provider, cost, and reviewer for each job.

08 / Portal work

Log every portal export or screen capture before use.

When data comes from a portal, stale VDR export, PDF, or admin screen with no API, the analyst logs screenshots or exports as evidence. No update hits a deck until someone reviews the run.

Every portal export or screenshot is logged as evidence.

Analysts approve before data affects any artifact.

No blind copy-paste from portals into memos or decks.

09 / Portfolio monitor

Track original diligence claims through post-close KPIs.

Revenue bridges and KPI watchlists start from original diligence assumptions, not a scramble after close. Portfolio updates show what changed since investment.

Operating plans start from the original investment case.

KPIs and owner notes keep source, owner, and version attached.

LP updates draw from approved progress, not last-minute assembly.

10 / Governance

Every memo or deck carries its source trail and approval log.

Partners see who approved each claim or artifact. LP exports stay separate from internal notes. Every memo and deck carries its boundary, reviewer log, and version history.

Partners see who approved each memo or deck.

Internal notes stay inside; exports show their audience check.

Every artifact carries its reviewer log and version history.

Studio - fund source view

diligence / IC / portfolio

Deal record

Facts, claims, and open questions stay in one record.

Deal facts, diligence claims, draft memos, and review state stay connected.

Deal rooms

Active processes with scoped access.

Review state

Claims waiting for partner or operator review.

Pipeline

Live

Advisor notes and market context in one review list.

Diligence

In review

Claims, sources, and open requests attached.

Outputs

Draft

IC memo, LP note, and operating plan share facts.

Diligence. IC. LPs. Portfolio.

The memo moves faster because the source trail is already there.

truesilver sets up intake paths for VDRs, CRMs, models, and notes so analysts build IC memos and LP decks from tracked claims, not scattered files. Every artifact keeps its source trail and approval log from diligence through portfolio monitoring.

Start a conversation Replay the tour

What changes for the fund

Cycle time

Diligence and deck work move from ad hoc assembly to source-backed drafts.

Defensibility

Claims, scores, and LP language keep source trail and approval state.

Leverage

Rubrics and templates improve across deals instead of resetting.