The CONTEXT Framework™ for Sales

I am a senior account executive at an AI training company selling enterprise workshops. My target is the VP of Operations at a 500-person manufacturing company. From their LinkedIn, they recently posted about struggling with quality control bottlenecks and mentioned they are evaluating automation options.

Write a cold email that earns a reply. The goal is to book a 15-minute discovery call, not to sell our product in the email.

Reference their specific LinkedIn post about quality control. Do not pitch our product or mention pricing. Ask a genuine question about their challenge. Keep it under 100 words because executives delete long cold emails. No attachments, no links, no images in the first touch. Do not use 'I hope this email finds you well' or any variation.

Peer-to-peer, not salesperson-to-prospect. Curious, direct, and respectful of their time. Zero corporate jargon.

Opening line style: 'Saw your post about [specific thing]. We are seeing the same pattern at 3 other manufacturers we work with.' This personalisation-plus-social-proof opening gets our best response rates.

Subject line (under 6 words, no clickbait), email body (80-100 words, 3 short paragraphs), and a single question as the CTA. No signature block beyond name and company.

I am an account executive who sent a personalised cold email to a Director of Sales Enablement 5 days ago. No reply. From their company's recent earnings call, I know they are expanding their sales team by 30% this quarter. My original email referenced their LinkedIn post about onboarding challenges.

Write a follow-up email that adds new value rather than just nudging. The goal is still to book a 15-minute call.

Do not say 'just following up' or 'bumping this to the top of your inbox.' Do not re-attach or re-paste the original email. Add a new insight or piece of value — reference the earnings call data about the 30% team expansion. Keep it even shorter than the first email. Give them a graceful exit by saying it is fine if the timing is wrong.

Confident, not needy. Helpful, not persistent. The tone of someone who has something genuinely useful to share and does not mind if the timing is wrong.

Follow-up style that works: 'Since I emailed, I saw your Q3 earnings call mentioned a 30% sales team expansion. That is going to make onboarding even more critical. One thing we have seen work: [specific insight]. Worth a 15-minute chat, or is the timing wrong?'

Subject line (reply to original thread), email body (60-80 words, 2 paragraphs), single CTA question with an easy 'no' option. No links, no attachments.

I am a solutions consultant at a cybersecurity firm. We completed a 3-week assessment of a healthcare company with 2,000 employees. They have 14 critical vulnerabilities, no incident response plan, and face a HIPAA audit in 4 months. The buying committee includes the CEO, CFO, and CISO.

Write the executive summary section of our remediation proposal. This is the page the CEO reads before deciding whether to approve the 450K budget.

Lead with regulatory risk (the HIPAA audit deadline), not technical vulnerabilities. Quantify the potential cost of a breach (average healthcare breach costs 10.93M according to IBM 2024 data). Do not list all 14 vulnerabilities — focus on the 3 most critical. Frame our solution as risk reduction, not a technology purchase. The CFO will reject anything that sounds like a vendor pitch.

Urgent but measured. The tone that makes an executive act without feeling manipulated. Factual, not emotional.

Opening sentence style: 'In 4 months, [Company] will face a HIPAA compliance audit. Based on our 3-week assessment, there are 14 unresolved vulnerabilities that put both compliance status and patient data at risk.'

250-300 words. 4 paragraphs: risk overview with deadline, key findings (top 3 only), recommended approach (high level), and investment range with ROI framing. No technical jargon. No bullet points — narrative paragraphs only.

I am the VP of Sales at a SaaS company selling AI-powered customer support tools. Our ACV is 85K. The most common objection we face is 'We already use Zendesk and it has AI features built in.' We win 35% of deals where this objection comes up, versus 60% overall close rate. Our key differentiators are: 40% faster resolution times, integration with internal knowledge bases, and no per-ticket AI surcharges.

Create an objection handling response for 'We already use Zendesk AI' that our sales reps can adapt to their own style.

Do not trash Zendesk — acknowledge it is a good platform. The response should reframe the conversation from 'replacement' to 'enhancement.' Use the specific differentiators (resolution time, knowledge base integration, pricing model) but lead with the customer's pain, not our features. Include a discovery question that exposes a gap Zendesk AI likely has. Address the switching cost concern proactively.

Consultative and confident. Not defensive. The tone of someone who respects the competitor but knows exactly where the gaps are.

Response framework: 'Acknowledge their choice, ask a specific question about their current experience, introduce one differentiator that addresses a likely gap, and propose a low-commitment next step.' Example: 'Zendesk is solid. How is it handling [specific scenario]? The reason I ask is...'

Structure: The Objection (verbatim), Why They Say It (2 sentences on the psychology), The Response (150 words, conversational script), The Follow-Up Question (one specific question), and a Low-Commitment Next Step (one sentence). Total: 300-350 words.

I am a sales development rep at a workforce management software company. I have a 20-minute discovery call with the HR Director at a 300-person retail chain. From my research, they use spreadsheets for scheduling, have high employee turnover (the industry average is 60% annually), and recently opened 5 new locations.

Create a structured set of discovery questions that uncovers their pain, quantifies the cost of the problem, and qualifies whether they are a good fit for our solution.

Do not ask more than 8 questions in a 20-minute call. Start with open-ended situational questions before narrowing to pain and impact. Include one question that quantifies the cost of their current process in hours or money. Do not mention our product until they have articulated their own pain. Include a question about their decision-making process and timeline.

Genuinely curious and professional. These should sound like a consultant trying to understand the business, not a rep running a qualification checklist.

Question progression: Situation ('Tell me about how scheduling works today across your locations'), Problem ('What happens when [specific scenario]?'), Impact ('What does that cost you in terms of [time/money/turnover]?'), Decision ('Who else would need to weigh in on a change like this?').

8 questions grouped into 4 phases: Situation (2 questions), Problem (2 questions), Impact (2 questions), Decision Process (2 questions). Each question has a 1-sentence note explaining what intelligence it is designed to uncover. Total: 300-400 words.

I am an enterprise account executive preparing for a first meeting with the CTO of a 1,200-person fintech company. The meeting is in 3 days. I sell enterprise AI integration services. I need to walk in knowing more about their AI challenges than they expect.

Create a pre-meeting research brief that gives me talking points, potential pain points, and a hypothesis about what they need.

Research should cover: recent news and press releases, their technology stack (check job postings for clues), leadership changes in the last 12 months, their competitive landscape, and any public statements about AI strategy. Include signals that suggest they are ready to buy (hiring AI roles, mentioning AI in earnings calls, recent funding). Flag any potential landmines (recent layoffs, regulatory issues, bad press).

Analytical and actionable. This is a prep document I will skim 30 minutes before the meeting. Bullet points, not paragraphs.

Research brief format: 'Company Snapshot: [key facts]. Recent Signals: [3-4 bullets]. Hypothesis: Based on [evidence], they likely need [our service] because [reasoning]. Opening Question: [specific question based on research].'

One page. Sections: Company Snapshot (5 bullet points), Recent Signals (4 bullets with sources), Technology Stack Clues (3 bullets from job postings), Competitive Pressure (2 bullets), Hypothesis (3 sentences), Potential Landmines (2 bullets), and 3 Prepared Opening Questions. Total: 400-500 words.

I am a mid-market account executive. My sales manager holds weekly pipeline reviews and expects a structured deal summary for every opportunity above 50K. I have a 120K deal with a logistics company that has been in the pipeline for 6 weeks. We have had 3 meetings, completed a demo, and they have asked for a custom ROI analysis.

Write a deal summary for this week's pipeline review that gives my manager everything they need to assess the deal and coach me.

Include the MEDDPICC qualification framework: Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identified Pain, Champion, and Competition. Be honest about gaps — we have not identified the economic buyer yet and we do not know the paper process. Include specific next steps with dates. Flag the main risk and what I plan to do about it.

Concise, honest, and structured. My manager respects reps who identify their own gaps. No optimistic spin.

Deal summary format: 'Deal: [Company] | Value: [amount] | Stage: [current stage] | Close Date: [target]. MEDDPICC Score: [X/8]. Key Risk: [one sentence]. Next Step: [specific action + date].'

Structure: Deal header (company, value, stage, target close date), MEDDPICC assessment (each element rated Green/Yellow/Red with a 1-sentence explanation), Top Risk (2 sentences), Next Steps (3 bullets with dates), and Ask (what I need from my manager). Total: 300-400 words.

I am the head of sales enablement at a cloud infrastructure company. Our main competitor in enterprise deals is AWS. We win on customer support (dedicated account team vs. self-serve), flexibility (no long-term contracts), and migration support (we handle the migration for free). We lose on brand recognition and breadth of services.

Create a competitive battlecard for our sales team to use when they encounter AWS in a deal.

Do not disparage AWS — our reps sound desperate when they do. Focus on reframing the buying criteria from 'biggest platform' to 'best outcome for this specific project.' Include specific questions reps should ask to expose AWS weaknesses (support responsiveness, contract lock-in, migration complexity). Address the 'nobody gets fired for choosing AWS' objection directly. Include win/loss data if possible (we win 45% of competitive deals vs AWS).

Confident and factual. The tone of a company that knows exactly where it wins and is not trying to be everything to everyone.

Battlecard format: 'When they say: [AWS claim]. We say: [our counter]. Question to ask: [specific question that exposes the gap].'

Structure: Competitor Overview (50 words), Where We Win (3 points with proof), Where They Win (2 points, be honest), Objection Handlers (3 common objections with responses), Discovery Questions to Ask (4 questions), and Win Story (one 50-word customer example). Total: 500-600 words. Format for quick scanning during a live call.

I am a customer success manager preparing for a quarterly business review with our largest client, a 2,000-person insurance company paying 240K ARR. They have been a customer for 18 months. Usage is up 25% quarter-over-quarter, but they raised a support escalation last month about API response times that took 2 weeks to resolve.

Create a QBR presentation outline that demonstrates value, addresses the support issue proactively, and plants seeds for an expansion conversation.

Lead with their success metrics, not our product features. Address the API issue before they raise it — acknowledge it, explain the fix, and share what we changed in our process to prevent recurrence. The expansion opportunity is adding 3 new departments (500 users). Do not make the expansion pitch heavy-handed; frame it as 'based on your usage patterns, here is where other similar clients get additional value.' Include a section on their goals for next quarter.

Partnership-oriented and transparent. The QBR should feel like a strategic planning session between partners, not a vendor trying to retain and upsell.

QBR slide format: 'Slide 1: Your Results This Quarter [3 key metrics with trend arrows]. Slide 2: What We Fixed [the API issue, proactively addressed]. Slide 3: What is Next [their goals + our recommendation].'

8 slides. Each slide: headline (under 10 words), 3-4 bullet points, and a speaker note (2 sentences). Structure: Welcome + Agenda, Usage Highlights, ROI Summary, Support Review (the API issue), Product Roadmap Preview, Expansion Opportunity, Their Q2 Goals, and Next Steps. Include a 1-page leave-behind summary.

I am a newly promoted enterprise account executive who just inherited a territory covering financial services companies in the Northeast US with 500-5,000 employees. There are 340 accounts in the territory. Last year's rep closed 1.2M against a 1.5M quota. I have access to our CRM data showing engagement history, and our marketing team can support 2 targeted campaigns per quarter.

Create a territory plan that prioritises accounts, defines my outreach strategy for each tier, and sets quarterly milestones toward a 1.5M annual quota.

Segment accounts into 3 tiers based on company size, existing engagement, and industry fit. Tier 1 should be no more than 30 accounts that I personally work. Include a coverage strategy for Tier 2 (100 accounts) using a mix of personal and marketing-supported outreach. Tier 3 (210 accounts) should be marketing-driven with trigger-based follow-up. Account for the 6-9 month enterprise sales cycle. Include pipeline coverage targets (3x quota in pipeline).

Strategic and realistic. This is a plan I am presenting to my VP of Sales. It should demonstrate that I think like a business owner, not just a quota-carrying rep.

Territory plan format: 'Tier 1 (30 accounts): Personal outreach cadence — Day 1 LinkedIn connect, Day 3 personalised email, Day 10 insight share, Day 21 call. Target: 15 qualified meetings in Q1.' This level of specificity shows I have a system.

Structure: Territory Overview (key stats in a table), Account Segmentation Criteria (the logic behind the tiers), Tier 1 Strategy (30 accounts, detailed cadence), Tier 2 Strategy (100 accounts, blended approach), Tier 3 Strategy (210 accounts, marketing-led), Quarterly Milestones (pipeline and revenue targets per quarter), and Resource Asks (what I need from marketing and leadership). Total: 800-1,000 words.