Acquisition Decision Review: Offers, Owners and Integration Evidence
Original website companion. This is not a manuscript excerpt or verified chapter summary. Its three independent packets are fictional teaching examples, not completed transactions or client outcomes.
Start with the decision the packet can actually support
A negotiation conversation, a list of advisers and an integration spreadsheet are different kinds of records. None is an executed acquisition. This exercise asks you to identify what each record establishes, what remains open and which next decision needs a named owner. The goal is a reviewable decision trail, not a score that predicts whether a deal will close.
Use the three fictional packets below as a small evidence-reading exercise. Read the supplied record before its interpretation, write your own review in the empty CSV field, and then compare. A useful answer points to a specific missing document or unresolved decision. “Looks good” does not identify the evidence needed to move forward.
These examples do not establish the value of a real business, the enforceability of a term or the availability of financing. They also do not represent a sequence of actual transactions. A01, T01 and I01 are separate invented scenarios; do not combine their numbers into one supposed deal.
A01: Distinguish a proposed concession from agreed terms
The invented offer memo starts at a total stated price of $600,000: $450,000 cash at closing and a $150,000 seller note. An unsigned buyer counter proposes a $580,000 total, divided into $400,000 cash and a $180,000 note. The packet contains no seller response. Both price components reconcile, but arithmetic does not make either proposal accepted.
Comparing the proposals gives a $20,000 decrease in stated total price, a $50,000 decrease in cash at closing and a $30,000 increase in the note. Calling this simply a $50,000 discount would hide the larger deferred component. The counter changes the funding mix as well as the stated price. Those differences say nothing by themselves about the economic value of the note.
Neither memo supplies the note interest rate, payment dates, maturity, security, guarantees, priority or default provisions. Do not fill these gaps with customary terms. Without a payment schedule and relevant assumptions, this packet cannot support a monthly payment, a debt-service comparison or a present-value conclusion. It also cannot establish that the buyer has the closing cash or that a lender permits the proposed structure.
A defensible review would request the seller response and a complete proposed payment schedule, then identify who will review the resulting terms. Keep “requested,” “received,” “reviewed” and “agreed” as separate states. The packet has reached the first state only when an actual request exists; a reviewer suggestion alone is not proof that anyone sent it.
T01: A contact list does not assign a review decision
The second invented packet lists a lawyer, accountant and lender as contacts. A task row says “review working-capital adjustment.” Its due date is Friday, but its owner and reviewer-acceptance fields are blank. An attached email says “we should have someone look at this.” There is no assignment message or acknowledgement.
The supported interpretation is an unassigned review task with a stated target date. Having three professional contacts does not prove that any of them accepted this work, received the relevant schedules or agreed to the deadline. Do not label the review complete because the contact list looks comprehensive.
A useful next record would name the proposed decision owner, describe the exact schedules and draft clause to review, and record whether the intended reviewer accepted the scope and timing. In real work, professional scope and engagement terms matter. This exercise cannot decide which profession or individual should own a particular legal, tax, accounting or credit conclusion.
Write the unresolved issue in the handoff itself. For example: “Owner is not yet assigned; obtain scope and acknowledgement before treating Friday as a committed review date.” This is a description of the missing evidence, not an instruction already delivered to a real adviser. Leave the observed review field empty until you carry out your own exercise.
I01: A planning benefit is not an observed saving
The third invented spreadsheet lists a $36,000 one-time migration cost and a proposed $3,000 monthly reduction in software expense. It contains no invoice, cancellation confirmation, revised vendor contract or post-migration expense record. The planning note says both teams would use one system. There is no tested data migration or documented acceptance by the operating teams.
If, solely for an arithmetic illustration, the entire $3,000 reduction begins immediately, recurs each month and no other costs change, $36,000 divided by $3,000 is 12 months. That is a simple undiscounted recovery calculation under those assumptions. It is not evidence that recovery will occur in twelve months, a valuation, a return forecast or a finding that the integration should proceed.
The packet omits duplicate-running costs, contract termination charges, implementation labor, timing of the reduction and any change in service quality. An unknown cost is not a measured zero. If only $2,000 per month were realized under the same simplified assumptions, the arithmetic would be 18 months; that sensitivity is another invented input, not an observed alternative outcome.
Before changing the status to “verified,” a review would need the relevant cost records and a defined operational acceptance test. Keep the proposed reduction separate from expenses actually avoided. A completed software installation would not by itself prove that a vendor bill stopped, users can complete required work or records migrated accurately.
Review the evidence states before the next commitment
For each packet, write three short statements: what is present, what is absent and what decision the missing evidence prevents. Use names of records rather than confidence adjectives. “No seller response in packet” is more traceable than “negotiation probably going well.” “Owner field blank” is more precise than “team seems aligned.”
The downloadable CSV contains the supplied records and supported interpretations plus an empty observed_review column. That blank is deliberate. It does not mean the packet failed a review, nobody responded or a benefit was zero. Complete it only with your own reading notes. All three rows are marked fictional, and none contains actual business, client or counterparty information.
Keep a proposed next step separate from its completion. A request for an executed document, an accepted assignment or evidence of a realized cost reduction may be the right question, but the question does not answer itself. This distinction also makes it easier for another reviewer to see where the decision trail stops.
Three fictional acquisition decision packets
A01: Unsigned offer counter
- Supplied record
- Separate fictional proposals: initial total of $600,000 = $450,000 cash + $150,000 note; unsigned counter total of $580,000 = $400,000 cash + $180,000 note. No seller response or note schedule supplied.
- Supported interpretation
- The counter decreases the stated total by $20,000 and closing cash by $50,000, while increasing note principal by $30,000. No acceptance, payment amount or financing approval is established.
- Review question
- Which response and complete note terms are needed before comparing obligations?
T01: Unassigned adviser review
- Supplied record
- Three professional contacts; working-capital review row due Friday; owner and acceptance fields blank; email suggests someone should review.
- Supported interpretation
- A target date exists, but neither assignment nor acceptance nor completed review is established.
- Review question
- What named scope and acknowledgement would turn the proposed handoff into an assigned task?
I01: Unverified integration benefit
- Supplied record
- Planning-only cost of $36,000 and proposed monthly reduction of $3,000; no invoices, cancellation evidence or accepted operational test. A separate hypothetical sensitivity uses $2,000 per month.
- Supported interpretation
- Simplified assumed arithmetic gives 12 months at $3,000 per month or 18 months at $2,000. Neither is observed recovery or a forecast; omitted costs and timing remain unknown.
- Review question
- Which cost records and operational acceptance evidence are missing before any benefit can be recorded as realized?
Download the fictional review packets CSV.
Return to Creative Acquisitions overview for book purchase options and other website reading companions. Use the book itself to verify its contents and chapter sequence.
Original website exercise by Robertson Books. Reviewed 2026-11-22.