---
name: personalized-outreach-sequence
description: Drafts a short, evidence-based sales outreach sequence from account research, value proposition, proof points, and channel constraints. Use for personalised prospecting, outbound sequence drafting, account-based messaging, first-touch copy, or follow-up message variants.
license: Apache-2.0
metadata:
  adlass.categories: "sales-crm/follow-ups, sales-crm/lead-research"
  adlass.industries: ""
  adlass.tags: "outreach, personalization, prospecting, messaging, sales, sequence"
  adlass.adaptation: "reference-doc"
  adlass.source: "n8n:3561, n8n:4539, original"
  adlass.version: "1"
---

# Personalized outreach sequence

## Purpose

Draft a concise sequence that earns relevance from verified account context and a clear value hypothesis. Produce variants for review while avoiding invented familiarity, unsupported claims, or automatic delivery.

## Scope

Target account and role, researched trigger, customer problem hypothesis, value proposition, proof point, message sequence, channel, tone, length, and objection preparation.

**Excluded:** sending messages, scraping private profiles, fabricating personalisation, and guaranteeing response.

## Data basis

- Account and contact research in scope.
- Approved offer, proof points, customer references, and tone guide.
- Channel and compliance constraints supplied as inputs or scope documents.

## Result

A 3–5 touch draft sequence, a variant sheet, and an objection-preparation note.

## Quality criteria

- Each personalised claim cites account evidence.
- Every message has one clear purpose and low-friction call to action.
- Length, tone, and channel rules are checked.
- No message implies a relationship or fact not supported by sources.
- Variants differ in angle, not factual accuracy.

## Instructions

Lead with the prospect's likely context, not product features. Use one evidence-backed hypothesis per sequence. Keep uncertainty visible in internal notes, not in awkward claims to the prospect. Do not use sensitive or personal data unless explicitly approved. Draft follow-ups with genuinely different value angles.

## Adapt before use
Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

- Add the offer, proof points, tone guide, and permitted channels.
- Define length, cadence labels, and compliance constraints.
- Add approved examples if a house style is required.