Which business records may qualify for a license, and which usually don't

If you've run a business for a decade or two, you've got a mountain of records. Proposals. Procedures. Support tickets. Project files. Years of email. Most of it sits in everyday software and nobody looks at it after the job's done.

Lately, more owners are asking a fair question: is any of that worth something on its own? The honest answer is "maybe, for some of it." Here's how to tell the difference before you talk to anyone.

What does "licensing" records actually mean?

A license is permission to use something under set terms. You don't sell the records, and you don't hand over your business. You grant a defined right to use certain material for a defined purpose, and you keep ownership. That's the same basic idea architects use with drawings: under the AIA's standard owner-architect agreement, the architect keeps the copyright in the drawings and gives the owner a license to use them for the project (AIA Contract Documents).

Whether a particular set of records may qualify depends on what it is, who owns it and what you're allowed to share. Nothing about it is automatic, and there's no promise of money.

Which records may qualify?

The strongest starting point is work your own people created in the normal course of business. Under U.S. copyright law, work an employee prepares within the scope of their job is generally a "work made for hire," which means the employer is treated as the author (U.S. Copyright Office, Circular 30).

Examples that may qualify, depending on the details:

• Internal procedures and playbooks. How your team actually does the work, step by step.
• Templates and proposals your staff wrote, with client specifics removed where needed.
• Support and service history. Tickets and responses from tools like help desks, often after personal details are taken out.
• Training materials and internal knowledge bases.
• Project records such as field notes, checklists and internal reviews that your company produced.

Years matter, too. A long, consistent history in the same main software is easier to review than scraps spread across a dozen systems.

Which records usually don't qualify?

This list matters as much as the first one:

• Work you didn't create or don't clearly own. Material from contractors without a clear assignment, purchased reports and licensed third-party data usually aren't yours to license.
• Records a contract restricts. Many client agreements and NDAs limit how you can use their information. Read them first.
• Records the law restricts. Tax return information is a good example. Federal rules generally require a preparer to get the taxpayer's written consent before using or disclosing return information for other purposes (IRS, Section 7216). Health information has its own rules under HIPAA (HHS).
• Mostly personal information. Files that are really just people's private details are a poor fit.
• Trade secrets you want to keep secret. Your crown jewels can lose protection if they're shared carelessly (USPTO, trade secret policy). Some records should simply stay home.

What should you check before talking to anyone?

1. Ownership. Did your employees create it on the job? Do contractor agreements assign the work to you?
2. Contracts. Do client agreements or NDAs restrict use of what's in the files?
3. Laws. Does the data include tax, health, financial or other regulated information?
4. People. How much personal information is mixed in, and can it be removed?
5. Your comfort. Would you be fine explaining this to your best client? If not, leave it out.

None of this replaces your own attorney's advice. It just keeps the first conversation honest.

Is this different for law, accounting, AEC and oil and gas firms?

Yes, each one has its own wrinkles, which is why there's a separate site for each. Law firms owe clients confidentiality, so any review has to protect client information and privilege. CPA firms deal with tax-information rules. AEC firms have contract terms about drawings and project files. I've written a separate guide for AEC owners on project files, RFIs and field notes, and you'll find more on law firms and CPA firms here too.

Why are owners asking about this now?

Because AI has made well-organized, real-world business records more interesting than they used to be. Research on professional-services firms keeps pointing to data quality as the thing that makes or breaks AI work. RSM found that data quality was the top reason professional-services AI pilots fell short (RSM, 2026). Clean, consistent, company-owned records are harder to come by than you'd think.

That doesn't mean every firm's files are valuable. It means it's worth a careful, no-pressure look. For more on how firms are using AI day to day, see what AI is actually doing inside small firms in 2026.