Account Intelligence Briefing Loop

By Juan Beltrán, Industrial B2B AI Transformation Executive.

What should we know before a strategic customer conversation? Use this before an executive meeting so the team enters with relevant facts, hypotheses, questions, and a clear next move. Account Intelligence Briefing Loop Decision to make: What should we know before a strategic customer conversation? Decision owner: Account owner with sales operations or marketing intelligence support. Working-session setup: - Timebox: 45 min working session - People in the room: Revenue owner, account or CRM owner, and the person closest to the customer evidence. - Preparation: Working prep: bring representative evidence, constraints, and a named owner. Context: [Paste your notes, excerpts, draft, meeting transcript, CRM fields, proposal text, public research, or examples here.] Context I should provide: - Account plan - Recent public news - Known initiatives - CRM notes - Stakeholder map - Current opportunity context Safety boundary: - Use only information I provide in this conversation. - Do not infer personal, confidential, regulated, pricing, customer, employee, or supplier facts. - If the material belongs in an approved enterprise environment, tell me before analyzing it. Instructions: Act as a strategic account briefing partner. Using the account context below, separate facts from hypotheses, identify the strongest business signals, and create a one-page briefing with likely priorities, executive questions, risks, and the recommended next move. Run the session in this order: 0. Inspect the context. If a missing fact could materially change the recommendation, ask no more than five focused questions and wait. If I ask you to continue, mark each missing fact as unknown. 1. Anchor the meeting objective: State the commercial decision or relationship move the meeting should influence. 2. Collect account signals: Summarize public news, leadership moves, strategy updates, projects, and CRM history. 3. Form hypotheses: Translate signals into likely priorities, constraints, and buying triggers. 4. Write executive questions: Create questions that test hypotheses without sounding scripted. 5. Define the next move: Recommend what the team should ask for, offer, or validate. Evidence rules: - Separate supplied facts, interpretations, assumptions, and unknowns. - Reference the exact note, excerpt, metric, or example supporting every material claim. - Show the strongest credible counterargument to the recommendation. - Do not invent customer facts, benchmarks, financial numbers, policy approvals, or system access. - Do not turn missing evidence into a confident recommendation. - Keep the answer useful for Revenue Leader. Output contract: A one-page account briefing that separates facts, hypotheses, risks, and recommended actions. Return: 1. BLUF: the decision, recommendation, or draft in plain language. 2. Evidence table: claim, supplied evidence, confidence, and gap. 3. Assumption ledger: what is assumed and how to verify it. 4. Counterargument: the strongest reason the recommendation may be wrong. 5. Decision record: decision status, accountable owner, next action, and due date or trigger. 6. Evidence still needed: only the gaps that could change the decision. 7. Stop condition: state when the work is complete and when it must pause. Evidence checklist: - Meeting objective - Three factual signals - Stakeholder context - Commercial hypothesis - Questions - Next ask Human operating ritual: - Separate facts from hypotheses. - Do not use research that the seller cannot explain. - Put the customer objective before the pitch. Do not use this loop when: Do not use it to manufacture certainty when the team has no first-party customer or CRM evidence. Stopping condition: Stop when the briefing can be read in five minutes and contains fewer than five questions.

Canonical URL: https://juanbeltran.ch/operating-loops/account-intelligence-briefing-loop