Portfolio monitoring for private equity, built on bank feeds.
We encode your fund’s monitoring rules against the bank feeds each portco already has, so the weekly cash position across the portfolio maintains itself.
Official services partner of the platforms defining AI
NVIDIA
Anthropic
Seventeen companies, seventeen ERPs, one Excel tracker.
From fund operators we have sat with: operating partners and VPs at lower-mid-market funds, portco CFOs at founder-owned companies — not shopping for software, already burned by platforms that need portcos to report in.
The tracker lives in one person’s Excel
The operating partner hand-built a portfolio cash tracker parsing BAI bank files — the weekly liquidity view your 13-week model is trying to be, maintained by hand.
Every acquisition multiplies the systems
Five acquisitions in two years on disparate ERPs, one portco on a 14-year-old vertical ERP with heavy manual workarounds, and consolidation pain compounding with each deal.
The bank feed is the only unambiguous number
Portco ERP data arrives shaped by manual workarounds, so the operating partner trusts the bank feed instead — it is unambiguous, and everything else needs interpretation.
Answers exist somewhere, and stay unfindable
Portfolio companies run on legacy systems, often outside major metros; the answers exist inside them somewhere, but connecting sources and centralizing on a schedule never survives the week.
Every deck assembled by hand
Recurring investor and portfolio decks get hand-assembled at 10–12 hours of executive-assistant time each, so the firm’s picture of its companies runs a cycle stale.
Manual portfolio company reporting is a line item, not a feeling.
What the manual way looks like at a lower-mid-market fund running its tracker in one person’s Excel. Your numbers will differ — the first cycles we run in parallel put figures on yours before anything gets built.
From anonymized engagements — lower-mid-market funds, seven to seventeen portcos, sub-$250M revenue each
Liquidity reporting across the portfolio maintains itself.
No portal for portcos to adopt, no ERP standardization project — we encode the monitoring rules your operating partner carries, and the weekly report assembles from the bank feed.
- 01
Map what the fund monitors today
The Excel tracker that exists today — its accounts, its thresholds, its cadence, what “late” means per company — is the spec we start from.
- 02
Encode the monitoring rules
Which accounts, which thresholds, which covenant definitions per company — encoded against BAI bank feeds plus the reports each portco already produces. No ERP access required.
- 03
The weekly position maintains itself
Bank feeds land on schedule and the report assembles; anything the rules cannot reconcile — a missing feed, an unusual outflow — goes to an exception queue.
Cash flow forecasting services for PE-backed portfolios, without the portal project.
The fund-data platforms are priced and shaped for institutional funds, and every one of them requires portcos to report into the platform. Seventeen companies, seventeen ERPs, seventeen reasons the portal never gets updated.
The platforms hold whatever gets typed in; we encode your monitoring rules and read the bank feeds directly — our AI does the reading, while your encoded rules do the judging.
Led by Peter Enestrom.
Asked by operating partners and portco CFOs.
The straight answers, before you book anything.
Portfolio monitoring in private equity is the ongoing tracking of a fund’s portfolio companies between board meetings: cash position, liquidity, covenant headroom, and performance against plan. For lower-mid-market funds the hard part is rarely the analysis — it is getting reliable numbers out of companies that run on different systems, on a cadence the fund can act on.
Most funds choose one of two paths: standardize every portco on one reporting system, or read the data each company already produces. The first is an ERP project per company. The second reads bank feeds and the reports each portco already generates — the bank feed is unambiguous even where ERP data carries manual workarounds — and encodes the fund’s monitoring rules against both.
No. Monitoring runs on BAI bank feeds and the reports each portfolio company already produces — bank statements, the weekly cash summary, the board pack. No portco staff time is required, no portal gets adopted, and no ERP gets touched. Monitoring that depends on portco behavior change dies at adoption; reading beats asking.
A 13-week cash flow forecast is a weekly, transaction-level projection of cash receipts and disbursements over the coming quarter. Lenders and sponsors use it to see a liquidity squeeze early enough to act on it. It is a forecasting discipline, distinct from the weekly cash position monitoring tracks — one projects forward, the other reconciles what has already happened.
Read access to the company’s bank feeds — typically BAI files or a direct bank connection — and copies of the reports the company already produces, such as the weekly cash summary or board pack. That is the full ask: no ERP access required, which matters when five acquisitions in two years landed on disparate systems.
Start with one workflow.
Tell us where your team loses hours. We will come back with a straight answer on whether AI can help, what it would take, and what it would pay.