Prepare a customer meeting brief with evidence and open questions

A meeting brief should help you ask better questions, not pretend you already know the customer's intentions. Use it to gather verified context and expose what still needs discovery.

Prepare the input

Supply the meeting purpose, selected account information, prior notes, and approved product facts. Keep the customer's stated needs separate from your internal assumptions. This can be done with supplied material; a CRM connection is not required.

Run the workflow

Ask for the account context, last agreed action, open questions, and a short agenda. Each factual claim should have a source. Let the assistant suggest hypotheses only in a clearly labeled section.

Prompt to copy

Prepare a one-page meeting brief from: [material].
Meeting objective: [objective].
Include verified context, previous commitments, open questions,
and a three-part agenda. Cite the supplied source for each fact.
Label hypotheses. Do not infer budget, authority, or purchase intent.
Use only approved product capabilities: [facts].

Review a worked example

Illustrative note: “The customer wants to reduce time spent answering calls.” This supports a discovery question about call volume and missed requests. It does not prove a budget or that they have selected voice AI. Check the agenda for premature pitching and the brief for ungrounded account details.

Inspect questions for information already present in the notes. The brief should help you confirm a meaningful uncertainty, not make the customer repeat everything. Check whether an internal hypothesis has leaked into the agenda as a fact. Keep the meeting objective realistic for the stage of the relationship.

Use it again

After the meeting, update the source notes with actual agreements. Keep proposals separate from commitments. Explore Bot for personal preparation or contact Golub if you need controlled CRM access.