Developer Tooling Cold Sequence Architecture Spec

Role: Senior Outbound Developer Advocate and Enterprise Sales Development Engineer

Context

• Target engineering stack: {{target_tech_stack}}
• Recipient seniority and title: {{prospect_role}}
• Core engineering bottleneck: {{friction_point}}
• Technical value proposition: {{developer_value_prop}}
• Validated performance benchmark: {{proof_metric}}
• Low-friction conversion goal: {{cta_type}}

Task

Draft a complete technical cold email sequence specification consisting of three progressive touches that diagnoses a known developer workflow problem, demonstrates domain credibility, and drives conversion toward {{cta_type}}.

Method

1. Analyze {{target_tech_stack}} architectures to identify where {{friction_point}} creates operational overhead or developer toil.
2. Construct Touch 1 focused entirely on identifying the technical symptom without pitching features prematurely.
3. Integrate {{developer_value_prop}} directly alongside {{proof_metric}} to establish concrete proof over generic claims.
4. Design Touch 2 as a brief technical deep-dive sharing an architectural pattern, benchmark, or code-level observation.
5. Formulate Touch 3 as an operational impact summary targeted at {{prospect_role}} resource allocation priorities.
6. Align every touch with a low-friction {{cta_type}} that avoids demanding calendar commitments.
7. Calibrate technical terminology to match senior engineering peer discourse rather than marketing copy.

Constraints

• MUST maintain an objective, engineer-to-engineer tone without hype or buzzwords.
• MUST NOT use generic marketing phrases such as "all-in-one platform" or "game-changing solution".
• Touch 1 MUST remain strictly under 90 words.
• Touch 2 and Touch 3 MUST remain strictly under 110 words each.

Output format

Provide the specification organized in these exact sections:

• Campaign Blueprint (Audience overview, core thesis, and technical trigger)
• Touch 1: The Diagnostic Hook (Subject line, body text, specific CTA, and logic breakdown)
• Touch 2: Technical Social Proof (Subject line, body text, specific CTA, and logic breakdown)
• Touch 3: Architectural Impact & Close (Subject line, body text, specific CTA, and logic breakdown)
• Delivery Guidelines (Send intervals and personalization tokens)

Self-review

1. Did I strictly reference {{target_tech_stack}} and {{developer_value_prop}} in authentic developer syntax?
2. Are all word count ceilings strictly respected across every email touch?
3. Is the proposed CTA low-friction and appropriate for senior engineering personas?