Illustrative workflow · fictional transaction
One merger. Many connected decisions.
Price, schedules, consents and funds flow must agree before anyone can call a closing amount final.
A / Packet · Identify the sources · 01 / 05
Know which document owns each fact.
- Source linked
- Provisional math
- Human decision required
The fictional packet includes a signed agreement, two schedules, capitalization support and a draft funds flow.
The packet register
Which document owns each fact- Merger agreementAgreementPrice formula, earnout and conditionsControlling text
- Demo schedule P-41ScheduleIllustrative cash, debt and escrow inputsSubject to review
- Demo schedule C-52ScheduleCustomer consent statusOpen item
- Cap tableCapitalization supportSeller interests and allocation supportReconcile
- Draft funds flowClosing funds flowProposed $104m closing lineUnapproved draft
A filename or folder position alone does not make a draft authoritative.
B / Map · Join the clauses · 02 / 05
Read the agreement as a connected set.
- Source linked
- Provisional math
- Human decision required
Cross-references matter more than a plausible isolated sentence. The second reader points to candidate clauses; deterministic checks compare definitions, schedules and the draft output.
The clause map
Agreement → schedules → supportThe model proposes each link; deterministic checks compare it with the schedules.
C / Bridge · Recompute the price · 03 / 05
Show the math without inventing the answer.
- Source linked
- Provisional math
- Human decision required
The known inputs reconcile to a provisional subtotal. The final working-capital adjustment has not been established, so the closing amount is held.
The price bridge
Source → schedule → numberThe $15m maximum earnout is contingent and excluded from this subtotal. $104m is neither a final wire nor the fund’s share of proceeds.
D / Hold · Resolve conflicts · 04 / 05
Put the contradictions in the open.
- Source linked
- Provisional math
- Human decision required
The draft funds flow repeats the $104m subtotal as if it were final. Working capital and the consent evidence say otherwise.
The contradictions
Each with a named owner- Working capitalPossible $3m credit; treatment and final amount unverifiedFinance owner
- Customer consentSchedule says pending; checklist says completeCounsel owner
- Closing funds flow$104m draft line omits unresolved adjustmentTransaction lead
- Seller allocationFinal proceeds and cap table not reconciledFund finance
Each contradiction goes to a named owner; none is resolved by the model.
E / Handoff · Show the decision · 05 / 05
A handoff that says what is known—and who owns the rest.
- Source linked
- Provisional math
- Human decision required
This illustrative artifact carries the cited subtotal, the separate contingent earnout and the two unresolved gates. It is a review packet, not a closing statement.
Brightwater / Orion · merger review sheet
Fictional · not approved- Price bridge$104m provisional; final adjustment openSource linked
- EarnoutUp to $15m contingent; excluded from closing cashTracked separately
- ConsentAnchor-customer status unresolvedCounsel review
- Funds flowDraft requires revised working-capital supportNot released
- Fund allocationAwait final proceeds and cap-table reconciliationNot computed
- Actual wire/posting$0 by this pageNo live action
A review packet, not a closing statement.
Who owns the rest
- Working capital
- Finance owner
- Customer consent
- Counsel owner
- Closing funds flow
- Transaction lead
- Seller allocation
- Fund finance
What this demonstrates
A traceable decision, not a magic answer.
No documents are uploaded, analyzed, signed or posted by this page.
Every term and amount here is invented.
The work behind a portfolio exit
Follow the terms across the packet.
Five views connect what each source says to the next decision. A plausible number is not treated as a closing instruction while a schedule or condition remains unresolved.
A merger agreement rarely travels alone. This example shows how a coded workflow can connect the packet, a focused model can point to relevant language, and named people can resolve the exceptions. It is a demonstration, not a review of a real deal.
From transaction to fund record
One agreement can affect every downstream book.
The fund lifecycle models portfolio exits. Choose Portfolio level there to see that event; this separate packet illustrates the document work behind an exit. A closed merger could change cost basis, realized proceeds, retained escrow, contingent consideration, LP allocations and reporting. Here the disputed inputs remain held, so none of those downstream results is asserted.
Connect documents and calculations, expose conflicts, and hand the exact open questions to the people authorized to resolve them.