What to Reveal to the Expert, and What Story to Tell

What to Reveal to the Expert, and What Story to Tell

Many interviews are won or lost before the first substantive question is asked. The opening minute shapes the expert’s expectations about the conversation. If you are too vague, the expert may give broad, generic commentary. If you are too specific, you may bias the answer, reveal unnecessary information, or signal what you want to hear. If you sound evasive, the expert may become guarded. If you sound overly informed and hypothesis-heavy, the expert may start reacting to your frame instead of offering their own.

7.1 Why the Framing Matters

Framing matters because experts do not answer questions in a vacuum. They answer them in response to cues. The moment you describe the project, the expert begins forming views about:

  • what you care about,
  • what you probably already believe,
  • how candid it is safe to be,
  • whether this is a broad educational conversation or a pointed diligence call,
  • whether you are likely to know enough to follow them,
  • whether you are likely to challenge them,
  • whether there are topics they should avoid.

All of that affects the quality of the answer. A good opening frame does four jobs.

First: it creates trust. The expert needs to feel that you are organized, professional, and not trying to lure them into a problematic conversation. A clear, calm opening increases candor.

Second: it improves relevance. A buyer-side expert will answer very differently if they understand that you are interested in decision criteria and switching barriers rather than a generic market overview.

Third: it reduces bias. Many interviewers accidentally lead the expert before the real interview begins. Once you do that, you have already shaped the conversation.

Fourth: it protects confidentiality. A good frame gives the expert enough orientation to be useful without disclosing the client name, the target, the live deal thesis, internal concerns, or other sensitive details that the expert does not need.

A useful rule: your opening should help the expert answer well, not help them guess what answer you want.

Framing also affects efficiency. In a 45- or 60-minute call, the team cannot waste the first ten minutes with muddled positioning. If the expert is confused about the scope, they may give a broad market lecture when you really need the procurement process. If the opening was neutral and disciplined, you have earned the right to ask sharper follow-ups later.

7.2 The Goals of Your Opening Narrative

The opening narrative should be short, but it should have a purpose. In most cases, you are trying to achieve six things in under a minute.

1. Orient the expert

The expert should know the general topic of the conversation. Not every internal nuance, but enough to understand what domain of experience is relevant.

For example:
“I’m trying to understand how large healthcare systems evaluate revenue cycle vendors.”
“I’d like to focus on how mid-market distributors choose warehouse management software.”
“I’m hoping to discuss service delivery and operational bottlenecks in home-based care.”

2. Explain why you are speaking with them

Connect their background to the subject.

For example:
“Given your experience running procurement at a multi-site provider, I thought you could be helpful on how these decisions are actually made.”
“Your background implementing these systems across several clients seemed especially relevant to the adoption side.”

3. Set the scope

You want the expert to understand what kind of conversation this is. Market overview? Buying process? Implementation realities? Competitive comparison? Pricing? Operational risk?

4. Establish the boundary conditions

It is usually wise to remind the expert, lightly and professionally, that you do not need confidential information and are interested in general experience and observations.

This often sounds like:
“I’m interested in your perspective based on your experience; no need to get into anything confidential.”
“I’d like to stay at the level of your general observations and things you’re comfortable discussing.”

5. Preserve neutrality

The opening should not reveal a loaded hypothesis unless there is a good reason to do so. In most cases, you want the expert’s unprompted mental model first.

6. Move quickly into an easy first question

The opening should flow directly into the first real question. Often the best first question is broad, factual, and easy to answer:

“Could you start by walking me through how a typical evaluation process works?”
“Could you describe how this market is segmented today?”
“What tends to matter most when buyers in your segment choose among vendors?”

A practical standard: an opening narrative is usually 20 to 45 seconds. The right tone is professional, calm, and matter-of-fact.

7.3 How Much to Reveal About the Client

In most expert-network interviews, the default should be: do not name the client unless there is a clear reason and permission to do so. That does not mean being evasive. It means separating what the expert needs to know from what they do not need to know.

Usually the expert does not need:

  • the exact client name,
  • the exact target name,
  • the name of the fund,
  • the company under review,
  • the deal status,
  • the internal sponsor,
  • the names of other parties involved.

Usually the expert does benefit from knowing the general sponsor type:

  • private equity investor,
  • corporate strategy team,
  • operating company,
  • management team,
  • board-level initiative,
  • market-assessment effort.

That is often enough context.

For example, these are usually appropriate:
“I’m working with an investor looking at the sector.”
“I’m supporting a corporate team trying to understand the market.”
“I’m helping a company think through how this function is evolving.”

When naming the client may make sense

There are cases where you may disclose more:

  • the client has approved disclosure,
  • the relationship is not sensitive,
  • naming the client materially improves the relevance of the answer,
  • the project is an internal transformation and the expert needs to know the company context to be useful,
  • the expert is being asked about broad practice rather than a live transaction,
  • the client identity is already obvious and non-sensitive.

Even then, keep the disclosure limited.

Why nondisclosure is often better

There are three recurring reasons to hold back. First, confidentiality. Second, answer quality. If the expert knows the exact client or target, they may anchor on that company rather than answer from broader experience. Third, information control. Once you disclose a name, you cannot undisclose it.

A useful disclosure ladder

It is often helpful to think in levels:

Level 1: no client disclosure
“I’m working on a project in this space.”

Level 2: sponsor-type disclosure
“I’m working with a financial sponsor evaluating the market.”

Level 3: broad company-description disclosure
“I’m supporting a large industrial company assessing expansion opportunities.”

Level 4: named-client disclosure
Only when approved and useful.

Most expert-network calls can be handled well at Level 2 or Level 3.

7.4 How Much to Reveal About the Project Objective

The expert usually needs to know the topic of the project and the lens of the discussion. They rarely need to know the full internal decision being made.

For example, the expert may need to know:

  • you are focused on buyer decision criteria,
  • you are trying to understand competitive differentiation,
  • you want to discuss implementation realities,
  • you are looking at operational bottlenecks,
  • you are interested in pricing and packaging.

The expert usually does not need to know:

  • whether the investment committee meets next Tuesday,
  • whether the client is bullish or nervous,
  • whether management’s forecast is under attack,
  • what multiple is being contemplated,
  • what recommendation the case team is leaning toward.

A good rule: reveal the objective at the level needed for a good answer, not at the level of the client’s internal decision process.

That often means describing the conversation in functional terms:
“I’d like to understand how buyers compare vendors in this category.”
“I’m trying to get a better sense of what makes implementations succeed or fail.”
“I want to understand how procurement and end-user preferences interact.”
“I’m hoping to understand how pricing is typically structured and where discounting shows up.”

These statements are more useful than either extreme:
too vague: “We’re trying to learn about the market.”
too specific: “We’re trying to determine whether management’s claim of 95 percent logo retention is credible.”

When more specificity helps

There are cases where more detail improves the interview:

  • when the expert’s relevance depends on a very specific workflow,
  • when the market is so broad that a vague objective will produce generic commentary,
  • when the operational context matters materially,
  • when you are speaking with a transformation expert and need them to understand the process area under review.

In those cases, specificity about the topic is good. Specificity about internal stakes is usually still unnecessary.

A useful discipline

Before the call, write two versions of the project objective:
Internal version: the full case objective, exactly as the team sees it.
External version: the version the expert needs to hear.

The external version should be shorter, cleaner, and less revealing, while still being accurate.

7.5 How Much to Reveal About the Hypotheses You Are Testing

This is where many interviews get biased early.

Most projects have hypotheses. The team may suspect:

  • the market is fragmenting,
  • the product is differentiated,
  • buyers care more about service than features,
  • switching costs are overstated,
  • implementation burden is underappreciated,
  • the upmarket move will be difficult,
  • pricing power is weaker than management suggests.

The mistake is to lead with those hypotheses too early.

In most interviews, especially early ones, it is better to first get the expert’s unprompted view. Let them describe the market, the decision process, the product differences, or the operational realities in their own words. Only after that should you test specific hypotheses.

Why this sequence matters

If you reveal your main hypothesis up front, three things can go wrong. First, the expert may anchor on it and unknowingly shape their answer around your frame. Second, the expert may start performing for you. Third, you may miss what they would have raised spontaneously.

A better sequencing pattern

A strong interview often follows this sequence:

  • Open neutrally
  • Get the expert’s broad mental model
  • Clarify process, facts, and segmentation
  • Surface surprises or tensions
  • Then test selected hypotheses explicitly

For example, instead of opening with:
“We’ve heard that switching costs are actually pretty low. Does that sound right?”
start with:
“Could you walk me through what typically makes customers stay with an incumbent versus seriously evaluate a switch?”

Only later, after the expert has answered, you can test the sharper version:
“Some people argue that switching costs in this category are lower than they look on the surface because buyers can use the threat of switching without actually moving. How does that square with your experience?”

When it is appropriate to reveal a hypothesis

There are times when a hypothesis should be revealed:

  • late in the call, to test a view already emerging from the discussion,
  • when the expert has already offered a broad answer and you want to pressure-test it,
  • when the hypothesis is one of several balanced possibilities,
  • when you need a reaction to a very specific claim.

When you do reveal a hypothesis, present it as a test, not a conclusion:
“One question we are exploring is whether…”
“We’ve heard competing views on whether…”
“Some people describe the market this way, others quite differently…”

Protect the most sensitive hypothesis

If one hypothesis is especially important and the expert may be reluctant to discuss it, do not lead with it. Earn your way there.

7.6 Neutral Framing vs. Over-Priming the Expert

Neutral framing does not mean being vague. It means describing the topic in a way that does not preload the expert’s answer.

What over-priming looks like

You are over-priming the expert when you:

  • use loaded adjectives too early,
  • reveal your directional thesis,
  • imply that one answer is more sophisticated than another,
  • repeat management claims before hearing the expert’s own view,
  • disclose concerns that should be tested, not advertised,
  • ask broad questions in a way that already contains the answer.

Examples of over-primed openings:
“We’re looking at a highly differentiated software provider and trying to understand why customers love it.”
“We’re hearing that the market is commoditizing quickly and pricing is collapsing.”
“We’re trying to understand why implementations fail so often.”
“We think the real issue is churn in the mid-market.”

What neutral framing looks like

Neutral framing keeps the topic clear but the direction open.

Examples:
“I’d like to understand how customers choose among vendors in this category.”
“I’m hoping to get your perspective on how this market is evolving and where the main points of differentiation sit.”
“I’d like to focus on implementation realities, including what tends to go well and what tends to go wrong.”
“I’m interested in renewal behavior and what drives customers to stay, expand, or consider switching.”

Neutral does not mean naive

You can ask informed, specific, well-structured questions while remaining neutral. For example:
“How do decision criteria differ between enterprise and mid-market buyers?”
“At what point in the process does the security review become decisive?”
“Where do implementations tend to get delayed: data work, workflow design, training, or something else?”

A practical test

Before the call, review your opening statements and first five questions. Ask:
If I heard this from the other side, would I be able to infer the answer they want?

Another useful test:
Would this wording still make sense if the opposite conclusion turned out to be true?

Strong framing is disciplined enough that the expert can disagree with your emerging view without first having to fight your wording.

7.7 Managing Confidentiality and Avoiding Unnecessary Disclosures

There are two confidentiality obligations in expert interviews. The first is obvious: do not solicit confidential or restricted information from the expert. The second is less discussed but equally real: do not disclose unnecessary confidential information to the expert.

Use the need-to-know standard

A simple rule works well: only disclose information that the expert needs in order to answer well.

That usually means the expert does not need:

  • the name of the client,
  • the name of the target,
  • the names of other experts,
  • internal client hypotheses,
  • preliminary conclusions,
  • sensitive internal data,
  • management’s confidential claims,
  • detailed deal status,
  • the internal politics of the project.

If those details are not needed to improve the answer materially, keep them out of the conversation.

Be selective, not deceptive

You do not need to tell the expert everything. But you should not lie about who you are, invent a fake project, or make false statements to get the person talking.

The right approach is to be accurate but incomplete:
“I’m working on a project in this space.”
“I’m trying to understand how buyers evaluate the category.”
“I can’t share the client name, but I can tell you the conversation is focused on procurement and implementation.”

Do not confirm guesses casually

Experts will sometimes ask, “Is this about Company X?” or “Is your client Y?” Do not confirm casually. A safe response is:
“I’m going to keep the specific parties confidential, but I can absolutely describe the topic we’re focused on.”

Avoid revealing more as rapport grows

As the conversation becomes more comfortable, interviewers sometimes loosen up and disclose more than they intended. Good rapport is helpful, but it should not change the disclosure standard.

Be careful in emails and scheduling notes

Confidentiality management starts before the call. Do not put unnecessary details into network emails, profile comments, scheduling notes, or pre-reads.

7.8 Different Scripts for Market Assessments, Diligences, and Transformations

Different project types usually call for slightly different opening narratives. The underlying principles stay the same, but the framing shifts.

Market assessment

In a market assessment, the opening can usually be a bit broader and more open-ended. The team is often trying to understand market structure, customer behavior, product differentiation, and where the sector is heading.

For example:
“I’m doing work to better understand this market, especially how buyers segment, what tends to drive vendor choice, and where the category is evolving. Given your background, I thought you could be helpful on how the market actually works in practice.”

Commercial diligence

In diligence, the opening should usually be more controlled. A useful diligence opening usually reveals the sponsor type and the topic, but not the target or the thesis.

For example:
“I’m supporting an investor looking at this part of the market. I’d like to focus on how buyers evaluate vendors, where the main differences among providers sit, and what tends to make customers stay with or move away from an incumbent. I’m interested in your general experience and observations, nothing confidential.”

In diligence, the interviewer should be especially careful not to say things like:
“We’re looking at a company that claims…”
“Management told us…”
“We’re trying to decide whether this is real or not.”

Transformation or performance improvement

In transformation work, the sponsor is often an operating company rather than an investor. In some cases, the company can be named. In many cases, even if it can be named, the internal agenda should still be framed carefully.

A useful transformation opening might be:
“I’m supporting a company that is trying to improve how it handles this process. I’d like to understand what good looks like, where companies usually run into friction, and what changes tend to create real improvement versus just more activity.”

If the client name is disclosed, keep the rest of the framing neutral. Do not say:
“The leadership team is worried that the COO is the problem,” or
“We think the salesforce is underperforming badly.”
That is internal politics, not useful framing.

A practical distinction

The broader the project, the more open the opening can be.
The more sensitive the project, the more selective and disciplined the opening should be.

But in every case, the formula is similar:

  • enough context to orient,
  • not enough to bias,
  • clear enough to be useful,
  • clean enough to protect confidentiality.

7.9 What to Say When the Expert Asks Who the Client Is

This happens often, and the answer should already be decided before the call starts.

A simple default response

“I’m going to keep the client name confidential, but I can absolutely describe the type of project and the topics I’d like to cover.”

That works well because it does two things:

  • it declines cleanly,
  • it redirects productively.

Sponsor-type responses

Often you can be a bit more specific without naming names:
“It’s for a financial sponsor evaluating the space.”
“It’s for a large corporate team thinking about the market.”
“It’s for an operating company working through a transformation question.”

When the expert keeps pressing

If the expert presses, do not get drawn into an awkward dance. Stay consistent:
“I understand the question. I need to keep the specific client confidential, but I can be as specific as helpful on the market questions and decision context.”

What not to do

Do not:

  • disclose because you feel socially pressured,
  • hint in a way that effectively reveals it,
  • confirm or deny company guesses casually,
  • invent a misleading answer,
  • overexplain why you cannot say.

If the client can be named

When disclosure is approved and useful, still keep it crisp:
“This work is for Company X, and the focus today is on how buyers evaluate this category and what tends to drive successful implementation.”

7.10 What to Say When the Expert Asks What You Already Believe

This question is also common, especially from experienced experts who want to calibrate the level of the conversation.

The best first move: get their unprompted view first

A strong default response is:
“We do have some preliminary views, but I’d rather hear your perspective first so I don’t put words in your mouth.”

Another good version:
“We’re still testing a few ideas, but it would be most helpful to start with your direct experience before I share any of the themes we’re hearing.”

When the expert genuinely needs calibration

Sometimes the expert just wants to know whether to start at a 30,000-foot market level or at a detailed process level.

In that case, give them scope, not conclusions:
“We’re most interested in buyer decision criteria, switching dynamics, and implementation realities.”
or
“We’re focused less on high-level market size and more on how the process works in practice.”

When you choose to share a view

Later in the conversation, it is often useful to test a view explicitly. When you do, share it as one perspective among several.

For example:
“We’ve heard some people describe this as a fairly sticky market and others say the stickiness is overstated once buyers get serious about a switch. How does that square with what you’ve seen?”
Or:
“One question we’re exploring is whether the service model matters more than feature breadth in actual vendor choice. Does that resonate, or is that overstated?”

What not to say

Avoid:

  • “We think the answer is X, do you agree?”
  • “Management told us Y, so we’re checking whether that’s true.”
  • “Everyone else is saying Z.”
  • “We are pretty convinced that…”

Do not posture: experts can usually tell.

7.11 Sample Opening Scripts

Below are sample scripts that can be adapted directly. They are intentionally short.

Script 1. General neutral opening

“Thanks for taking the time. I’m doing work in this area and wanted to get your perspective based on your experience. I’d like to focus on how this market works in practice, especially decision criteria, differences among providers, and what tends to drive outcomes. No need to get into anything confidential. To start, could you give me a quick sense of how you think about the market today?”

Script 2. Market assessment

“Thanks for joining. I’m working on a market assessment in this space and hoped to get your perspective given your background. I’m especially interested in how the market is segmented, how buyers differ across segments, and where the main sources of differentiation sit. I’m looking for your general observations and experience, not anything confidential. Maybe to begin: how would you segment the market today?”

Script 3. Commercial diligence

“Thanks for taking the time. I’m supporting an investor looking at this part of the market, and I wanted to focus today on how buyers evaluate vendors, what tends to matter most in actual selection, and how sticky incumbents really are. I’m interested in your experience and market-level observations, nothing confidential. To start, when a buyer in your segment seriously evaluates vendors, what usually triggers that process?”

Script 4. Buyer-side procurement interview

“Thanks for joining. Given your background on the buyer side, I thought you could be especially helpful on how these decisions really get made. I’d like to understand who drives the process, what criteria actually matter, and what makes an incumbent hard or easy to displace. No need for any confidential details. Could you start by walking me through the last meaningful vendor evaluation you were involved in?”

Script 5. Implementation-focused interview

“Thanks for taking the time. I’m trying to understand implementation realities in this category, especially where projects tend to go well, where they tend to get stuck, and what buyers often underestimate before go-live. I’m interested in your general experience across projects, not anything confidential. Could you walk me through a typical implementation from kickoff to stabilization?”

Script 6. Transformation / operating-model interview

“Thanks for joining. I’m supporting work on how companies improve performance in this area, and I’d like to get your perspective on what good really looks like in practice. I’m especially interested in bottlenecks, capability gaps, and which improvement levers actually move the needle. No need for any confidential specifics. To begin, where do you most often see this process break down?”

Script 7. When you need to be especially guarded

“Thanks for making the time. I’m working on a project related to this sector and wanted to get your perspective based on your background. I’d like to focus on broad market behavior, buying dynamics, and practical differences among approaches in the category. I’m not looking for anything confidential, just your general observations from experience. To start, what tends to matter most when customers choose among options here?”

Script 8. When the expert asks who the client is

“I’m going to keep the specific client confidential, but I can tell you the work is for a financial sponsor evaluating the sector, and the focus for today is on vendor selection, switching dynamics, and implementation realities.”

Script 9. When the expert asks what you already believe

“We do have some preliminary themes, but I’d rather hear your perspective first so I don’t bias the discussion. The areas we’re most focused on are decision criteria, switching barriers, and how implementation affects long-term outcomes.”

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]