Purpose

Prepare for, run, and advance an enterprise discovery opportunity through a concrete Codex + ChatGPT + sales-representative operating loop. The playbook turns account research, call preparation, rehearsal, live discovery, and follow-through into five linked tasks with clear artifacts and approval gates.

When to use

Use this playbook before and immediately after an enterprise discovery call when the outcome depends on multiple stakeholders, a defined buying process, technical validation, or a cross-functional pilot.

Role design

• Codex recovers account context, converts it into a discovery plan, captures the post-call outcome, and prepares the follow-up and CRM update proposal.
• ChatGPT runs the account-specific role-play in a separate text or Voice Mode session.
• Sales representative leads the customer conversation and owns customer commitments.
• Human approval is required before any external follow-up or CRM change.

What you need

• A named account and a sales representative
• Any available CRM opportunity, account history, prior interactions, and internal notes
• An account-specific ChatGPT role-play context for Step 3
• A recording, transcript, or reliable notes after the customer meeting

When a source is missing, Codex records the gap as an open question rather than filling it with an assumption.

How to run it

Materialize the workflow as a tracked run and map human to the sales representative. The run creates a root goal and five dependent tasks. Codex and ChatGPT steps are assigned to their respective agents; use the generated task IDs for logs and status changes, rather than reusing the workflow alias as a task reference.

Guardrails

• Keep facts, assumptions, and unknowns distinct.
• Do not present ChatGPT role-play statements or unverified research as customer confirmation.
• Do not send follow-ups or modify a CRM without explicit human approval.
• Do not mark a task done merely because a draft exists; satisfy its completion condition.
• If no customer owner or date is agreed, preserve the gap as an unresolved item.

Close and improve

Close the root goal only when the call is captured, approval status is explicit, and the next step has an owner and date. After a completed run, have Codex generate an Epismo track review, send any concrete improvement as workflow feedback, and rate the workflow according to its actual outcome.