---
name: [vp-slug]
description: >
  Value proposition module for [one-line description of the offer].
  Use when campaign targets [persona] and the offer is [what you're giving them].
  Load via campaign-builder.md when value_proposition = [vp-slug].
---

# Value Prop: [Full Name]

---

## ① Concept (2–4 sentences)

What is the core offer? What problem does it solve for the prospect?
Why would a busy CXO/decision-maker care enough to respond?

---

## ② Offer mechanics

| Element | Detail |
|---|---|
| Format | [e.g. Typeform / PDF / Call / Tool / Report] |
| Output | [What the prospect receives] |
| Cost | [Free / Paid — be explicit] |
| Next step | [What happens after they engage] |
| CTA URL | **[PLACEHOLDER — insert URL before launch]** |

---

## ③ Required campaign inputs

> These inputs must be provided when running campaign-builder for this VP.
> If missing, flag as [PLACEHOLDER] and proceed.

```
[vp_specific_input_1]:   [description — e.g. typeform_url: link to the form]
[vp_specific_input_2]:   [description — e.g. report_sender_name: name shown on report email]
[vp_specific_input_3]:   [description — or remove this line if only 2 inputs needed]
```

---

## ④ Smartlead sequence name slug

```
name_slug: [CamelCase — e.g. DevTeamSatisfaction, TechAudit, ReferralProgram]
```

This value is used in: `ICP_[name_slug]_[campaign_type]_[YYYY-MM]`

---

## ⑤ Target persona

**Primary title(s):** [e.g. CTO, CPO, VP Engineering, Technical Co-founder]
**Secondary (if any):** [e.g. COO at tech-heavy SMB]

**Company profile:**
- Size: [headcount range]
- Stage: [e.g. post-PMF scaling, Series A–C, enterprise]
- Tech profile: [e.g. has in-house dev team, uses X stack]
- Verticals: [e.g. FinTech, SaaS, Logistics — list from Agilie core verticals]
- Geography: [Rich / specific subset]

**Psychographic — what this persona cares about:**
- [Pain 1 — what keeps them up at night]
- [Pain 2]
- [What they're proud of / don't want to admit is broken]
- [What they respond to — data? peers? vision? efficiency?]

---

## ⑥ Segment exclusions

Do NOT target:
- [e.g. companies with 50+ in-house developers]
- [e.g. pure services companies with no product]
- [e.g. companies that already use Agilie]

---

## ⑦ Trigger signals (use for Email 1 personalisation)

Observable signals that make the outreach feel timely and specific.
Each signal should pair with a one-line observation pattern.

```
Signal 1: [Observable event — e.g. "Posted 3+ engineering job listings in 30 days"]
Pattern:  "[Company] is scaling fast — that pace usually surfaces [pain]."

Signal 2: [e.g. "LinkedIn post about AI tools or team productivity"]
Pattern:  "Saw your post about [topic] — we built a benchmark that maps exactly this."

Signal 3: [e.g. "Recently raised funding"]
Pattern:  "Congrats on the [round] — scaling engineering post-raise is where most teams hit [pain]."

Signal 4: [e.g. "Job posting mentions 'improve processes' or 'DevOps'"]
Pattern:  "Noticed [Company] is hiring for [role] — usually signals a [pain] push."
```

---

## ⑧ Email hooks by touch point

### Email 1 — Hook (observation + offer)
Core pattern:
```
[First name],

[One-sentence trigger signal observation].
[One-sentence insight — what that usually means for a company like theirs].

[Offer — what you're giving them and why it's worth 3 minutes].

[Soft CTA — no pressure, just a link or a question].

[Your name]
```

Key rules:
- Do NOT open with "I" or "My name is"
- Do NOT mention Agilie services in Email 1
- Observation must be company-specific, not generic

### Email 2 — Proof
Core angle: [one concrete proof point, benchmark, or case study to use here]
Key line: [the most compelling single sentence for this email]

### Email 3 / CTA email
Core CTA: [exact ask — e.g. "Fill in the checklist: [URL]" or "15 minutes this week?"]
Fallback if no reply: [what to say if they've already opened but not acted]

### Breakup email
Tone: [short and human — e.g. "Closing the loop" / "Last one, I promise"]
Leave-open line: [one sentence that keeps the door open without being needy]

---

## ⑨ Proof points

Pull from `global/agilie.md` for company-level proof.
Add VP-specific proof points here:

- [Specific result or case study relevant to this value prop]
- [Benchmark or data point — e.g. "teams that implement X typically see Y"]
- [Social proof — client type, duration, outcome]

---

## ⑩ What Agilie is NOT doing in this campaign

Be explicit about what should NOT appear in the cold sequence:

- Do NOT mention [X] in the first [N] emails
- Do NOT use [tone / phrase type] language
- DO position as [framing that works for this VP]
- The services conversation happens [when — e.g. after the report, after the call]

---

## ⑪ Post-engagement follow-up (if applicable)

If there's a trigger after the prospect engages (e.g. fills Typeform, downloads PDF,
clicks a link), define the follow-up here:

**Trigger:** [what event fires the follow-up]
**Delay:** [X hours after trigger]
**Sender:** [name and email]
**Goal:** [move to call / send report / schedule demo]

```
Subject: [subject line]

[Body template]
```