What Actually Happens on a Market Intelligence Discovery Call (And How to Get the Most Out of It)

A market intelligence discovery call is where the research actually starts. The call settles four things: the decision the research has to inform, what's riding on it, what would change your mind, and when the answer is really needed. Everything after is built on those four.

You don't need to arrive with a formal brief. This post walks through what a good discovery call covers, why each question gets asked, and how knowing what to expect from a market research consultation gets you sharper, faster research from any firm.

Who this is for: Leaders and managers about to commission market intelligence or market research, and anyone preparing for a first discovery call with a research or intelligence firm.

Key Takeaways

• The research starts on the discovery call, not when the analyst starts digging. That call shapes the scope, the timeline, and whether the findings change anything.

• A strong discovery call uncovers four things: the decision the research will inform, what is at stake, what would change the client's mind, and the real timeline.

• "What is happening" is data. "What does it mean for us" is intelligence. A good discovery call reaches the second question even when a client walks in with the first.

• Broad requests, unclear decisions, and existing hunches are normal starting points, and the call is for working through them.

• If you want to prepare, spend five minutes on what decision this is for and what happens if you get it wrong.

The Market Intelligence Discovery Call Is Where The Research Actually Begins

Most people assume the real work on a market intelligence project begins once an analyst starts searching, interviewing, and building spreadsheets. The real work begins earlier, on the discovery call, because that is where the question the research will answer gets decided.

In the trades, nobody quotes a sign without seeing the wall it's going on. A discovery call is the site visit. It usually opens with a request that sounds simple, like "tell us about this market" or "find out what this competitor is doing," and my job is to find out what sits underneath it.

At CTRS, our discovery calls usually last for 30 minutes. It’s best to have the project sponsor and anyone else who will be providing us with access to internal materials or will be reviewing our work as we go. After this discovery call, we write up a proposal. Once someone says yes to a proposal, we schedule a kickoff meeting to go over everything in detail, then produce a detailed work plan for the client to sign off on before we begin.

A project scoped around the surface request answers the question as asked. A project scoped around the decision underneath answers the question the client needed answered. You don't need to prepare a document for the call. You benefit from knowing what is being asked, and why.

A Good Discovery Call Listens For The Decision Beneath The Request

When a client tells me what they want, I'm listening for three things underneath it: the decision the work will inform, who is making that decision, and what "useful" looks like to them. None of that is a form to fill out. The decision matters most, because research attached to a decision gets used and research attached to curiosity gets filed.

A client's first framing of a problem often needs gentle reshaping before research can start, because it comes from inside the organization, in its own vocabulary. The analyst's job is to check what those words mean before spending a day on them.

Skipping that check is expensive. I once asked a junior researcher to look into the "trailer" market for a client that meant mobile field housing, the small buildings used in mining camps. She spent 20 hours on recreational travel trailers, the kind people tow to campsites. The client's word was right, and the reading of it was wrong, a story I tell in How AI Is Changing Market Intelligence, and What Leaders Need to Know.

The client's job isn't to have perfect answers ready. The client's job is to be willing to think it through out loud.

"What Is Happening" Is Data, And "What Does It Mean For Us" Is Intelligence

A client who wants to know what a competitor is doing is asking for data. A client who wants to know what that move means for their own next step is asking for intelligence, and only the second changes a decision. I lay out the difference between data, information, and intelligence in Who Owns Market Intelligence In Your Organization?

Getting from the first question to the second doesn't take a better-prepared client, and it isn't me steering. It usually takes two questions: what prompted this now, and what would you do differently if you knew?

The following example is illustrative. It describes a common pattern, not a specific client engagement.

A regional services company asks for a profile of a competitor that has just opened an office in its territory. Asked what prompted the request, the owner says two long-standing clients mentioned the competitor at renewal time, and the real worry is whether to cut prices before next year's renewals. The research shifts from profiling everything the competitor does to how it prices, which clients it is winning, and what the company's own clients value besides price.

A Good Discovery Call Uncovers Four Things Before Any Research Begins

A strong discovery call brings out four things, and none of them need to arrive pre-packaged. They emerge through the conversation, which is what the call is for. The CTRS contact form already asks for two of them: what you're trying to decide and your timeline, along with what a good outcome looks like.

Every Project Needs A Decision Attached

Every market intelligence project should be attached to a decision: whether to enter a market, how to price, which segment to prioritize, whether to build or partner. The question that draws it out sounds like "What will you decide differently depending on what we find?"

The Stakes Set How Much Certainty The Research Needs

The stakes decide how much certainty the research needs and how much it is worth spending to get it. A decision that commits $50,000 needs a different standard of evidence than one that commits $5 million. The question sounds like "What does it cost if this goes wrong?"

What Would Change Your Mind Shows What To Test

Asking what evidence would change a client's mind surfaces the assumptions the decision rests on, which tells the analyst exactly what the research needs to test. The question sounds like "What would you need to see to decide against this?" I cover how to pressure-test those assumptions in Three Pre-Decision Questions That Pressure-Test Your Market Intelligence.

The Real Deadline Is The Decision Date

The deadline a client names first is often not the date that really matters. The date that matters is when the decision gets made: the board meeting, the budget approval, the lease signing. Research that arrives after that date is too late, no matter how good it is.

Scope, timeline, and the shape of the final findings all get sharper once the four things are clear. A client who knows why these questions get asked can engage with them far more productively, and that is the real value of knowing what to expect.

Broad Starting Points And Early Hunches Are Normal, And The Call Is Built For Them

Almost every project starts a little broad or a little uncertain, and that's what the call is for. The difference between a fast, sharp project and a slower one usually isn't how prepared the client was. The difference is how well you work through these starting points together early.

An Unclear Decision Gets Worked Backward

Sometimes a client knows something is wrong but not what decision it points to. A good call works backward by asking what the client would do if the answer were bad news, and what they would do if it were good news. If neither answer changes anything, the research isn't ready to scope, and a phone call is a cheaper place to learn that than a finished report.

A Broad Request Gets Narrowed To The Unknowns That Matter

A broad request such as "tell me about this market" takes longer to turn into a project than a specific concern, because it can mean a hundred questions. The call narrows it by asking which part of the market the client would act on first, and which one or two unknowns would move that action.

A Hunch Gets Tested Alongside An Alternative

A client who already suspects the answer is common, and the hunch is often partly right. A good call tests the hunch alongside exploring it, usually by adding a question the hunch doesn't expect.

CTRS ran a study for a national non-profit on entrepreneurs from an equity-seeking community who were being turned down by banks for business financing. The project brief presupposed the conclusion: discrimination. I pushed back on that framing and added a second research question: what else might be true about these businesses that would cause a lender to decline the application?

A significant share of the owners surveyed weren't incorporated, which ends the conversation for a commercial lender, and many of those unincorporated owners believed they had been declined because of who they were. The finding reframed the problem around uneven access to knowledge of how institutional lending works, and the recommendation to banks became educating the market on what qualifying requires.

Catching one of these patterns during the call is cheaper than catching it after the report lands. If you notice you're in one, say so, and work it through with the analyst.

You Don't Need A Brief Before A Discovery Call, Just A Sense Of What's At Stake

There's no homework before a market intelligence discovery call. If you want a head start, spend five minutes on two things: what decision this is really for, and what happens if you get it wrong. The call will work through everything else, and questions that sound like pushback, such as "what would change your mind?", are the analyst doing the work.

The clients who get the most out of market intelligence aren't the most prepared on paper. They're the ones willing to think it through, out loud, with someone asking the right questions.

If you have one of these calls coming up, write two sentences before it: "We are deciding ___" and "If we get it wrong, ___." Bring them to the call or put them in the contact form, and start there.

Frequently Asked Questions

What happens on a market intelligence discovery call?

A market intelligence discovery call is a first conversation in which an analyst works out the decision the research will inform, what is at stake, what would change the client's mind, and the real timeline. The answers shape the scope, method, and timing of the project.

Do I need to prepare a brief before talking to a market intelligence firm?

A formal brief isn't needed before a first call with a market intelligence firm. The most useful preparation is a rough sense of the decision the research is for and what is at stake if it goes wrong.

Why does a market intelligence firm ask what would change my mind?

Asking what would change your mind surfaces the assumptions a decision rests on, which tells the analyst what the research needs to test. It is one of the fastest ways to turn a broad request into a focused project.

Work with CTRS

CTRS Market Intelligence scopes its work around the decision behind the request, and the discovery call is where that happens. If you have a decision coming up and want to see what that call looks like in practice, book a call with CTRS.