@agentled/cli/skills/agentled/references/outreach-and-scale.md

CLI for Agentled — manage workflows, apps, and knowledge from the command line. Zero context-window cost for AI agents.

# Outreach Scale, Segmentation & Discovery Questions

> Loaded on demand from the Agentled skill. Read this for any outbound, sales,
> investor, founder, or lead-generation workflow — classify the motion before
> designing.

## What to ask — and what not to ask

After orienting on the workspace, ask **at most three to five** targeted questions. Focus only on what the workspace inspection cannot answer.

**Good questions:**
- "What is the primary goal: source more paying leads, run each event smoothly, or report pipeline health?"
- "Where is the bottleneck today: finding leads, getting replies, converting to paid, or operational follow-up?"
- "What is the system of record for payments/bookings right now: Stripe webhook, a booking page, a manual form, or a KG list?"
- "Which actions must be approval-gated: customer emails, status changes, or all customer-facing messages?"
- "What success metric should this optimize: conversions per week, leads contacted, confirmations, fill rate, or operator time saved?"

**Do not ask:**
- Step type names, app action names, schema syntax, or implementation details — discover these from the workspace and CLI.
- Every possible future integration question before the first useful slice is designed.
- Anything answerable by running `agentled workspace inspect`.

## Outreach scale and segmentation

For outbound, sales, investor, founder, or lead-generation workflows, classify the motion before designing the workflow. See `docs/OUTREACH_SCALE_GUIDANCE.md`.

**Core diagnostic:**
- PCPL = prospects contacted / positive replies over the last 30 days. PCPL at or below 250 is a scalable winner; above 250 means diagnose deliverability, then copy, then offer-audience match.
- Daily volume = last 30 days sent / 22 working days.
- TAM = total reachable prospects in the CRM, KG list, enrichment tool, or target account universe.
- Reply ops = whether positive replies are handled quickly and followed up persistently.

**Tier guidance:**
- Tier 1 (~100/day, a few thousand prospects): enrich every account, route by strongest signal, use high-touch multi-channel outreach. This is the default for most small Agentled Ops / AngelHive-style motions.
- Tier 2 (~1,000/day, 50K-100K prospects): split into top 200-500 home-run accounts with Tier 1 treatment plus segmented automation for the long tail.
- Tier 3 (~10K/day, hundreds of thousands): test angle x offer x segment, generate script variations, keep tests running in parallel, and track PCPL per combination.
- Tier 4 (50K-100K/day, millions): require provider segmentation, live monitoring, sender reserve capacity, hourly testing cadence, and reply-handling SLAs before increasing volume.

**Workflow implications:**
- Small TAM problems are usually segmentation and signal-enrichment problems, not copy-only problems.
- Store `outreachAngle`, `offer`, `segment`, `campaignVariant`, `channelUsed`, `sender`, `contactedAt`, `replyStatus`, `meetingStatus`, and `positiveReplyAt` when the KG schema allows it.
- Configure business metrics for prospects contacted, positive replies, PCPL, meetings/bookings/paid confirmations, bounce/failed-send count, and segment/angle performance. These are `analyticsConfig` business metrics, not ROI assumptions.
- Literal PCPL should use `type: "ratio"` with `ratioMode: "raw"`. Use the default percentage ratio behavior for rates such as `positive_replies / prospects_contacted`.