Portfolio Pulse Dashboard
A portfolio dashboard built on direct integrations into the systems your portcos already use — Stripe for revenue, Mercury for cash, AWS/GCP billing for technical-spend, GitHub for engineering velocity. Read-only, opt-in per portco, refreshed daily.
- Engagement
- 8–12 week build · ongoing data ops
- Built for
- Partners · Portfolio teams · Platform team
Visible.vc and Standard Metrics work — if your portcos consistently upload their monthly data. They never consistently upload. The result is partial visibility, lagging by weeks, with the same partner emails asking for the same updates.
What this is
A portfolio monitoring platform built around the principle that data should come to the fund, not the other way around. Three layers:
- Integration layer. Read-only OAuth integrations into the systems portcos already use. Each integration is opt-in, scoped, and revocable by the portco.
- Canonical metric layer. Per-portco data normalized to fund-standard metrics — revenue, gross margin, cash runway, customer count, churn (where computable), engineering velocity.
- Cross-portco surface. Partner-side dashboard with anomaly detection, drill-down per portco, configurable alerting.
How it's built
OAuth integration adapters per source, Postgres for canonical storage, dbt for the metric normalization layer. Dashboard in Metabase or a custom UI per fund preference. Anomaly detection runs at the canonical metric layer — declarative thresholds for the common patterns (runway shortening, revenue stall), classifier-based detection for the subtler cases.
What you get
- The integration adapters per source — maintained as ongoing data ops.
- The canonical metric layer with documented definitions.
- The partner dashboard with drill-down and alerting.
- Weekly partner summary email.
- Per-portco onboarding playbook for the integration-grant conversation.
Engagement is shape, not list.
Length and price are functions of the data and the destination. The shape below is the typical engagement.
- Length
- 8–12 week build · ongoing data ops
- Lead
- Bogdan
- Cadence
- Async, weekly
- Bar
- Production
Scoped during the discovery call against the actual data and the operation it integrates with.
Principal engineer. Architecture and most code ships through one keyboard.
Written updates between, calls when the decision needs the room.
Async correctness, capacity under burst, observability at every boundary.
Products this composes with.
Same suite, or vertical-specialized versions in another.
- Same suite · Venture Capital Suite
Follow-on Decision Engine
A decision-support layer that takes the fund's reserves, the portco's current performance and trajectory, and the round terms — outputs a structured recommendation against the fund's discipline rules with documented assumptions.
- Same suite · Venture Capital Suite
Fund Communications Engine
An LLM-and-templating layer covering the fund's recurring and one-off communications — investor updates, LP letters, fundraise materials (data room, pitch deck) — drafted from portfolio data with the fund's voice and finalized by the IR team.
What buyers ask about this one.
Will portcos actually agree to read-only API access?
Most early-stage portcos agree — the alternative is them filling out the fund's monthly form, and read-only API access is less work for them. The integration ask is explicit about scope (financials only, no customer PII, no employee data) and reversible (they can revoke any time). Adoption rate in our experience is meaningfully higher than upload-form adoption.
Which integrations are supported?
At launch: Stripe (revenue and customer count), Mercury (banking and cash position), AWS / GCP / Azure billing (technical spend trajectory), GitHub (commits, PRs, contributor count as engineering proxy). Per-engagement we add the ones the fund's portfolio uses heavily — common adds: Vanta (compliance posture), Linear (product velocity), HubSpot (top-of-funnel).
What about portcos that won't grant API access?
Fall back to the upload-form pattern; the dashboard handles both flows. The point is to make access frictionless for the portcos who'll grant it, not to gate the portfolio view on universal adoption.
What's the partner-side experience?
Cross-portco dashboard — sortable by metric, drillable per portco. Plus an anomaly-detection layer that flags portcos with material deviation from their trajectory (revenue stall, cash runway shortening faster than burn, eng velocity dropping). The partner gets a weekly summary.
Pricing?
Scoped to portfolio size and integration breadth. Discovery call covers both.
If the deliverable matches the gap, the next step is one call.
We'll scope length and price against your data and the operation it integrates with. No retainer, no fishing.
Bogdan and team · async-first · OP—2026