SaaS & Tech

Write a cold email to [FOUNDER NAME], technical founder of [COMPANY].

Context:
- They recently [SIGNAL: launched on Product Hunt / raised seed funding / posted on HN]
- Company stage: [STAGE: pre-seed / seed / Series A]
- Their product: [WHAT THEY BUILD]
- I help [TYPE OF COMPANIES] with [PROBLEM I SOLVE]

Tone: Technical peer, not salesy. Respect their time.

Rules:
- Subject line: 5 words max, no clickbait
- Opening: Reference the signal, show you did research
- Body: One specific way you could help, tied to their stage
- CTA: Low commitment (15-min call or async)
- Total length: Under 100 words
- No "hope this finds you well" or "I'm reaching out because"

Write a cold email to [NAME], VP of Engineering at [COMPANY].

Context:
- Company size: [EMPLOYEE COUNT]
- Their stack: [TECHNOLOGIES THEY USE]
- Signal: [SIGNAL: hiring engineers / scaling infrastructure / tech debt mentions]
- We help engineering teams with [PROBLEM]

Tone: Peer-to-peer, technical credibility matters.

Structure:
1. Hook: Reference something specific about their engineering challenges
2. Problem: One sentence on the pain they likely feel
3. Credibility: One proof point (customer result, not features)
4. CTA: Specific and low-friction

Rules:
- No buzzwords (leverage, synergy, cutting-edge)
- Mention specific tech if relevant
- Under 80 words

Write a cold email to [NAME], Product Manager at [COMPANY].

Context:
- They recently [SIGNAL: launched a new feature / posted about product challenges / hiring for PM role]
- Product area: [THEIR PRODUCT AREA]
- We help PMs with [YOUR VALUE PROP]
- Team size: [THEIR TEAM SIZE]

Tone: Fellow product person, empathetic to PM struggles.

Structure:
1. Hook: Something specific about their product work
2. Pain: One PM-specific challenge you solve
3. Proof: Quick metric from similar PM
4. CTA: "See how [Similar Company] did it?"

Rules:
- Under 75 words
- No feature lists
- Speak their language (roadmap, velocity, stakeholders)

Write a cold email to [NAME], CFO at [COMPANY] during budget planning season.

Context:
- Company revenue: [REVENUE RANGE]
- Fiscal year end: [MONTH]
- Signal: [SIGNAL: earnings call mention / LinkedIn post / job posting]
- We help finance teams [YOUR VALUE PROP]
- ROI we typically deliver: [ROI METRIC]

Tone: Financially literate, respect their time, data-driven.

Key angles to consider:
1. Budget planning = open to new line items
2. Show clear ROI timeline
3. Align with their fiscal planning cycle

Rules:
- Lead with a financial insight, not product pitch
- Include one specific number
- CTA tied to their planning timeline

Write a cold email to [NAME] at [COMPANY] who currently uses [COMPETITOR].

Context:
- Their current solution: [COMPETITOR NAME]
- How long they've used it: [IF KNOWN]
- Known pain points with competitor: [GAPS/ISSUES]
- Our key differentiator: [YOUR ADVANTAGE]
- Similar customer who switched: [REFERENCE CUSTOMER]

Tone: Respectful of their choice, not trash-talking competitor.

Strategy:
1. Acknowledge they have a solution (validates their decision)
2. Plant a seed about one specific limitation
3. Offer comparison value, not hard pitch
4. Make it safe to explore options

Rules:
- Never badmouth competitor directly
- Focus on what they might be missing
- Low-commitment CTA

Generate discovery questions for a technical buyer evaluating [YOUR PRODUCT TYPE].

Context:
- Buyer role: [TITLE: VP Eng / CTO / Tech Lead]
- Company stage: [STAGE]
- Known pain points: [WHAT YOU KNOW]
- Competitors they might be evaluating: [COMPETITORS]

Question categories needed:
1. Current state (how they do it today)
2. Pain quantification (time/cost/risk of current approach)
3. Decision process (who else is involved, timeline)
4. Technical requirements (integration, security, scale)
5. Success criteria (how they'll measure if it worked)

Format: 3 questions per category, ordered from easy to probing.
Include follow-up prompts for each question.

Generate discovery questions to qualify budget and timeline.

Context:
- Prospect company: [COMPANY]
- Your ACV: [DEAL SIZE]
- Typical sales cycle: [LENGTH]
- Champion role: [THEIR TITLE]

Generate questions for:
1. Budget discovery (without asking "what's your budget?")
2. Decision timeline reality check
3. Competing priorities that could delay
4. Approval process and stakeholders
5. Past purchase experiences (how they bought last tool)

Format each question with:
- The question itself
- Why you're asking (the intel you need)
- Follow-up if they're vague
- Red flag answers to watch for

Generate questions to map the buying committee.

Context:
- Deal size: [ACV]
- Prospect: [COMPANY NAME]
- Current contact: [NAME, TITLE]
- Your product affects: [DEPARTMENTS/ROLES IMPACTED]

Question categories:
1. Who else will be involved in this decision?
2. Who needs to approve budget at this level?
3. Who might block this internally? (IT, legal, procurement)
4. Who will be the day-to-day users?
5. Who has failed to buy something like this before? Why?

For each answer, provide:
- Natural way to ask without seeming interrogative
- How to position as helping them navigate internally
- When in the conversation to ask this

Help me respond to this objection from a technical buyer:

"We've already built something in-house that does this."

Context:
- My product: [YOUR PRODUCT]
- Their company size: [SIZE]
- Their likely in-house solution: [WHAT YOU THINK THEY BUILT]
- My key differentiator: [WHAT MAKES YOU BETTER]

Response framework needed:
1. Acknowledge their investment (don't dismiss it)
2. Curious questions to understand their solution's scope
3. Subtle wedge questions (maintenance burden, opportunity cost, feature gaps)
4. Bridge to your value (only if there's a real gap)

Tone: Respect their engineering effort. Never trash their work.
Goal: Understand if there's a real opportunity, not to "win" the objection.

Help me respond to: "We don't have budget for this right now."

Context:
- My product: [YOUR PRODUCT]
- Deal size: [ACV]
- Their company stage: [STAGE/SIZE]
- Value I provide: [KEY BENEFIT]
- Their fiscal year: [IF KNOWN]

Explore these angles:
1. Is this a priority problem? (If so, budget finds a way)
2. Reframe as cost of inaction (what's the cost of waiting?)
3. Creative pricing options (if applicable)
4. Plant seeds for next budget cycle
5. Find smaller entry point

Provide:
- 3 diagnostic questions to understand the real blocker
- 2 reframe responses
- 1 graceful exit that keeps door open
- Follow-up timing recommendation

Help me respond to: "Let me think about it and get back to you."

Context:
- Deal stage: [STAGE: post-demo / post-proposal / post-trial]
- What we covered: [LAST INTERACTION SUMMARY]
- Their apparent concerns: [IF ANY SURFACED]
- Their timeline mentioned: [IF ANY]
- Competition: [IF YOU KNOW]

This objection often masks:
- Unspoken concern they didn't raise
- Need to socialize internally
- Evaluating competitor
- Not a real priority
- You haven't earned the next step

Provide:
- 3 ways to gently probe what's really happening
- Questions to surface hidden objections
- How to offer help without being pushy
- Clear mutual action plan suggestion

Write an executive summary for a SaaS proposal.

Deal context:
- Prospect: [COMPANY NAME]
- Champion: [NAME, TITLE]
- Economic buyer: [NAME, TITLE]
- Problem they're solving: [PROBLEM]
- Our solution: [YOUR PRODUCT]
- Deal size: [ACV]
- Competition: [WHO ELSE THEY'RE EVALUATING]

Key wins from discovery:
- [PAIN POINT 1 + QUANTIFIED IMPACT]
- [PAIN POINT 2 + QUANTIFIED IMPACT]
- [PAIN POINT 3 + QUANTIFIED IMPACT]

Success metrics they mentioned:
- [METRIC 1]
- [METRIC 2]

Write a 200-word executive summary that:
1. Opens with their goal, not your product
2. Summarizes the problems you'll solve (in their words)
3. Previews the ROI case
4. Creates urgency without being pushy
5. Ends with a clear next step

Create the ROI/business case section for a SaaS proposal.

Deal context:
- Prospect: [COMPANY]
- Annual deal value: [ACV]
- Contract length: [MONTHS/YEARS]
- Implementation cost: [IF ANY]

Value drivers discovered:
- Time savings: [HOURS/FTEs SAVED]
- Revenue impact: [GROWTH/RETENTION IMPROVEMENT]
- Risk reduction: [COMPLIANCE/SECURITY BENEFITS]
- Cost reduction: [TOOLS CONSOLIDATED/COSTS AVOIDED]

Their current costs:
- Current solution cost: [IF KNOWN]
- Manual process cost: [TIME × SALARY]
- Opportunity cost: [DEALS LOST/DELAYED]

Build a business case that shows:
1. Year 1 ROI calculation
2. 3-year TCO comparison
3. Payback period
4. Risk-adjusted projections
5. Soft benefits (harder to quantify)

Format: Clear table + narrative explanation.

Write a follow-up email after a product demo.

Demo context:
- Attendees: [NAMES AND TITLES]
- Key features shown: [FEATURES DEMOED]
- Their biggest reactions: [WHAT EXCITED THEM]
- Questions they asked: [KEY QUESTIONS]
- Concerns raised: [OBJECTIONS/HESITATIONS]
- Agreed next step: [WHAT YOU SAID YOU'D DO]

Structure:
1. Thank + personalized observation (not generic)
2. Recap what resonated (in their words)
3. Address any open questions
4. Attach relevant resources
5. Clear CTA with specific date/time

Rules:
- Send within 2 hours of demo
- Under 150 words
- Include mutual action plan
- Don't re-pitch—you already demoed

Write a "break-up" email for a prospect who's gone dark.

Context:
- Last contact: [DATE]
- Previous touchpoints: [# OF FOLLOW-UPS SENT]
- Stage when they went dark: [STAGE]
- Last topic discussed: [TOPIC]
- Value they acknowledged: [WHAT THEY SAID THEY LIKED]

Write 3 versions:
1. Soft break-up (assumes they're busy)
2. Value-add break-up (shares useful resource)
3. Direct break-up (asks for a no)

For each version include:
- Subject line
- Body (under 50 words)
- The psychology behind why it works

Goal: Get a response (even if it's no) or permission to follow up later.