A Trusted Business Partner Takes You to Lunch and Starts Asking Specific Questions About Financial Performance, Product Timelines, and Strategic Plans. The Questions Feel Like Relationship Management. The Pattern Is Information Extraction.

Quick Answer

When does discussing business with a vendor or partner cross into disclosing material nonpublic information?

The line is specific. General discussion about market conditions, industry trends, and publicly available information is a legitimate business conversation. The moment a conversation moves to specific undisclosed financial results, unannounced product timelines, or strategic decisions that have not been made public — and particularly when the other party is in a position to trade on that information — the conversation has crossed into MNPI territory.

The recognition signal is the shift in questioning pattern: from general to specific, from public to internal, from relationship to extraction. When that shift occurs, the right call is to redirect — not to decline the relationship, but to decline to answer questions about information that hasn’t been publicly disclosed.

Pressure Type: Relationship · Normalization · Ambiguity

Three years of a relationship makes the conversation feel like a routine check-in. Every business partnership involves sharing plans, discussing pipelines, and aligning expectations. The questions feel like due diligence, not intelligence gathering. The ambiguity is real — and it is exactly what makes this scenario difficult to recognize in the moment rather than in the debrief afterward.

Choice AAnswer the questions as helpfully as he can within reason. Marcus is a trusted partner and deserves honest engagement. If the company isn’t comfortable sharing this information, they should have a formal policy about it rather than leaving him to guess.

Choice BRedirect all specific questions to public information. “I can share what’s on our website and in our public announcements — I can’t go beyond that on anything that hasn’t been disclosed.” Report the pattern of questions to compliance after lunch.

Choice CAnswer the broad questions (“Q3 is tracking well”) but draw a clear line at anything more specific, explain to Marcus that he has compliance obligations that prevent him from discussing undisclosed plans, and log the specific questions asked when he returns to the office.

The Right Call

Choice B — redirect and report. Choice C is acceptable if the logging is formal.

Choice A creates exposure proportional to how specifically David answered — and the ambiguity about Marcus’s intentions makes that exposure entirely uncontrollable. Choice B is the right call because it preserves the business relationship (deflection is not hostility), protects the company, and routes the compliance determination to the function qualified to make it. The report to compliance is essential — not as an accusation against Marcus, but because compliance needs to know which partners are asking which questions ahead of which announcements. That pattern data is itself material. Choice C achieves most of the same protection, but the logging must be formal — a written record of the specific questions asked and the responses given, filed with compliance. An informal mental note is not sufficient.

The questions arrive framed as relationship management, not intelligence gathering.

No one in a structured information extraction scenario announces their intentions. The framing is always legitimate — contract planning, partnership alignment, due diligence. The recognition signal is not the stated purpose of the question, but the specificity and timing of the question. Specific questions about undisclosed financial performance, asked close to an earnings cycle, from a party with any investment position in the company, are the pattern. Training employees to notice the pattern — rather than evaluate the stated purpose — is the difference between recognition and rationalization.

These conversations spike dramatically during IPO roadshow periods.

When a company announces an intention to go public, every vendor, partner, competitor, and industry contact immediately begins trying to build a trading thesis from available fragments. The number of specific questions employees receive about financial performance and strategic direction increases dramatically in the weeks before and after an S-1 filing. Employees who have never thought of a routine vendor lunch as a securities compliance risk suddenly find themselves in multiple such conversations simultaneously. Pre-IPO training needs to address this shift explicitly — the relationship hasn’t changed, but the legal stakes of the conversation have.

Declining to answer feels like it damages a business relationship worth protecting.

David values his relationship with Marcus. Redirecting a question mid-lunch feels awkward, potentially insulting, and possibly relationship-damaging. The compliance reflex that should fire — “this question involves undisclosed information” — has to compete with the relationship reflex that says “I don’t want to make this lunch weird.” Practicing the redirect language before lunch — “I’m happy to share what’s publicly available, but I can’t go beyond that” — is what makes the right call executable in the moment rather than just theoretically correct afterward.

When does discussing business plans with a vendor become an insider trading risk?

The threshold is specificity and non-disclosure. General discussion about published strategy, public product roadmaps, and available financial information carries no insider trading risk. Sharing specific undisclosed financial results, unannounced product timelines, or strategic decisions not yet made public — particularly to a party who might trade on that information — crosses into MNPI territory regardless of the business context of the conversation.

Should employees report unusual questions from business partners to compliance?

Yes — particularly questions that are unusually specific about undisclosed financial performance, timing of announcements, or strategic decisions, asked close to earnings cycles or material announcements. Compliance teams track these patterns across the organization. A single report from one employee may be inconclusive. Multiple employees reporting similar questions from the same partner, in the same window, before the same announcement, is a pattern that has enforcement significance. The report costs nothing. Not reporting denies compliance information it needs.

What is the right way to redirect a question about undisclosed company information?

“I can share what’s publicly available but I can’t go beyond that on anything we haven’t announced yet.” That sentence is complete, it is not hostile, and it does not damage the relationship. It communicates that there is a compliance boundary without suggesting the question was inappropriate. Employees who have this sentence ready before a business conversation are significantly more likely to use it than employees who have to construct it under relationship pressure in the moment.

How to Use This Scenario in Training

Most effective for sales, business development, and account management teams — the employees most likely to have lunch with partners and vendors and most likely to feel that helpfulness is part of their professional identity. The dual framing (innocent due diligence vs. structured extraction) is the strongest element of the discussion—it highlights that the right response is identical regardless of the other party’s intent, which removes the cognitive load of trying to read the situation correctly.

For pre-IPO training, run this scenario as part of the roadshow preparation module, alongside training on what legally changes when the S-1 is filed. The volume of vendor and partner fishing conversations increases dramatically in the weeks leading up to an IPO announcement.

Is It Insider Trading If I Didn’t Trade? →

An engineer shares exciting news with a friend. The friend buys stock. The engineer never traded. Two perspectives on tipping liability.

Can I Tell My Spouse About Company Earnings? →

The dinner table financial planning conversation and why it cannot happen during a blackout period.