Call Centres Briefing is a digital platform providing news and analysis
from the worlds of call centres & customer care

    Preparing an owner evidence pack for an initial acquisition conversation

    By Joash Boyton, founder, owner and CEO of Acquiry

    Sponsored educational article by Acquiry.

    An initial acquisition conversation needs a small set of reliable facts, clear definitions and an honest account of what remains unresolved. An owner should prepare enough evidence to explain the business, its ownership, its commercial model and the outcome being considered. The first exchange should be selected for the next decision, rather than becoming an unrestricted transfer of the company's records.

    The preparation task has two parts. First, organise the underlying evidence privately so important statements can be supported. Second, decide which approved summaries or documents should be shared with the intended recipient at the present stage. A well-organised internal pack does not mean every item is ready for external circulation.

    This guide offers a first-discussion versus later-diligence checklist, an evidence-control method and a hypothetical example. It is a commercial preparation framework, not accounting, legal or tax advice and not a universal diligence specification. Qualified advisers should resolve specialist questions. The goal is a useful next conversation, with fewer avoidable inconsistencies and no implied promise of a buyer, valuation or transaction.

    Give the pack a specific purpose

    Begin with the decision the next conversation should support. The buyer may be assessing strategic fit, discussing the possible perimeter or deciding whether to devote resources to a deeper review. Each purpose calls for a different level of evidence.

    Write a short cover note stating the business or perimeter under discussion, the period covered, the intended audience and the questions the pack is meant to address. Where identity disclosure is not authorised, use an approved non-identifying description. Include important limitations so the recipient does not interpret a preliminary summary as a completed diligence assessment.

    Ask the buyer to prioritise its questions. A broad request for all financial, customer and technology material may reflect a standard template rather than the immediate decision. It is reasonable to clarify which items matter now and which can wait for an appropriately scoped later stage.

    A useful pack should make the next meeting more focused. The reader should understand what the business does, how the relevant measures are defined, which dependencies matter and what the owner wants to explore. It should also make the open questions easy to find.

    Separate preparation from disclosure

    Prepare a private master index of potentially relevant records, including materials that should not be shared initially. This allows you to identify gaps and respond coherently later without exposing sensitive information simply because it has been collected.

    Create a separate release set for each authorised purpose. An initial summary, a financial review pack and a specialist technology review may contain different information. The same document can be suitable for one recipient and unsuitable for another, depending on role, purpose and the applicable arrangements.

    Do not put an opportunity's name or identifying details into an external draft without explicit approval for that disclosure. An internal discussion about the business does not automatically authorise external circulation. An anonymous overview is a useful default where identification has not been approved, provided the combination of details does not identify the business indirectly.

    Keep the focus on proportionate evidence. Confidentiality arrangements and appropriate advice support the process, but they do not make every request necessary. Ask what decision each item supports and whether a less sensitive form would answer the question accurately.

    Describe the business in operational language

    The business outline should explain what customers receive, why they buy it and how the company delivers it. Avoid relying on broad labels such as platform, technology provider or recurring-revenue business without describing the actual activity.

    Identify the principal products or services, customer segments, routes to market and major delivery dependencies. A buyer should be able to distinguish software subscriptions from implementation services, a direct customer relationship from a reseller arrangement and owned capability from access provided by an outside supplier.

    Explain the proposed perimeter. If the conversation concerns a product line rather than the whole business, identify shared functions at a high level. If several entities are involved, show which activities sit where without assuming that a brand name corresponds to a single legal entity.

    Keep promotional claims separate from factual descriptions. A statement that a product is essential to customers requires evidence different from a description of what the product does. For an initial pack, a clear account of the workflow and known customer use is often more useful than an unsupported claim of market leadership.

    Put definitions before financial comparisons

    Financial summaries become difficult to interpret when periods, currencies and measures are inconsistent. State the beginning and end of each period, the currency used and the basis of the figures. Distinguish historical information from forecasts and management estimates from figures reviewed through a more formal process.

    Define the measures used in the conversation. Revenue, invoiced amounts, cash receipts, contracted value and recurring subscription measures can refer to different things. Do not present them as interchangeable. Ask the accountant or appropriate financial adviser to help explain the actual records and presentation basis.

    Identify the reporting perimeter. A consolidated group figure may include activities outside the contemplated transaction. A product-level summary may allocate shared costs using assumptions that need to be explained. The first pack should make these boundaries visible rather than allowing the buyer to infer a standalone result.

    Where management uses adjusted figures, show the adjustments and their rationale separately from the starting measure. Do not quietly replace the underlying result with a more favourable number. Whether an adjustment is appropriate for a transaction assessment is a question for the relevant advisers and buyer review.

    Build a simple reconciliation map

    A reconciliation map connects each headline figure to the record supporting it. It should identify the source report, period, preparer, review status and known differences from other reports. This is an information-control tool; it does not substitute for professional accounting work.

    Start with the figures most likely to shape the initial conversation. If a revenue summary differs from a sales dashboard, establish whether the reports use the same dates, entities, categories and definitions. A difference may have an understandable explanation, but the explanation should be documented rather than assumed.

    Record unresolved differences in an issues list. State the amount or nature of the difference where appropriate, the possible reasons, the person investigating and the expected next evidence. Do not force a reconciliation by changing source data or choosing whichever report produces the stronger story.

    The initial external summary can remain concise. It should state the definitions and material limitations, with supporting work available for an authorised later review. A buyer does not need every transaction record to understand that a figure is provisional or that two reports cover different periods.

    Explain recurring business without overclaiming certainty

    If recurring income is important to the business model, describe what makes it recurring in the records. Is the figure based on active subscriptions, contracted service arrangements, repeated purchases or another measure? Explain the relevant population and period.

    Distinguish recurring categories from one-off work where the records allow it, and identify any judgment involved. Implementation, project services, usage charges and subscriptions may behave differently. The pack should not turn a mixed revenue model into a simpler story merely because a buyer prefers a particular label.

    Where retention or cancellations are discussed, state the unit and time window. Customer counts, account groups and financial measures answer different questions. Do not compare percentages that use different populations or exclude important categories without explanation.

    At the initial stage, it is acceptable to say that a metric needs further reconciliation. Explain what is available and what is being checked. A clear limitation is more useful than a precise-looking figure whose calculation cannot be reproduced.

    Prepare ownership and perimeter information

    Internally assemble a current entity and ownership outline with references to supporting records. Identify which entities and assets may be involved in the proposed discussion and which are outside it. If the structure is uncertain or records need updating, make that an explicit preparation task.

    Distinguish legal ownership questions from commercial descriptions. The founder may describe a product as belonging to the business, but the relevant rights and arrangements should be verified through the actual documents and appropriate advice. The initial pack can identify the question without pretending it has been resolved.

    Record who needs to participate in decisions about the proposed transaction. Do not assume one owner can commit others or that an operational manager has authority over ownership matters. Ask legal advisers to assess the applicable governance and approval requirements.

    For external sharing, choose the level of detail appropriate to the stage. A high-level structure may support an initial perimeter discussion, while detailed ownership records can remain for an authorised later review. Personal information should not be distributed merely because it appears in a corporate document.

    Inventory rights and dependencies

    List the capabilities on which the business depends and the evidence supporting access to them. These may include software, content, data, brands, domains, supplier services, distribution arrangements and customer contracts. The inventory should distinguish what is owned, licensed, supplied or otherwise accessed, subject to verification.

    For each important item, identify the relevant document or record and the specialist question. Does the proposed transaction require a different arrangement? Is a right held by an entity outside the perimeter? Is the commercial operation dependent on an individual or third party? Counsel and other qualified advisers should determine the legal effect of the actual arrangements.

    The initial pack should highlight material dependencies in plain language. It need not include complete agreements or technical repositories before the purpose and access conditions are settled. A buyer should nevertheless be able to recognise when a central acquisition assumption requires further work.

    Do not interpret customer use, audience size or possession of a file as proof of transferable rights. The evidence needed depends on the right in question. Keeping the inventory factual prevents a commercial description from becoming an unsupported legal conclusion.

    Summarise customer mix without unnecessary identities

    A buyer may need to understand concentration, customer segments and purchasing patterns before it needs individual customer names. An aggregated initial summary can often support that discussion, provided the definitions are clear and important dependencies are not hidden.

    Define the customer unit. A billing account, operating subsidiary and corporate group may represent different ways to count the same commercial relationship. State whether concentration is measured by individual accounts or grouped relationships, and use a consistent basis across the summary.

    Specify the period and measure used for concentration. A share of historical revenue is different from a share of current contracted value or cash receipts. Avoid switching between them without explanation. If grouping is incomplete or the source data needs review, state that limitation.

    Keep names and identifying combinations out of the initial external version unless their disclosure has been explicitly approved and is appropriate. Later customer review can be scoped with advisers. The first pack should make the commercial dependency understandable without exposing more information than the decision requires.

    Describe operating capacity and founder dependence

    Prepare a functional outline of how the business operates. Identify who is responsible for sales, product, delivery, finance and other essential activities. At an early stage, roles and responsibilities may be sufficient without individual employment details.

    Explain where the founder remains essential. This might involve customer relationships, technical knowledge, approvals or delivery work. Avoid presenting founder involvement as either automatically positive or automatically problematic. Its significance depends on the buyer's plan and the owner's intended role.

    Identify external dependencies that affect continuity. A contractor, key supplier or shared group function may provide work that the buyer assumes sits inside the business. The pack should flag the dependency and the evidence needed to understand it.

    Separate current operation from the proposed future model. An owner may believe a role can be delegated or a system replaced, but that is a plan requiring resources and verification. State the assumption and work needed rather than presenting the future arrangement as already established.

    Make owner goals and constraints understandable

    Include a concise statement of what the owner is willing to explore. The discussion may concern a full exit, retained ownership, succession or another commercial objective. Define the possibilities without assuming a final transaction structure.

    Describe the intended level of involvement after a potential transaction and any material timing constraints. Distinguish firm requirements from preferences. This helps the buyer understand whether the contemplated process and operating plan can plausibly align.

    Do not include unnecessary personal detail. A commercial statement that the owner seeks a reduced operating role may be sufficient without explaining private circumstances. Share sensitive context only when it is necessary and appropriately authorised.

    Keep the objectives current. If the owner's position changes during discussions, update the relevant summary and inform authorised participants. An old statement about willingness to remain involved can create confusion if it is repeated in later materials without review.

    Use an unresolved-items register

    An evidence pack becomes more credible when it shows the limits of the information clearly. Create a register for missing documents, inconsistent reports, unclear definitions and questions requiring specialist review. The register should identify work to do, not conceal material issues in a footnote.

    For each item, state the question, why it matters to the next decision, what is currently known, the evidence needed and the responsible person. Add a review event or realistic expected update where one has been agreed. Avoid describing every open item as minor before its effect is understood.

    Separate missing evidence from an identified problem. An agreement that has not yet been located is different from an agreement known to contain a relevant restriction. Both require attention, but the summary should not overstate or understate what is known.

    Decide which unresolved items must be addressed before external discussion and which can be disclosed as limitations. Specialist advisers can help assess sensitive questions. The objective is neither to delay indefinitely nor to present an apparently complete pack that rests on unexamined assumptions.

    First discussion versus later diligence checklist

    The following checklist separates a proportionate initial exchange from supporting material that may belong later. It is a recommended starting point, not a universal request list. The actual release should depend on purpose, recipient, permission and appropriate advice.

    Do not interpret the later column as automatic permission to release everything when diligence begins. It identifies categories of evidence that may become relevant. Each request still needs a defined purpose, suitable recipient and appropriate handling.

    A hypothetical minimum first-conversation pack

    Consider a wholly hypothetical owner preparing for a buyer interested in a specialist software capability. The business, figures and circumstances in this example are invented. They do not describe an Acquiry client, a live opportunity or a typical transaction.

    The owner prepares a short business outline, a financial summary, an aggregated customer schedule, a functional team outline and a list of unresolved items. The first pack explains that the discussion concerns the operating business, while one supporting service is supplied by a separate related entity. That dependency is highlighted for later review rather than assumed to be included.

    The financial summary covers a twelve-month period ending in June. A product dashboard covers a different twelve-month period ending in September. The owner does not place the totals side by side as though they measure the same window. The accountant is asked to help prepare a consistent comparison and explain any remaining differences.

    For a simple concentration illustration, assume the relevant period's revenue is 1,000,000 illustrative currency units. Two billing accounts contribute 120,000 and 80,000 units and belong to the same customer group. Together they contribute 200,000 units, or 20% of the total. A schedule that treats them separately shows different account-level shares and should not be described as group-level concentration.

    The owner uses anonymised labels in the external summary and explains the grouping basis. The underlying identities remain in the private master record until a specific disclosure is authorised. The arithmetic is straightforward, but the definition determines what the buyer can conclude.

    The functional outline shows that the founder handles a key product decision and wants a reduced operating role. The pack does not claim the dependency has been solved. It identifies the need to discuss transition capacity. The unresolved-items register also notes that one rights document requires legal review.

    The next conversation can now focus on perimeter, concentration, transition and the buyer's strategic rationale. A complete data room is unnecessary for those initial questions. If the discussion proceeds, the parties can agree a more detailed review of the relevant evidence.

    Create an index that makes later questions easier

    Give each item a stable identifier, descriptive title, owner, date and status. Record the source and the version used in any external summary. Keep the index concise enough to maintain, with sensitive material stored in appropriately controlled locations.

    Use names that describe the content rather than implying certainty. Management revenue summary for a stated period is clearer than final financials if the figures have not reached the review status the latter suggests. A label should help the recipient understand the evidence, not make it sound more authoritative.

    Maintain a change log for material revisions. If a figure is corrected or a perimeter assumption changes, explain the difference and identify which shared versions are affected. This prevents the buyer from continuing to rely on a superseded statement.

    Assign responsibility for answers. A financial question may go to the accountant, a rights question to counsel and an operating question to the relevant manager. Coordinating responses through the pack owner helps maintain consistency without asking one person to answer beyond their expertise.

    Prepare the pack in a controlled sequence

    First, gather existing records and identify the immediate decision. Avoid commissioning a large presentation before understanding which facts are missing. A visual redesign cannot repair inconsistent definitions or unavailable evidence.

    Second, align the perimeter, dates and terminology. Ask the relevant preparers to confirm what each report means. Record differences and decide which require resolution before the first discussion. Keep the original sources intact while the summary is developed.

    Third, write the business and owner-objective summaries in plain language. Use the same definitions throughout. Identify material dependencies and unresolved questions where the reader will see them, rather than burying them in supporting material.

    Fourth, create the proposed release set and check permissions, recipients and handling arrangements. Fifth, conduct a dry run with an authorised reviewer who was not involved in preparing every figure. Ask them to explain what the pack says and where its limits are. Revise anything that produces a materially stronger interpretation than the evidence supports.

    Use a release gate rather than a general permission

    Before sharing, ask four questions: What decision will this information support? Is it reliable enough for that use? Has this recipient and disclosure level been approved? Could a less sensitive version answer the same question accurately?

    Check the actual contents, not only the filename. A document may include hidden identifying context in an example, a customer grouping or an attachment. An external draft can disclose information before it is formally sent if other people have access to the workspace.

    Obtain appropriate advice for confidential, personal, competitive or otherwise sensitive material. Record the version shared and any limitations on its use. If the recipient or purpose changes, revisit the release rather than assuming the original permission is unlimited.

    The release gate should not become a reason to hide a material limitation. If a buyer cannot make the decision without information that cannot yet be shared, explain that constraint. The parties can then decide whether a controlled next stage is appropriate or whether the conversation should pause.

    Adapt the evidence to the business model

    A common pack structure is useful, but the supporting questions should reflect how the business earns and delivers. Do not force every company into a software-style recurring-revenue narrative or a product-sales template. Explain the operating reality and let the relevant advisers determine the appropriate financial presentation.

    For a services business, the initial summary may need to distinguish ongoing engagements from discrete projects, explain delivery capacity and identify where client relationships depend on individuals. A large project pipeline should be described according to its actual stage rather than blended with completed work. Supporting schedules can show what has been agreed, what remains prospective and what resources delivery would require.

    For a software business, explain the relationship between products, subscriptions, implementation and support. Identify whether the figures count organisations, accounts or users. If a key capability depends on an external provider, include that dependency in the business outline rather than leaving it to a later technical discovery.

    For a content or information business, describe the revenue sources and the distinction between audience access, customer relationships and underlying rights. An audience count does not answer the rights question. The initial pack can identify the relevant assets and evidence needed for specialist review without circulating detailed contracts or personal data prematurely.

    For a business with several models, keep the categories visible and explain shared resources. A combined total may be suitable for a high-level overview, but it should not conceal that one activity has a different delivery burden or dependency. The buyer can then decide which part of the model needs deeper investigation.

    A final pack-quality review

    Before approving the release set, ask an authorised reviewer to answer the following questions using only the proposed pack. If the answer requires an unsupported assumption, revise the text or record the limitation.

    This review should produce specific corrections rather than an overall confidence score. A pack can be strong in most areas while one unclear perimeter statement materially changes the conversation. Resolve that statement or make the uncertainty prominent. Do not average an important weakness away because the remaining documents are well organised.

    Questions owners often ask

    What if a historical record cannot be located?

    Record the gap and investigate appropriate alternative evidence with the relevant adviser. Distinguish a reconstruction from an original record and explain its basis. Do not recreate a document in a way that implies it existed at the time or describe an unsupported recollection as verified evidence. The buyer should understand what can and cannot be established.

    Do I need a full data room before the first call?

    Not necessarily. Prepare the underlying records privately, but select the first exchange for the decision at hand. A concise, reliable summary can support an initial fit discussion. A full diligence request should follow a clearer scope, appropriate permissions and relevant advice.

    What if the financial reports do not match?

    Identify whether their periods, definitions, entities and categories differ. Ask the appropriate financial professional to help reconcile them. State material limitations in the summary and track unresolved differences. Do not quietly choose the report that makes the business look stronger.

    Should customer names appear in the initial pack?

    Only when their disclosure is necessary, explicitly approved and appropriate under the relevant arrangements. Aggregated information may answer initial questions about concentration and segments. Explain the grouping basis and limitations so anonymity does not create a misleading picture.

    How should forecasts be presented?

    Separate forecasts from historical results and state the principal assumptions, period and preparer. Explain which assumptions depend on actions or resources not yet in place. A forecast should not be presented as a result already achieved or as a guaranteed outcome.

    Can unresolved rights questions wait until later?

    That depends on their significance and appropriate advice. A question central to the capability the buyer wants may need attention early. At minimum, make the uncertainty visible and identify the evidence and specialist review required rather than presenting ownership as settled.

    What if the buyer requests more than the current stage seems to justify?

    Ask which decision the request supports and whether a narrower summary or specialist review would suffice. Explain the information boundary and propose a proportionate next step. If the question cannot be answered within the authorised scope, acknowledge the limitation rather than improvising a conclusion.

    Where Acquiry's process is relevant

    Acquiry offers selected sell-side advisory alongside its buy-side origination focus and describes structured preparation, confidential exchanges and diligence stages. That process is relevant to owners who need help organising a credible transaction discussion, subject to the actual engagement scope and suitability.

    An owner may first need an accountant to reconcile financial information, counsel to clarify rights or an internal operating review to explain dependencies. Those tasks should be assigned to the appropriate people rather than assumed to be resolved by an advisory presentation. Preparation supports a better conversation; it does not establish buyer appetite or a particular valuation.

    The useful test is whether another authorised person can understand the business, trace the important statements and identify what remains uncertain. A focused evidence pack gives the owner a controlled way to answer the next question while preserving the deeper material for a properly defined later review.

    About the author: Joash Boyton is the founder, owner and CEO of Acquiry, an international M&A advisory firm based in Melbourne with a core focus on buy-side acquisition origination and selected sell-side work. acquiry.com.

    Sources and further reading