CTA designer

CTA Designer — Permissionless Value Promise (PVP)

The core idea

Most outreach dies at the CTA. "Would you be open to a 30-minute call?" is high friction, seller-centric, and creates a binary lose/lose: the prospect either ignores it or commits to something they don't want yet.

A Permissionless Value Promise (PVP) flips this. The CTA itself delivers standalone value — an insight, a resource, a benchmark, a question — that the prospect finds genuinely useful *before* buying anything. They reply because they're curious, not because you pressured them.

A good PVP CTA:

• Gives something useful with no strings attached
• Doesn't mention your product or pitch anything
• Implies no obligation ("happy to share if useful")
• Is specific to their context (their industry, role, trigger, or pain)
• Requires a simple yes or short reply — not a calendar commitment

Step 1 — Gather context

Before generating CTAs, check the conversation for any existing context:

• ICP / company type: industry, size, growth stage
• Persona: role, seniority, their core pain
• Trigger: recent event (funding, hiring, tech change, job change, etc.)
• Your offer: what problem you solve and how
• Channel: email, LinkedIn DM, voice note

If critical context is missing (especially the persona's pain or your offer), ask 1–2 targeted questions. Never generate generic CTAs — specificity is what makes PVPs work.

Step 2 — Generate 5 PVP CTAs

Produce 5 CTAs across different angles. For each, write:

• The CTA itself (ready to paste into an email/message)
• Type (see below)
• Friction (🟢 Low / 🟡 Medium)
• Why it works (1 sentence)

Aim for at least 3 with 🟢 Low friction. Never propose a "book a call" CTA — that can come *after* the reply.

---

CTA Types

1. Insight CTA

You share a specific, public observation about their company or industry and offer to send a deeper analysis.

> "I noticed [Company] has been [expanding into X / hiring heavily for Y / doing Z]. Put together a quick breakdown of how similar companies are handling [related pain]. Happy to forward it — useful or not?"

Works because: it's already partly personalized, they feel seen, and the ask is a single "yes."

---

2. Benchmark CTA

Offer a comparison to peers — everyone wants to know how they stack up.

> "We've been tracking [metric] across [industry/segment]. Companies like [Company] are typically sitting around [X]. Curious how you compare — want me to share the full breakdown?"

Works because: benchmarks create instant relevance. No one ignores "how do you compare to your competitors?"

---

3. Resource CTA

Offer a specific, named asset tied to their pain — not a generic "guide" but something that sounds tangible and pre-built.

> "I put together a [quick checklist / one-pager / list of 5 templates] on [specific pain point] — built it from talking to [X type of companies]. Want me to send it over?"

Works because: the asset exists, it's theirs to keep, no obligation implied. The specificity of the asset signals real expertise.

---

4. Trigger-Based CTA

Use a buying signal (recent funding, new hire, product launch, tech change) as the hook and offer something contextually relevant.

> "Saw [Company] just [raised / launched / expanded into X]. When that happens, [related challenge] tends to come up. Put together a short playbook on how [similar companies] navigated it — worth a send?"

Works because: it's timely, it shows you did your homework, and the resource maps directly to what they're experiencing right now.

---

5. Diagnostic Question CTA

Instead of offering something, ask one sharp question that surfaces the pain — and signals you know their world.

> "Quick question — are you currently [doing X to track / measuring Y / handling Z manually]? Reason I ask is most [roles] I speak with tell me [that's where things break down]."

Works because: it makes *them* think about the pain. If the answer is "no" or "it's messy," they reply. And the reply *is* the conversation.

---

Step 3 — Prioritization logic

After generating the 5 options, recommend the top 1–2 based on context:

| Situation | Best type | |---|---| | Strong buying trigger available | Trigger-Based | | Prospect is data-driven (ops, finance, analytics) | Benchmark | | Persona deals with a concrete, recurring problem | Resource | | You know their specific company context well | Insight | | You want to qualify before offering anything | Diagnostic Question | | LinkedIn DM (shorter = better) | Diagnostic Question or Trigger-Based | | Cold email step 1 | Insight or Benchmark | | Follow-up step 3+ | Resource (justify why you're back) |

Step 4 — Sequence fit

CTAs should evolve across a sequence. If the user is building a multi-step campaign, suggest:

• Step 1: Insight or Benchmark (establish relevance)
• Step 2: Resource (add value, reinforce expertise)
• Step 3: Diagnostic Question (if no reply — flip the angle, make them think)
• Step 4+: Soft social proof or direct ask for 15 min (only once trust is built)

Never use the same CTA type twice in a row.

Quality bar

A PVP CTA passes if:

• ✅ The prospect could use the insight/resource even if they never buy from you
• ✅ Your product is not mentioned
• ✅ The ask requires a one-word or one-sentence reply
• ✅ It's specific enough that it couldn't be sent to 1,000 random people
• ✅ There's no implied urgency or pressure

If a CTA fails any of these, rewrite it before presenting it.