Questions to ask a buyer when selling your business
Sellers should ask a buyer about strategy, systems and archives, side initiatives such as a data license, deal terms and people before granting exclusivity. This checklist adds reference calls with former sellers and a table for reading the answers, so owners and advisors can compare buyers on more than price.
Why should a seller ask questions of the buyer?
Sellers should interview the buyer because the buyer's plans decide what happens to your people, systems and records after closing. A price is only one term; integration, earn-out control and records handling shape the rest of your outcome. This is reverse diligence, and it works best when your advisor runs it alongside the buyer's own review.
The list below is built for owners and their advisors. It focuses on areas most buyer-question lists skip: what the buyer will do with your systems and archives, how it treats side initiatives such as a data license, and what former portfolio CEOs say about how it behaves after closing.
The checklist
Group questions by topic and mark the answers in writing. Ask in a management meeting, then confirm by email.
Strategy and fit
- Why do you want this business, and what is the plan for it in years one to three?
- Will we operate as a standalone brand, merge into an existing unit or be absorbed?
- What happens to our management team's roles, reporting lines and compensation?
- Which of our products or customers would you prioritize, reduce or end?
- How many similar acquisitions have you completed, and what did you change afterward?
Systems, archives and records
- Which of our systems will you keep, migrate or decommission, and on what timeline?
- Who owns the export plan for email, chat, CRM, finance, support and engineering tools before anything is shut down?
- How long will you preserve our historical records, and where will they live?
- Will our current subscriptions stay in place, or will contracts need assignment or consent? See whether software licenses transfer in an acquisition.
- How do you handle customer data we hold under confidentiality or privacy promises?
Side initiatives and data licensing
- How do you treat a data licensing arrangement signed or contemplated before closing?
- Would you accept a pre-close license if its term and exclusivity are disclosed, and would you want approval rights?
- Do you plan your own licensing of acquired records, and would that conflict with ours?
- If a license delivery is still pending at closing, who owns the obligation and the proceeds?
- Are there reps or covenants you would add about data, and how long would they survive? The survival period explainer shows the usual structure.
Deal terms and certainty
- What are the conditions to closing, financing sources and approvals required?
- How much of the price is cash at close, rollover, earn-out or deferred?
- How are working capital, debt-like items and the earn-out calculated, and who controls the metrics?
- What happens in confirmatory diligence if you find an issue? See what happens after the LOI.
- Do you plan to use representation and warranty insurance? The underwriting call guide lists the questions to prepare.
People and communication
- Which employees are critical to retain, and how do you plan to keep them?
- What is your approach to employee communication, and when? Read when to tell employees.
- What integration team will I work with, and who is my day-to-day contact after closing?
How do you check what the buyer says?
Reference calls test the answers. Ask the buyer for contacts at former portfolio companies and former sellers, and call at least two whose outcomes were not the best.
| Ask the reference | What you learn |
|---|---|
| What changed in the first 100 days? | Whether the integration plan matched the promise |
| How did the buyer treat your older systems and archives? | Whether records were preserved or retired on a fixed schedule |
| Did side projects or licensing ideas get support or blocked? | How the buyer treats initiatives outside its plan |
| Were earn-out metrics honored as agreed? | Whether post-close control matched the term sheet |
| What would you negotiate differently? | The sharpest risk in the buyer's standard terms |
How should you read the answers?
| Answer type | What it means | Next action |
|---|---|---|
| Specific, with dates and owners | The buyer has done this before | Get it into the LOI or the purchase agreement |
| General reassurance | Plan may not exist yet | Ask for a written summary |
| Refusal to discuss | The topic may conflict with their model | Weigh it in your price comparison |
| Contradicted by a reference | Risk of poor follow-through | Request a covenant or change the structure |
What if you manage an MSP or other services business?
Ask the same questions with extra attention to customer contracts, staff transitions and tool consolidation, since a buyer often merges platforms quickly. Ask when each tool will be retired and whether ticketing and monitoring histories will be exported first.
Why does the systems section matter for licensing?
Companies with 50+ full-time employees at peak (contractors excluded) and years of records across many systems can qualify for a SourceX data licensing introduction. The company keeps ownership, data is licensed, not sold, and nothing is binding until the company signs. If archives will be retired after a sale, the window to export them narrows. Ask the buyer early, and review the guide on what to share before the LOI so disclosure is timed correctly. Your advisor may also help; see how to choose a software M&A advisor.
Red flags in a buyer's answers
- The buyer cannot name who will own the export of historical records.
- The buyer asks you to sign exclusivity before addressing integration.
- The buyer will not allow reference calls with former sellers.
- The buyer rejects disclosure of a prior license rather than discussing terms.
- Earn-out metrics depend on systems the buyer controls with no reporting commitment.
Next step
Print the checklist, add your own questions and run it with your advisor before signing the LOI. If you are also exploring a data license, use the company fit checker and the who qualifies page. Professionals who know a qualifying company can register as a partner; advisors may also want the guide on asking an owner for permission to make an introduction. Companies can apply directly at sourcex.si/apply.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
When should a seller start reverse diligence on a buyer?
After you receive indications of interest and before you grant exclusivity. At that stage you still have alternatives, so the buyer has reason to answer in detail. After exclusivity begins, your leverage drops and refusals become harder to act on.
Who should ask the buyer these questions?
Your advisor can ask the structured questions in writing, while the owner asks the strategic and cultural ones in a management meeting. Using both channels shows whether the answers are consistent. Keep a log of answers so you can compare buyers side by side.
How many reference calls should I make?
At least two or three, including a seller whose deal went less smoothly. Ask for contacts that the buyer did not hand-pick if possible. One strong reference is encouraging, but patterns across several calls are more reliable.
What should I ask about my company's data and archives?
Ask who owns the export plan, which systems will be retired and when, and how long historical records will be preserved. If you have a data license signed or under discussion, ask how the buyer would treat it. Get answers in writing before exclusivity.
Can a data license conflict with a buyer's plans?
It can. An exclusive license for an agreed term may restrict how the buyer uses the same records, and a pending delivery may need coordination. Disclose it early, ask the buyer's view, and have counsel reflect the outcome in the purchase agreement.
Related pages
- Are software licenses transferable in an acquisition, and what happens to the data?
- How long do reps and warranties survive, and how do data licenses affect claims?
- What is confirmatory due diligence, and what happens after the LOI?
- RWI underwriting call questions: data, privacy and AI topics to prepare
- When to tell employees you are selling your business, and in what order
- What should a seller share with buyers before an LOI, and what should they hold back?
Free resources
- PDF bank statement to CSV converter — Turn Chase, Bank of America or Wells Fargo PDF statements into CSV, privately in your browser.
- Client data licensing eligibility checker — A transparent preliminary screen for one company.
- Enterprise value calculator — Enterprise value from equity value, debt and cash.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment