Usually, buyer contact with employees or customers is justified only when a defined diligence question cannot be answered reliably from records, management, or advisers. It should be staged, limited to the people and topics needed, approved by the seller, and conducted under a written confidentiality and contact protocol. Early outreach can disrupt relationships, reveal a possible sale, or expose competitively sensitive information, especially when buyer and seller compete. Later access may be appropriate after serious interest and a clearer purpose, but timing is not a substitute for consent or legal review. The seller should appoint a human owner, use an agreed script, document what was asked and learned, and stop if a participant raises a concern or the conversation moves outside scope.
Start with the diligence question, not the contact list
Direct access is not a diligence milestone by itself. Begin by writing the decision the conversation is meant to inform. A buyer may need to test whether a key relationship depends on one executive, understand how service delivery works, or confirm how a team handles a complex process. A customer conversation may be relevant when renewal risk, concentration, implementation dependency, or contract transferability cannot be assessed from agreements and operating records. An employee conversation may be relevant when role coverage, succession, or process ownership is unclear.
The question should identify the source of truth, the gap in that source, and the consequence of leaving the gap unresolved. If invoices, retention data, customer contracts, policy documents, or management interviews answer the question, direct contact may add disruption without adding reliable evidence. The FTC recommends tailoring information shared to a specific diligence or premerger integration issue and limiting the amount of information to what is needed. [1] Use that principle for conversations too.
Use a staged access plan
A sensible sequence often starts with anonymized or aggregated information, then moves to controlled management discussions, and only later considers named employee or customer calls. The exact sequence depends on the business, transaction structure, relationship sensitivity, and applicable law. A seller should not promise that every buyer will receive the same access. It can set objective gates tied to seriousness of interest, a signed confidentiality agreement, a defined diligence request, and a plan for protecting the relationship if the transaction ends.
Early-stage bidders generally need less detail than a party conducting confirmatory diligence. The FTC recommends stronger safeguards as diligence becomes more detailed, including clean teams or third-party consultants where competitively sensitive information must be reviewed. [1] For a customer list, that can mean anonymized cohorts or contract attributes before names. For employees, it can mean role summaries before identifying individual contributors. Naming a person should be treated as an additional disclosure decision, not an automatic next step.
Get consent and check the legal perimeter
Consent has several layers. The seller must authorize the outreach. The person being contacted should receive an accurate explanation of who is calling, why the conversation is taking place, what participation means, and whether the person may decline or stop. The buyer and seller should also check employment agreements, customer contracts, confidentiality terms, privacy duties, sector rules, labor requirements, and restrictions on personal or commercially sensitive information. Governing law may vary by jurisdiction and by the person or customer involved, so qualified counsel should review the proposed protocol when the facts warrant it.
Do not describe a call as confidential in an absolute sense unless counsel has confirmed what that promise means. Do not ask an employee to disclose another person's pay, medical information, protected complaint, trade secret, or other restricted information. Do not ask a customer for information outside the agreed business purpose. The ABA notes that diligence should account for relevant jurisdiction, confidentiality obligations, use restrictions, privacy and data security practices, and the limits of seller-provided disclosures. [2]
Set a written contact protocol
Before a call is scheduled, record the purpose, approved participants, topics, prohibited topics, timing, channel, note-taking method, and escalation path. Identify one accountable human owner on the seller side and one on the buyer side. Neither side should allow software or a workflow to send outreach, alter the script, approve a disclosure, or expand the contact list without human authorization.
The protocol should define stopping conditions. Stop if the participant asks not to continue, if the discussion reaches competitively sensitive pricing or strategy, if personal or privileged information appears, if the buyer asks for an unapproved person, or if the conversation starts to sound like an employment promise or customer commitment. The FTC recommends monitoring established protocols and stopping problematic exchange or coordination when discovered. [1] The same discipline is useful for live conversations.
Make the script narrow and neutral
A useful opening identifies the buyer, the seller's authorization, the limited purpose, the expected duration, and the participant's ability to decline. Questions should be open enough to surface facts but narrow enough to avoid fishing. For an employee, ask which responsibilities are documented elsewhere, which processes depend on one person, and what training or handoffs a new owner would need. For a customer, ask which services are covered by the current agreement, what operational outcomes the relationship depends on, and whether renewal, transfer, or service-continuity conditions exist.
The interviewer should not request a promise to renew, solicit an employee to leave, negotiate price, discuss post-closing authority, or criticize the seller. The script is a control, not a substitute for judgment. A human interviewer should distinguish firsthand observations from speculation, record material uncertainty, and route legal or contractual questions to counsel rather than answering from memory.
Protect competitive and relationship-sensitive information
A buyer that competes with the seller needs special care. Current or future prices, costs, strategic plans, customer-specific terms, and other competitively sensitive information can create risk if shared too broadly before closing. The FTC advises using clean teams, independent agents, aggregation, redaction, access restrictions, and clear destruction instructions where appropriate. [1] A customer call should not become a route around those safeguards.
The NDA should define the permitted purpose and the people who may receive information. A filed SEC transaction agreement illustrates controls commonly used in practice: need-to-know representatives, notice of confidential status, reasonable precautions, use limited to the permitted purpose, and responsibility for representatives. [3] That agreement is an example, not a universal template. Counsel should tailor terms to the transaction, information, and jurisdictions involved.
Supervise, document, and reconcile what was learned
Notes should identify the date, participants, approved purpose, questions asked, answers received, unresolved points, and any consent or concern expressed. Keep observations separate from conclusions. If a customer says a relationship is important, that is not the same as a binding renewal commitment. If an employee describes an undocumented process, verify it against records and an appropriate second source before treating it as a diligence fact.
Compare call notes with contracts, customer records, operating procedures, and management representations. Material discrepancies should be escalated to the accountable human owner and, where appropriate, counsel. Access to notes should follow the same confidentiality rules as the underlying conversation. At the end of the process, follow the NDA's return or destruction instructions and record unresolved issues for the next diligence gate.
A practical approval test for owners
Before approving a contact, ask six questions: What precise decision will this conversation inform? Why cannot existing records answer it? Why is this person the right source? What information will be withheld? What happens if the person declines or the deal stops? Who will review the notes and verify the answer? If the team cannot answer these questions, defer the call and close the information gap another way.
The test should be stricter for key employees, vulnerable relationships, regulated customers, direct competitors, and contacts whose identity would itself reveal the sale. A relationship-dependent business may need fewer conversations, not more. The goal is dependable evidence with minimal disruption. If a buyer insists on broad or unsupervised access, the seller can make access conditional, provide an alternative evidence package, or decline the request after considering qualified counsel's advice.
Put the workflow under owner control
Maintain a contact register with the approved purpose, status, consent or authorization record, script version, assigned interviewer, notes location, escalation status, and stop reason. Require a human reviewer to approve each contact and reconcile its output to source records. If software or AI helps organize questions or summarize notes, use only approved information, verify every material statement against the source, and run a small trial first. Stop the trial if it invents facts, merges participants, loses a qualification, exposes restricted content, or makes an unapproved recommendation. The tool should not contact anyone, negotiate, approve access, or disclose information on its own.
Acquivo is a software platform that delivers the entire sell-side M&A process, valuation, marketing materials, buyer matching, and deal management, on one platform for business owners, M&A attorneys, and boutique investment banks. Acquivo gives business owners the entire sell-side process an investment bank would run, as software, with no success fee. It is user-operated software, so the owner and advisers remain responsible for permissions, review, and transaction decisions.
Key Points
- Approve contact only for a defined diligence question that records and management cannot answer reliably.
- Stage access, starting with anonymized or aggregated evidence and adding named contacts only when justified.
- Use written consent, a narrow script, a named human owner, and explicit prohibited topics and stop conditions.
- Protect customer identities and competitively sensitive information with counsel-reviewed controls, clean teams, or third-party review where appropriate.
- Reconcile every material statement to source records and never allow software or AI to conduct outreach, negotiate, approve, or disclose autonomously.
Sources and references
Source retrieval dates record research access, not article publication. Read our editorial and date policy.
Choose your next step
Acquivo is user-operated software. Owners and their professionals remain responsible for decisions, communications, and professional review.
Educational information, not individual legal, tax, or investment advice. Consult qualified professionals for your circumstances. Acquivo provides software, not representation or negotiation on your behalf.