Skip to main content

23 posts tagged with "Sales Automation"

View All Tags

How to Build a 24/7 Pipeline Monitor with OpenClaw [2026]

Β· 8 min read
MarketBetter Team
Content Team, marketbetter.ai

Your best deals are dying in your pipeline right now. And you won't know until your weekly forecast meeting.

Deal velocity stalls. Champions go silent. Competitors sneak in. By the time you notice, the damage is done.

What if you had an AI agent watching your pipeline 24/7β€”catching problems the moment they appear?

This guide shows you how to build exactly that using OpenClaw, for free.

Pipeline Monitor Dashboard

What You'll Build​

By the end of this tutorial, you'll have an AI agent that:

  1. Monitors deal velocity β€” Alerts when deals stall for too long
  2. Tracks engagement signals β€” Knows when proposals are being viewed (or ignored)
  3. Detects risk patterns β€” Identifies deals that match historical loss patterns
  4. Sends smart alerts β€” Notifies you via Slack with context and recommended actions

The agent runs continuously on your infrastructure. No third-party access to your CRM data. No monthly fees.

Why DIY Pipeline Monitoring?​

Generic tools miss the nuance. Every sales org has different velocity benchmarks, different risk signals, different thresholds. A deal that's "stalled" for an enterprise might be normal pace for a startup.

Off-the-shelf solutions are expensive. Clari, Gong, and similar tools charge $15-40K annually. Most of that cost is for features you don't need.

Your CRM already has the data. HubSpot, Salesforce, Pipedriveβ€”they all expose APIs. The intelligence layer is what's missing.

With OpenClaw + a modern AI model, you can build exactly what you need.

Architecture Overview​

Pipeline Monitor Architecture

Here's how the system works:

HubSpot/Salesforce API
↓
OpenClaw Agent
(Scheduled every 4 hours)
↓
AI Analysis
(Claude/GPT)
↓
Slack Alerts
(With context + next actions)

The agent:

  1. Pulls active deals from your CRM
  2. Analyzes each deal against your defined risk criteria
  3. Uses AI to generate context-aware alerts
  4. Sends notifications to Slack with recommended next steps

Prerequisites​

Before starting, you'll need:

  • OpenClaw installed (Quick start guide)
  • CRM API access (HubSpot, Salesforce, or similar)
  • Slack webhook (for notifications)
  • ~30 minutes for initial setup

Step 1: Define Your Risk Criteria​

Before writing any code, define what "at risk" means for your org.

Common criteria:

SignalThresholdWhy It Matters
Days since last activity7+ days (varies by deal size)Champion may have gone cold
Proposal views0 views in 72 hoursThey're not engaged
Stage duration2x average for that stageSomething's blocking progress
Multiple stakeholders gone quiet2+ contacts inactiveDecision is stalled
Competitor mentionedAny recent mentionYou're being evaluated

Start with 3-5 criteria. You can always add more later.

Step 2: Create Your OpenClaw Agent Configuration​

Create a new agent configuration file. OpenClaw uses a workspace folder structure:

~/openclaw-workspace/
β”œβ”€β”€ AGENTS.md # Agent behavior rules
β”œβ”€β”€ SOUL.md # Agent personality
└── pipeline-monitor/
β”œβ”€β”€ config.json # Your risk criteria
└── HEARTBEAT.md # What to check on each run

Here's a sample config.json:

{
"riskCriteria": {
"daysWithoutActivity": 7,
"minDealSize": 10000,
"proposalViewThreshold": 72,
"stageVelocity": {
"demo_scheduled": 5,
"proposal_sent": 10,
"negotiation": 14
}
},
"notifications": {
"slackChannel": "#sales-alerts",
"urgentThreshold": 3
}
}

Step 3: Write the Monitoring Logic​

Here's the core logic for your agent. This goes in your HEARTBEAT.md file (what OpenClaw checks periodically):

## Pipeline Check

Every 4 hours:

1. Pull all active deals from HubSpot with deal size > $10,000
2. For each deal, check:
- Days since last activity (email, call, meeting)
- Days in current stage vs. average
- Proposal engagement (if applicable)
3. If any deal meets 2+ risk criteria:
- Generate a brief analysis of why it's at risk
- Suggest 2-3 specific next actions
- Send to #sales-alerts with deal link
4. If a deal meets 3+ risk criteria:
- Mark as URGENT
- Send additional notification to deal owner directly

Step 4: Connect to Your CRM​

OpenClaw can interact with any API. For HubSpot, you'll use their Deals API.

Example interaction flow (what you'd tell your agent):

Agent, fetch all deals from HubSpot where:
- Pipeline is "Sales Pipeline"
- Stage is not "Closed Won" or "Closed Lost"
- Amount is greater than $10,000

For each deal, also fetch:
- Last activity date
- Associated contacts and their last engagement
- Any notes from the past 30 days

OpenClaw's built-in exec tool can run curl commands against APIs, or you can write a simple Node.js script for more complex interactions.

Step 5: Set Up Slack Notifications​

Slack webhooks make this easy. In your Slack workspace:

  1. Go to Apps β†’ Incoming Webhooks
  2. Create a new webhook for your alerts channel
  3. Copy the webhook URL

Your agent can then send alerts like:

🚨 **DEAL AT RISK: Acme Corp ($75,000)**

**Signals detected:**
- 12 days without activity (threshold: 7)
- Proposal sent 8 days ago, 0 views
- Champion hasn't opened last 3 emails

**Recommended actions:**
1. Try reaching Sarah's colleague (Mike, CTO) via LinkedIn
2. Send a breakup email to create urgency
3. Ask for a referral to re-engage

[View in HubSpot](https://app.hubspot.com/deals/...)

Step 6: Deploy and Test​

With OpenClaw running, your agent will:

  1. Wake up every 4 hours (configurable)
  2. Run through the HEARTBEAT.md checklist
  3. Analyze your pipeline
  4. Send alerts as needed

Testing tip: Start with a shorter interval (every 30 minutes) and looser thresholds to make sure everything works. Then tune for production.

Advanced: AI-Powered Risk Scoring​

Basic threshold-based monitoring is good. AI-powered analysis is better.

Here's how to level up:

Pattern Matching Against Historical Losses​

Train your agent on your closed-lost deals:

Agent, analyze our last 50 closed-lost deals.
Identify common patterns in the 30 days before we lost them:
- How long were they in each stage?
- What was the engagement pattern?
- Were there any warning signs we missed?

Use these patterns to score current deals.

Natural Language Deal Analysis​

Instead of just checking numbers, have your agent read recent communications:

For each at-risk deal:
1. Pull the last 5 emails exchanged
2. Pull meeting notes from the last 30 days
3. Analyze for sentiment and buying signals
4. Flag if you detect hesitation, competitor mentions, or budget concerns

Weekly Forecast Digest​

Beyond individual alerts, generate a weekly summary:

Every Monday at 8 AM:
1. Analyze the full pipeline
2. Identify the 5 deals most likely to close this month
3. Identify the 5 deals most at risk
4. Calculate commit vs. best-case forecast
5. Send to #sales-leadership

Real Results: What This Looks Like in Practice​

Here's what one SDR leader reported after implementing this system:

"We caught a $120K deal that had gone quiet. The agent flagged it at day 8. Turns out our champion had switched teams and nobody told us. We re-engaged the new stakeholder and closed it two weeks later. That one alert paid for our entire setup time."

Typical Outcomes:​

  • 15-20% improvement in deal-to-close time
  • Earlier intervention on at-risk deals (average 5 days sooner)
  • Fewer surprises in forecast meetings
  • Better rep accountability (everyone knows deals are being watched)

Cost Breakdown​

ComponentCost
OpenClawFree (open source)
Hosting (VPS)$5-10/month
AI API calls~$20-50/month
Your time2-4 hours setup

Total: ~$50/month vs. $15-40K/year for enterprise alternatives.

Common Pitfalls to Avoid​

1. Alert Fatigue​

Don't alert on everything. Start strict and loosen only if you're missing real problems.

2. Wrong Thresholds​

Your thresholds should match your actual sales cycle. A 7-day activity gap means something different for a 2-week sales cycle vs. a 6-month enterprise deal.

3. No Next Actions​

An alert without a recommended action is useless. Always include what to do.

4. Ignoring False Positives​

When your agent is wrong, update the criteria. This is a learning system.

Extending the System​

Once you have basic monitoring working, consider adding:

  • Competitor mention detection (scan emails and meeting notes)
  • Multi-thread tracking (are all stakeholders engaged?)
  • Renewal risk monitoring (for customer success)
  • Automated follow-up drafts (agent writes, human sends)
Free Tool

Try our AI Lead Generator β€” find verified LinkedIn leads for any company instantly. No signup required.

Getting Started Today​

  1. Install OpenClaw: docs.openclaw.ai
  2. Define 3 risk criteria for your org
  3. Set up a test deal in your CRM that meets the criteria
  4. Watch the alert come through
  5. Iterate based on real results

Your pipeline is too important to check once a week. Build a system that watches it for you, 24/7.

The tools are free. The setup takes an afternoon. The deals you'll save are worth it.

Want to add visitor identification and buying signals to your pipeline monitoring? MarketBetter shows you who's on your site and what they care about. Book a demo β†’

OpenAI Codex vs Claude Code for Sales Automation [2026]

Β· 7 min read
MarketBetter Team
Content Team, marketbetter.ai

GPT-5.3-Codex dropped three days ago. Claude Code has been the go-to for AI-powered development. If you're building sales automation, which one should you use?

The honest answer: Both. For different things.

Codex vs Claude Comparison

This isn't a "which is better" post. It's a practical guide to when each tool excelsβ€”specifically for GTM use cases.

The Core Difference​

Here's the fundamental distinction:

OpenAI Codex is optimized for building software. It excels at:

  • Writing code from scratch
  • Multi-file refactoring
  • Creating integrations
  • Building applications

Claude Code is optimized for reasoning and judgment. It excels at:

  • Analyzing unstructured data
  • Writing persuasive copy
  • Making nuanced decisions
  • Understanding context

For sales automation, you need both capabilities.

Head-to-Head: Sales Automation Tasks​

Let's get specific. Here's how each performs on common GTM automation tasks:

Task 1: Build a CRM Integration​

Goal: Create a script that syncs data between HubSpot and your custom database.

CriteriaCodexClaude Code
Code quality⭐⭐⭐⭐⭐⭐⭐⭐⭐
Speed⭐⭐⭐⭐⭐⭐⭐⭐
Error handling⭐⭐⭐⭐⭐⭐⭐⭐
Documentation⭐⭐⭐⭐⭐⭐⭐⭐

Winner: Codex

Codex was literally built for this. It understands API patterns, handles edge cases well, and the new mid-turn steering lets you course-correct as it builds.

Task 2: Analyze Sales Call Transcripts​

Goal: Extract action items, objections, and next steps from call recordings.

CriteriaCodexClaude Code
Comprehension⭐⭐⭐⭐⭐⭐⭐⭐
Nuance detection⭐⭐⭐⭐⭐⭐⭐⭐
Context retention⭐⭐⭐⭐⭐⭐⭐⭐
Output quality⭐⭐⭐⭐⭐⭐⭐⭐

Winner: Claude Code

Claude's 200K context window and superior reasoning make it far better at understanding long, nuanced conversations. It catches subtleties that Codex misses.

Task 3: Write Personalized Cold Emails​

Goal: Generate custom outreach based on prospect research.

CriteriaCodexClaude Code
Personalization quality⭐⭐⭐⭐⭐⭐⭐⭐
Tone consistency⭐⭐⭐⭐⭐⭐⭐⭐
Creativity⭐⭐⭐⭐⭐⭐⭐
Template variation⭐⭐⭐⭐⭐⭐⭐⭐

Winner: Claude Code

Writing persuasive copy requires understanding human psychology. Claude consistently produces more natural, compelling emails.

Task 4: Build a Lead Scoring Model​

Goal: Create a system that scores leads based on behavioral data.

CriteriaCodexClaude Code
Algorithm design⭐⭐⭐⭐⭐⭐⭐⭐⭐
Implementation⭐⭐⭐⭐⭐⭐⭐⭐
Data pipeline⭐⭐⭐⭐⭐⭐⭐⭐
Iteration speed⭐⭐⭐⭐⭐⭐⭐⭐

Winner: Codex

Building a scoring model means writing code, connecting data sources, and iterating on logic. Codex handles this better.

Task 5: Prioritize Accounts for SDRs​

Goal: Analyze a list of accounts and rank them by likelihood to convert.

CriteriaCodexClaude Code
Data processing⭐⭐⭐⭐⭐⭐⭐⭐
Qualitative assessment⭐⭐⭐⭐⭐⭐⭐⭐
Reasoning explanation⭐⭐⭐⭐⭐⭐⭐⭐
Pattern recognition⭐⭐⭐⭐⭐⭐⭐⭐⭐

Winner: Claude Code

Account prioritization requires judgmentβ€”understanding market signals, company trajectory, buying patterns. Claude's reasoning shines here.

The Winning Stack: Use Both​

Sales Automation Workflow

Here's the pattern that works best for most GTM teams:

Data Processing / Infrastructure β†’ Codex
Analysis / Judgment / Writing β†’ Claude
Orchestration / 24/7 Operation β†’ OpenClaw

Real Example: Automated Competitive Intel​

Let's say you want to monitor competitors and alert sales when relevant changes happen.

Step 1: Build the monitoring system (Codex)

  • Create web scrapers for competitor pricing pages
  • Set up alerts for their job postings
  • Build RSS feed aggregation for their blogs
  • Store everything in a database

Step 2: Analyze and prioritize (Claude)

  • Read new competitor content and extract key messages
  • Identify changes that affect specific deals
  • Generate briefings for sales team
  • Write custom battle card updates

Step 3: Orchestrate everything (OpenClaw)

  • Run scrapers on schedule
  • Route data to Claude for analysis
  • Send alerts to appropriate channels
  • Maintain state across sessions

Real Example: SDR Research Assistant​

Step 1: Build data pipelines (Codex)

  • LinkedIn profile scraper
  • Company database enrichment
  • News aggregation system
  • CRM integration layer

Step 2: Generate insights (Claude)

  • Analyze prospect's recent activity for conversation hooks
  • Identify likely pain points based on company signals
  • Write personalized research summaries
  • Suggest specific talking points

Step 3: Deploy as always-on agent (OpenClaw)

  • Trigger research when new lead enters pipeline
  • Deliver summary to rep via Slack
  • Update research weekly for active deals

Speed vs. Quality Trade-offs​

When Speed Matters Most​

Use Codex when:

  • You need working code fast
  • You're iterating on infrastructure
  • The task is well-defined
  • You'll review the output anyway

Codex's 25% speed improvement over the previous version makes it noticeably faster for rapid prototyping.

When Quality Matters Most​

Use Claude when:

  • The output goes directly to prospects
  • You need nuanced judgment
  • Context is complex or ambiguous
  • Mistakes would be embarrassing

Claude's longer context window (200K tokens) means it can hold entire conversation histories, deal contexts, and company profiles in memory.

Cost Comparison​

Both tools charge by token usage. Here's a rough comparison for typical sales automation tasks:

TaskCodex CostClaude Cost
Build CRM integration~$0.50~$0.80
Analyze 10 call transcripts~$2.00~$1.50
Generate 50 personalized emails~$1.00~$0.75
Weekly competitive analysis~$0.30~$0.50

Monthly estimate for active GTM automation: $30-80 (using both tools for their strengths)

Compare this to enterprise sales automation platforms at $35-50K/year.

Integration Considerations​

Codex Strengths for Integration​

  • Native support for most programming languages
  • Better at handling API authentication flows
  • Superior error handling for production code
  • Mid-turn steering allows real-time debugging

Claude Strengths for Integration​

  • Better at explaining what it's doing (self-documenting)
  • More reliable for structured output (JSON formatting)
  • Superior at following complex, multi-step instructions
  • Better at handling ambiguous requirements

The OpenClaw Layer​

Both Codex and Claude are powerful, but they're toolsβ€”not agents.

OpenClaw turns them into always-on systems that:

  • Run on schedules
  • Respond to events
  • Maintain memory
  • Connect to your channels

The architecture:

Your Sales Process
↓
OpenClaw
↓
Routes to:
β”œβ”€β”€ Codex (for building/coding tasks)
└── Claude (for analysis/writing tasks)
↓
Delivers via:
β”œβ”€β”€ Slack
β”œβ”€β”€ Email
└── CRM updates

Practical Recommendations​

If You're Just Starting​

Pick one tool first. Claude is more forgiving for beginners because it explains its reasoning. Once you're comfortable, add Codex for infrastructure work.

If You're Building Production Systems​

Use both from the start. Design your architecture to route tasks to the appropriate model. The cost difference is negligible compared to the quality improvement.

If You're Budget-Constrained​

Start with Claude. It's more versatile for sales tasks specifically. Add Codex when you need to build more complex integrations.

If You Need Maximum Speed​

Lead with Codex. The 25% speed improvement in GPT-5.3-Codex makes it noticeably faster for iteration. Use Claude for final review of customer-facing content.

Common Mistakes to Avoid​

1. Using Codex for Copywriting​

Codex can write functional copy, but Claude writes persuasive copy. For anything customer-facing, use Claude.

2. Using Claude for Complex Infrastructure​

Claude can write code, but Codex handles multi-file projects and API integrations more reliably.

3. Not Combining Them​

The tools complement each other. Building with one while ignoring the other limits what you can achieve.

4. Manual Orchestration​

Without OpenClaw (or similar), you're manually running prompts. Automation requires an agent layer.

Future-Proofing Your Stack​

Both OpenAI and Anthropic are shipping improvements constantly. The pattern that will survive:

  1. Keep your prompts modular. You should be able to swap models without rewriting your entire system.

  2. Abstract the orchestration layer. OpenClaw (or your own framework) should handle routing, not your application code.

  3. Store your context externally. Don't rely on model memory. Keep prospect data, conversation history, and preferences in your own database.

Free Tool

Try our AI Lead Generator β€” find verified LinkedIn leads for any company instantly. No signup required.

The Bottom Line​

Use CaseBest Tool
Build integrations and pipelinesCodex
Analyze conversations and dataClaude
Write customer-facing contentClaude
Create automation infrastructureCodex
Make judgment callsClaude
Rapid prototypingCodex
Always-on operationOpenClaw (orchestrating both)

Don't pick a side. The teams winning with AI automation in 2026 are using the right tool for each job.


Want to see how MarketBetter combines visitor intelligence with AI automation? We identify who's on your site and what they care aboutβ€”then help you act on it. Book a demo β†’

Codex Prompts for SDRs: 10 Templates + Best Practices [2026]

Β· 13 min read
MarketBetter Team
Content Team, marketbetter.ai

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.

SDR Productivity Prompts

Anatomy of a Great Codex Prompt​

Anatomy of a great Codex prompt: role and goal, structured output, constraints, exclusions, placeholders

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.

SDR Prompts Checklist

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.


Free Tool

Try our AI Lead Generator β€” find verified LinkedIn leads for any company instantly. No signup required.

The Productivity Math​

TaskManual TimeWith CodexWeekly OccurrencesWeekly Time Saved
Company research15 min2 min204.3 hours
Meeting prep20 min3 min82.3 hours
Email sequences90 min15 min22.5 hours
CRM cleanup3 hours30 min12.5 hours
Proposal customization45 min10 min31.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.



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 β†’