Close More Deals with Codex Sales Followups

When sales context is spread across meeting notes, Slack signals, CRM exports, and scattered follow-up tasks, it is easy to lose track of what needs attention first. In this guide, you will use a simple Codex system to send better sales follow-ups, faster. It helps you figure out which accounts need attention, draft the next email, clean up your CRM, and build a close plan so you can save time and keep more deals moving.

The workflow stays review-first from the start. Codex reads local files, reasons across them, and creates drafts and review artifacts. It should not send customer emails, post Slack messages, or update a live CRM unless a human explicitly approves that step.

This is useful if you manage sales follow-up, account prioritization, customer notes, or CRM hygiene and feel like the useful context is always split across too many tools.

It is especially helpful for:

• reps who want a cleaner post-call follow-up process
• founders or operators managing a small pipeline
• account teams that need a weekly priority queue
• managers who want CRM updates proposed, not silently applied

You will build a local Codex workspace that acts like a sales follow-up operator. It reads account data, meeting notes, Slack-style signals, CRM field rules, and product notes, then creates the review files a rep needs before sending anything.

The finished workspace gives you a single place to inspect the priority queue, review CRM changes, check the close plan, and open a local Gmail-style draft. In the demo, all of that happens in one local review surface instead of inside live sales tools.

By the end, the workspace can produce:

• a ranked follow-up priority queue
• a follow-up packet for a specific account
• a customer email draft
• an internal Slack-style update
• proposed CRM field updates
• a seven-day close plan

• The Codex desktop app
• A paid ChatGPT plan signed into Codex
• A clean project folder
• The attached starter template files from this guide's resources, or your own exported sales context
• Account data from your CRM
• Recent meeting notes from your note-taking app
• Relevant Slack or team-channel signals
• A clear rule that all customer-facing work starts as a draft

Once the file-based workflow works, turn it into a reusable Codex skill:

Turn this sales follow-up workflow into a project skill.

The skill should:
- inspect account data, meeting notes, Slack signals, CRM field rules, product notes, and approval rules
- rank follow-up opportunities
- draft customer follow-up packets
- propose CRM updates for review
- create seven-day close plans
- never send messages or mutate live CRM data without explicit approval

Save the skill as skills/sales-followup-operator/SKILL.md.

You can also add relevant skills as references. For example, install the public outreach drafting skill:

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill draft-outreach

Then ask Codex to inspect any local prospecting, Gmail, or Slack skills for patterns. Treat those as references first. Do not give Codex live customer data until the local review workflow is working.

The recording also showed an optional dashboard prompt:

Make me a simple HTML website that visualizes this data and makes it interactive so I can check boxes and edit things.

Codex built a static index.html review surface with editable views for the priority queue, CRM review, close plan, and local Gmail-style draft. That is useful once the Markdown workflow is stable, but it is not required for the core setup.

Start with the draft files. Get the review loop right. Then connect live tools and build a nicer interface only after the workflow is reliable.