---
name: Growth Engineer Positioning
slug: growth-engineer-positioning
description: The Growth Engineer offer, ICP, voice, and what NOT to claim in cold outbound. Used by every outbound agent.
category: outbound
---

# Growth Engineer — positioning

## What we sell, in one sentence

Growth Engineer builds AI agents into B2B tech teams' existing GTM stack (HubSpot, Lemlist, Salesforce, etc.) so the boring rep work — sourcing, qualification, sequence drafting, follow-up logging, CRM hygiene — moves out of the AE's hands and reps spend their time on calls and replies.

## What we do NOT claim in cold outbound

This is critical. The previous draft of this skill file had several over-promises that need to stay out of cold emails:

- ❌ "First agent live in 7 days" — over-promise, leave timeline for the call
- ❌ "$5k/mo starting" — no pricing in cold emails, decide on call
- ❌ "Replace your Clay → Apollo → Lemlist stack" — too declarative, sounds like vendor pitch
- ❌ "Run a 5-rep team like 50" / "1 rep does the work of 5" — no multiplier claims
- ❌ Specific reply-rate or pipeline-lift percentages — no public case study yet
- ❌ "Fully autonomous" — we're approval-loop by default
- ❌ Made-up URLs to writeups (`/agents/sourcing` etc.) that don't yet have content
- ❌ Naming the past employer ("dealroom") in email body unless explicitly approved per campaign

## What we CAN say (defensible)

- "I build AI agents into B2B GTM stacks (sourcing, qualification, sequence drafting, etc.)"
- "I was head of growth at a Series A B2B before this, built the same loop for our team"
- "Last B2B/VP I built one for, the AEs went from maintaining 3 enrichment workflows to zero"
- "Runs inside HubSpot and Lemlist, reps only see qualified leads already sequenced"
- "Reps spend their time on calls and replies, not the prep"
- "Agent does the research, qualifies the lead, drafts the sequence, pushes it to Lemlist"

These are all describable workflow changes — defensible on a follow-up call without case-study links.

## ICP — who we sell to

- B2B tech / SaaS, has an active sales motion (book-a-demo, AE-led)
- 10–500 employees (sweet spot 25–150)
- Recently funded (Seed → Series C) — has GTM budget, growth pressure
- English-primary market (US / UK / EU / APAC English)

## Anti-ICP — disqualify

- Pure consumer / B2C
- Agencies, consultancies, dev shops
- Pre-revenue / stealth (no GTM yet)
- Mega-corps 1000+ headcount (procurement hell)
- Pure self-serve PLG with no sales team
- Marketplace plays with no AE motion

## Persona angles

**Founder / CEO** — strategic / hire-replacement angle.
- Concern: "When do I need to hire a Head of Growth?"
- Tell them: I build the workflows that Head of Growth would build, before you hire one.
- See `founder-outreach` skill file for the canonical sequence.

**VP Sales / CRO / Head of Growth / RevOps** — workflow-pain angle.
- Concern: "My AEs are spending half their week on enrichment + drafting instead of selling."
- Tell them: I move that work out of the AE's hands. Reps only see qualified, sequenced leads.
- See `sales-leader-outreach` skill file for the canonical sequence.

## Voice / vibe

- **Peer-to-peer.** Like an operator who's done it talking to other operators. Not a vendor pitching.
- **Normal grammar and capitalization.** Use "I" properly. Don't go all-lowercase.
- **No buzzwords.** No "AI-powered", "next-gen", "synergy", "leverage", "transform", "unlock".
- **Show, don't tell.** "The agent does the research and drafting" beats "AI-powered automation".
- **Short.** Email 1 under 80 words. Email 2 under 100. Email 3 under 30.

## URLs allowed in cold emails

- `https://growthengineer.ai` — the homepage / offer
- `https://growthengineer.ai/agents` — the public agent showcase index (only if it has real content)
- A meeting link from `GE_MEETING_LINK` env var, if set, used for "book intro call" CTAs

**Never invent URLs.** Specifically: do not reference `/agents/sourcing` as a "writeup" until that page actually has shipped, real content. If you don't have a relevant link, don't include one.

## Sender identity

- Sign emails as "Peter" (first name only).
- No title in the signature. No "VP of GTM at Growth Engineer" — that's vendor-coded.
- Sender email comes from `GE_SENDER_EMAIL` env var.

## Proof points (use sparingly, only when defensible)

These are real, measured, and okay to reference:

- "I was head of growth at a Series A B2B before this" -- verifiable, defensible
- "Last B2B I built agents for, we processed 2,600+ leads in 8 days and booked 68 meetings"
- "The agents ran across 30 campaigns and 4 reps, 3,800+ emails sent"
- "AEs went from maintaining 3 enrichment workflows to zero"
- "43 seconds average to process a lead from form fill to sequenced in Lemlist"
- "Happy to send a one-pager on what I'd build first" -- we have the PDF deck

Do NOT cite:
- Named customer logos (name is redacted for now)
- Specific revenue numbers from the client
- Exaggerated multiplier claims ("10x pipeline")
- Anything you can't back up on a follow-up call