Cold Outreach Quality Gate Loop

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

Should this outbound message be sent, rewritten, or stopped? Use this before AI-assisted outreach goes out and damages trust with weak relevance, fake personalization, or unsupported claims. Cold Outreach Quality Gate Loop Decision to make: Should this outbound message be sent, rewritten, or stopped? Decision owner: Revenue leader with marketing operations and sales development. 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: - Target account segment - Message draft - Personalization fields - Proof points - Sending rules - Recent reply data 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 B2B outreach quality gate. Review the outbound message and target context below. Decide send, revise, or stop. Flag fake personalization, weak relevance, unsupported claims, buyer effort, privacy risk, and brand risk. Rewrite only if the message deserves to exist. 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. Define the right to speak: State why this company, person, and moment deserve outreach. 2. Audit the claim: Remove fabricated insight, inflated benchmarks, and generic AI personalization. 3. Check the reader cost: Estimate how much effort the buyer must spend to understand why this matters. 4. Inspect operational risk: Check domain reputation, suppression lists, privacy rules, and unsubscribe patterns. 5. Decide send, revise, or stop: Approve only messages that pass relevance, evidence, and respect tests. 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 send, revise, or stop decision with a cleaner message only when the message deserves to exist. 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: - Specific account reason - Valid role reason - Public or first-party evidence - No fake personalization - Clear ask - Suppression check Human operating ritual: - Read the message aloud as if the buyer forwarded it to their boss. - Keep a kill sample of messages that should never ship. - Review negative replies as evidence, not annoyance. Do not use this loop when: Do not use it to manufacture certainty when the team has no first-party customer or CRM evidence. A human authority must approve the final decision and the operating environment. Stopping condition: Stop when the sequence has a documented quality gate and any message failing it is blocked from sending.

Canonical URL: https://juanbeltran.ch/operating-loops/cold-outreach-quality-gate-loop