How To · 7 min read · Oct 24, 2026

How to Run a Content Discovery Call That Surfaces the Right Context

A practical guide to running discovery calls that uncover business context, audience detail and approval realities, so writers can produce stronger first drafts.

A useful discovery call does not start with a brief. It starts with the gaps in the brief: what the business is trying to achieve, who the content is really for, what the team already knows, and where the writing needs to be careful. If those details stay vague, the first draft usually carries the cost later, in rewrites, approvals and tone corrections.

For Hally Writer, the point of the call is not to interrogate the client. It is to gather the context a writer needs to make sound editorial decisions. That means asking questions that reveal business reality, listening for what is left unsaid, and turning the conversation into structure, tone and priority. The call should feel collaborative, but it should not be loose. Writers still need enough shape to produce useful, on-brand content.

Why the discovery call matters before the brief exists

A brief often arrives after a lot of assumptions have already been made. The discovery call is where those assumptions surface early enough to be useful. Without it, the writer may have topic direction but still miss the business context that changes how the piece should be framed.

That context usually sits in three places: the organisation’s commercial goal, the audience’s level of knowledge, and the practical constraints around approval, compliance or internal preference. A writer who understands those factors can make better choices about angle, depth and tone. A writer who does not will often produce content that is technically fine but strategically off.

The main mistake is treating the call like a form to be completed in conversation. The better approach is to use the call to understand how the business thinks, not just what it wants written. That often reveals why a topic matters now, what the piece needs to support, and where the team is likely to disagree later.

Which questions reveal useful business context?

The best questions do not ask for more words. They ask for better decisions. A useful discovery call usually covers the purpose of the content, the audience, the offer or service it supports, and the brand nuances that should carry through the writing.

A simple way to think about the questions is to separate them by job:

Good questions are usually concrete. Instead of asking, “What do you want this piece to say?”, ask, “What should a reader understand after finishing it that they may not understand now?” Instead of, “Who is the audience?”, ask, “Is this aimed at someone researching, comparing, or ready to buy?” Those answers create better structure than a generic audience label ever will.

It also helps to ask what the client does not want. That can expose old positioning, overused claims or phrases the team is trying to move away from. Those boundaries are often more useful than a long list of preferred words.

What should you listen for when answers are vague?

Vague answers are not a dead end. They are a signal that the client has not yet pinned down the decision the content needs to support. When someone says, “We just need something informative”, the real job is to find out what useful means in that context.

Listen for inconsistency between what is said and what is implied. A prospect may describe the audience as “senior decision-makers” and then keep talking about beginner-level objections. That usually means the actual reader is wider than the title suggests, or the piece needs to work harder on framing before it can get into detail.

There are a few phrases that often need follow-up:

• “We want to educate the audience.” Ask what they need to know before they can act.
• “It should be thought leadership.” Ask what opinion, decision or point of view makes it worth reading.
• “We just need it to sound polished.” Ask what parts of the voice matter most. Formality, clarity, authority or warmth?
• “Everyone on the team needs to agree.” Ask which disagreements are likely to come up in review.

When answers stay broad, keep narrowing with examples. “Can you show me an existing piece that feels close to what you want?” often reveals more than abstract discussion. So does asking what the team has already tried, what has been rejected, or where previous content failed. Those answers point to the real friction behind the request.

How do you turn call notes into writing direction?

Call notes only help if they become editorial choices. The goal is not to store information. The goal is to translate it into a usable direction for the draft.

A practical handover usually covers four things:

1. The content goal.
2. The reader and their likely level of knowledge.
3. The angle or main argument.
4. The constraints that affect structure, tone or approval.

That can be enough to write well if it is clear. For example, a note such as “Audience is aware of the service category but sceptical about implementation, so lead with practical trade-offs rather than overview” is far more useful than pages of transcript. It tells the writer what to prioritise and what to leave out.

The same applies to tone. “Professional but not stiff” is too vague on its own. “Clear, calm and commercially confident, with no sales-heavy language” gives the writer something they can use while drafting and editing.

Good notes also separate facts from interpretation. If the client says the audience is time-poor, note whether that is a confirmed operational reality or a hunch from the team. That distinction matters because it changes how strongly you frame the content. Editorial judgement improves when the writer knows which points are certain and which are inferred.

How do you keep the call collaborative without making it feel formal?

The best discovery calls feel structured, not bureaucratic. They work when the client can talk freely, but the writer still steers the conversation towards the information that affects the draft.

That starts with framing. If the call is introduced as a way to make the content more useful, most teams will understand the purpose quickly. You do not need to sound process-heavy to be disciplined. A short explanation of what you are trying to learn is often enough: business context, audience detail, tone and anything that could affect approval.

It also helps to avoid turning every question into a checklist item. Let the conversation move when the client gives a useful example or a specific concern. If they mention a product limitation, internal tension or an upcoming launch, that is often more valuable than forcing the next question in sequence. Good discovery is responsive.

The tone matters because it affects the quality of the answers. If the call feels like an audit, people tend to give safe answers. If it feels like a working session, they are more likely to reveal the details that actually shape the draft. That is especially important for service businesses and marketing teams that need content to be accurate, on-brand and repeatable across multiple pieces.

A simple way to use the call before drafting

A discovery call works best when it leads to a clear editorial decision, not just a fuller transcript. Before the writer starts, the notes should answer four practical questions:

• What is this content trying to do?
• Who is it really for?
• What should the reader understand or do after reading?
• What would make the draft wrong, off-brand or hard to approve?

If those answers are clear, the writer can build structure with confidence. If they are not, the draft will usually drift into generalities. That is where rework starts.

For teams that need scalable content, the real value of the discovery call is consistency. The same few questions, asked well, can produce better context across topics, writers and stakeholders. That makes the writing process faster in the long run, because the team spends less time correcting the same avoidable gaps.

Better context makes the draft easier to trust

A good discovery call does not try to capture everything. It aims to capture the information that changes the writing. That includes business context, audience knowledge, brand nuance and the constraints that shape approval. When those pieces are clear, the draft is more likely to sound useful on the first pass.

For teams that want content to be both scalable and on-brand, the call is where editorial judgement begins. If you want help turning those conversations into stronger content direction, Hally Writer can support the process without turning it into a formal or heavy-handed exercise.