How to sell a software development company, and what you actually own

How to sell a software development company: the short answer

Acquirers of custom software firms buy three things: client relationships that will survive the owner's exit, a delivery team that will stay, and a repeatable way of winning and running projects. Assemble evidence of each before outreach, then run a focused process with IT services consolidators, PE-backed digital engineering platforms, larger agencies and strategic buyers who want your team or your vertical.

Ownership needs its own workstream. The code your engineers wrote for clients is, in many engagements, the client's property under the master services agreement, and it is out of scope for any data license. What the firm created for itself is different: estimates and proposals, sprint and time records, post-mortems, internal tools and engineering standards. Those records may qualify for a SourceX license, before the sale or apart from it.

What do acquirers diligence in a dev shop?

Code review is a diligence stream of its own; the guide to source code due diligence covers what buyers scan for and how to prepare.

Who owns the code: client work versus the firm's own records

Ownership comes from employment and contracts. Under the Copyright Act's definition of a work made for hire, work an employee prepares within the scope of employment belongs to the employer, while a commissioned work qualifies only in nine listed categories and only with a signed written agreement. Custom software is not one of those categories, so a client's ownership of code your team writes usually comes from the assignment clause in the MSA or statement of work. Read each one: many assign deliverables to the client on payment while letting the vendor keep its pre-existing tools and know-how.

Contractors are the recurring trap. A freelancer who built an internal tool may own it unless a signed agreement assigns it to the firm, and contractors do not count toward SourceX's size baseline either.

Why AI buyers value a dev shop's own records

AI developers building agents that write and maintain software need examples of the work around the code: how a scope became an estimate, how the estimate compared with actual hours, why a sprint slipped and what the team changed afterwards. Public repositories show code but rarely the decisions behind it.

Public text is also finite. Epoch AI researchers have projected that, if current trends continue, language models could fully use the stock of public human-generated text between 2026 and 2032. It is a forecast with wide uncertainty, but it explains why permissioned, non-public records of real engineering work draw interest from AI labs and data buyers.

Which software development companies fit?

• US-based, with 50+ full-time employees at peak (contractors excluded). Developers supplied by outside vendors count as contractors.
• Several years of operations with internal records across ticketing, version control, time tracking, CRM, finance and chat.
• Records the firm created itself, rather than work done entirely inside clients' tools.
• An owner or officer who can authorize a license and will consider exclusivity for AI training for an agreed term.

Strong candidates include product engineering firms with their own delivery playbooks, QA and testing firms, custom development agencies with long client histories, and modernization specialists with years of migration estimates. Firms that mainly place developers inside clients' teams usually own much less. The who qualifies page lists the full baseline.

Rights and confidentiality pitfalls specific to dev shops

• Client confidentiality. Estimates and post-mortems can reveal a client's architecture or plans. Redaction and anonymization rules are agreed with the company before any work starts.
• Repositories that look internal but are not. Client code sometimes lives in the firm's own GitHub or GitLab organization. Location does not change ownership.
• Shared channels. Slack Connect or shared Teams channels contain the client's people and messages.
• Candidate data. Coding assessments and interview notes carry personal information.
• Prior licensing. Records already licensed for AI training are a red flag.

Where does a license fit in the sale timeline?

Before the CIM goes out, a license is the owner's decision, and the data inventory doubles as diligence preparation. After an LOI, interim covenants generally require the buyer's consent. After closing, the acquirer decides. Compare the SaaS company sale guide, where the company owns its product code outright, and the guide to selling a cybersecurity firm or MSSP, where client security data narrows what can be licensed.

Who can introduce a dev shop, and how

Software and IT services M&A advisors, fractional CFOs, PE operating partners at IT services platforms and implementation partners who subcontract to dev shops all meet owners at decision points. The M&A advisor referral page covers the advisor workflow, and owners can also put their own firm forward; see whether a business owner can refer their own company.

1. The partner registers, then submits the firm or sends the owner a referral link.
2. SourceX confirms headcount, operating history, record breadth and rights directly with the firm's leadership.
3. The firm builds a data inventory of its own systems; the partner never sees, exports or describes any record.
4. The firm and SourceX agree one all-in price and terms, then AI labs and data buyers review.
5. After signing, data is prepared under the agreed redaction rules and delivered only with the firm's authorization, and the firm is paid.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Payment follows only after the buyer pays and SourceX receives its fee, and no reward is guaranteed.

Conversation starter for a dev shop owner

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

Next step

Put the firm through the company fit checker before anyone drafts the CIM. If it clears the screen, register as a partner to log the introduction, or have the owner apply at sourcex.si/apply via your referral link so your credit is preserved.