Codex Prompts for SDRs: 10 Templates + Best Practices [2026]
Last updated: July 2026.
Codex isn't just for developers. It's one of the most capable AI assistants for anyone willing to describe what they want in plain English — which makes it a quietly powerful tool for sales development.
This is a working library of Codex prompt templates for SDRs: copy them, swap in the bracketed placeholders, and start reclaiming hours every week. Below the templates you'll also find the anatomy of a great Codex prompt, a set of 2026 best practices, and a short FAQ — so you can go from copying prompts to writing your own. Want more depth? See our full library of the 30 best Codex prompts for sales and GTM.
Anatomy of a Great Codex Prompt
Every high-performing prompt in this library shares the same five-part structure. Learn it once and you can write your own instead of hunting for templates:
- Role and goal — Tell Codex what job it's doing and what "done" looks like ("Create a sales briefing," not "tell me about this company").
- Structured output — Ask for numbered sections, bullets, or a table. Vague prompts get vague answers; specifying the format is the single biggest quality lever.
- Constraints — Word limits, tone, and hard rules ("under 100 words," "no corporate buzzwords") force quality more than adding requirements.
- Exclusions — Listing what you don't want ("skip anything you can't verify," "don't use 'just following up'") reliably beats listing more things you do want.
- Placeholders — Mark the variables with
[BRACKETS]so the same template works across every prospect, deal, and industry.
Keep that skeleton in mind as you read — every template below is just these five parts, filled in for a specific SDR task.
Before You Start: Quick Setup
Install the Codex CLI:
npm install -g @openai/codex
Or use Codex directly in the OpenAI dashboard at codex.openai.com.
Pro tip: Use mid-turn steering. When Codex starts going in the wrong direction, just interrupt with corrections.
Prompt 1: Instant Company Research Summary
Use case: Before reaching out, get a 60-second briefing on any company.
Research [COMPANY NAME] and create a sales briefing. Include:
1. What they do (2 sentences max)
2. Recent news (funding, acquisitions, product launches, leadership changes)
3. Their likely tech stack (based on job postings)
4. Pain points companies like them typically face
5. Potential conversation starters based on recent events
Format as bullet points. Be specific. Skip anything you can't verify.
Output example:
Acme Corp Briefing
- B2B logistics software for mid-market freight companies (Series B, 200 employees)
- Recent: Raised $45M in January, expanding to European markets
- Tech stack: Salesforce, Snowflake, AWS (based on job postings)
- Likely pains: Scaling customer support, data integration complexity, international compliance
- Conversation starter: "Congrats on the European expansion—how's the team handling GDPR compliance for your customer data?"
Time saved: ~15 minutes per prospect
Want this to run automatically instead of copy-pasting each time? See our full walkthrough on how to automate lead research with Claude Code — it turns a company name into a complete prospect brief in minutes.
Prompt 2: LinkedIn Profile Analyzer
Use case: Understand your prospect's priorities and communication style.
Analyze this LinkedIn profile and tell me:
[PASTE LINKEDIN PROFILE TEXT]
1. What they care about (based on posts, interests, experience)
2. Their communication style (formal/casual, technical/business)
3. Best topics to lead with
4. What NOT to mention (based on their apparent values)
5. Suggested subject line for a cold email
Be specific. Don't guess—only include what's supported by the profile.
Why it works: Codex picks up on subtle signals in how people present themselves. The "what NOT to mention" is often the most valuable insight.
Prospecting mostly out of LinkedIn? Pair this with our guide to automating LinkedIn Sales Navigator to build lists and research profiles at scale.
Time saved: ~10 minutes per prospect
Prompt 3: CRM Data Cleanup Script
Use case: Fix inconsistent data in your CRM without manual editing.
Write a script that:
1. Connects to HubSpot using their API (I'll provide API key later)
2. Finds all contacts where:
- Job title is blank but company is filled
- Phone number format is inconsistent
- Email domain doesn't match company domain
3. For job titles: Enriches using the company's LinkedIn page
4. For phone numbers: Standardizes to E.164 format
5. For mismatched emails: Flags for review (don't auto-change)
Output a report of what would change before actually making changes.
Use Node.js with proper error handling.
Why it works: Codex handles the tedious API work. You get a working script instead of spending hours in the HubSpot UI.
Time saved: 5+ hours of manual cleanup
Prompt 4: Meeting Prep One-Pager
Use case: Walk into every meeting prepared without the prep work.
I have a meeting with [PROSPECT NAME] at [COMPANY] about [TOPIC/PRODUCT].
Create a one-page meeting prep doc:
1. **Key Facts** — Company size, industry, recent news (3-5 bullets)
2. **Likely Objections** — What will they push back on?
3. **Discovery Questions** — 5 questions that uncover real pain
4. **Competitive Position** — Who else might they be talking to?
5. **Success Metrics** — What would make this a "win" for them?
6. **Next Step Options** — 3 logical next steps if the meeting goes well
Keep each section to 3-5 bullets. Prioritize actionable info.
Time saved: ~20 minutes per meeting
Prompt 5: Objection Response Generator
Use case: Never get caught off-guard by common objections.
Generate responses for these sales objections in [INDUSTRY].
For each objection, provide:
1. A brief acknowledgment (show you understand)
2. A reframe (shift the perspective)
3. A proof point (specific example or stat)
4. A question to continue the conversation
Objections:
- "We're already using [COMPETITOR]"
- "We don't have budget this quarter"
- "We need to talk to [OTHER STAKEHOLDERS] first"
- "Can you just send me some info?"
- "The timing isn't right"
Keep responses conversational, not scripted. SDRs need to sound human.
Why it works: You get battle-tested frameworks, not generic scripts. The "question to continue" keeps the conversation moving.
Prompt 6: Email Sequence Builder
Use case: Create a multi-touch sequence in minutes.
Build a 5-email sequence for [ICP DESCRIPTION] selling [PRODUCT/SERVICE].
Sequence structure:
- Email 1: Pattern interrupt (day 1)
- Email 2: Social proof (day 3)
- Email 3: Pain agitation (day 6)
- Email 4: Different angle/use case (day 10)
- Email 5: Breakup email (day 14)
Requirements:
- Subject lines under 40 characters
- Body under 100 words each
- One clear CTA per email
- Personalization placeholders marked with [BRACKETS]
- Tone: professional but not corporate, direct but not pushy
Don't use: "Hope this email finds you well," "Just following up," or "Checking in"
Why it works: The constraints force quality. Specifying what NOT to include prevents generic AI-speak.
For ready-to-adapt copy, grab our library of AI sales email templates built with Claude Code.
Time saved: 1-2 hours per sequence
Prompt 7: Call Script Framework
Use case: Structure your cold calls without sounding robotic.
Create a cold call framework for calling [ICP TITLE] at [COMPANY TYPE].
Structure:
1. **Opening** (5 seconds) — Pattern interrupt, state name/company
2. **Permission** (5 seconds) — Brief reason for call + ask for 30 seconds
3. **Hook** (15 seconds) — Specific pain point or insight
4. **Qualify** (30 seconds) — 2-3 questions to confirm fit
5. **Bridge to meeting** — How to transition if qualified
6. **Objection handlers** — Top 3 objections and responses
7. **Exit** — Graceful close if not interested
Include exact language options, not just concepts. Make it sound natural.
Time saved: 30+ minutes crafting talk tracks
Prompt 8: Lead Prioritization Logic
Use case: Build a scoring system for your specific pipeline.
Create a lead scoring model for my sales process.
Context:
- We sell [PRODUCT] to [ICP]
- Average deal size: [AMOUNT]
- Average sales cycle: [LENGTH]
- Our best customers tend to have: [CHARACTERISTICS]
Build a scoring system (1-100) that weighs:
- Company fit signals (industry, size, tech stack)
- Behavioral signals (website visits, content downloads, email opens)
- Timing signals (funding, hiring, tech changes)
Output as a decision matrix with specific thresholds:
- 80+ → Hot lead, prioritize
- 60-79 → Warm lead, nurture
- 40-59 → Potential, needs more info
- Below 40 → Low priority
Include the logic so I can implement it in my CRM.
Why it works: Codex creates a customized scoring model based on YOUR sales process, not a generic template.
Prompt 9: Competitive Battle Card
Use case: Win more deals against specific competitors.
Create a battle card for competing against [COMPETITOR NAME].
Include:
1. **Positioning Summary** — How they describe themselves vs. how we do
2. **Their Strengths** — What they're actually good at (be honest)
3. **Their Weaknesses** — Where they fall short (with specific examples)
4. **Common Objections** — What prospects say when evaluating them
5. **Discovery Questions** — Questions that expose their weaknesses
6. **Landmines to Plant** — Things to mention early that hurt them later
7. **Proof Points** — Specific wins/case studies against them
8. **Quick Comeback Sheet** — 5 common competitor claims and how to respond
Be specific and tactical. This is for reps who encounter them weekly.
Time saved: 2-3 hours of competitive research
Prompt 10: Proposal Customization Engine
Use case: Customize templates instantly for each prospect.
I have a proposal template for [PRODUCT]. Customize it for [COMPANY NAME].
Original template sections to customize:
- Executive summary (make it about THEIR goals)
- Problem statement (reference THEIR specific challenges)
- Solution overview (connect features to THEIR use case)
- Timeline (adjust for THEIR urgency)
- Investment section (frame ROI for THEIR situation)
Context about this deal:
- [DEAL CONTEXT]
Maintain my company's voice and formatting. Only change the content to reflect this specific prospect's situation.
Output the full customized proposal with changes highlighted.
Why it works: You keep your proven template structure but personalize the substance. Prospects feel like it was written for them—because it was.
Time saved: 45+ minutes per proposal
Bonus: Combining Prompts with OpenClaw
These prompts are powerful on their own. They're unstoppable when automated.
With OpenClaw, you can:
Trigger prompt 1 automatically when a new lead enters your CRM
Run prompt 3 on a weekly schedule to keep data clean
Chain prompts together:
- New deal created → Run company research (Prompt 1)
- Meeting scheduled → Generate prep doc (Prompt 4)
- Proposal requested → Customize template (Prompt 10)
The prompts become agents that work while you sleep. If you want to see this end to end, follow our tutorial on building your first AI sales agent in 30 minutes — free and open source.
Prefer Claude over Codex? We break down the trade-offs in Claude vs ChatGPT for sales teams.
Codex Prompt Best Practices for 2026
The templates get you started. These practices are what separate SDRs who get generic AI output from the ones who get usable, first-draft-final results.
1. Be Specific About What You Don't Want
Listing exclusions ("don't use buzzwords," "no generic openers") improves output more than adding requirements. Codex is better at avoiding a named pattern than inferring good taste.
2. Include Examples
When asking for a specific format or style, paste an example of what good looks like. One strong example beats three paragraphs of description.
3. Use Mid-Turn Steering
Codex lets you redirect while it's generating. If you see it going off-track, interrupt and correct instead of waiting for a bad answer and starting over.
4. Iterate in the Same Session
Codex maintains context within a session. Follow up with "make it more concise" or "add more specific data points" rather than re-pasting the whole prompt.
5. Front-Load the Constraints
Put word limits, tone, and hard rules near the top of the prompt, not buried at the end. The model weights early instructions more heavily.
6. Save and Version Your Best Prompts
Build a library of prompts that work for YOUR sales process, and keep the winning versions. A refined prompt you reuse 50 times a week compounds far more than a clever one-off.
Try our AI Lead Generator — find verified LinkedIn leads for any company instantly. No signup required.
The Productivity Math
| Task | Manual Time | With Codex | Weekly Occurrences | Weekly Time Saved |
|---|---|---|---|---|
| Company research | 15 min | 2 min | 20 | 4.3 hours |
| Meeting prep | 20 min | 3 min | 8 | 2.3 hours |
| Email sequences | 90 min | 15 min | 2 | 2.5 hours |
| CRM cleanup | 3 hours | 30 min | 1 | 2.5 hours |
| Proposal customization | 45 min | 10 min | 3 | 1.75 hours |
Total weekly time saved: ~13 hours
That's 13 hours back for actual selling—calls, meetings, relationship building.
Codex Prompts FAQ
What is a Codex prompt?
A Codex prompt is the plain-English instruction you give OpenAI's Codex to get a specific result — a research brief, an email sequence, a data-cleanup script. A good one names the task, specifies the output format, and sets constraints, so you get a usable first draft instead of a vague answer.
What makes a good Codex prompt for sales?
The best sales prompts follow the five-part structure above: a clear role and goal, structured output (numbered sections or a table), constraints (word limits, tone), explicit exclusions, and [BRACKET] placeholders so one template works across every prospect.
Are these Codex prompts free to use?
Yes — every template on this page is free to copy, edit, and adapt to your own sales process. You only need access to Codex itself.
Can I turn these prompts into an automated workflow?
Yes. Each prompt runs manually today, but you can chain and schedule them so they fire on CRM triggers — new lead, meeting booked, proposal requested. See the OpenClaw automation section above and our guide to building your first AI sales agent in 30 minutes.
Codex or Claude for sales prompts?
Both work well; the right choice depends on your stack and workflow. We compare them head-to-head in Claude vs ChatGPT for sales teams and lay out the full Claude workflow in Claude for SDRs: The Complete Guide.
Related Reading
- Claude for SDRs: The Complete Guide — the full playbook for AI-assisted sales development
- Automate Lead Research with Claude Code — a 6-hour research week, automated
- Automate LinkedIn Sales Navigator with Claude Code — build lists and personalize at scale
- LinkedIn Outreach Automation with Claude Code — turn profiles into pipeline
- Build Your First AI Sales Agent in 30 Minutes — free, open source
Want to supercharge these prompts with real buyer intent data? MarketBetter shows you who's on your site and what they care about, so your AI-powered outreach hits even harder. Book a demo →