For an independent consultant or advisor preparing for a prospective-client meeting, I recommend a short research plan. Its output is specific: the question to prepare for, useful sources, what those sources establish and what still needs asking.
I would start with the purpose of the conversation, then research information that could change how I prepare. A complete business profile is unnecessary if the useful next step is a question for the contact.
Start with the meeting question
Before collecting background, I would write the discussion or decision the meeting should support. If its purpose is unclear, clarifying that purpose comes first. I would not assume a client problem simply to give the research a direction.
For each proposed check, my question is: Which part of the conversation could this inform? If I cannot name one, I would leave the check outside this preparation round.
My source choices would be public primary material or specifically authorized inputs, with each reference kept beside the observation it supports. Background information does not necessarily establish the client’s current internal process.
Use six fields to bound the research
| Field | What I would record |
|---|---|
| Meeting question | The discussion or decision the preparation supports |
| Research check | One fact or uncertainty that could change the conversation |
| Suitable source | The relevant primary page or authorized record, with its reference |
| Adequate evidence | What the source establishes, including its date and scope limits |
| Stop rule | When I will use the evidence, leave the gap open or ask in the meeting |
| Further verification needed | A consequential conflict or uncertainty that still needs attention |
I can open the copyable research-plan worksheet to record those fields. The page requires no signup or download.
A fictional example: preparing a question about report review
In this illustration, I am the imaginary consultant preparing for a first meeting. The prospective client’s public services page is the source, not a reply from a client conversation. Its complete mock text is:
Reporting services are offered.
The type of report is unspecified. No real company, client, source page, date or result is represented.
For this example, the imaginary consultant has chosen report review as a possible discussion topic. It is not an established client request; I would first confirm whether that topic is useful to the contact.
The page supports one narrow observation: it describes a reporting service. It identifies no reviewer, review steps, delay or problem. My preparation would retain those limits:
| Field | Completed fictional entry |
|---|---|
| Meeting question | What would be useful to understand about report review? |
| Research check | Does the supplied page identify a reviewer or review steps? |
| Suitable source | Fictional page A, the complete mock text above; no real URL or date is supplied |
| Adequate evidence | The mock page describes a reporting service. The internal process remains unknown. |
| Stop rule | With only this mock page available, record the gap and prepare a neutral question rather than invent process details |
| Further verification needed | Confirm the topic’s relevance, then seek an attributable account or suitable process evidence before advice depending on review steps |
If the topic is relevant, my prepared question would be: Who reviews the report, and what happens between preparation and release? No message or answer is supplied in this example. Missing public detail establishes neither a failure nor a reason to automate.
Use AI for a bounded check, if useful
With material suitable for the chosen tool, I could ask:
Using only the material I supply, list which of my meeting questions it addresses. Identify the supporting passage and separate unanswered questions. Suggest no client facts beyond that material.
I would compare the response with the original passages. Unsupported goals or problems would come out, and unanswered questions would stay visible. The same check can be done manually by matching each question to its supporting passage.
Before uploading private client material, I would confirm authorization for the particular tool and use. A reusable checklist can retain the method without carrying another client’s records into it.
Stop with a usable handoff
My handoff would contain the relevant sources, their limits and the questions still worth asking. Adequate support for the immediate question can be a reason to stop. So can recognizing that a conversation is needed. A consequential conflict needs more attention before I rely on it for advice.
The plan can then supply a short client brief, with source-supported context, interpretation and open questions kept separate. After the meeting, I would note which checks helped and improve the reusable method without copying client-specific facts into it.