VC Portfolio Tracking Software: Metrics, Anomalies, and LP Reporting

Portfolio monitoring is the operational function that most directly serves the fund's core purpose: generating returns. Yet it's also the function most commonly handled through informal, inconsistent processes — a mix of founder emails, board deck slide decks, quarterly Notion updates, and whatever the GP can remember from their last call.

The gap between what GPs know about their portfolio and what's actually happening is often wider than they realize. A founder who reports "things are going well" in a monthly call is not necessarily reporting the same information as a company with $200,000 ARR, $180,000 monthly burn, and 11 months of runway that's been quietly missing revenue targets for two quarters. The difference between those two information states can be the difference between a proactive extension round at a defensible valuation and a distressed recap at 70% dilution.

This guide covers what metrics to track, how to collect them systematically, how anomaly detection works as an early warning system, how portfolio data connects to LP reporting, and how to choose between spreadsheet and software-based tracking approaches.

What to Track: The Essential Portfolio Metrics

Not all metrics matter equally for all companies. A pre-revenue company has no ARR to track; a Series B company with 200 employees has different burn dynamics than a 5-person seed company. The right metrics framework acknowledges these differences while maintaining enough consistency to aggregate across the portfolio.

Universal Metrics (Every Company, Every Quarter)

ARR / MRR. Annual recurring revenue and monthly recurring revenue are the foundational SaaS metrics, but analogous revenue metrics apply to non-SaaS companies: GMV (marketplaces), transaction volume (fintech), revenue (direct consumer), contracted revenue (B2B services). Every portfolio company should report a primary revenue metric every quarter.

MoM or QoQ Growth Rate. The growth rate matters as much as the absolute number. A company with $500K ARR growing 15% MoM is in a very different position than one with $1M ARR growing 2% MoM. Track the growth rate explicitly, not just the level.

Burn Rate. Monthly net cash outflow (gross burn minus revenue). The single most operationally critical metric for early-stage companies. Burn rate changes that aren't explained by strategic decisions are a major warning signal.

Runway. Cash on hand divided by monthly net burn. Express in months. This number tells you when you need to be paying attention, not afterward. A company at 18 months of runway is fine. A company at 6 months of runway needs active engagement now.

Headcount. Total employees and any significant headcount changes (hires or terminations). Headcount is a leading indicator for both burn rate changes and organizational stress. Unexplained headcount reductions are a significant warning signal.

Cash Position. Total cash and equivalents on hand. Independent of runway calculation — some companies have receivables or credit facilities that affect effective runway but don't show up in cash position.

Stage-Appropriate Additional Metrics

Pre-product companies (pre-revenue): - Milestone progress (product development, regulatory approval, customer discovery) - Pilot or LOI count and status - Team completion (key hires made/still needed) - Runway (most critical at this stage)

Early revenue companies ($0-$1M ARR): - MRR and MoM growth - Customer count and churn - Customer acquisition cost (CAC) — even if directional - Net revenue retention (early signal of product-market fit) - Gross margin

Growth stage companies ($1M+ ARR): - Full unit economics: CAC, LTV, CAC payback period - Net revenue retention (NRR) - Sales efficiency (new ARR / sales spend) - Gross margin by segment - Product engagement metrics (DAU, MAU, feature adoption) - Pipeline and forecast

Hardware, biotech, and non-SaaS: - Domain-specific KPIs: clinical trial milestones, manufacturing yield, regulatory submission status, SKU-level economics - These require custom metric definitions in your tracking system

Valuation Metrics

Portfolio valuations for venture-backed companies are almost always marked to last round (the most recent priced financing round) in the absence of a more recent valuation signal. The exceptions are material write-downs (when a company's trajectory is clearly below the valuation implied by the last round) and write-ups (when an objective valuation event — an acquisition offer, a financing round with new investors — establishes a higher fair market value).

Track for each company: - Valuation at investment (entry price) - Current valuation (last round, with date) - Your ownership percentage (post all dilutive events to date) - Implied portfolio value (current valuation × ownership) - MOIC (implied portfolio value / cost basis)

This is the data that flows into your fund-level TVPI calculation. It needs to be accurate and updated after every funding event in the portfolio.

Building a Founder Reporting System

The metrics are only useful if you actually get them. Systematic founder reporting — not ad hoc when you ask, but on a defined cadence — is the operational foundation of portfolio monitoring.

Setting Up the Reporting Relationship

In the weeks after closing an investment, establish the reporting relationship explicitly:

1. Define the metric set. Send the founder a clear list of what you'll track, at what frequency, and why. Founders who understand the purpose of the reporting (it helps you identify companies that need help proactively, not just flag failures reactively) are more likely to report honestly.

2. Set the cadence. Quarterly is the minimum standard for most early-stage companies. Monthly is appropriate for companies within 9 months of anticipated fundraising or companies showing stress signals. Bi-annual is acceptable only for very early pre-revenue companies with slow-moving milestones.

3. Create a submission mechanism. This can be a short form, a structured email template, or a founder portal. Whatever it is, make it as frictionless as possible. Founders who have to spend 2 hours preparing quarterly data for their investors are less likely to do it consistently. The submission should take 20-30 minutes maximum.

4. Automate the request. Don't rely on remembering to ask. Schedule the data collection request to go out automatically on the first day of the month following each quarter end. Automated reminders 7 and 14 days later for non-respondents. This removes the human memory dependency from the collection process.

What Good Founder Reporting Looks Like

A founder quarterly report should include: - Key metrics for the quarter (pre-populated fields, not a blank form) - Narrative on what drove the results (brief — 3-5 sentences) - Top priorities for next quarter - Help requested from investors (introductions, advice, resources) - Anything the investor should know that isn't captured in the metrics

The "help requested" field is often the most valuable. It's a real-time signal of where your portfolio companies are struggling and where you can add value. A founder who fills this in with "need introductions to Series A leads in enterprise SaaS" is telling you what to do this week.

Handling Non-Reporters

Some founders won't submit on time, some won't submit at all. The appropriate escalation:

Day 1-7 past due: Automated reminder from the system.

Day 8-14 past due: Personal email from you, brief and direct: "Hey [name] — just following up on the Q3 update, I haven't received it yet. Anything I can do to help or is there a better format that would make this easier?"

Day 15+ past due: Direct call. Not aggressive, but present. The failure to report is usually either busyness (startup chaos), disorganization, or avoidance of bad news. The call surfaces which it is and addresses it directly.

A founder who consistently fails to report — after good faith engagement on your end — is signaling something. Either the relationship has broken down, the company is in serious distress and they don't want to report it, or they don't take their investor obligations seriously. All three of these are important to know.

Anomaly Detection: Early Warning Signals

The most operationally valuable function of portfolio monitoring is not trend reporting — it's anomaly detection. Surfacing unusual patterns before they become crises is where portfolio monitoring generates direct financial value.

What Anomalies Look Like

Sudden burn spike. A company that's been burning $180K/month increases to $250K/month without a corresponding explanation (major hire, marketing push, one-time expense). This could signal expense control breakdown, undisclosed hiring, or financial distress spending.

Revenue plateau or decline. A company with consistent 10-15% MoM growth goes flat or negative for two consecutive months. This could signal customer concentration (loss of a major account), product issues, increased churn, or market shift. Early detection allows for early intervention.

Runway compression. A company that had 18 months of runway now has 11 months, but the burn rate is roughly unchanged. If cash has decreased by more than the expected amount, investigate immediately. Cash management surprises in portfolio companies are a serious flag.

Headcount reduction without disclosure. If your monthly headcount tracking shows a reduction you weren't told about, that's a problem. Layoffs are a major company event that boards are typically informed about in advance. Learning about them through your own tracking rather than the founder is a governance failure.

Non-reporting itself. A company that has reported consistently for six quarters and then misses two consecutive quarters is more concerning than a company that has always been inconsistent. The pattern change is the anomaly.

Metric deterioration in multiple dimensions simultaneously. Growth slowing while burn is increasing and headcount is declining is not three isolated signals — it's a single compound signal of serious company distress. Correlation across metrics amplifies the concern.

Building an Anomaly Detection Framework

Simple anomaly detection is achievable without machine learning. The logic:

1. For each metric, calculate the average and standard deviation over the past 4-6 quarters
2. Flag any reading that falls more than 1.5-2 standard deviations from the trailing average
3. Weight the flags by risk severity (runway under 9 months = high severity; revenue plateau for 1 month = medium severity)
4. Surface the flagged companies in a weekly portfolio review

This gives you a structured, consistent process for identifying which portfolio companies need attention, rather than relying on intuition or whatever you happened to last discuss with a founder.

More sophisticated implementations use predictive modeling — correlating current metric patterns with historical outcomes for similar companies — to generate probability-weighted risk assessments. This is what institutional funds with large portfolios do. For an emerging fund with 15-25 companies, the simple framework above captures most of the value.

Archstone's portfolio tracker includes built-in anomaly detection that flags portfolio companies showing unusual metric patterns — automatically surfaced in the dashboard so you're not relying on manually scanning 20 company snapshots each week.

From Detection to Intervention

Anomaly detection is only valuable if it drives action. The appropriate response to a detected anomaly:

Mild anomaly (single metric, one quarter): Schedule a brief check-in call with the founder. Don't alarm — frame it as a proactive touchpoint. "Hey, I noticed your burn ticked up a bit last quarter, just wanted to check in." This either reveals an explanation (one-time expense, hiring) or surfaces a real issue early.

Moderate anomaly (multiple metrics or two consecutive quarters): Request an off-cycle update and a call. "I'd love to spend 30 minutes going through Q3 in more detail — there are a few things I want to make sure I understand." Bring specific data to the call.

Serious anomaly (runway under 9 months, revenue declining, headcount reduction): Immediate escalation. This company needs active board engagement, and the GP needs to be in direct, frequent contact with the founder. If you're on the board, an emergency board call is appropriate. If you're not on the board, activate your investor rights and ensure you're getting the information you're entitled to.

How Portfolio Data Feeds LP Reports

LP reporting is not a separate function from portfolio monitoring — it is the output of your portfolio monitoring system. If you have clean, current portfolio data, LP report preparation is a matter of formatting and narrative. If you don't, LP report preparation requires reconstructing information that should have been captured systematically.

The Data Flow

Portfolio metrics (collected from founders) → Portfolio tracker (aggregated, cleaned, trend-charted) → LP report (formatted, contextualized, narrativized)

This data flow should be nearly automatic. The quarterly LP report should pull directly from your portfolio tracker, not require fresh data collection or manual assembly.

What Goes Into the LP Report

Fund Performance Summary: - TVPI (Total Value to Paid-In): (unrealized value + distributions) / invested capital - DPI (Distributions to Paid-In): distributions / invested capital - RVPI (Residual Value to Paid-In): unrealized value / invested capital - Gross and net IRR (gross before fees and carry; net after) - Capital utilization: capital deployed / total capital committed

Portfolio Summary: - Number of companies in portfolio - Total invested capital - Current implied portfolio value (sum of company-level valuations × ownership) - Breakdown by status (active, follow-on, watch list, written down) - New investments in the quarter

Company Updates: For each active portfolio company, a brief update: revenue trend (directional, not necessarily specific numbers — many founders don't want specific financials in LP reports that circulate widely), major milestones, key hires, and investor perspective. This is where qualitative judgment adds value to the quantitative data.

Deals That Didn't Close: A brief note on significant deals you evaluated but passed on, and why. This demonstrates your decision-making process and gives LPs visibility into what you're seeing in the market.

Market Observations: 2-3 paragraphs on what you're observing in the market relevant to your thesis. Valuation trends, sector shifts, emerging opportunities. This is where your GP perspective adds unique value beyond the portfolio update.

Operational Notes: Management fee calculations for the quarter, any compliance items, fund expenses, and upcoming capital calls or distributions.

Frequency and Format

Quarterly LP reports are the standard. Delivered within 30-45 days of quarter end. For most emerging managers, the quarterly report is a 4-6 page document combining a narrative letter with structured tables.

Annual reports are more detailed and typically include: - Audited financials (if available) or a clearly labeled unaudited financial summary - Detailed MOIC and IRR calculations by company - Portfolio company performance summary with year-over-year comparisons - Management fee reconciliation - Carry calculation (accrued, not necessarily distributed)

Fund close reports (when a company in the portfolio has a significant exit or write-down event) should be sent within 2 weeks of the event. Don't wait for the quarterly cycle to inform LPs of a major portfolio event.

Spreadsheets vs. Portfolio Tracking Software

The honest assessment of the spreadsheet vs. software decision for portfolio monitoring:

When Spreadsheets Work Well

• - Portfolio of fewer than 10 companies
• - Single GP or very small team
• - Consistent data entry discipline (the spreadsheet is only as good as the data in it)
• - Simple metric set (no custom metrics, no complex aggregation)
• - LP reports done infrequently or manually assembled

If all of these apply, a well-designed Google Sheets portfolio tracker — with consistent formula logic, locked header rows, and a quarterly update cadence — is a functional approach for 2-3 years.

When Spreadsheets Break Down

Collaboration. Multiple people updating the same spreadsheet simultaneously is a recipe for version conflicts, overwritten data, and merged-cell disasters. If you have a team of two or more reviewing portfolio data, shared software beats shared spreadsheets.

Historical trend analysis. Spreadsheets store point-in-time data well, but trending metrics across quarters requires either duplicating data across tabs or building complex formulas. Software built for portfolio tracking stores time-series data natively and generates trend charts without formula maintenance.

Anomaly detection. A spreadsheet doesn't flag anomalies automatically. You have to review every number yourself to spot them. This works for a portfolio of 8 companies; it doesn't scale to 20 or 25.

LP report generation. Pulling portfolio data from a spreadsheet into an LP report is a copy-paste exercise that takes 2-4 hours per quarter and introduces transcription errors. Software with integrated reporting templates pulls current data automatically.

Data integrity. Spreadsheets have no data validation constraints — anyone can overwrite a formula, enter data in the wrong format, or delete a row by accident. Portfolio tracking software enforces data types, audit-trails changes, and prevents accidental data loss.

Founder portal integration. If your founders submit their quarterly metrics directly to a portal that populates your tracker automatically, you eliminate the data re-entry step entirely. Spreadsheets can't do this natively.

Evaluating Portfolio Tracking Software

Key features to require: - Metric tracking with time-series history (not just current-quarter snapshots) - Configurable metric definitions by company or sector - Automatic trend charts and portfolio-level aggregation - Founder data submission portal (email or web form that populates the tracker directly) - Anomaly flagging or alert configuration - LP report generation from tracker data - Integration with the fund's deal pipeline (so closed deals flow in automatically)

Integration considerations: A portfolio tracker that lives in isolation from the rest of your fund management stack creates the same data synchronization problem as a standalone deal flow tool. Your portfolio tracker should connect to your data room (company documents), LP portal (feeding quarterly reports), and fund accounting (informing NAV calculations and capital call logic).

An integrated fund management platform that includes portfolio tracking as one module among several — alongside the data room, LP portal, deal pipeline, compliance, and fund operations — eliminates the need to maintain separate systems and ensures data flows automatically across functions.

Building the Portfolio Review Rhythm

Portfolio monitoring software is only as valuable as the organizational habits built around it. The data doesn't act on itself.

A high-functioning portfolio monitoring rhythm includes:

Weekly portfolio scan (solo GP) or team meeting (multi-partner fund): Review the anomaly flags. Look at any companies that submitted data in the past week. Identify any companies with upcoming runway events (raising, fundraising process beginning).

Monthly check-in with active portfolio companies: Not necessarily a formal call — even a brief text or email exchange with each founder keeps the relationship current and surfaces early signals before they become crises.

Quarterly data collection cycle: Automated requests go out, reminders follow up, data is reviewed and entered, anomalies are escalated before the LP report is drafted.

Annual portfolio review: A formal review of every portfolio company — current trajectory, exit scenario modeling, pro rata exercise decisions for upcoming rounds, write-down or write-up decisions. This feeds the annual LP report and helps the GP maintain an accurate picture of portfolio health.

The combination of systematic data collection, anomaly detection, and a regular review cadence creates an early warning system that dramatically improves the odds of proactive intervention when portfolio companies hit turbulence. Most portfolio company deaths and distressed outcomes are not sudden — they're the result of problems that were visible weeks or months earlier to an investor who was paying close attention.

Portfolio monitoring is not an administrative function. It's the active practice of paying attention to the companies you're responsible for, with the discipline and systems to make that attention systematic rather than dependent on luck or founder transparency. Build the systems, build the habits, and the portfolio data will tell you what you need to know before it's too late to act on it.