Day 6: Prepare for Discovery Calls Like a Consultant
The Concept
Most freelancers walk into discovery calls underprepared and leave having talked too much. The typical pattern is familiar: a few minutes of small talk, a question about what the client is looking for, a long answer from the client, and then a pivot to explaining your services and your process. The client gets a presentation. You get a vague sense of their situation. At the end, someone says they will follow up, and the momentum dissipates.
The problem is not effort — it is preparation. A discovery call is not a conversation that happens before the real work starts. It is itself a piece of work that requires research, a prepared set of questions, and a framework for evaluating what you hear. Consultants who charge premium fees do not turn up to discovery calls and ask clients to explain their business from scratch. They arrive already knowing the industry context, the pressures this type of company faces, and the kinds of problems that typically drive this kind of hire. Their questions are specific and sharp because their preparation was specific and sharp. That preparation is what creates the impression of expertise before a single piece of work is delivered.
The asymmetry of a well-prepared discovery call
When you arrive at a discovery call already understanding the prospect's market, the questions you ask change entirely. Instead of "tell me about your business," you can ask "I noticed you recently moved upmarket with your new enterprise tier — how has that affected the kind of content you need to produce?" That question does several things simultaneously. It demonstrates that you did your homework. It signals that you understand the commercial logic behind their content decision. And it gives the client something specific to respond to, which tends to surface far more useful information than open-ended questions do.
The asymmetry is this: a well-prepared freelancer sounds like a peer who understands the client's world. An unprepared one sounds like a vendor who needs to be briefed. The client treats these two people differently — in the call, in the proposal review, and in the negotiation.
What AI can do in 10 minutes that would take you an hour
Preparing properly for a discovery call used to mean forty-five minutes of research: reading the company website, scanning their LinkedIn, checking recent news, thinking through the industry context, drafting questions. Most freelancers skip this because they do not have forty-five minutes spare before every call, especially when several are in the diary in a given week.
AI compresses that process dramatically. With a few specific inputs — the company name, industry, size, and what they reached out about — a language model can generate a business context briefing, a set of intelligent questions, and a set of hypotheses about what the real problem might be in under two minutes. The output is not a replacement for genuine industry knowledge, but it is an excellent first briefing layer that raises the floor of your preparation significantly. You spend your remaining time refining the questions for this specific prospect rather than starting from nothing.
The three hypotheses technique
One of the most valuable elements in today's prompt is the three hypotheses about what the client's real problem might be. This matters because clients rarely articulate their core problem clearly in an initial enquiry. What they say they want — a content strategy, a new website, a brand refresh — is usually the solution they have already decided on, not the problem underneath it. Your job in a discovery call is to test whether their proposed solution is actually the right one, and whether you are the right person to deliver it.
Having three hypotheses before the call keeps you listening actively rather than passively. You are not just absorbing information — you are evaluating it against your working assumptions, updating them as the client speaks, and refining your understanding of what the project actually is. That kind of active listening is what allows you to say, at the end of a call: "Based on what you have described, I think the real challenge is X — and that is slightly different from what you came in asking for. Here is why that matters." That sentence alone positions you as someone worth hiring.
What to listen for — and what to listen out for
Knowing what to listen for is as important as knowing what to ask. In any discovery call there are signals that point towards a good project — a clear decision-maker in the room, a specific outcome they are trying to achieve, a timeline with real commercial stakes attached, openness to professional guidance. And there are signals that point away from one: multiple stakeholders with conflicting views, budget conversations that come up in the first five minutes, or an expectation that you will replicate exactly what the previous person did, just cheaper.
Preparing these criteria before the call, rather than trying to evaluate them from memory afterwards, makes the assessment more reliable and the decision easier. By the time the call ends, you should know whether you want this project — not just whether the client wants you.
Prompt of the day
Copy this into your AI tool and replace any bracketed placeholders.
Prompt
You are a business research analyst preparing a freelance consultant for a discovery call with a prospective client. Here is what I know about the prospect: - Company name: [e.g. Thornfield Digital] - Industry: [e.g. B2B SaaS, project management software] - Company size: [e.g. 40 employees, Series A funded] - What they reached out about: [e.g. they want help with their content marketing strategy] - Anything else I know: [e.g. they recently launched a new product tier and are trying to move upmarket] My freelance specialism: [e.g. content strategy for B2B SaaS companies] Prepare me for this discovery call by producing: 1. Business context summary — a one-paragraph briefing on this type of company at this stage, the pressures they typically face, and the commercial goals that usually drive decisions like hiring someone like me 2. Five intelligent questions I should ask in the call that go beyond surface-level and show I understand their market — questions that would surprise a prospect who expected generic discovery questions 3. Three hypotheses about what their real problem might be, based on what they told me — including one that is more uncomfortable or nuanced than they are likely to have stated outright 4. Two things I should listen for in the call that would tell me whether this is a good fit or a project I should decline 5. One thing I should never say in this type of discovery call, and why Write as if you are briefing a senior consultant before a high-stakes meeting.
Your 15-minute task
Fill in what you know about the prospect — even if some fields are incomplete. Partial information is fine; AI will make reasonable inferences and flag where it is doing so. Run the prompt at least 30 minutes before your next discovery call or a call you want to prepare for in advance. Read the business context summary first, then the questions. Select the three questions that feel most relevant to this specific prospect. Write them on a notepad you will have in front of you during the call — not a screen you will glance at, a physical notepad. The act of writing sharpens your recall under pressure.
Expected win
A pre-call briefing document that takes under ten minutes to generate and makes you the best-prepared person in the conversation — with intelligent questions that signal expertise, hypotheses that keep you listening actively rather than passively, and a clear sense of what a good fit looks and sounds like before the call begins.
Power user tip
Immediately after the call, while it is still fresh, paste this into AI: 'I just completed a discovery call with [PROSPECT]. Here is what I learned: [PASTE YOUR NOTES]. Based on this, write me: a one-paragraph summary of their real situation as I now understand it, the strongest argument for why I should take this project, the strongest argument for why I should not, and the first paragraph of a follow-up email I can send within the hour.' The post-call debrief prompt turns scattered notes into a decision and a next step before the clarity of the conversation fades.