We built a custom portfolio platform that cut quarterly LP reporting time by 90% for a $200M+ climate-tech fund. The speed got the attention. But the part that actually changed how the fund ran was quieter: LPs and partners stopped looking at the same screen.
That sounds backwards. Most LP portal software sells you the opposite — one clean dashboard, same view for everyone, transparency as a single pane of glass. It feels like the safe default. It isn't. A shared dashboard for every LP and every partner is the anomaly, not the standard. The rest of the fund-LP relationship figured that out a long time ago; the software just hasn't caught up.
The argument here is simple. Role-based, tiered visibility — different people see different things, on purpose — beats one-size-fits-all. Not because it's a clever feature to sell, but because it's already how funds and their investors actually work.
IYour LPs already don't see the same thing — the legal side got there first
Open up almost any fund's paperwork and you'll find that LPs already have different rights to information. That's what side letters are for — the standard legal mechanism a GP uses to grant an individual LP different reporting and information rights outside the main Limited Partnership Agreement. Enhanced reporting on portfolio company financials, extra transparency, custom cadence: side letters are where that lives.
Stack Most Favored Nation clauses on top and the tiering gets sharper still. MFN lets certain LPs — usually the ones above a commitment threshold — elect into terms other investors negotiated. Bigger check, more access. That's not a loophole; it's the ordinary contract law of funds.
So the differentiated-access question was settled at the legal layer years ago. Some LPs get more than others, and everyone signed for it. The only place that still pretends every investor is identical is the dashboard.
IIRegulators assumed tiered access was normal too — until a court fight said otherwise
Regulators baked the same assumption in. The SEC's Private Fund Adviser Rules included a "Preferential Transparency Rule" that barred a GP from giving one LP portfolio-level detail if doing so would materially harm the others. Read it closely and it's an admission: regulators took for granted that not every LP sees the same data, and tried to police the edges of that.
Then the whole package got struck down. In June 2024, the Fifth Circuit vacated the Private Fund Adviser Rules in their entirety, the transparency rule with them. So it's unenforced today — but the principle it encoded is still exactly how the industry thinks about disclosure.
Meanwhile the floor keeps rising. The updated ILPA Reporting Template (v2.0), released in January 2025 and required from the first quarter of 2026 for GPs still in their investment period, removes a GP's ability to modify, reorder, or supplement line items — one standardized structure for the report every LP receives. That's the point worth holding onto: the ILPA template is a floor, the baseline fund-level report everyone gets. It was never meant to be a ceiling on what a larger or more sophisticated LP can see beyond it.
IIIWhat LPs actually say they want: transparency, not sameness
Here's where the "one dashboard" instinct comes from — the sense that LPs are demanding more transparency, so give everyone everything. The demand is real. The conclusion is wrong.
Look at what LPs actually say:
- 68% now prioritize operational transparency over even performance track record when evaluating GPs, per a CSC survey cited by Altvia — reporting infrastructure is now a selection criterion, not a back-office detail.
- 73% cite inconsistent reporting from managers as a significant challenge in alternatives, per Preqin.
- 80% of investors expect higher transparency, especially at the individual-asset level, per an Intertrust Group survey via Allvue.
Read those together and the ask isn't "show everyone the same thing." It's a reliable, consistent process, and more of the relevant detail. A lowest-common-denominator dashboard — flattened so the least sophisticated LP isn't overwhelmed — actively works against that. It gives your biggest LPs less than they want and your smallest ones more than they can use.
IVThe two-layer model: fund-level by default, portfolio-company detail on request
The fix is structural, and it's boring in the best way. Two layers.
The default view is fund-level: TVPI, DPI, MOIC, net IRR, and sector and stage exposure. A best-practice framework for VC LP portals reckons that view should drive roughly 80% of LP portal sessions. Portfolio-company-level detail sits underneath it as an optional drill-down — there when someone wants it, not in the way when they don't.
Why default to the fund level? Scale. That same framework notes a $200M VC fund can hold 40 to 60 portfolio companies, versus 8 to 12 for a comparable PE fund. Dump 50 companies of granular detail on the landing screen and you haven't been transparent — you've buried the two or three numbers most LPs came for. Fund-level first, company-level on request, is how you serve both the LP who glances once a quarter and the one who wants to go deep.
VIt's not just LPs — advisors, auditors, and portfolio operators need different seats too
Zoom out from LPs and the case for tiering gets stronger, because the people touching fund data aren't only investors.
An investor-portal vendor guide treats granular, role-based permissions as table stakes: a tax advisor acting on an LP's behalf should reach that LP's tax documents while being blocked from capital notices and the portfolio dashboard. Access scoped by who the viewer is — not just which fund they're attached to.
The legal guidance is stricter still. U.S. fund guidance says restrict material non-public portfolio company information to people with a genuine need-to-know, require confidentiality agreements, and log who accessed what and when. That's a need-to-know model, not a shared view. And GPs have gated access by risk for a long time: one peer-reviewed finance study found that after 2002 court rulings let public LPs' VC portfolio data leak out through public-records requests, top VC firms simply excluded public LPs from new funds — a lost-access cost the study estimates at $1.6 billion in returns against $14 billion of commitments. GPs already decide who sees portfolio detail based on confidentiality risk. Your software should make that easy, not fight it.
VIThe security case nobody puts on the LP-experience slide
There's a colder argument for tiering, and it rarely makes the sales deck. Broad access is a liability you can measure.
IBM's 2025 Cost of a Data Breach research found that 97% of organizations reporting an AI-related security breach lacked proper access controls, and pegged the global average breach at $4.44 million in 2025. A single dashboard with wide-open access to sensitive fund and portfolio data isn't just a UX shortcut — it's an unpriced risk sitting on your infrastructure. Tiered access is a control, not a courtesy. Every person who can't see a thing is a door that can't be walked through.
VIIWhat we built when a fund needed this in practice
Back to that climate-tech fund. It was running on 30-plus disconnected spreadsheets. We replaced them with a custom platform — Retool for the interface, Xano for the data layer, the Affinity API for the CRM feed, and Claude doing the language work — and quarterly LP reporting time dropped by roughly 90%.
The access design mattered as much as the speed. Partners got the deep, real-time drill-down: company-by-company revenue, hiring, and runway, refreshed live. We also gave them a Slack layer for querying portfolio data in plain English from Slack — a partner can ask "which companies are ahead on revenue but behind on hiring?" and get an answer in seconds. That question used to take about four hours of manual cross-referencing.
LPs got something different from the same underlying data: the standardized quarterly packet, generated from live data in minutes rather than days, on branded templates ops signs off before anything goes out. Same source of truth, two very different seats. And a separate piece — normalizing portfolio company KPIs into a single partner digest — pulls board decks into a consistent partner-facing view without a human retyping numbers. The fund's VP of Operations owns the whole system and now uses it as a differentiator on LP calls.
One thing worth being clear about: the reporting layer sits alongside the fund's independent accounting and audit function. It doesn't replace it. The numbers come from live operational data; the books stay where the books belong.
VIIIDesigning this without buying an enterprise suite
You don't need to buy into an enterprise investor-relations suite to get this right. Permission logic — who sees the fund level, who drills into companies, who's scoped to documents — is something you can build into a lightweight custom stack that sits next to your fund accounting and audit system rather than swallowing it.
We've written up what a $10K/month build-vs-buy retainer actually replaces if you want the honest cost math. The backdrop for why funds are re-examining this now: one estimate puts the VC fund-management software market at around $1.04 billion as of April 2026, growing about 11.4% a year as GPs shift from static quarterly PDFs to live digital investor experiences (a secondary figure, worth treating as directional). The direction is what matters. As the reporting floor rises and LPs expect more, the funds that win are the ones whose access design matches how their investor relationships already work.
Black Matter VC is a solo, operator-led AI studio and consultancy — we build and run custom AI systems and data infrastructure for funds, not a fund ourselves.
IXFAQ
Do we need to replace our fund admin software to do this?
No. In the builds we run, the tiered-reporting layer sits alongside your existing fund accounting and audit system and reads from live operational data. Your books, your admin, and your auditor stay exactly where they are.
What's the minimum viable version of tiered access?
Two layers. A standardized fund-level dashboard every LP can see — TVPI, DPI, MOIC, net IRR, exposure — plus a portfolio-company drill-down gated by role. That alone covers the majority of what LPs and partners actually need, and you can add finer scoping (advisors, auditors, per-company operators) as you go.
Who should have partner-level access?
GPs, partners, and fund ops — the people making decisions and running the system. Not every LP by default. An LP earns deeper access through a side letter or MFN election, and even then it's scoped to what they negotiated, not a blanket key to everything.
XThe takeaway
The question was never whether to give LPs and partners different views. Legally and contractually, you almost certainly already do — that's what side letters, MFN clauses, and need-to-know rules have always been. The only real question is whether your dashboard reflects that, or is still pretending everyone needs the same one.
— Michael Rouveure
