Feature Request: Cross-Fund Price-Per-Share & SAFE Benchmarking



Summary
Decile should build a shared, company-level object for pricing data — priced-round price per share (PPS) and SAFE terms — aggregated across the GPs on your platform who hold a position in that company. Today each fund's Decile instance is an island. If ten different GPs hold Company X, Decile has ten independent, unreconciled data points sitting in ten separate accounts, and none of us can see the other nine. Surface that as a shared object and you turn Decile from a bookkeeping system into the pricing utility of record for the venture asset class.

The Problem
Early-stage investors write small checks at pre-seed and seed and routinely lose contractual information rights by the Series A or B. By the time a company reaches Series C or D, we often have no reliable way to know the current price per share short of emailing the founder directly and hoping they respond. That means our marks on older, smaller positions are frequently stale, guessed, or simply carried at last-round cost long after the company has repriced multiple times in either direction.

This isn't a hypothetical. I'm currently running a reconciliation across our own fund between Decile, our internal Airtable, and our management schedule, and the discrepancies are exactly the kind of thing this feature would catch automatically instead of manually. Every GP on your platform has some version of this problem. You're sitting on the data to fix it and you're not using it.

Proposed Feature

1. Priced-round price per share, aggregated by company

For any portfolio company held by two or more funds on Decile, surface:
  • Latest price per share on file across all contributing funds, with the date and round name attached to each data point
  • Highest price per share in the system for that company, and which fund/round it corresponds to
  • Lowest price per share in the system for that company, and which fund/round it corresponds to
  • Median and count of contributing marks, so a GP can tell whether they're an outlier of one against a group of nine, or whether the "market" itself is only two data points deep and shouldn't be trusted
  • Your own fund's current mark shown side by side against that range, with a flag if you're above the highest peer mark or below the lowest

2. Do the same for SAFEs

SAFEs need their own version of this because they don't have a clean single "price" the way a priced round does. At minimum:
  • Valuation cap (and whether it's pre-money or post-money) — highest, lowest, latest, median across contributing funds
  • Discount rate, if any
  • MFN status and whether an MFN clause has since been triggered by a later, more favorable SAFE
  • Conversion status (converted / outstanding), and if converted, into what round and at what terms

3. A reconciliation and audit view for fund accounting

This is the actual deliverable GPs will pay for. Not just the numbers, but the workflow:
  • A per-portfolio-company report showing "here's what you're marked at, here's what the system-wide range is, here's the delta"
  • A portfolio-wide audit report that surfaces every position where a fund's mark falls outside the peer range (either direction), sorted by dollar impact so the biggest valuation errors surface first
  • A prompt, at the point a GP is about to lock a quarterly mark, showing the current cross-fund range for that company so the mark isn't made blind

4. Guidance, not just data, on aggressive vs. conservative marking

GPs are going to ask "should I mark at the high end or the low end of the range," and Decile is well positioned to give a defensible, documented answer rather than making every GP invent their own policy. At minimum, show standard conservative approaches (e.g., last-round price, or the lower of last-round price and the most recent contributing mark) next to the aggressive alternative (e.g., latest priced round regardless of recency, or highest observed mark), so a GP can pick a stated policy and apply it consistently, and so LPs and auditors can see the policy was applied consistently rather than cherry-picked deal by deal.

What Carta Already Does, and Where This Should Go Further
Carta has adjacent functionality worth being aware of. Their Data Desk / Round Benchmarking Tool surfaces aggregate round-size, valuation, and dilution benchmarks across their network, filterable by stage, sector, and region, and their platform description references "last preferred valuation" as a data point available to investors. That's market-level benchmarking (what are Series B valuations doing broadly), not the same thing as this request. It doesn't appear to give a GP a company-specific, cross-fund reconciliation view showing exactly who else holds Company X, what they're marked at, and where a specific fund's number is out of line with peers holding the identical security. That's the gap. Decile's fund administration relationship with GPs (as opposed to Carta's broader company-cap-table-plus-investor footprint) may actually put you in a better position to build the reconciliation and audit workflow specifically, rather than just the market-benchmarking layer Carta already has.

Implementation Considerations
  • Consent and disclosure. Funds will need to opt in (or out) to contributing their data to the shared pool, and probably opt in per-company or per-fund rather than as a blanket platform setting. Anonymize the contributing fund identity by default (show "Fund A held at $X, Fund B held at $Y" rather than naming funds), with an option for GPs to identify themselves to each other if they want to.
  • Data provenance. Every data point needs a timestamp, a source (priced round vs. secondary vs. GP-entered estimate), and ideally a confidence flag, since a number pulled from a signed round document is not the same quality as a number a GP typed in from memory.
  • Stale data handling. A "latest" price per share from fourteen months ago should be visually distinguished from one dated last week. Don't let an old number silently anchor a current mark.

The Ask
I'd like to talk through scoping this, including whether it's a near-term roadmap item or something that needs a design partner group of GPs to pilot. Happy to be a design partner given we're actively living this problem on our own portfolio reconciliation right now.