VENTURE CAPITAL OPERATING SHELL
A workflow for deal intake, research, diligence, investment decisions, portfolio monitoring, reporting, and fund operations.
Manage the active venture workflow session, reopen saved work, and keep intake, diligence, portfolio, and reporting context in one place.
Capture inbound deals in a standard format, classify them against the firm taxonomy, score thesis fit, and route to the right owner.
Generate the standard pre-call research brief and then expand into structured diligence with reusable artifacts.
Draft a structured research package covering market, founder background, competitors, comparables, and news monitoring.
Build the standard diligence checklist, parse the data room, and score key risks before IC memo drafting.
Structure the diligence process, capture evidence, and assemble the material needed for a disciplined investment decision.
Convert diligence into a draft IC memo, clear recommendation, and a scannable decision package for the partners.
Define the KPI template, alert thresholds, and the questions the firm should ask portfolio companies every month or quarter.
Capture the investment decision formally, preserve the rationale, and generate partner- and firm-facing communications.
Draft quarterly LP updates, company spotlights, and fund-performance narratives from live portfolio data.
Define workflow triggers, FinOps controls, telemetry, and the integrations/admin foundations that turn separate skills into an operating system.
Monitor portfolio companies through standard KPI extraction, follow-up agendas, reporting, and continuous optimization.
Build the KPI extraction layer, flag deviations, and surface the companies that need partner attention first.
Expose runway, growth, red/amber/green status, and cross-portfolio questions in one dashboard.
Wire CRM, email, data room, RBAC, SSO, MFA, export APIs, and the audit trail that regulated funds require.
Keep platform adapters agnostic. Configure the providers in Settings, then use this tab as the launch point for tickets, information radiators, and integration packets.
Connect a ticketing / workflow system in Settings. Example: Jira or another tracker.
Connect an information radiator workspace in Settings. Example: Confluence, Notion, or another reporting hub.
Package deal flow, reporting, orchestration, and platform-governance context into a reusable implementation packet.
Configure the integration target in Settings, then generate a reusable packet from the active venture workflow session.
Token visibility lives here so the shell stays clean and Settings remains the single configuration surface.
User-level credentials override server config. Leave a field blank to keep the current stored value.
Keep the shell agnostic. Define the ticket workspace and information radiator workspace here, then the Reporting tab will use these settings for VC operations.
Define the integration target once, then venture workflow sessions can generate an implementation packet and launch the destination from Reporting.
Connected. Tap a skill or say “Hey SassiE”.