# Systems integrator roll-ups: records and client rights

Canonical: https://refer.sourcex.si/industries/systems-integrator-roll-up-private-equity
Last updated: 2026-10-20

A private equity systems integrator roll-up can often license its own delivery records, such as SOW libraries, estimates versus actuals, methodology playbooks and support histories, but not the deliverables and data its clients own. Sponsors should screen the platform and each add-on for contract terms, contractor IP assignments, preserved archives and 50+ full-time employees at peak.

## What a systems integrator roll-up can license

Systems integrators hold two kinds of records. The first is the firm's own delivery history: how it scopes, estimates, staffs, runs and supports implementations on platforms such as Salesforce, ServiceNow, NetSuite, Microsoft Dynamics or Workday. The second is client work product: configurations, custom code, data and documents created for clients and usually assigned to them. The first can be a licensable asset. The second generally is not, unless the client consents.

Roll-ups make that split more important, not less. Every acquired partner firm brings its own contracts, templates and archives, and integration projects tend to retire the very systems where that history lives.

## Which records an integrator typically holds

| System | Records | Why AI labs and data users value them | Who usually owns them |
|---|---|---|---|
| PSA and project accounting | Time entries, estimates versus actuals, change orders, staffing plans | Show how scope and effort evolve on real multi-step projects | The firm |
| CRM and proposal library | Discovery notes, SOWs, scoping questionnaires, win and loss reasons | Pair a client problem with the proposed approach and the outcome | The firm, though client details are confidential |
| Methodology and knowledge base | Delivery playbooks, templates, checklists, lessons-learned reviews | Encode expert procedure step by step | The firm |
| Work tracking such as Jira or Azure DevOps | User stories, defects, sprint histories | Link requirements to fixes and acceptance decisions | Mixed: often the client's own instance |
| Code repositories | Reusable accelerators and packages, plus client customizations | Show engineering decisions and review comments | Split: accelerators often the firm's, customizations often the client's |
| Application support desk | Post-go-live tickets, escalations, resolutions | Labeled problem-to-resolution sequences | Mixed: depends on the support contract |
| Internal chat and email | Delivery discussions, escalations, handoffs between teams | Capture the reasoning between steps | The firm, but full of client confidential information |

The richest licensable material is usually the firm's own: years of scoped engagements, each with the estimate, the actual effort and the reasons the two diverged.

## Which roll-ups and add-ons fit

To qualify, an integrator must be based in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia (outside the U.S., Canada and the EU, at least 90% of the data must be in English), with 50+ full-time employees at peak (contractors excluded), a documented operating history stretching back several years, clear rights to what it would license and an executive able to sponsor the decision. Integrators lean heavily on subcontractors and offshore delivery partners, so count only the firm's own full-time staff.

Strong candidates include:

- Platform-focused implementation partners with long histories in one ecosystem, such as CRM, IT service management, ERP or HR systems.
- Data and analytics consultancies with their own delivery methodology and reusable accelerators.
- Application managed services practices that run support desks after go-live.
- Add-ons acquired with their archives intact, especially where the founders documented their methods carefully.

Integrator revenue mixes project work with recurring support, which shapes how a buyer values the business; see [T&M versus managed services valuation](/compare/time-and-materials-vs-managed-services-valuation). A license is a one-time payment and sits outside both.

Whether a group with several acquired entities is best presented as one company or entity by entity depends on which entity holds the records and the rights. Raise it with SourceX at qualification rather than guessing.

## Client rights: the line an integrator cannot cross

Most of an integrator's rights questions are answered by three documents: its standard MSA, its SOWs and its subcontractor agreements.

- **Deliverables:** MSAs commonly assign work product to the client while the integrator keeps its pre-existing materials, tools and know-how. Read the actual clause, because its wording decides which side of the line playbooks and accelerators fall on.
- **Employees versus contractors:** work prepared by an employee within the scope of employment is a work made for hire owned by the employer, but content from an independent contractor generally is not, unless it falls in a listed category and both sides signed a written work-for-hire agreement, or the rights were assigned in writing ([Copyright Office Circular 30](https://www.copyright.gov/circs/circ30.pdf)).
- **Partial rights:** copyright ownership can be transferred in whole or in part, and any exclusive right can be transferred and owned separately ([17 U.S.C. 201](https://www.law.cornell.edu/uscode/text/17/201)). A firm may already have granted clients rights in some materials while keeping others.
- **Confidentiality:** tickets, chat and status reports name clients, describe their processes and sometimes contain credentials or data copied from client sandboxes. These are excluded or redacted under rules agreed with the company before any work begins.
- **Platform partner terms:** ecosystem partner agreements can restrict how vendor training and certification materials are used. Leave vendor content out.

| Record | Usually licensable by the firm? | What to check |
|---|---|---|
| Internal delivery playbooks and templates | Yes, if employees created them in firm systems | The pre-existing IP clause and contractor authorship |
| Estimates versus actuals and staffing history | Yes, once de-identified | Client names and rates removed |
| Win and loss notes and the SOW library | Often, once de-identified | Confidentiality clauses in client MSAs |
| Support tickets and resolutions | Sometimes | Support contract terms and client data inside tickets |
| Client configurations and custom code | Rarely | Usually assigned to the client; needs consent |
| Client data held in sandboxes | No | Exclude entirely |

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

## The split test for the platform and each add-on

Run the same five questions on the platform and on every add-on before introducing it.

- [ ] **Contract split:** does the standard MSA reserve the firm's pre-existing IP, methods and tools?
- [ ] **System split:** are delivery records kept in firm-owned tools, or mostly inside client instances?
- [ ] **People split:** do subcontractor and offshore partner agreements assign IP to the firm?
- [ ] **Archive check:** were the add-on's PSA, ticketing and file shares exported before tenant consolidation?
- [ ] **Sponsor check:** can the CEO, CFO or another authorized representative approve a license?

A no on the contract or sponsor question stops the introduction for now. A no on the archive question is urgent rather than fatal: if the old systems are still running, exports can still be taken.

Integrators pose a different rights problem from [industrial services firms](/industries/industrial-services-private-equity), whose inspection and field records are mostly their own. For integrators, a [COO's records review](/guides/coo-private-equity-backed-company) is a natural place to map which SOPs and systems the firm owns outright.

## Who can introduce an integrator

| Role | What they see | Best moment to raise it |
|---|---|---|
| Operating partner | Platform strategy and the add-on pipeline | Integration planning after each add-on closes |
| Platform CEO or COO | Delivery methodology and tooling | Standardizing methodology across acquired firms |
| CIO or integration lead | Tenant, PSA and ticketing consolidation | Before legacy systems are switched off |
| Sell-side adviser on an add-on | The founder's records and contracts | During sale preparation, before closing |
| Fractional or portfolio CFO | Revenue mix and contract terms | Annual planning and budget review |

A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. The reward rate is 25% of Actual Supplier Payout. The cumulative cap is $100,000 per referred company. It is calculated on the actual supplier payout, never a deduction from what the integrator receives, and rewards are not guaranteed.

## A conversation starter for the platform CEO

> "We're consolidating PSA and ticketing across the add-ons this year. Before we switch anything off, it's worth asking whether our own delivery history, meaning the playbooks, estimates and support records we own outright, could be licensed to SourceX for a one-time payment. Client deliverables stay out. SourceX can tell us quickly whether we qualify, and nothing is binding until we agree terms."

## Next step

List the platform and each add-on with the [network opportunity finder](/tools/network-opportunity-finder), run the split test, and check the full baseline on [who qualifies](/who-qualifies). Then [register as a partner](/register) to introduce the companies that pass.

## Sources

- https://www.copyright.gov/circs/circ30.pdf
- https://www.law.cornell.edu/uscode/text/17/201