Owner decision
Which owner dependencies and governance gaps reduce confidence before a transaction?
Owner-only relationships, knowledge, access, approvals, controls, contracts, and decision rights create operating-transfer questions a buyer or adviser may investigate. Reduce and test those dependencies before a transaction, but do not infer buyer confidence, valuation, terms, or readiness without buyer-specific and qualified evidence.
Use this now: Build a transaction-confidence record across customers, people, knowledge, access, contracts, controls, authority, succession, and recovery time.
Owner worksheet
Transaction dependency-confidence register
| Check | Write down |
|---|---|
| Dependency surface | List customer, supplier, employee, knowledge, access, approval, financial control, contract, and decision surfaces still dependent on one owner. |
| Owner-only evidence | Attach the relationship record, credential, approval history, process gap, contract, or operating test proving the dependency exists and quantify recovery time. |
| Buyer uncertainty | State what a buyer cannot verify, operate, control, or price because of the dependency and the likely diligence, valuation, term, or transition consequence. |
| Remediation and backup | Name the receiving owner, authority or access transfer, documentation, continuity control, and completion date for reducing the exposure. |
| Verification test | Run the relationship, access, decision, reporting, or absence test a buyer could inspect and record pass, failure, evidence, and retest date. |
| Specialist boundary | Identify governance, ownership, accounting, tax, legal, or transaction issues requiring qualified review rather than an operating worksheet conclusion. |
Close the decision: Reduce the dependency with the largest buyer uncertainty and verify the transfer; do not claim transaction readiness from documentation alone.
Worked example
Illustrative buyer-ready owner-dependency evidence packet
Illustrative only: No valuation, buyer-confidence, deal-term, tax, legal, accounting, or transaction-readiness result is claimed.
| Step | Illustrative input | Replace with your evidence | Completed test or status |
|---|---|---|---|
| Diligence question | Can the illustrative company retain and serve Customer A if the founder is absent for 90 days? | Actual buyer/adviser diligence request or internally approved readiness question. | The question is operational; no valuation effect is assumed. |
| Owner-only condition | Founder holds the executive relationship, renewal history, pricing exceptions, and one system credential; Customer A represents an illustrative 35% of revenue. | Customer denominator/period, access inventory, relationship history, and authority record. | Concentration and owner dependency are documented separately. |
| Transfer work | Introduce account leader, document exception authority, establish approved backup credential, and run renewal preparation without hidden founder approval. | Introduction record, authority map, access test, and renewal file. | Documentation alone is not treated as transfer proof. |
| Verification test | Run a 90-day bounded absence simulation; pass only if service, exceptions, access, and relationship cadence continue inside actual limits. | Dated test receipt and failed-case register. | Illustrative duration is a test input, not a universal sale-readiness period. |
| Transaction boundary | Package the evidence for qualified transaction, legal, tax, accounting, and valuation review; do not claim buyer confidence, price, terms, or readiness from the packet alone. | Specialist review and buyer-specific response if one exists. | Decision: hold any readiness claim until transfer tests pass and actual transaction reviewers assess it. |
Decision produced: Build and verify the dependency packet, but do not claim improved buyer confidence, valuation, terms, or transaction readiness without buyer-specific and qualified evidence.
