The short answer: introduce the division, the entity signs
Yes, you can refer a division. Partners often know a division president or general manager better than the corporate CEO, and that is a perfectly good place to start. But an unincorporated division is part of a company, not a company, so it cannot sign a license on its own. The records it generates belong to the legal entity, and the officers who can bind that entity under its bylaws and delegation-of-authority policy make the decision.
Your practical job is to give the division leader a clear, bounded proposal they can carry upstairs without rewriting it.
Who owns a division's records
The company does. The people who write a division's tickets, reports and proposals are employed by the legal entity, and under 17 U.S.C. 201 the employer owns a work made for hire unless the parties agree otherwise in a signed writing. The same section allows ownership to be transferred in whole or in part, and lets any exclusive right be transferred and owned separately. That is what allows a company to license one division's records while keeping everything else untouched.
This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.
Division, subsidiary or business unit: who signs?
The label on the org chart matters less than the legal structure underneath it.
| Structure | Is it a legal entity? | Who can sign a license | What to check |
|---|---|---|---|
| Unincorporated division | No | Officers of the company it belongs to | Delegation-of-authority matrix and bylaws |
| Business unit or reporting segment | No | Same as a division | Whether the unit leader has any signing limit |
| Wholly owned subsidiary | Yes | The subsidiary's own officers, within parent policy | Parent approval rules and intercompany agreements |
| Joint venture | Often | Whoever the joint venture agreement names | Each venturer's consent rights and data ownership terms |
| Division sold or being sold | Depends on the deal | Whoever owns the records after closing | The purchase agreement's books-and-records clauses |
How the decision usually travels
In companies with a written delegation-of-authority policy, an unusual contract follows a path like the one below. The company's own policy controls the details.
- The division leader sees the fit and agrees to sponsor the idea internally.
- The leader drafts a one-page scope: which systems, how many years, roughly how many people generated the records, and what is out of bounds.
- The general counsel or outside counsel checks rights: customer contracts, confidentiality clauses and employee notices.
- IT confirms which systems are shared with sister divisions and whether the division's records can be separated.
- The CFO or CEO approves, and the board does too if the policy or the deal's significance requires it.
- An authorized officer signs for the entity, with the division leader as day-to-day contact.
Each approver needs something slightly different from the proposal:
| Who | Role in the decision | What they need to see |
|---|---|---|
| Division president or general manager | Champion and day-to-day sponsor | A bounded scope and a sense of the inventory effort |
| Corporate CFO | Financial approval | One all-in price, a one-time payment and accounting questions to raise |
| General counsel | Rights and contract review | Which customer, vendor and employee terms apply |
| CIO or CISO | Export and separation | Which systems are shared and how filtering would work |
| CEO or board | Final approval where policy requires | Strategic fit and any effect on a sale or other transaction |
How to frame the introduction so it can go upstairs
The division leader should be able to forward your note unchanged. Keep it factual, bounded and free of payment promises.
Shared systems and other complications
Divisions rarely run fully separate stacks. When a division shares a Slack workspace, ERP or CRM with its siblings, its records have to be filtered by channel, project, cost center or account before anything is inventoried. The guide to carve-out data separation explains how teams split shared systems in a divestiture, and the same methods apply here.
SlackOther complications to flag early:
- Headcount and history. The baseline of 50+ full-time employees at peak (contractors excluded) and several years of documented operations is applied during qualification; share both the division's and the parent's figures rather than guessing which one counts.
- Parent policies. Some groups prohibit any data sharing outside the enterprise. Find out before the division leader spends political capital.
- A pending sale of the division. If the division is on the block, a license has to fit the sale process and the purchase agreement, so coordinate with the deal team first.
- A non-US parent. A US division of a foreign group raises its own questions, covered in referring companies outside the United States.
- Your own relationship. If you know the division because your company buys from it, the guidance on referring a supplier your company buys from applies as well.
How credit and rewards work for a division introduction
Credit goes to the first valid referrer whose introduction leads to a verified company application within the attribution window, so record both the parent entity's legal name and your division contact when you submit. 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, and nothing is payable until the buyer pays and SourceX receives its fee. No reward is guaranteed. Check the program terms for how referrals are recorded.
Next step
Ask the division leader two questions: which corporate officer signs unusual contracts, and which systems the division owns outright. Then run a preliminary screen with the company fit checker, confirm the baseline on who qualifies, and register as a partner to submit the introduction in the parent company's name. M&A advisors working on divestitures will recognize the same scoping questions.