Multi-Client Portfolio Infrastructure for Fund Administrators, Consultants, and OCIOs
One platform serving every client institution with the same fiduciary-grade infrastructure. Per-organization data isolation, ILPA reconciliation against fund-administrator quarterly templates, AI-augmented sourcing research with methodology-appendix PDFs, and pluggable commercial-vendor overlay configured per-client per-asset-class. Built for the service-provider workflow specifically: many clients, many funds, one analytical foundation, no cross-tenant access path.
The Challenges Service Providers Face
Multi-Tenant Data Isolation Without Compromise
Operating across multiple LP clients means per-client mandates, per-client commercial-vendor subscriptions, per-client reporting requirements. Most platforms either flatten this into a single view (compliance and IP risk) or require separate deployments per client (operational nightmare). Meridian's organization-scoped tenancy enforces isolation at every database boundary while running on shared infrastructure.
ILPA Reconciliation at Scale
Quarterly ILPA 2025 template ingestion across every fund in every client portfolio is a data-quality discipline that doesn't scale linearly. Meridian's four signed-convention reconciliation formulas — NAV roll-forward, commitment, fee netting, carried-interest — validate to $1 tolerance per fund per quarter; flagged exceptions surface as fiduciary warnings the analyst sees before the IC does.
Consistent Output Quality Across Engagements
When client A asks for a sourcing memo and client B asks for the same memo a month later, the analytical foundation must be identical — not a copy-paste cycle that depends on which analyst is on duty. Meridian's AI-Assisted Sourcing Research workspace produces structurally consistent per-fund decision memos every session, with citation chips and a methodology-appendix PDF documenting the audit trail end-to-end.
Commercial-Vendor Posture Per Client
Client A subscribes to Preqin; client B uses PitchBook; client C operates on public data only. Most platforms force a single vendor choice at deployment time. Meridian's commercial-overlay abstraction lets each client configure their own vendor per asset class — or run on Layers 1-4 (SEC + Wikipedia + GP web + LP-internal + macro) with no commercial dependency at all.
How Meridian Helps
Organization-Scoped Tenancy at the Database Boundary
Per-client data isolation enforced at the organization_id boundary across 40+ tables. No cross-tenant access path exists in the codebase. Per-org commercial-vendor opt-in via LPConfiguration cascade. Fernet-encrypted credential storage isolated per organization. Standard institutional review (SOC 2 Type II targeting 2027) operates against this same architecture; the multi-tenant separation is structural, not policy-only.
Quarterly ILPA Reconciliation Across Every Client Portfolio
Automated ingestion of GP-distributed ILPA 2025 quarterly templates with four signed-convention formulas validating to $1 tolerance per fund: NAV roll-forward (5 cash-flow line items), commitment reconciliation, fee netting (with rebate + waivers + offsets), and carried-interest accrual (accrued/earned split with returned clawback). Twelve ILPA fee-offset categories enumerated. Material differences flag as fiduciary warnings; the methodology paper at /resources details the discipline end-to-end.
AI-Assisted Sourcing Research with Methodology-Appendix PDF
Per-fund decision memos generated against a 7,200-firm public-research substrate (SEC ADV + Wikipedia rosters + GLEIF cross-reference). Six research channels synthesize into citation-tagged rationale prose with click-through source chips. Per-asset-class verification SLAs surface coverage gaps explicitly when channels fall short of institutional thresholds. Every session produces a methodology-appendix PDF documenting every LLM query, every source artifact, every fact, and every gap — the audit-trail document that goes into the IC packet alongside the recommendation memo. Sample artifact: see /resources for a representative output.
Pluggable Commercial-Vendor Overlay (Per Client × Per Asset Class)
CommercialGPDataProvider abstraction supports per-organization opt-in for Preqin, PitchBook, Burgiss, Cambridge Associates, or any future vendor. Configured via per-client LPConfiguration — client A's PE allocation runs with Preqin overlay, client B's RE allocation runs Layers 1-4 only. Vendor unavailability is a non-blocking gap: the rose-banner synthesis_error surfaces it, and the run completes on Layers 1-4. Same code path produces institutional-quality output regardless of vendor configuration.
Custom Reports + Audit Trail per Client
Generate institutional-quality board reports and IC memos for each client institution with AI-drafted narratives, six report types, and a 21-block composable template builder. Every IC vote, override, and assessment recompute is captured in append-only audit-history tables. The methodology-appendix PDF for any sourcing session, the reconciliation certificate for any ILPA-imported fund, the override-history view for any IC decision — all reconstructible per-client at any point in the future.
Per-Asset-Class Mandate Fit Scoring at Every Stage
Unified Assessment Engine v1.2 ratifies a single deterministic scoring discipline applied at sourcing, screening, due diligence, and IC review stages. 22 dimensions across 4 categories (policy / quality / fiduciary / thesis), with stage-availability gating, asymmetric thesis modifier, and stage-aware disposition derivation. Scoring rules are per-asset-class (BOOTSTRAP_WEIGHTS for all 6 asset classes); per-LP overrides via LPConfiguration cascade. The same engine, the same inputs, the same audit trail — across every client.
Multi-client portfolio dashboards with per-organization data isolation
Preview the Platform
Provide your details to view this screenshot — and to unlock all platform screenshots across the site for the rest of your visit.
See How Meridian Works for Service Providers
Schedule a personalized demo tailored to your workflow.