Run a Customer Engagement Cycle
Use when an FDE, consultant, or customer success owner must prepare, conduct, and complete follow-through for a substantive customer meeting, including a recurring account review. Produce a decision-ready brief and accurate follow-up, not just a transcript summary. Do not use for meeting scheduling alone, asynchronous status messages, or an active incident that needs incident command. Work from authorized sources and never send messages or change CRM records without the required permission.
Don't just read it. Run it.
Start the work here, keep the important context together, and hand it off to people or AI.
Starting inputs
- account *
Customer/account name or stable identifier; do not put confidential details here.
string
- participants
Optional participant names or roles; verify instead of assuming attendance.
array
- meetingContext
Optional links or references to previous notes, account records, documents, and agenda.
array
- meetingPurpose *
The outcome or decision needed from this meeting.
string
Steps
- 1
Reconstruct the account context and outstanding commitments
Read available account history, prior meeting notes, opportunity or implementation status, and recent relevant communications. Identify objective, customer stakes, stakeholder roles, commitments still open, conflicts between sources, and changes since the previous interaction. Cite the source/date for consequential facts; mark stale or absent signals as unknown. If an authorized CRM or workspace is unavailable, use the user's notes without inventing missing context. Summarize the three issues most likely to change the meeting outcome. Gate: the brief distinguishes confirmed facts, assumptions, and the specific decisions or clarifications needed.
kind: account-briefdescription: One-page context with source-linked facts, stakeholders, prior commitments, and unresolved questions. - 2
Design a meeting that can reach a decision
Turn the meeting purpose into no more than three prioritized outcomes. Propose a timed agenda, evidence needed for each decision, pointed questions, likely objections, and an explicit ask to the relevant decision maker. Include alternate questions for discovery versus review meetings. Do not imply that a draft agenda is customer-approved. If a key stakeholder or document is missing, state how the meeting can still productively proceed. Gate: each agenda item has a purpose and produces a decision, confirmed fact, or named follow-up.
kind: meeting-plandescription: Agenda, decision questions, evidence checklist, and proposed meeting asks. - 3
Process the actual meeting evidence
After the meeting, use a transcript or contemporaneous notes to identify what was said, not what was expected. Separate confirmed decisions, proposed options, commitments, action owners, dates, customer concerns, and unresolved questions. Attribute consequential statements where the notes support it; never infer an owner or deadline from silence. Reconcile contradictions against the preparation brief and flag ambiguous promises for confirmation. If no meeting notes are available, stop at a clearly labeled preparation result, not a fabricated debrief. Gate: every decision and action is supported by a meeting source or marked unconfirmed.
kind: meeting-debriefdescription: Decision log, action list with owner and date status, issues and open questions. - 4
Prepare and verify follow-through
Draft a short customer follow-up using the customer's terminology, listing agreed decisions, reciprocal actions, dates only when confirmed, and questions requiring clarification. Prepare internal-facing updates separately; map proposed CRM/activity fields to the live schema rather than guessing field names. Compare the draft against notes for accidental promises, invented dates, confidentiality, and attribution. Send, publish, create tasks, or edit CRM only when authorized, then verify success through the relevant system. Gate: the follow-up is source-accurate, actionable, and leaves no material ambiguity hidden.
kind: follow-up-packagedescription: Customer-ready message draft, internal update proposals, and verified execution status where authorized.