Launch filmLaunch filmTalk to SKOR

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.

The Brightwater / Orion packetMerger closing packet · Harborlight Ventures I
Pre-closing / draft funds flowFictional transaction
View A of E
The trace

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.

Documents5In the fictional packet
Source linked2Controlling text · schedule P-41

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.

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.