Portfolio Intelligence Platform
A unified portfolio platform: ETL pipelines from each portco system (Excel, QuickBooks, NetSuite, Sage, Stripe) plus third-party data (Preqin, Bloomberg), normalized to a single schema, exposed through cross-portco dashboards with covenant tracking and liquidity alerts.
- Engagement
- 12–20 week build · ongoing data ops
- Built for
- Operating partners · GP principals · Portfolio teams
Each portco has its own ERP, its own dashboards, its own monthly cadence. Operating partners see the book one portco at a time — by the time anomalies show up across the portfolio, two quarters have passed.
What this is
The data infrastructure layer that gives operating partners and GP principals a single, current view across the portfolio. Three planes:
- Ingestion. Per-portco connectors — API-based where the portco's stack supports it, monthly-export pipeline where it doesn't. Idempotent, retried, point-in-time.
- Normalization. Unified schema with per-portco mapping. Documented chart-of-accounts crosswalk, KPI reconciliation, currency normalization, intercompany elimination where relevant.
- Surface. Cross-portco dashboards (KPI rollups, sector benchmarking, covenant tracking), liquidity alerts, configurable drill-down per portco.
How it's built
Postgres or Snowflake as canonical storage, dbt for the transformation layer, Prefect or Airflow for orchestration. Dashboard layer in Metabase, Superset, or whatever your firm already uses — we'd rather plug into your existing BI than introduce another tool. Per-portco connectors built once, maintained as a recurring data-ops engagement.
What you get
- The unified schema, documented and versioned.
- Cross-portco dashboards in your existing BI layer.
- Liquidity and covenant alerts wired into your firm's alerting infrastructure.
- Data-quality monitoring that surfaces drift before it shows up in reporting.
- Runbook for the ongoing data ops.
Engagement is shape, not list.
Length and price are functions of the data and the destination. The shape below is the typical engagement.
- Length
- 12–20 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 · Private Equity Suite
Portfolio Forecasting Engine
Predictive forecasting models per portco — quarterly cash-flow and EBITDA projections trained on the portco's internal financials and sector-comparable data, with structured scenario planning (cost-cut sensitivity, price-elasticity scenarios, demand-shock testing) that feeds straight into the fund's valuation model.
- Same suite · Private Equity Suite
Pricing & Margin Optimizer
An ML layer on the portco's product, customer, and channel data — estimates price-elasticity per segment, identifies the margin levers worth pulling, simulates the impact of pricing and packaging changes before they ship.
- Same suite · Private Equity Suite
Post-Acquisition Integration Tracker
An NLP and ML layer that reads the recurring integration artifacts — board decks, weekly status reports, ops dashboards, strategy memos — extracts integration-milestone status, predicts timeline slippage, and surfaces missed synergies before board prep makes them visible.
What buyers ask about this one.
We've tried platform consolidation before and it failed because the portcos resisted. How is this different?
The integration runs against existing systems — we don't ask the portco to migrate their ERP. The portco gets a read-only connector (or a monthly export pipeline if real-time isn't feasible). The friction surface is small enough that it usually clears.
What's the schema?
A unified chart-of-accounts mapping with per-portco aliases, plus KPI definitions (gross margin, cash conversion, net retention, etc.) reconciled to your fund's reporting standards. Schema is documented and versioned — when a portco's accounting changes, the mapping updates without touching the dashboards.
What does covenant tracking actually look like?
For each portco's debt covenants, the platform tracks the relevant ratios monthly and surfaces ratios approaching thresholds 60–90 days before a breach. The operating partner gets the alert with the underlying trajectory; the finance team gets the workspace to model the cure path.
How do you handle data quality issues from a portco that runs its books on Excel?
Excel portcos are the common case in lower mid-market. The pipeline standardizes the templates, applies validation at ingest, and surfaces data-quality flags when the input drifts. We work with the portco finance team to fix structural issues; we don't pretend that bad data is good data.
Pricing?
Scoped to portfolio size, source-system complexity, and integration depth. Discovery call covers all three.
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