Key takeaway
Four recipient names can still leave most planned receipts exposed to one common group.
Count economic dependencies, not just logos
A licensing plan with several recipients can look diversified while two or more depend on the same parent, sponsor, acceptance process or operating platform. Before relying on the count, identify the legal payer, relevant group relationships and any shared event that could delay receipts. Unknown ownership is an unresolved diligence item, not evidence that recipients are independent.
The OCC's September 2026 version 3.0 concentration handbook describes common sensitivities and related exposures in regulated banking. That is a useful analogy for grouping dependencies, not a rule for licensing owners. No banking concentration threshold is adopted here. The current version and relevant passages were read 10 October 2026. The commercial tool below is an original scenario, not a forecast, deal offer or claim of recipient demand.
Work a four-license quarter
This hypothetical USD scenario assumes four separately accepted, nonexclusive licenses for a frozen package, with no refresh duty and payment due within one quarter after each separate acceptance. A pays $40,000, B $20,000, C $30,000 and D $10,000. A and B share verified fictional parent G1; C and D belong to different groups. The $100,000 total is an assumption about executed, accepted contracts, not a pipeline estimate.
The largest individual share is 40%, but the largest group share is 60%. If G1's two payments move outside the quarter while C and D pay on time, in-quarter receipts fall to $40,000. This scenario models correlated timing, not permanent default probability, legal liability or statistical correlation. It also does not assume that a common parent guarantees either entity's obligations; contractual responsibility still needs its own review.
| Hypothetical recipient | Quarter receipt | Verified illustrative group |
|---|---|---|
| A | $40,000 | G1 |
| B | $20,000 | G1 |
| C | $30,000 | G2 |
| D | $10,000 | G3 |
| Total | $100,000 | Largest individual 40%; G1 group 60% |
Put the dependency beside costs and timing
In this hypothetical quarter, assume $25,000 of incremental cash costs remain payable in the quarter even if receipts are delayed: a preparation contractor works 200 hours at $50 per hour, legal/privacy review costs $5,000, four delivery tasks cost $1,000 each, and recipient support costs $6,000. These are fictional vendor cash payments, not a valuation of unpaid founder time. There are no other external fees, recurring refresh charges or deductions in this simplified scenario; tax, financing and other business overhead are excluded.
Full-payment quarter cash contribution is $100,000 − $25,000 = $75,000. With G1 delayed, it becomes $40,000 − $25,000 = $15,000. If no license produces a receipt and the same preparation/delivery/support cash is still incurred, the no-deal cash result is −$25,000. Actual no-deal costs may be lower if work stops earlier; change those assumptions explicitly. None of these totals promises profit or shows the within-quarter peak funding requirement.
OpenStax’s differential-analysis framework compares relevant future revenues and costs while separating sunk costs. Here the quarter ledger counts the stated future vendor payments as cash outflows; earlier spending is outside its defined period. The grouping guidance supplies a dependency question, and all dollar amounts remain original assumptions rather than observations from those sources.
| Quarter scenario | Receipts | Costs | Cash contribution |
|---|---|---|---|
| All four pay | $100,000 | $25,000 | $75,000 |
| G1 receipts delayed beyond quarter | $40,000 | $25,000 | $15,000 |
| No receipts; stated work still paid | $0 | $25,000 | −$25,000 |
Build a small exposure register
Record contract entity, payer, verified parent/group, payment trigger, due period, disputed/accepted status and shared dependencies. Keep executed receivables separate from unaccepted offers and exploratory leads. A receiving-program conversation belongs in a pipeline view with uncertainty, not in the committed cash total. If group information is unavailable, show an unknown bucket and a task to resolve it.
Run at least one group-delay scenario and one shared-process scenario. Two otherwise unrelated recipients might use one evaluator, platform or funding event; grouping only legal parents may miss that dependency. Conversely, common ownership alone does not prove payments will move together. Write the scenario assumption and its consequence without inventing a probability. The register should support a decision about optional work, contract milestones or contingency funds, not a universal recipient-count target.
A second banking analogy comes from the agencies’ third-party guidance, which considers subcontractor reliance and dependence on one provider for several activities. In a licensing plan, ask whether separate recipients share a necessary downstream evaluator or acceptance service. Record the actual relationship and a scenario before claiming independence or correlated delay. The guidance concerns banks; this question is an original commercial review tool and does not impose its supervisory framework on a data owner.
Use concentration to change a concrete decision
For the example, the executive can see that removing G1's timing dependency leaves $15,000 of quarter cash contribution under the stated costs. The next action is to verify both contracts' acceptance and payment obligations, identify which costs can stop or move, and review whether the company can absorb the scenario. Offer comparison helps track differing triggers; Earnings can recompute a simpler aggregate cost case, but neither tool automatically identifies related groups.
VOID has no upfront seller referral fee and may receive conditional compensation from a receiving program. That referral compensation is separate from seller license proceeds and is not deducted here. Approve a named recipient and exact metadata before an introduction; samples, evaluation and each license need separate decisions. An additional recipient name does not by itself establish a new independent revenue source, a paid outcome or a guarantee of earnings.