NexusConnect the systems that run your portfolio
For middle-market firms with three or more portfolio companies, portfolio reporting is rarely a single-system problem. Every acquisition brings its own ERP, CRM, databases and industry-specific systems, often completely different from the sponsor’s stack and from the rest of the portfolio. Nexus creates a governed integration and orchestration layer across the portfolio while each company keeps the systems that run its business.
Your portfolio is not one technology stack
At the portfolio level, technology variation compounds quickly, and multiple ERPs and CRMs are only the beginning. A manufacturing company may depend on MES, WMS, QMS and CMMS platforms. An IT-services company may rely on PSA, ticketing, time-entry, project-management and resource-planning systems. Others operate on specialized databases, vertical SaaS applications, custom software or industry-specific APIs.
These systems hold the operating data that explains revenue, margin, cash generation, customer performance, utilization, throughput, delivery and growth. Replacing every platform can disrupt the business. Leaving them disconnected forces the sponsor to assemble portfolio reporting through exports, spreadsheets, one-off mappings, manual reconciliation and point-to-point integrations. Nexus provides another approach.
One governed layer across every company’s stack
Nexus connects to the systems each portfolio company already operates through native connectors, relational databases, JDBC, APIs and files. UQL provides a consistent way to query across connected systems, pipelines extract, transform, normalize and move data between them, and reports, dashboards, applications and downstream platforms consume standardized financial and operating data, without requiring every company to run the same software.
Connect ERPs, CRMs, databases, APIs, files and specialized operating platforms without waiting for platform consolidation.
Map company-specific accounts, fields, records and terminology into common portfolio definitions for revenue, EBITDA, cash, working capital, pipeline, customer metrics and operating KPIs.
Query responsive systems live, or synchronize slower and rate-limited systems on a schedule. Each source uses the integration pattern that makes sense for it.
Each ERP, CRM, database and operating application keeps owning its information. Nexus connects and orchestrates across those systems without replacing them.
One Nexus instance per company. One governed view at the sponsor.
Nexus can be deployed independently inside each portfolio company while staying connected to a sponsor-level environment. Each company instance connects locally to that business’s ERP, CRM, databases and industry-specific systems. The sponsor instance connects to the company instances and consumes the standardized datasets each one exposes upstream.
Nexus A
ERP · CRM · MES · WMS
Nexus B
ERP · CRM · PSA · Ticketing
Nexus C
ERP · CRM · APIs · Databases
Sponsor Nexus
Consumes governed, standardized datasets from each company instance.
The company deployment owns its local connectors, credentials, mappings, pipelines and workflows. The sponsor receives governed financial and operating data instead of maintaining direct integrations into every underlying system. The result is a modular portfolio architecture: another acquisition adds another Nexus environment instead of another web of point-to-point integrations.
Built for acquisition, ownership and exit
Connect the systems the company already operates. Establish financial and operational visibility before deciding whether ERP, CRM, infrastructure or application consolidation is necessary.
Maintain a live or scheduled flow of standardized financial data and operating KPIs to the sponsor. Expand from reporting into reconciliation, exception management, workflow orchestration and automation as the value-creation plan develops.
Separate the company from the sponsor environment without dismantling integrations across the rest of the portfolio. The sponsor connection can be removed while the company’s local integrations, mappings, pipelines and workflows stay intact.
The architecture grows and separates with the ownership lifecycle.
Standardize the definitions, not the applications
The sponsor defines a common portfolio data model once, and each company maps its own systems into that model.
- Revenue, gross profit, EBITDA
- Cash, debt, working capital
- Accounts receivable and payable
- CapEx
- Bookings and pipeline
- Customers and retention
- Churn
- Customer concentration
- Headcount and utilization
- Inventory and throughput
- Project delivery
- Production and service levels
- Manufacturing metrics
- Professional-services metrics
- Distribution and field-service metrics
- Subscription and industry KPIs
Revenue may come from NetSuite at one company, QuickBooks at another and a different ERP at a third. Utilization may come from a PSA platform, production throughput from a manufacturing database, customer activity from Salesforce, HubSpot or an industry CRM. Nexus does not require those businesses to operate the same way. It gives the sponsor a consistent way to connect, query, normalize, govern and use the data they produce.
Where Nexus sits in the private-equity stack
Nexus
Nexus does not replace the portfolio company’s ERP, CRM or operating applications, and it does not replace the sponsor’s portfolio-monitoring, fund-accounting or BI platforms. It provides the governed integration, query and orchestration layer between them.
Each deployment runs in its own tenant
Nexus deploys as a managed application inside each company’s own Azure environment, and the sponsor instance inside the firm’s. Each deployment owns its connectors, credentials, mappings, pipelines and audit history, so data ownership follows the company through the hold period and out at exit.
How to roll it out
- Connect the first company. Establish governed bridges to its ERP, CRM, databases and operating systems.
- Define the sponsor reporting model. Set the common portfolio definitions for financial, commercial and operating metrics once.
- Add each acquisition. Stand up another governed Nexus deployment instead of another web of point-to-point integrations.
- Standardize portfolio visibility. Consume comparable metrics across companies without forcing every business to look the same.
How this maps to the platform
Every claim on this page is grounded in the Nexus documentation.
Integration note. Specific integrations depend on the interfaces exposed by each third-party product. Nexus may connect through a native adapter, supported database/JDBC connectivity, REST/GraphQL APIs or other supported interfaces. Read, write, discovery, event and latency capabilities vary by source and should be validated for each implementation.
Build a portfolio data layer that grows, and separates, with the portfolio
Connect the first company, define the sponsor reporting model, then add each acquisition as another governed Nexus deployment. Standardize portfolio visibility without forcing every company to look the same.