Selling a business11 min read

What a buyer's analysts ask for, and what they are really testing

After a letter of intent, a buyer's analysts work through a request list on a clock. Behind hundreds of requests sit five questions. How each finding turns into escrow, an earn-out, a deduction or a walk-away, which flags are yellow and which are red, what technical reviewers check beyond the website, and how to run the data room and the questions log.

The short answer. Diligence is the buyer checking whether what you have told them is true, and whether it will still be true the day after closing. Their analysts work from a request list, usually after a letter of intent, inside an exclusivity period and on a clock. Every item you cannot answer cleanly becomes one of four things: a question, a lower price, a condition in the contract, or a reason to walk away. Which of the four depends on whether the problem can be measured and fixed. The owners who come through it well are the ones who asked themselves the same questions a year earlier.

Who the analysts are

"The buyer's analysts" is rarely one person. On a small or mid-sized deal it is usually a handful of teams, each with its own list.

  • The buyer's own deal team, which owns the investment case and decides what matters.
  • Accountants who test the earnings: whether profit is real, repeatable and correctly adjusted. On larger deals this is a formal quality of earnings review.
  • Lawyers who read the contracts, the leases, the employment terms and anything that could change hands badly.
  • Commercial and technical reviewers who look at customers, the market, the systems, the code and the data.
  • The lender's advisers, if the purchase is financed, who repeat part of the work for their own comfort.

Each team asks in its own language, and they often ask for the same thing twice. They also compare notes. An answer given to the accountants that does not match the one given to the lawyers is noticed, and it costs more than either answer alone.

When the questions come, and why speed matters

The serious questions usually arrive after both sides sign a letter of intent. The seller agrees not to talk to other buyers for a period, often a few months, and the buyer uses that time to confirm what they are paying for. The request list can run to hundreds of items.

That clock works for the buyer. While you are bound by exclusivity, your alternatives are paused, and every week of slow answers gives the other side more room. Analysts also read the pace itself. A seller who answers quickly and consistently looks like a business that is run well. A seller who answers late, partially or differently each time looks like risk, and risk gets priced.

What they are really testing

Behind the hundreds of requests there are only a few questions. It helps to know them, because they tell you which gaps matter most.

  1. Are the earnings real and repeatable? Monthly results, revenue by customer and product, one-off items, how much depends on a few accounts.
  2. Does the business run without the owner? Who sells, who delivers, who knows how things work, what happens if one person leaves. Our note on owner dependence is about this test.
  3. Does the company own what it runs on? The brand, the code, the designs, the data, the domain and the accounts, on paper and in practice.
  4. Is anything hidden? Liabilities, disputes, contracts that end or need consent when the owner changes, security incidents, licence breaches.
  5. Is the buyer's plan possible? Whether the systems, the team and the market can carry the growth the buyer is paying for.

How a finding becomes a term

Owners often expect a problem found in diligence to end in an argument about price. More often it ends in the structure of the contract, and the choice of tool follows a simple logic. If a problem can be fixed before closing, the buyer makes the fix a condition. If its cost can be measured, they deduct it. If it can only be judged later, they hold back money or tie part of the price to future results.

The examples below show how that logic usually plays out. The figures come from the US deal studies listed at the end and describe the middle of the market, not a rule and not advice; every deal is negotiated on its own facts, and the terms are for your attorney and accountant.

FindingTypical responseWhy that tool
Code or designs made by freelancers or former staff with no signed transfer of rightsSigning the missing assignments becomes a condition of closing, or part of the price is held in escrow until they are signed. In US private deals without deal insurance the median escrow is about 10 percent of the priceThe company cannot sell what it does not own; the gap is fixable, so the buyer waits or holds money until it is
One customer brings a large share of revenue (buyers and lenders start to see a risk at around 10 percent), or sales depend on the owner personallyPart of the price moves into an earn-out, paid over about two years, the median length, if revenue holdsThe risk cannot be measured today, so the buyer pays for it when it has not happened
A critical security vulnerability, unlicensed software or end-of-life systems that must be replacedThe cost to fix is deducted from the price, usually with a margin on top for risk and the buyer's timeThe cost can be estimated, so it is taken off directly
Accounts, subscriptions or the domain held by a person, not the companyTransfer before closing as a condition, sometimes with a short holdbackFixable in weeks, so it rarely costs money if it is done in time
Known dispute, tax question or past breach that may cost money laterA specific indemnity, often backed by escrow for an agreed periodThe amount is uncertain, so the seller keeps the risk for a while

Each of these costs the seller something: money, time or certainty. A gap you close before the letter of intent is a gap nobody can trade against you.

Yellow flags and red flags

Not every finding is equal, and owners who treat them the same either panic over trifles or ignore what can end a deal. Buyers sort findings into two groups.

Yellow flags can be solved with money, time or a clause. Messy analytics, a dated website, accounts in personal names, missing documentation, outdated software with a realistic plan to update it, an employee contract without a proper confidentiality clause. They lower the price or add conditions, but the deal goes on.

Red flags are risks the buyer cannot fix or measure, and they often end the deal. Code the company does not own and cannot get assigned, because the person who wrote it refuses or cannot be found. Core software copied from somewhere it should not have been. Lawsuits or claims that were not disclosed. Tax arrangements that do not hold up. Numbers that do not reconcile with the bank. A key contract that ends on a change of owner, with a customer who will not consent.

The difference is rarely the size of the problem. It is whether the buyer learned about it from you, with a plan, or found it themselves. A disclosed red flag can sometimes be structured around; a discovered one destroys the trust the rest of the deal depends on.

The technical layer, beyond the website

In owner-run businesses the first surprises are usually basic. When we ask for access on behalf of an owner, there is often no analytics account, the domain is registered to a person, and the hosting is renewed by a former contractor who asks for a transfer once a year while nobody has seen the account. We list those assets in our guide to digital assets a buyer will ask about.

For any business with its own software, systems or customer data, technical reviewers go much further. Three areas come up in almost every review.

Licences. Whether the product respects the licences of the open source code inside it. Some licences, such as the GPL family, can require the source code to be shared when the software is distributed, and the AGPL extends that to software offered over a network. A reviewer runs a scan of every component and its licence. The same question applies to paid services: whether cloud hosting, the CRM, the ERP and other critical subscriptions are contracted by the company, or paid on the founder's personal card under the founder's name.

Security and personal data. Where customer personal data is stored and who can reach it, whether privacy rules such as the GDPR in Europe or the CCPA in California apply, whether there has ever been a breach and how it was handled. Reviewers check that backups exist and have actually been restored, that access is separated by role, that former staff and contractors no longer have it, and that two-factor sign-in protects the accounts that matter.

Single points of failure. What happens if the one system administrator or lead developer leaves. Reviewers look for documentation of the architecture and of how the software is deployed, credentials kept in a company vault rather than in someone's head, and evidence that someone else has done a release. A business that stops when one person is away fails the second test as surely as one that depends on the owner. Our note on key-person risk in technical due diligence goes deeper.

The request owners bring to us

When an owner realises a buyer will look at all this, the first thing they ask us is usually to fix it fast. Update the systems in a day or two. Get back into search within a month: we were at the top ten years ago, then stopped, and now there is nothing.

Some things can be fixed in days, and should be. But analysts do not only look at the current state. They look at history: how traffic and enquiries moved over years, when the software was last updated, how long problems were left alone. A fix made a month before a sale shows up as exactly that. It is a promise, not evidence. We learned how long evidence takes on our own studio: when PERETZ, where The Structure started, rebuilt its neglected presence from its own experience, it took about six months of steady work before traffic grew roughly sevenfold, and it is still compounding.

Running the data room and the questions

The most useful preparation is to build the buyer's request list before the buyer does, and answer it. The mechanics matter as much as the content.

Number the folders. A data room indexed by number lets every team cite a document the same way and see at once what is missing. A common structure:

  • 01. Corporate: formation documents, ownership, board decisions
  • 02. Financials: statements, tax returns, monthly results, adjustments
  • 03. Commercial: customers, contracts, pricing, pipeline
  • 04. People: staff, contractors, agreements, key roles
  • 05. IP and Technology: rights assignments, licences, architecture, security, data
  • 06. Legal and Compliance: disputes, permits, privacy, insurance
  • 07. Property and Assets: leases, equipment, the digital assets register

Each document gets its own number, such as 05.03, and every answer refers to those numbers.

Keep one questions and answers log. Every question from every team goes into one register: a number, the date, who asked, the question, the answer, the documents it refers to, who on your side answered, and its status. Before answering, check whether the same thing was asked before and answer it the same way. The log is what stops the buyer's lawyers and accountants from finding contradictions between answers given on different days by different people.

Only final documents. Put in signed contracts, approved statements and current policies, not drafts, e-mail threads or working notes. Raw correspondence raises questions nobody needed to ask, and every page in the room may later be treated as something you disclosed. If a document does not exist yet, say so in the log and say when it will.

One person in charge. One person, on your side or an adviser, owns the room and the log, so nothing is answered twice or in two versions. And write down the weak points yourself, with what is being done about each, before an analyst finds them.

For a software business, the technical folder is covered in detail in what goes into the technical section of a data room. The slow work, anything that must show up in the results, needs a year or more; our 24-month plan before selling a business puts it in order.

A one-day test

Could you produce each of these within one working day, without calling anyone outside the business?

  1. Monthly results for the last three years, with revenue by customer and product.
  2. A customer list showing how much of the revenue the largest customers bring.
  3. Contracts with customers and suppliers, and which ones need consent when the owner changes.
  4. Signed agreements with staff and contractors transferring to the company what they created.
  5. A list of open source components in your software and their licences.
  6. Critical subscriptions and cloud accounts contracted and paid by the company.
  7. A map of where customer personal data is stored and who can access it.
  8. Proof that a backup was restored in the last year.
  9. Documentation of how the systems are built and deployed, usable by someone new.
  10. The domain, hosting, e-mail and website admin, all in the company's name.
  11. A short written description of how the business wins and serves customers.
  12. A list of known problems, sorted into yellow and red, with what is being done about each.

Every item you cannot produce today is a question an analyst will ask later, when the clock is running.

Who does the work

We review a business the way a buyer's analysts will and say plainly what needs fixing. When an owner wants the technical and digital work done, PERETZ can do it. We share an owner, and we disclose that. Working with PERETZ is never a condition of working with us, a fix is never priced or sold inside a review, and PERETZ work is never checked by the people who did it. Many owners use their own teams, and that is fine.

Where this fits in preparing a sale

This is the work of sale preparation. Gaps in who owns what are covered in ownership gaps in a software acquisition.

We do not value businesses, introduce buyers or negotiate deals, and nothing here is legal, tax or financial advice. Escrow, earn-outs, indemnities, conditions of closing and the structure of any sale belong with your attorney and accountant. Questions about open source licences and privacy law need a qualified lawyer.

Sources

Questions

What do a buyer's analysts ask for when a small business is sold?

Usually several years of monthly results and tax returns, revenue by customer and product, key contracts, staff and contractor agreements, proof of who owns the brand, designs and code, and access to the systems the business runs on. The exact list depends on the buyer and the deal and can run to hundreds of items.

When does due diligence start in the sale of a business?

The detailed requests usually arrive after a letter of intent, when the seller agrees to an exclusivity period, commonly 30 to 60 days and sometimes longer. The buyer uses that time to confirm what they are paying for, so slow or inconsistent answers work against the seller.

What happens when diligence finds a problem?

In general terms the buyer may ask for a lower price, a specific promise with compensation, part of the money held back in escrow, a fix before closing, or payments tied to future results; or they may walk away. How to respond is a question for your attorney and accountant.

Which diligence findings can end a deal?

Problems the buyer can neither fix nor measure: code the company does not own and cannot get assigned, copied core software, undisclosed lawsuits, tax arrangements that do not hold up, numbers that do not reconcile, or a key contract that ends on a change of owner. Disclosed early with a plan, some can be structured around; discovered by the buyer, they usually end the deal.

How should a seller organise a data room and diligence questions?

Number the folders (for example 01 Corporate, 02 Financials, 03 Commercial, 04 People, 05 IP and Technology), number every document, keep one log of every question and answer with document references, put in only final signed documents, and have one person own the process.

Written by
Yevhen Borovoi
FounderYevhen Borovoi

Founder of PERETZ, DeZZign, The Structure and NEX, partner at SCHOEFFEL. An engineer by training who reads a business as one system: strategy, product, technology, processes and economics.

Next step

Preparing a sale or looking at a target?

We reply within one business day. NDA before any documents change hands.