Write a cold outreach email based on a specific trigger event.

Prospect name: [name]
Company: [company name]
Trigger event: [e.g., company announced expansion / job posting for a role that indicates a need / recent funding round / published article or press release]
What the trigger tells me about their likely challenge: [your inference]
What my product/service solves: [one sentence — specific to their inferred challenge]
Specific ask: [one thing — 15-minute call / reply to one question / review a resource]

Email should: open with the trigger (not "I" or your company name), connect it to a likely challenge, show the connection to your solution in one sentence, and make a low-friction ask. Under 150 words. Subject line included.

Write a personalized cold email using publicly available research.

Prospect name: [name]
Prospect's LinkedIn headline or recent post: [paste or describe]
Company challenge I've identified: [specific — from news, earnings calls, job postings, or LinkedIn activity]
How my solution connects: [specific connection to the challenge]
Social proof relevant to them: [a client in a similar situation / industry / company size]
Ask: [specific low-friction CTA]

Open with something specific they said or did publicly — not a generic opener. Under 150 words. Do not mention that you "came across their profile." Lead with insight, not surveillance.

Write a LinkedIn connection request message.

Prospect name: [name]
Why I'm connecting: [specific reason — shared connection / saw their post / research on their company]
What I offer that's relevant: [one sentence, specific to their context]
No hard ask: this is a connection, not a pitch.

Under 300 characters (LinkedIn limit). Direct, human, not salesy. Do not say "I'd love to connect" — say why this specific connection makes sense.

Write a re-engagement email for a prospect who went cold.

Prospect name: [name]
Last contact: [approximate date and what was discussed]
Why they may not have responded: [your honest assessment — timing / not a priority / wrong person]
New reason to reach out: [something changed — product update / new case study / their company news / time has passed and circumstances may have changed]
Specific ask: [one thing]

Under 150 words. Do not apologize for "bugging them." Lead with the new reason, not the history. Acknowledge it's been a while in one sentence, then move forward.

Write an email to a happy customer asking for a referral.

Customer name: [name]
Their result with your product/service: [specific outcome — real number if possible]
Type of referral that would be valuable: [describe the ideal prospect — role, company type, challenge]
The ask: [introduction / name / LinkedIn connection]
What you'll do with the referral: [brief — be specific, not vague]

Under 150 words. Lead with their success, then make the ask directly. Do not use the phrase "if you know anyone" — describe who specifically would benefit. Include how easy it is for them to act.

Write a discovery call agenda for the following prospect.

Company: [name]
Prospect's role: [title]
What I know about their situation: [pain point, trigger, or context]
My goal for this call: [one thing — qualify / uncover specific pain / advance to demo / get intro to economic buyer]
Time available: [X minutes]

Create a call agenda with: a brief opening that establishes credibility in one sentence, 4-5 discovery questions organized by theme (situation → problem → impact → initiative), and a specific next step to close on. Under 300 words. Not a script — an agenda. The questions should flow like a conversation, not an interrogation.

Write discovery questions tailored to a specific buyer persona.

Persona: [e.g., VP of Sales / CFO / Head of Operations / IT Director]
Typical challenges this persona faces: [list 2-3 known pain points]
What they care about most: [metrics, KPIs, or outcomes relevant to their role]
My product/service: [brief description]

Write 8-10 discovery questions that: uncover whether this pain exists, understand the scale and urgency of the problem, explore what they've already tried, and reveal how decisions get made. Organize by theme. Do not include "so what keeps you up at night" — use specific, insightful questions that demonstrate you know their world.

Write a pre-call research summary for a discovery call.

Company name: [name]
Industry: [industry]
Company size: [employees / revenue]
What I found in research: [recent news / LinkedIn activity / job postings / earnings call notes / product or pricing changes]
Key inference about their current situation: [your hypothesis based on the research]
My solution's most relevant connection to this company: [specific]

Format: internal prep note, under 250 words. Answer: what do I know? What do I think is happening? What question will test my hypothesis?

Write a stakeholder discovery map for a complex sale.

Company: [name]
Stakeholders identified so far: [name/role for each]
Economic buyer: [who actually owns the budget]
Technical evaluator: [who has to approve the solution]
Champion: [who wants this to happen]
Blocker: [who might resist]
Unknown stakeholders: [roles I haven't reached yet]

For each stakeholder, write: what they care about / what their success metric looks like / what objection they're most likely to raise / who I should talk to next. Under 400 words. This is a working document to update as the deal progresses.

Write competitive positioning notes for a discovery call where a competitor is in the mix.

Competitor name: [name]
What they do well: [honest assessment]
Where they fall short for this specific prospect: [based on the prospect's stated or inferred priorities]
Our differentiated strengths relevant to this prospect: [specific — not generic marketing language]
How to handle "why are you better than [competitor]?" without disparaging them: [diplomatic but clear comparison]

Under 300 words. Prepare to acknowledge competitor strengths — buyers trust reps who are honest about the competitive landscape more than reps who trash competitors.

Write an executive summary for a sales proposal.

Prospect company: [name]
Decision-maker name and title: [name, title]
Their stated business challenge (use their exact words if possible): [challenge]
The outcome they told me they want: [specific — use their language]
How our solution addresses their specific situation: [tailored, not generic]
What we're proposing: [brief description of scope]
Expected timeline and investment: [range or specific]

Under 250 words. Written from the buyer's perspective — their problem, their words, their desired outcome. They should read this and think "this company understood us." Do not start with your company background.

Write a business case section for a proposal.

Prospect's current pain (quantified if possible): [e.g., "losing X hours per week to manual data entry"]
Cost of the problem: [dollar amount or calculation — even a rough estimate with stated assumptions]
Expected outcome with our solution: [specific improvement — e.g., "reduce time by 60%"]
Value calculation: [savings per year / revenue impact / risk reduction]
Payback period: [how quickly the investment is recouped]
Assumptions: [what numbers came from the prospect vs. our industry benchmarks]

Under 300 words. Every number must have a stated source or assumption. Buyers reject business cases with round numbers and no methodology — show your work.

Write an implementation timeline section for a proposal.

Product/service type: [brief description]
Typical implementation phases: [list the phases with expected duration each]
What the prospect needs to contribute in each phase: [their time/resources]
Key milestones and dates: [if known from conversation]
First 30 days post-launch focus: [what success looks like]

Format: visual timeline narrative, under 300 words. Acknowledge their concern about implementation complexity if they raised it. Include a "what we handle vs. what you handle" breakdown.

Write a follow-up email after sending a proposal.

Prospect name: [name]
Proposal sent: [date]
Key point from the proposal to emphasize: [one specific element relevant to their priority]
Next step: [what I want to happen — review call scheduled / questions answered / decision timeline]
Any open question from the last conversation to address: [if applicable]

Under 150 words. Do not ask "did you get a chance to look at it" — assume they have it and ask for the next specific step. Reference one specific detail from their situation to show this isn't a template follow-up.

Write customization notes for adapting a standard proposal to a specific prospect.

Standard proposal sections: [list your standard sections]
What I know about this prospect that changes the standard approach: [specific — their industry / company size / tech stack / stated priorities / decision criteria]
Sections that need significant customization: [list and why]
Prospect's exact language to incorporate: [phrases they used that should appear in the proposal]
What to remove or de-emphasize: [standard content that doesn't apply to this prospect]

Under 300 words. This is a prep document — use it before starting the proposal, not after.

Write a follow-up email immediately after a discovery call.

Prospect name: [name]
What we discussed: [3-4 key points — use their exact words where possible]
What they said their priority is: [specific]
Next step agreed on in the call: [what we said we'd do and when]
Something valuable to include: [resource / case study / specific data point relevant to their situation]

Under 200 words. Send within 2 hours of the call. Lead with a specific reference from the conversation — not "thanks for your time today" but a specific thing they said. Confirm the next step with the specific date and time.

Write a follow-up email after a product demo.

Prospect name: [name]
Features that resonated most (based on their reactions): [specific]
Their specific use case as they described it: [their words]
Open question or concern they raised: [address it directly]
Next step: [trial / pricing discussion / technical evaluation / stakeholder introduction]
Timeline they mentioned: [if they shared one]

Under 200 words. Tie the follow-up to specific moments from the demo. If they showed excitement about a particular feature, name it. If they raised a concern, address it directly instead of hoping they forgot.

Write a 4-email follow-up sequence for a prospect who has gone quiet after showing interest.

Context: prospect engaged (responded to outreach, took a call, or requested information) but has not responded to my last message.
Last contact: [date and what was discussed]
Their stated interest: [what they said they were trying to solve]

Write 4 emails spaced 4-7 days apart:
Email 1: Add value — a resource, data point, or insight relevant to their stated challenge.
Email 2: New angle — approach their challenge from a different perspective.
Email 3: Direct — acknowledge the silence, ask directly if the timing is wrong.
Email 4: The break-up — close the loop professionally, leave the door open.

Each email under 100 words. Subject lines for each included.

Write a re-engagement email for a deal that has stalled at a specific stage.

Prospect name: [name]
Deal stage: [e.g., waiting for budget approval / stuck in procurement / champion has gone quiet]
Time since last contact: [X weeks/months]
What I know about why it stalled: [your best assessment]
New angle or reason to re-engage: [something changed / their quarter ended / competitive intelligence / new capability]

Under 150 words. Do not reopen with "just checking in" — that's the worst follow-up. Lead with new information or a new perspective on their situation.

Write a re-engagement email for a closed-lost prospect, 6-12 months after the decision.

Prospect name: [name]
When they chose a competitor or decided not to buy: [approximate date]
Reason given for not choosing us (if known): [their stated objection]
What has changed since then: [product improvement / pricing change / their situation likely changed / their chosen solution may have failed to deliver]
What we're offering: [specific — not a rehash of the original pitch]

Under 150 words. Acknowledge the previous conversation briefly. Lead with what's different now. No hard feelings, no grudges — just a new conversation.

Write a response framework for the "it's too expensive" objection.

Our price: [$X / pricing model]
Competitor price (if known): [$Y]
What our price includes that competitors don't: [specific differences]
The prospect's stated business problem and its cost: [quantified if possible]
ROI or payback period: [specific]

Write a response that: acknowledges the concern without immediately discounting, reframes price as investment with specific ROI context, and offers a path forward (smaller scope / different package / phased implementation). Under 200 words. The goal is to advance the conversation, not win an argument.

Write a response to the objection "we're happy with what we currently have."

Their current solution: [named competitor or internal process]
Known limitation of their current approach: [based on research or the call]
What our differentiation offers that they may not have considered: [specific — not generic "we're better"]
Question to surface latent dissatisfaction: [a question that helps them identify a problem they haven't articulated]

Under 150 words. Don't argue that they're not happy — ask questions that help them discover a gap they haven't named yet. The objection means they haven't felt enough pain, not that there's no problem.

Write a response to the "not the right time" objection.

What they said about their timeline: [e.g., "let's revisit next quarter" / "we're in a budget freeze" / "we have too many projects right now"]
The cost of delay (if quantifiable): [what not solving this problem costs them per month/quarter]
What we can do in the meantime: [pilot / free trial / planning conversation / stakeholder introduction]
When to follow up: [specific date to put in writing]

Under 150 words. Acknowledge the timing reality — don't argue with it. Establish a specific follow-up date and make sure they agree to it before ending the conversation.

Write a response to help advance a deal when the prospect needs internal buy-in.

Prospect's role: [individual contributor / manager / director — someone who needs approval]
Who needs to be convinced: [their boss / committee / procurement / IT / finance]
What each stakeholder likely cares about: [brief — based on their role]
How I can help them sell internally: [specific support — executive briefing / ROI summary / case study / competitive comparison for procurement]

Write a response that: offers to help them build the internal case, surfaces who the key stakeholders are, and advances the deal by scheduling a next step that includes those stakeholders. Under 200 words.

Write a response to the "just send me some information" brush-off.

Context: [initial cold call / follow-up call / end of a meeting]
What they specifically asked for: [e.g., "send me your brochure" / "send me a case study" / "send me pricing"]
The real concern underneath the request: [usually: not interested / not the decision-maker / not ready to engage]
How to respond with a specific resource and maintain the conversation: [send something specific AND ask a question that requires a response]

Under 100 words. If you send information without a hook that requires a reply, you've lost the deal. Attach a specific, brief question to every "send me information" response.

Write a CRM note after a discovery call.

Prospect name: [name]
Company: [name]
Call date: [date]
Their stated problem (their exact words): [quote or close paraphrase]
Their desired outcome: [what they want to achieve]
Timeline and urgency: [when they need to solve this]
Budget context: [what they shared about budget / if nothing shared, note that]
Decision process: [who else is involved / how decisions get made]
Next step: [specific — what, who, when]
Deal stage to update: [stage]

Format: structured CRM note. Under 250 words. Written as if this deal resurfaces in 9 months and you need to re-engage — every important detail should be here.

Write a deal summary for advancing a deal to the next stage.

Prospect: [name, company]
Current stage: [stage]
Next stage: [stage]
Evidence that this deal is real: [what has happened — engaged stakeholders / agreed next step / defined problem / budget confirmed]
Risk factors: [what could kill this deal]
What needs to happen in the next 30 days: [specific]
Probability assessment: [X% — your honest estimate]

Format: internal deal review note, under 250 words. This is the note your manager reads in a pipeline review. Be specific and honest — over-inflating deal probability only hurts your forecast and credibility.

Write a deal briefing for handing off a prospect to another rep or account executive.

Prospect: [name, company, role]
Deal background: [how the relationship started and what's happened]
Their situation: [problem, context, urgency]
Relationship notes: [communication preferences / what they respond to / what they care about beyond the stated problem]
Deal status: [stage, timeline, decision process]
What the new rep needs to do first: [specific first action]
What NOT to do: [something that might damage the relationship]

Format: internal handoff document, under 350 words. Include one thing about the prospect as a person, not just as a deal — what do they care about, what's their communication style?

Write forecast commentary for a weekly pipeline review.

My current pipeline: [list deals by stage with expected close date and amount]
Deals closing this week: [list — confidence level for each]
Deals at risk: [list — and why each is at risk]
New opportunities added this week: [list]
My action items this week: [top 3 things that will move the pipeline]

Format: concise weekly pipeline commentary, under 300 words. Written for your manager in a pipeline review. Be specific about risks — a deal "at risk" with no explanation is useless to everyone.

Write a closed-won debrief note for a deal you just closed.

Deal: [company name]
Value: [$amount / deal type]
Time to close: [days from first contact to close]
Why they chose us (their words): [specific reasons they gave]
What almost lost the deal: [honest assessment]
What accelerated the deal: [specific — a champion / competitive pressure / a specific piece of content / a demo moment]
What I'd do differently: [one or two things]

Format: internal learning document, under 300 words. These notes are only valuable if they're honest. The "almost lost it" section is often the most useful part — write it carefully.

Write a closed-lost analysis for a deal you lost.

Deal: [company name, size]
Stage reached: [how far it got]
Stated reason for loss: [what the prospect said]
Real reason for loss (your honest assessment): [what you think actually happened]
What I could have done differently: [specific — in discovery / in the proposal / in handling a specific objection]
What this loss reveals about our product or positioning: [if anything]
What I'll do differently next time: [1-2 specific behaviors]

Format: internal learning document, under 300 words. The stated reason is rarely the real reason. The analysis is only valuable if you go deeper than "they chose a competitor."

Write a competitive loss analysis for a deal lost to a specific competitor.

Competitor: [name]
Prospect: [company]
Why they chose the competitor (stated): [their words]
Why they chose the competitor (your analysis): [deeper reasons — price / relationship / feature gap / timing]
What we did well in the competitive evaluation: [honest assessment]
Where we lost ground: [specific — a feature / a price point / a relationship / a demo failure]
Feedback to bring to product/marketing: [specific — what would have changed the outcome]

Under 300 words. One honest competitive loss analysis is worth more than ten optimistic pipeline reviews. Be specific about what the competitor did right, not just what we did wrong.

Write a monthly sales activity and results report.

Month: [month/year]
Quota: [$X]
Attainment: [$Y / X%]
Deals closed: [number and total value]
New pipeline created: [$value, number of opportunities]
Key activities: [calls / demos / proposals / events]
What drove the result: [specific — what worked]
What limited the result: [specific — what didn't work or what was missing]
Next month focus: [top 3 priorities]

Format: concise monthly report, under 350 words. Written for your manager and for yourself. Be specific about what drove the results — "I worked hard" is not an analysis.

Write an action plan for hitting quota from a deficit position.

Current date: [date]
Month/quarter end date: [date]
Current attainment: [$X / Y%]
Gap to close: [$amount]
Pipeline available to pull forward: [list deals that could close in the remaining time]
New activities that could generate near-term revenue: [specific — who to call / what offer to make / what urgency to create]
One thing I can do today: [specific first action]

Under 300 words. A quota deficit requires a specific action plan, not general effort. List the actual deals and activities. Be honest about what's realistic to close vs. what you're hoping for.

Write a customer expansion opportunity analysis.

Customer name: [name]
Current product/plan: [what they buy now]
Usage data or signals: [what you know about their usage — high adoption / new use cases / team growth]
Expansion opportunity: [upsell / cross-sell / new seat licenses / new product line]
Value to the customer of expanding: [specific — not "more features" but the business outcome they'd gain]
Timing rationale: [why now is the right time to have this conversation]
Opening for the conversation: [how to bring it up naturally]

Under 300 words. Expansion conversations that lead with customer value close faster than those that lead with new features. Write this analysis before the call, not after you've already pitched.