Client data is information you hold to deliver a service, and it usually belongs to the client under your contract. Company data is what your own business created to run itself. Only the second is yours to license. Service firms often find most records are client data, but their own process knowledge can still be sold.
Why this ends more deals than anything else
The most common reason a data sale stops is not privacy law or price. It is that the records the company wanted to sell turn out to belong to its clients. This is especially true of service businesses, whose daily work consists of handling other companies' information.
The mistake is natural. The records sit in the firm's systems. The firm's staff created many of them. The firm pays for the storage. None of that decides who has the right to license them. The contract with the client does.
Finding this out early saves time for everyone. A seller who sorts client data from company data before approaching a buyer knows what it can offer and avoids building a deal on records that will be excluded.
The rule runs in both directions. A buyer that accepts client-owned data inherits the problem, since it cannot safely train on records the seller had no right to supply. Careful buyers therefore exclude such data even when the seller is willing to include it.
Three kinds of record
Most records in a service business fall into one of three groups. Client data is information the client supplied, or that the firm created for the client as part of the service. Company data is information the firm created to run its own business, such as its procedures, training material, internal discussions and tooling.
The third group is mixed. A ticket in the firm's own system may describe a client's problem, quote the client's configuration and record the firm's own diagnostic reasoning. A project plan may combine the firm's standard method with one client's confidential goals. Mixed records are the hard part, and they are usually the majority.
A fourth, smaller group is data about the client relationship itself: the firm's own invoices, its account notes, its record of hours. These are the firm's business records, but they describe a client, and the confidentiality clause usually reaches them. Treat them as mixed.
How to tell from your contracts
The answer for any client is in the paperwork: the master services agreement, statements of work, the data processing agreement, any NDA, and the firm's own standard terms if the client signed those. Older clients may be on older versions with different wording. The clauses below carry the answer.
Read the definition first. Many agreements define customer data broadly enough to cover anything the firm produces in the course of the engagement. Where a contract is silent, do not treat silence as permission. Confidentiality duties and privacy law may still apply, and the cautious reading is the one a client's lawyer will take.
Where the firm's own standard terms were used, check which version each client signed and whether any client struck or amended the data clauses. Large clients often replace the vendor's paper with their own, and their terms are usually stricter. A small number of large clients on their own paper can account for most of the data.
- Definition of customer data or client data: what it covers, and whether it includes outputs and derived data.
- Ownership clause: who owns the data and the work product or deliverables.
- Permitted use: commonly limited to providing the services to that client.
- Confidentiality: what counts as confidential information and who may receive it.
- Aggregated or de-identified data: some agreements let the provider use such data for its own purposes. The exact wording decides how far that goes.
- Return and deletion: a duty to delete at the end of the engagement means old client data should not be in an archive at all.
- Data processing terms: a processor or service provider acts only on the client's instructions.
Examples by business type
The table shows how the split usually falls for five kinds of service business. It reflects common contract terms, not any particular agreement. Your own contracts decide.
| Business | Usually the client's | Usually the firm's own |
|---|---|---|
| Marketing agency | Campaign assets, audience data, performance data from client ad accounts, brand strategy | Briefing templates, creative process, internal reviews, pitch methods, staff training |
| Managed service provider | Client network configurations, credentials, device inventories, tickets tied to client systems | Runbooks, triage procedures, escalation rules, internal tooling and scripts |
| Business process outsourcer | Call recordings, transcripts, case records and customer details handled for clients | Quality frameworks, coaching material, workforce procedures, internal operations chat |
| Law firm | Client files, advice, matter documents and communications, which are also privileged | Internal know-how notes and precedents stripped of client facts, practice management procedures |
| SaaS company | Content customers upload or create in the product | Source code, product documentation, own support playbooks, internal engineering discussion |
Mixed records
Mixed records can sometimes be separated. Three approaches are used, in rising order of effort. The first is to drop them and license only records that are clearly the firm's own. The second is to extract the firm's contribution, such as the diagnostic steps from a ticket, and discard the client's facts. The third is to de-identify the record and rely on a contract clause that permits use of de-identified data.
The third approach needs care. De-identification answers privacy concerns. It does not answer a confidentiality clause. If a contract bars disclosure of the client's confidential information, removing the client's name leaves the confidential information in place. Only a clause that actually grants the right, or the client's consent, changes that.
Whichever approach is used, apply it consistently and record the rule. A buyer's review will sample the output. If one extracted record still names a client's system or quotes a client's document, the reviewer will reasonably doubt the rest.
What can still be sold: your own process knowledge
A service firm with very little licensable client-related data often still has something of value. It knows how to do a kind of work, and that knowledge is written down in places the client never sees.
Standard operating procedures, runbooks, decision trees, quality rubrics, onboarding and training material, internal templates, and staff discussion about how to handle difficult cases are generally the firm's own. So is source code the firm wrote for its own tools. These show how experienced people approach a task, which is what AI labs are trying to teach models.
The same caution applies in smaller form. A procedure written for one client under that client's statement of work may belong to the client. Internal discussion may quote client facts that need removing.
The test for whether knowledge is the firm's own is whether it would be the same if a given client had never existed. A triage procedure used across every account passes that test. A configuration guide for one client's environment does not.
Asking clients for permission
A firm can ask its clients to agree. Some will, particularly where the data is de-identified, the client is not named, and the client shares in the benefit. The request should be specific about what data, what use and what safeguards, and the consent should be in writing as a contract amendment.
Weigh the request before sending it. It tells the client that the firm is considering licensing data, and some clients will respond by tightening their terms. For future engagements, the cleaner route is to settle the question in new contracts, in plain words, before the work starts.
Some firms offer clients a choice at renewal: a standard contract that permits de-identified use, or an opt-out at the client's request. This keeps the decision with the client and creates a clear record. It works going forward only. It does not reach data collected under the earlier terms unless the amendment says so.
How the question is checked in a deal
A careful buyer will not take a seller's word on ownership. Outrich Data runs a data title search before an offer is final, which reads customer contracts, data processing terms and NDAs against the proposed dataset and marks each part as clear, conditional or excluded.
A seller can prepare by gathering its contract templates and the exceptions negotiated by major clients, and by mapping which systems hold which kind of record. A company that arrives with that map will get a faster and more accurate answer about what it can sell.
Expect the answer to be partial. It is common for a review to clear internal documentation and the firm's own operational records while excluding most client-facing material. That is a normal result for a service business, not a failed deal.