Who Inside the Company Needs to Know You Are Selling

Short answer

Deciding who inside the company knows you are selling is a finance-function problem before it is a communications problem, because nearly every early diligence request has to be filled by someone with access to the books. The safe answer is not "nobody." It is a deliberate, recorded decision about who is read in fully, who is read in on a narrow slice, and who is asked for work without being told why.

A leak almost never comes from an org-wide announcement. It comes from a request that did not make sense. A controller asked for three years of revenue by customer, by month, formatted differently than anyone has ever wanted it, in a week when the owner is unusually unavailable, will draw the correct conclusion within a day. Sometimes two.

So the question is not whether to trust your team. It is which requests require someone inside to be told, and how to fill the rest without the request doing the telling.

The three access tiers, compared

A read-in is a deliberate decision to tell a specific person that the business is for sale, recorded with the date and the reason you made it. Everything below sorts people into one of three tiers.

Read one column at a time.

A full read-in sees the entire process and is accountable for the package holding together. This group should be small enough to name on one hand, and it has to include whoever owns the finance function, because a diligence list that nobody reviews as a whole produces internally inconsistent answers.

A slice read-in is told that a confidential process is underway and is given one workstream, without buyers, timeline, or the rest of the list. This tier exists because access should follow the record rather than the org chart. The head of operations may need to produce a customer schedule while never seeing anything about price or process.

Not read in is where most of your team belongs for most of the process, and it is a workable position only when the requests they receive look like ordinary work. That is the constraint that decides how large the other two tiers have to be.

Who has to be read in fully, and why the group stays small

The full read-in group is defined by the work, not by loyalty or tenure, and the work usually names three or four seats: you, whoever owns the finance function, your outside accountant, and your attorney. That is it at the start.

The finance seat is not optional, and this is where owners most often try to compress the group to one. It does not hold. The early diligence list is largely accounting: monthly financials, revenue detail by customer, reconciliations, adjustment support, receivables aging, and the tie-out between internal statements and filed returns. Specific requests vary by buyer and by the scope of the review, but the accounting core is consistent. An owner filling that list alone, on nights and weekends, produces a package with mistakes in it, and mistakes in the first package are expensive to walk back.

If nobody inside can fill that seat without being read in, the alternative is filling it from outside. An outside accounting partner is already covered by an engagement and can produce the same schedules without adding a name to your internal list. That is often the cheaper answer, and it is why founders working with an outsourced finance function have an easier time keeping a process quiet than founders with one in-house bookkeeper who knows everything.

The one-name rule, and the request log that goes with it

The one-name rule: for each item on the diligence list, exactly one internal person is named as the preparer of record, and if an item cannot be filled without adding a second internal name, it goes to an outside preparer instead.

Keep the log in one place, one line per request, with four columns: the item, the preparer of record, the date it was filled, and the tier that person sits in. That log does three things at once. It shows you the real size of your read-in group rather than the one you assume you have. It catches the moment when a new item would require a new person, which is the exact moment to decide deliberately rather than by reflex. And when a buyer asks a follow-up question six weeks later, it tells you who built the original answer, which matters, because inconsistent second answers are read as evasion rather than as forgetfulness.

The log is also the artifact that makes the wind-down clean. Deals do not all close. If yours does not, you want a written record of who knew what and when, so you can decide who needs a conversation rather than reconstructing it from memory.

How to ask for work without announcing the deal

Ask for the output, not the reason. This is the whole technique, and it works because most diligence artifacts are things a well-run business should be producing anyway.

• Ask for it in the format you already use. A reconciliation, a revenue-by-customer report, a margin-by-month view. A request that arrives in the standard format, on the standard cadence, is invisible. A request for the same data in a new template is not.
• Do not invent a reason. A false explanation that later unravels costs more trust than the original silence would have, and a team that catches one stops believing the next one. "I want to see this monthly from now on" is usually both true and sufficient.
• Fold non-urgent items into ordinary review. Fixed asset listings, inventory counts, and contract files are all things a business tightens up periodically, and periodically can be now.
• Route the items that cannot be disguised to the outside. A three-year normalized earnings schedule with adjustment support has no plausible internal purpose. That is what your accountant is for, and it is the clearest case for keeping a name off the internal list.
• Keep the monthly close on its normal calendar. A close that suddenly speeds up, or a founder who suddenly cares about a report they never opened, is a signal by itself. Standing routines are the best cover available and they cost nothing, because you should be running them regardless.

Where the workload actually lands, and what that forces

A quiet process concentrates work on the smallest group, which is the real reason confidentiality fails. The failure is rarely a betrayal. It is a founder and one finance person absorbing a diligence list on top of a full operating month, until either the close slips or someone else gets pulled in without a decision being made.

Two conclusions follow, and both are unglamorous. Get the recurring reporting current before a process starts, because current records convert most diligence requests from projects into retrievals, and a retrieval does not need a new person. And decide in advance where the surge capacity comes from, naming it before you need it, so that the answer at week six is not whoever happens to be available.

The reports you should already be running during a live process are covered in seven reports to keep running while your business is under contract, and what actually leaves the building, in what order, is covered in what to send a buyer, and when.

Choose the tier by what the request needs

Four rules, in the order they usually apply.

• Read someone in fully if they cannot do their part of the work without seeing how the parts fit together. In practice that is the finance seat and your outside advisors, and almost nobody else at the start.
• Read someone in on a slice if a specific record they own is on the list and cannot be produced without them. Give them the workstream and the confidentiality expectation, not the process. Whether any retention or severance arrangement should accompany that conversation is a question for your attorney and your CPA, because those terms vary by state and by agreement.
• Leave someone out if every request you need from them looks like ordinary work in the ordinary format. This is the default, and current records are what make it available.
• Read the room instead of the rule if someone has already guessed. This is the honest fourth answer. A long-tenured manager who has watched you take unusual calls and pull unusual reports has drawn a conclusion, and denying it damages more than confirming it under a confidentiality expectation would. Move them up a tier deliberately, record the date, and give them a defined scope. An unmanaged suspicion spreads faster than a managed disclosure.

The short version

Access should follow the record, not the org chart, and every read-in should be a decision with a date on it rather than something that happened. Keep the full tier to the seats the work requires, use outside capacity for the items that cannot be requested innocently, and keep your standing reporting on its normal calendar, because routine is the cheapest cover you have.

The other half of this problem lives outside the building, where the questions are blind profiles, staged NDAs, and how much competition you can create without exposure. Texas Exit Advisors covers how a confidential sale process is actually run.

Last reviewed: September 2026. This is general information, not accounting, tax, or legal advice. Disclosure obligations, employment terms, and confidentiality agreements vary by state, by contract, and by circumstance, so have your attorney review what you plan to say and to whom. Thryve Accounting & Advisory is not a tax preparation firm and does not provide income tax planning or filing.

Where Thryve fits

Thryve Accounting & Advisory is frequently the reason a process stays quiet, because an outsourced finance function fills the accounting side of a diligence list without adding a single name inside the company. Monthly closes that stay on calendar, reconciliations that are already current, adjustment support captured as it happens, and schedules produced by people who are already under an engagement.

If you are thinking about a sale in the next couple of years and your finance function is one person who would have to be told, that is worth a conversation now rather than in week six of a live process.