2 posts tagged with "Prompts"

Most "AI prompt" lists are the same ten generic prompts rewritten a hundred times. This isn't that.

Below are 30 Codex prompts organized by the actual job you're trying to do — research a prospect, write the email, prep the meeting, clean the pipeline, win the deal. Each one is copy-paste ready and built for GPT-5.3-Codex. At the end, you'll get the reusable prompt template that lets you write your own from scratch, so you're never dependent on someone else's list again.

If you want the shorter starter set first, our 10 Codex prompts that 10x SDR productivity is the fastest place to begin. This library goes deeper and covers the full GTM motion.

Before You Start: 60-Second Setup​

Install the Codex CLI:

npm install -g @openai/codex

Or run Codex in the browser at codex.openai.com. New to the tool? Our OpenAI Codex CLI GTM guide walks through the full setup, and if you're deciding between models, read Codex vs Claude vs ChatGPT for GTM before you commit.

Three rules that make every prompt below work better:

1. Fill in every [BRACKET]. The prompts are templates. Vague inputs get vague outputs.
2. Steer mid-generation. When Codex drifts, interrupt and correct it — don't restart. See mid-turn steering for GTM.
3. Iterate in one session. Codex holds context. Follow up with "tighten this" or "add a data point" instead of starting over.

Category 1: Research & Prospecting​

The prep work that eats your morning. These four prompts turn an hour of tab-switching into a few minutes.

Prompt 1: Account Deep-Dive Brief​

Use case: A full account brief before you touch the phone.

Build a research brief on [COMPANY]. Structure it as:

1. One-line description of what they sell and to whom
2. Company stage (headcount, funding, growth signals)
3. Top 3 strategic priorities you can infer from recent news, job posts, and their site
4. The single team most likely to feel the pain [YOUR PRODUCT] solves
5. One specific, non-generic opener referencing something real from the last 90 days

Only include facts you can support. Mark anything speculative as "inferred."

Prompt 2: Buying-Committee Map​

Use case: Know who to multithread before you send a single email.

For [COMPANY] evaluating [PRODUCT CATEGORY], map the likely buying committee:

- Economic buyer (title + why they care)
- Champion (title + the win that makes them look good)
- Technical evaluator (title + their top concern)
- Likely blocker (title + their objection)

For each, give me one message angle that resonates with that specific role.

Pair this with our multithreading stakeholder playbook to turn the map into a sequence.

Prompt 3: Trigger-Event Scanner​

Use case: Find a real reason to reach out today.

Given these recent signals about [COMPANY]:
[PASTE NEWS / JOB POSTS / FUNDING / PRODUCT LAUNCHES]

Rank the top 3 as outreach triggers. For each, tell me:
- Why it creates urgency for [YOUR PRODUCT]
- The exact first sentence of an email that references it
- What NOT to say so it doesn't feel like I'm just name-dropping the news

Prompt 4: ICP Look-Alike Builder​

Use case: Turn your best customer into a target list definition.

My best customer is [CUSTOMER + why they're ideal]. Reverse-engineer the
firmographic and technographic profile that made them a great fit:

- Industry, size band, and growth stage
- Tech stack signals that indicate readiness
- Org signals (roles hiring, team structure) that predict need
- 3 disqualifiers that mean "don't bother"

Output as a checklist I can score prospects against.

For scoring the list you build, see AI lead scoring with Codex.

Prompt 5: Rep-Ready Research Digest​

Use case: Compress five sources into one scannable card.

Turn the raw notes below into a 5-bullet pre-call card an SDR can read in
20 seconds. No fluff, no restating the company name. Lead with the most
useful fact for booking a meeting.

[PASTE RAW RESEARCH]

Category 2: Personalized Outreach & Email​

Volume is easy. Relevance is hard. These prompts optimize for reply rate, not send count.

Prompt 6: First-Touch Cold Email​

Use case: One email, one idea, one ask.

Write a cold email to [TITLE] at [COMPANY] about [PROBLEM YOU SOLVE].

Constraints:
- Under 90 words
- Subject line under 40 characters, no clickbait
- One specific observation about their business (use: [TRIGGER])
- One clear, low-friction CTA (not "hop on a 30-min call")
- No "hope this finds you well," no "just reaching out," no "circling back"

Tone: peer-to-peer, direct, mildly curious. Not salesy.

Prompt 7: Reply-Rate Rewrite​

Use case: Fix an email that isn't landing.

Here's an email getting a [X]% reply rate:
[PASTE EMAIL]

Diagnose why it's underperforming, then rewrite it. Show:
1. The 3 biggest problems (be blunt)
2. A rewritten version
3. One A/B variation with a different angle

Keep it human. If it reads like AI wrote it, you failed.

Prompt 8: Multi-Touch Sequence with a Thesis​

Use case: A sequence where every email earns the next.

Build a 5-touch sequence for [ICP] selling [PRODUCT]. Each touch must
introduce a NEW idea, not repeat the last one:

- Touch 1: Provocative observation about their world
- Touch 2: Proof (customer story or stat)
- Touch 3: Reframe the problem they think they have
- Touch 4: Direct, specific ask
- Touch 5: Honest breakup

Under 90 words each. Mark personalization with [BRACKETS]. One CTA per email.

Prompt 9: LinkedIn-to-Email Bridge​

Use case: Convert a LinkedIn interaction into a real conversation.

I [connected with / got a like from / commented alongside] [NAME], [TITLE]
at [COMPANY]. Context: [WHAT HAPPENED].

Write a short follow-up that references the interaction naturally, adds value,
and earns a reply — without pitching in the first message.

Prompt 10: Objection-Preempting P.S.​

Use case: Neutralize the obvious objection before they raise it.

For an email to [TITLE] about [PRODUCT], the most likely brush-off is
"[OBJECTION]." Write 3 one-line P.S. options that quietly defuse it without
sounding defensive.

Category 3: Discovery & Meetings​

Walk in prepared, run a tighter call, follow up faster.

Prompt 11: Discovery Question Set​

Use case: Questions that surface real pain, not surface-level nods.

Generate a discovery guide for a [MEETING TYPE] with [TITLE] at [COMPANY].

Give me:
- 3 situation questions (fast, build rapport)
- 4 problem questions (surface pain)
- 3 implication questions (make the cost of inaction real)
- 2 vision questions (paint the after-state)

For each, add a one-line note on what a good answer tells me.

Prompt 12: Live Meeting Prep One-Pager​

Use case: Everything you need on a single screen.

Meeting with [NAME] at [COMPANY] about [TOPIC]. Build a one-pager:

- 3 key facts about them
- 2 likely objections + my response
- Top 3 discovery questions
- Who else they might be evaluating
- 3 next-step options if it goes well

Keep every section to bullets. Prioritize what helps me advance the deal.

Selling the demo itself? Pair this with demo personalization with Codex.

Prompt 13: Real-Time Objection Handler​

Use case: A comeback sheet you can glance at mid-call.

For [PRODUCT] sold to [ICP], generate a comeback sheet for the 6 most common
objections. For each: a 1-line acknowledgment, a reframe, a proof point, and
a question that moves the conversation forward. Conversational, not scripted.

Want a repeatable in-call diagnostic? See our discovery call diagnostic: 8 signals that predict close.

Prompt 14: Post-Call Follow-Up in 60 Seconds​

Use case: Send the recap while the call is still warm.

Turn these call notes into a follow-up email:
[PASTE NOTES]

Include: a one-line recap of their goal, the 2-3 points that mattered most
to them, the agreed next step with a date, and nothing they didn't actually
say. Under 120 words. Founder-to-buyer tone.

Prompt 15: Deal Recap for the Champion​

Use case: Arm your champion to sell internally without you.

My champion [NAME] needs to pitch [PRODUCT] to their [BOSS/COMMITTEE].
Write a short internal-forward doc they can paste into Slack or email:

- The problem in their words
- The 3 outcomes that matter to leadership
- The cost of doing nothing
- The simple next step

Make my champion look smart. Zero jargon.

Category 4: Pipeline, CRM & Ops​

The unglamorous work that quietly kills quota. Automate it.

Prompt 16: Pipeline Hygiene Audit​

Use case: Find the deals lying to your forecast.

Given this pipeline export:
[PASTE DEALS: name, stage, amount, last activity, close date]

Flag every deal that is: stalled (no activity in 14+ days), slipping (close
date pushed twice), or mis-staged (stage doesn't match activity). For each,
give me the one action that unsticks it. Output as a prioritized list.

More on this in Codex CRM pipeline cleanup and CRM hygiene automation with Codex.

Prompt 17: CRM Field Standardizer​

Use case: Fix messy data without hand-editing rows.

Write a Node.js script that reads a CRM contact export (CSV) and:
- Standardizes phone numbers to E.164
- Title-cases names and job titles
- Flags (does not auto-change) email domains that don't match company domain
- Outputs a change-preview report before writing anything

Include error handling and a dry-run flag.

Prompt 18: Weekly Forecast Summary​

Use case: Turn a spreadsheet into a narrative your manager reads.

From this deal list [PASTE], write a 6-line forecast summary:
- Committed vs best-case number
- The 2 deals most likely to close this period and why
- The 2 biggest risks
- The one thing I need help with

No hedging. If the number is soft, say so.

For accuracy tuning, see AI sales forecasting accuracy with Codex.

Prompt 19: Lead Router​

Use case: Route inbound to the right rep instantly.

Design routing logic for inbound leads. Inputs available: [LIST FIELDS].
Rules I care about: [e.g., enterprise by headcount to AE tier 1, SMB to SDR
pod, existing customers to CSM]. Output a decision tree plus edge-case
handling for missing data.

Deeper build in AI lead routing system with Codex.

Prompt 20: Activity-to-Insight Rollup​

Use case: Turn raw activity logs into coaching signal.

Here are my last 2 weeks of activity [PASTE: calls, emails, meetings].
Tell me: where I'm spending time vs where deals actually move, my highest
and lowest ROI activity, and the one habit to change next week. Be direct.

Category 5: Competitive & Deal Strategy​

Win the deals that are genuinely up for grabs.

Prompt 21: Battle Card Generator​

Use case: A tactical card for a competitor you hit weekly.

Build a battle card for competing against [COMPETITOR] when selling [PRODUCT]:

1. How they position vs how we should
2. Their real strengths (be honest)
3. Their weaknesses with specific examples
4. 4 discovery questions that expose the gaps
5. 3 traps to set early that hurt them later
6. Quick comebacks to their 5 most common claims

Tactical and specific. This is for reps, not marketing.

Automate the whole thing with AI sales battle card automation.

Prompt 22: Deal Risk Diagnosis​

Use case: Get an honest second opinion on a stuck deal.

Here's a deal: [CONTEXT — stage, stakeholders, timeline, what's happened].
Play skeptical sales manager. Tell me: the 3 biggest risks, the question I'm
avoiding, whether this is real or happy ears, and the single next move with
the highest leverage.

Prompt 23: Mutual Action Plan​

Use case: A shared close plan that keeps the deal on rails.

Create a mutual action plan to get [COMPANY] from [CURRENT STAGE] to signed
by [DATE]. List every step, owner (us or them), and date working backward
from close. Flag the 2 steps most likely to slip.

Prompt 24: Pricing & Packaging Framer​

Use case: Present price as value, not sticker shock.

For [PRODUCT] priced at [PRICE MODEL], and a prospect who cares most about
[THEIR PRIORITY], write 3 ways to frame the investment around ROI and cost
of inaction. Include the exact language for the "why this is worth it" moment.
No discounting.

Prompt 25: Loss Post-Mortem​

Use case: Extract a lesson from every closed-lost.

We lost [DEAL] to [COMPETITOR / no-decision] because [WHAT HAPPENED].
Diagnose the real root cause (not the stated one), the earliest point I could
have changed the outcome, and the one process change that prevents a repeat.

Category 6: Manager & Team Enablement​

For the people who carry a number and a team.

Prompt 26: 1:1 Coaching Prep​

Use case: Walk into every 1:1 with a plan.

My rep [NAME] has this pipeline and activity [PASTE]. Prep my 1:1:
- 2 genuine wins to open with
- The single metric holding them back
- 3 coaching questions (not lectures)
- One deal to inspect together and why

Coach, don't manage.

Prompt 27: Playbook Builder​

Use case: Codify what your best rep does.

Turn these notes on our top performer's process [PASTE] into a repeatable
playbook: the motion stage by stage, the "if this, then that" plays, and the
3 habits that separate them from the median rep. Written so a new hire can run it.

Full walkthrough in AI sales playbook generator with Codex.

Prompt 28: Onboarding Ramp Plan​

Use case: Get new reps productive faster.

Design a 30-60-90 ramp for a new [ROLE] selling [PRODUCT] to [ICP]. For each
phase: the outcome, the skills to build, the certifications to pass, and the
leading indicator that predicts they'll hit quota.

Prompt 29: Team Performance Benchmark​

Use case: See where the team really stands.

Given this team's metrics [PASTE], benchmark each rep on activity, conversion,
and deal velocity. Identify the top pattern among winners, the common failure
mode among laggards, and the one team-wide change with the biggest upside.

See SDR performance benchmarking with Codex for the full method.

Prompt 30: Cold Call Script Optimizer​

Use case: A talk track that doesn't sound like a robot.

Write a cold call framework for calling [TITLE] at [COMPANY TYPE]:
opening (5 sec), permission ask, 15-second hook on [PAIN], 2 qualifying
questions, bridge to meeting, top 3 objection handlers, graceful exit.
Give exact language, not concepts. Make it sound like a human, not a script.

More at AI cold call script optimizer with Codex.

The Anatomy of a Great Codex Prompt (Steal This Template)​

The prompts above work because they share a structure. Once you internalize it, you'll stop hunting for lists and start writing better prompts than any list gives you.

Here's the reusable template:

[ROLE / CONTEXT]      -> Who you are and the situation
[TASK]                -> The one job, stated plainly
[INPUTS]              -> The real data, marked with [BRACKETS]
[CONSTRAINTS]         -> Length, tone, format, and what to avoid
[OUTPUT FORMAT]       -> Exactly how you want it back
[EXCLUSIONS]          -> What NOT to do (the secret weapon)

Filled in, it looks like this:

You're an SDR selling [PRODUCT] to [ICP].
Task: write a first-touch cold email.
Inputs: prospect is [TITLE] at [COMPANY]; trigger is [EVENT].
Constraints: under 90 words, one CTA, peer tone.
Output: subject line + body.
Don't: use "hope this finds you well," buzzwords, or a hard ask.

Five rules that separate good prompts from great ones:

1. State the exclusions. Telling Codex what to avoid improves output more than piling on requirements. "No buzzwords, no generic openers" does more than three extra instructions.
2. Give real inputs, not placeholders. The prompt is a template; your data makes it useful. Paste the actual trigger, the real notes, the true numbers.
3. Specify the output format. "Return a 5-bullet card" beats "summarize this" every time.
4. Constrain length up front. Unbounded prompts produce unbounded fluff. Set the word count.
5. Iterate, don't restart. Codex keeps context in a session. "Tighten this" and "make it more specific" refine faster than a fresh prompt.

For choosing the right tool for these prompts, compare Codex vs Claude Code for sales automation. If you lean Claude, our Claude SDR daily routine and how to use Claude for lead generation cover the same motion.

From Prompts to Autopilot​

Prompts save you minutes. Automation saves you the job entirely.

Each prompt above can become a trigger:

• New lead lands in the CRM → run the Account Deep-Dive Brief (Prompt 1) automatically
• Meeting booked → generate the Live Meeting Prep One-Pager (Prompt 12)
• Every Friday → run the Pipeline Hygiene Audit (Prompt 16)

Chain them and the prompts stop being things you run and start being work that runs itself.

The Real Unlock​

Even the best prompt is only as good as the input you feed it. "Research this company" gets you public info anyone can find. The reps who win know who's actually on their site right now and what those buyers care about — then feed that into prompts like the ones above.

That's the gap MarketBetter closes. We tell you who's showing intent and what to do next, so your Codex prompts run on real buying signals instead of guesses.

Want to feed your prompts real buyer intent? Book a demo →

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:

1. 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").
2. Structured output — Ask for numbered sections, bullets, or a table. Vague prompts get vague answers; specifying the format is the single biggest quality lever.
3. Constraints — Word limits, tone, and hard rules ("under 100 words," "no corporate buzzwords") force quality more than adding requirements.
4. 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.
5. 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:

1. New deal created → Run company research (Prompt 1)
2. Meeting scheduled → Generate prep doc (Prompt 4)
3. 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.

The Productivity Math​

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 →