# Software development agencies: data licensing fit

Canonical: https://refer.sourcex.si/industries/refer-software-development-agency-data-licensing
Last updated: 2026-11-05

A custom software agency can be a data licensing fit with 50+ full-time employees at peak, years of documented projects and rights to its own records. Estimates, retrospectives, handbooks and workflow records may qualify, while delivered client code is usually assigned to clients and excluded without their consent.

## Is a dev shop's data licensable, and which part?

Sometimes. A dev shop with 50+ full-time employees at peak (contractors excluded) and years of documented projects keeps pull requests, code reviews, tickets, estimates and QA records across many engagements. That is the material agentic-coding buyers look for: real engineering work with review comments and outcomes. The catch is ownership. Most delivered code is assigned to clients, so the licensable slice is usually the agency's own process records, not the code it wrote for others.

This page maps own versus client-owned records so a partner can judge the opportunity in one conversation.

## What records does a software agency keep?

| Source | Records | Why AI labs and data users may value them | Ownership question |
|---|---|---|---|
| Git hosting | Pull requests, review threads, commit history | Code change with reasoning and revision | Code is often assigned to the client |
| Issue tracker | Epics, stories, bugs, acceptance criteria, status history | Requirements tied to implementation and outcome | Mixed: the agency's workflow, the client's product details |
| Estimating files | Estimates, assumptions, actual hours | Predicted versus actual outcomes | Usually the agency's own |
| QA and test records | Test plans, defect reports, regression notes | Failure found, cause, fix | Mixed |
| Engineering handbook | Coding standards, architecture decision records, onboarding docs | Codified practice | Usually the agency's own |
| Chat and email | Technical discussion, client threads | Reasoning and trade-offs | Client threads are sensitive; internal chat needs notice review |
| Retrospectives | Sprint retros, project post-mortems | Explicit outcome reflection | Usually the agency's own |

## Who owns what: a rights map

Under US copyright law, a work made for hire is owned by the employer, and content from outside contractors may not be the company's unless assigned in writing, as the [Copyright Office circular on works made for hire](https://www.copyright.gov/circs/circ30.pdf) explains. The Copyright Act also provides that [copyright ownership can be transferred in whole or in part](https://www.law.cornell.edu/uscode/text/17/201), which is what most client agreements do with delivered code. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

The practical result for an agency:

- **Often the agency's own:** internal process records, estimating models, handbooks, reusable internal tools it kept rights in, internal tickets and chat, retrospectives.
- **Often the client's:** the delivered codebase, client-specific specs, anything under a confidentiality or assignment clause.
- **Needs a closer look:** commit history and review threads inside client repositories the agency can still reach, and work done by freelancers without written assignment.

Ask the founder one question: "Where do your master services agreements land on ownership of work product and reuse of process information?" You do not need the answer in detail; you need to hear that someone knows.

## The 3-layer test for a dev shop

1. **Layer one, process:** are estimates, retrospectives and standards documented and stored in the agency's own systems?
2. **Layer two, work in progress:** are tickets and review threads structured, with outcomes recorded?
3. **Layer three, delivered product:** does the agency retain any rights, or is everything assigned?

Layers one and two decide the opportunity. Layer three is a bonus when rights exist. A firm strong in layer one with a clean contract position is worth a [company fit checker](/tools/company-fit-checker) pass.

## Which agencies tend to screen well?

- [ ] 50+ full-time employees at peak, contractors excluded
- [ ] Five or more years of projects, ideally across several client types
- [ ] A consistent ticket workflow and written definition of done
- [ ] Estimates and actuals tracked per project
- [ ] A founder, CEO, CTO or CFO who can authorize a license
- [ ] Mostly full-time staff rather than a rotating freelancer pool

A product studio or contractor marketplace with little full-time staff generally falls short.

## How the introduction works

1. You send the agency to your referral link or submit it through the referral form, giving headcount band, years and the founder's name.
2. SourceX qualifies size, history, data breadth and rights, starting with the agency's client agreements.
3. The agency lists its repositories, trackers, estimating files and handbook in a data inventory, marked own, client or mixed.
4. Price and terms are agreed; nothing is binding until the agency signs.
5. SourceX completes its final review; once deal-ready, SourceX typically responds within about two weeks.
6. On close, data is delivered under agreed redaction rules and the agency is paid, within 60 calendar days after SourceX receives a valid invoice following Closing.

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 the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. The USD 50,000 floor applies once per referred company, to its first qualifying transaction. No reward is guaranteed.

## What to say to an agency founder

> "Your estimates, retros and engineering handbook are your own work, and AI developers need records of how real software teams plan, review and ship. An agency can license that kind of material for a one-time payment and keep ownership. Client code stays out unless clients agree. Want a quick screen?"

## Red flags for software agencies

- Every client agreement assigns all work product and bars reuse of process information
- Repositories were deleted at project handover with no internal copy
- Code and notes were produced by AI mainly to create something to sell
- The same records were already licensed for AI training
- No one can export tickets or review history

## Who can introduce them

Likely introducers include PE teams with a software services platform, M&A advisors working on agency sell-sides, fractional CFOs, ERP and CRM implementation partners, and technology attorneys. See how this compares with [independent insurance agencies and MGAs](/industries/refer-insurance-agency-data-licensing), [HVAC contractors](/industries/refer-hvac-contractor-data-licensing), [IT consulting firms](/industries/refer-it-consulting-firm-data-licensing) and [architecture firms](/industries/refer-architecture-firm-data-licensing). If the agency is mid-roll-up, read the guide to [buy-and-build sectors](/guides/buy-and-build-sectors-private-equity) and the note on [software consolidation introductions](/guides/a-software-consolidation).

## Questions to ask in the first call

1. "Do your estimates and final hours sit in the same system, and for how many years?" Paired predictions and actuals are the cleanest outcome labels an agency has.
2. "Do your reviewers write comments that explain why, or only approve?" Explained reviews carry the reasoning buyers want.
3. "Which projects did you keep the right to reuse, if any?" Some agencies negotiate retained rights in frameworks and accelerators.
4. "Who would sign a license on your side?" Identify the authorized sponsor early.

Keep your notes to headcount band, years of history, system names and the sponsor. Never ask for a repository, a ticket export or a sample.

## Next step

Ask one agency founder who owns the estimating model and the handbook. If the answer is the agency, [register as a partner](/register) and make the introduction. The [who qualifies](/who-qualifies) page lists the full baseline.

## Sources

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