---
name: dev-team-satisfaction
description: >
  Value proposition module for CXO-level cold outreach built around a free
  AI & SDLC Health Check — a Typeform assessment that benchmarks an engineering
  team across SDLC maturity, AI tool adoption, and company-level automation,
  then delivers an automated personalised report.
  Use when campaign targets CTOs, CPOs, VPs of Engineering, or technical
  co-founders at scaling tech companies.
  Load via campaign-builder.md when value_proposition = dev-team-satisfaction.
---

# Value Prop: Dev Team Satisfaction (AI & SDLC Health Check)

---

## ① Concept

Cold outreach to CXO-level contacts offering a **free AI & SDLC Health Check** —
a 4-minute Typeform that benchmarks their engineering team across SDLC process
maturity, AI tool adoption, and company-level automation. The prospect fills in
the form and immediately receives an automated personalised report with a score
per section and top 3 recommendations.

This is not a pitch. It is a free diagnostic. The report delivers standalone
value — the prospect could act on it without ever speaking to Agilie. That
credibility gap is what earns the follow-up conversation.

---

## ② Offer mechanics

| Element | Detail |
|---|---|
| Format | Typeform — 15 questions across 3 sections, ~4 minutes |
| Output | Automated report: Level 1–4 score per section + top 3 recommendations |
| Cost | Free, no strings attached |
| Next step | Report delivered instantly → Agilie follows up 24–48h later to discuss findings |
| CTA URL | **[PLACEHOLDER — insert Typeform URL before launch]** |

**Report framing:** Positions Agilie as the author of the benchmark framework,
not as a vendor. Language: "Here's how your team compares to high-performing
engineering orgs we've worked with over 16 years."

---

## ③ Required campaign inputs

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

```
typeform_url:        URL of the AI & SDLC Health Check form
report_sender_name:  Name shown as sender of the follow-up email (e.g. "Sergey from Agilie")
booking_link:        Calendar link for the 30-min findings call (e.g. Calendly)
```

---

## ④ Smartlead sequence name slug

```
name_slug: DevTeamSatisfaction
```

Used in: `ICP_DevTeamSatisfaction_[campaign_type]_[YYYY-MM]`

---

## ⑤ Target persona

**Primary titles:** CTO, CPO, VP Engineering, VP of Engineering, Technical Co-founder, Head of Engineering
**Secondary:** COO or CEO at a tech-heavy SMB where the founder is technical

**Company profile:**
- Size: 20–200 employees
- Stage: Post-product-market-fit, scaling phase (Series A–B or bootstrapped equivalent)
- Tech profile: Has an in-house or mixed dev team; ships software as a core part of the business
- Verticals: FinTech, SaaS, Logistics, HealthTech, B2B platforms
- Geography: Rich (default)

**Psychographic — what this persona cares about:**
- Responsible for delivery quality — privately feels the gap between where the team
  is and where it should be, but hasn't had a structured way to measure it
- Has read about AI coding tools but isn't sure if the team is adopting them
  correctly or if it's actually improving anything
- Worried about technical debt and SDLC gaps slowing down new feature delivery
  as the team scales
- Values peer benchmarks — "how does our process compare to other engineering orgs?"
- Responds to expertise and data, not vendor pitches or "we'd love to help" language

---

## ⑥ Segment exclusions

Do NOT target:
- Pure services companies / agencies with no product of their own
- Companies with 50+ in-house developers (too mature, process likely covered)
- Companies already using Agilie
- Early-stage pre-PMF startups (no meaningful SDLC to assess yet)
- Non-technical founders where CTO is the first engineering hire (too early)

---

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

Observable signals that make the outreach feel timely and specific.

```
Signal 1: Posted 3+ engineering job listings in the last 30 days
Pattern:  "[Company] is scaling the engineering team fast —
           that pace usually surfaces process gaps before anyone notices."

Signal 2: LinkedIn post by CTO/CPO about AI tools, team productivity,
          or engineering culture
Pattern:  "Saw your post about [topic] — we built a benchmark
           that maps exactly this. Thought it might be worth 4 minutes."

Signal 3: Recently raised a funding round (Seed / Series A / Series B)
Pattern:  "Congrats on the [round] — scaling engineering post-raise is
           where most teams hit their first serious process ceiling."

Signal 4: Job posting mentions 'improve engineering processes',
          'AI adoption', 'DevOps', or 'platform engineering'
Pattern:  "Noticed [Company] is hiring for [role] — usually signals a
           process improvement push. We have a benchmark that might
           shortcut some of that work."

Signal 5: Company recently launched a new product or major feature
Pattern:  "[Product] launch caught my attention — post-launch is usually
           when SDLC debt becomes visible fastest."
```

Automation:
- Signals 1, 3, 4 → fully automatable via Apollo Hiring Intent + Apollo Signals
- Signal 2 → Apify LinkedIn Post Scraper + keyword filter (semi-automated)
- Signal 5 → Apify or Product Hunt monitoring (semi-automated)

---

## ⑧ Email hooks by touch point

### Email 1 — Hook (observation + offer)

```
[First name],

[One-sentence trigger signal observation — company-specific, not generic].
[One-sentence insight — what that usually means for a team at their stage].

We built a free AI & SDLC Health Check used by engineering leaders at scaling
[FinTech / SaaS / Logistics] companies — it benchmarks your team across
process maturity, AI tool adoption, and automation gaps in 4 minutes,
and gives you a personalised report immediately.

No call needed to get it: [TYPEFORM_URL]

[report_sender_name]
Agilie | agilie.com
```

Key rules:
- Do NOT open with "I" or "My name is"
- Do NOT mention Agilie services in Email 1
- Trigger signal observation must feel company-specific — not "many CTOs tell me..."
- End with a link, not a question — lower friction

### Email 2 — Proof

Core angle: Make the benchmark concrete. Show what the report reveals.

Key lines:
- "Most teams at your stage score Level 2 on CI/CD and Level 1 on AI tooling measurement."
- "The report shows exactly where the gap is and what Level 4 teams do differently."
- "16 years working with engineering orgs in FinTech and Logistics — the patterns repeat."

CTA: "Takes 4 minutes. Report lands in your inbox immediately: [TYPEFORM_URL]"

### Email 3 — Breakup

```
[First name],

Last one — if the timing is off I completely understand.

If [specific pain from Email 1] is still on the radar,
the benchmark is still there: [TYPEFORM_URL]

[report_sender_name]
```

Tone: Short, no pressure. Leave the door open without being needy.
Leave-open line: "The benchmark doesn't expire — happy to discuss the findings whenever it's useful."

---

## ⑨ Proof points

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

- "16 years working with engineering teams across FinTech, IoT, and Logistics —
  we've seen what Level 4 SDLC looks like, and what keeps teams stuck at Level 2."
- "Our Norwegian smart home client has been with us since 2013 —
  13 years of continuous delivery across a growing engineering team."
- "AI-augmented SDLC is part of how we work internally, not a service we sell —
  embedded in our planning, QA, and delivery processes."
- Benchmark data: "The most common gap we see: AI tools are in use but no one
  is measuring whether they're actually improving delivery."

---

## ⑩ What Agilie is NOT doing in this campaign

- Do NOT mention pricing or services in any of the 3 cold emails
- Do NOT use "we'd love to work with you" or "I wanted to reach out" language
- Do NOT list Agilie capabilities — the checklist demonstrates expertise without stating it
- DO position the report as peer-level insight, not a lead gen tool
- DO make the follow-up call optional — the report has standalone value
- The services conversation happens after the findings call, not before

---

## ⑪ Post-engagement follow-up

**Trigger:** Typeform submission webhook fires
**Delay:** 24 hours after automated report is sent
**Sender:** [report_sender_name] — same person as the cold sequence sender
**Goal:** Book a 30-minute findings call

```
Subject: Your AI & SDLC Health Check results — [Company]

[First name],

Thanks for taking the time to complete the Health Check.

Based on your scores, the area with the highest leverage for [Company] right now
is likely [Section with lowest score — SDLC / AI tooling / Automation].

Happy to spend 30 minutes walking through what that looks like in practice
for a team your size — no commitment, just a conversation.

[BOOKING_LINK]

[report_sender_name]
Agilie | agilie.com
```

**If no booking after 72h — one follow-up:**

```
Subject: Re: Your AI & SDLC Health Check results

[First name],

Just checking the report landed — sometimes it ends up in spam.

If you saw it and the timing isn't right, no problem at all.
The offer for a 30-min walkthrough stands whenever it's useful: [BOOKING_LINK]

[report_sender_name]
```