---
# === IDENTITY ===
id: consulting/recipes/signal-stack-engagement-playbook/2026
canonical_question: "How do you run a Signal Stack consulting engagement from audit to flywheel activation?"
aliases:
  - "Signal Stack engagement lifecycle end to end"
  - "Intent signal consulting project plan"
  - "How to scope and deliver a Signal Stack vertical intelligence engagement"
entity_type: execution_recipe
domain: consulting > recipes > Signal Stack Engagement Playbook
region: global
jurisdiction: global
temporal_scope: 2026-2027

# === VERIFICATION ===
last_verified: 2026-03-29
confidence: 0.85
version: 1.0
first_published: 2026-03-29

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: "Initial release — Signal Stack methodology v1.0"
  next_review: 2026-09-25
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Data sources must be publicly accessible or licensed — no scraping behind authentication without legal sign-off"
  - "LLM classification requires human-in-the-loop validation for first 100 dossiers per vertical"
  - "No platform extraction until 3 paying customers in vertical #1 — hard gate"
  - "GDPR/PECR/CAN-SPAM compliance mandatory before any outreach delivery"
  - "Minimum viable pilot: 10 dossiers/week for 4 weeks — shorter pilots produce unreliable conversion data"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User only needs the signal audit phase"
    use_instead: "consulting/recipes/signal-source-audit/2026"
  - condition: "User only needs the taxonomy workshop"
    use_instead: "consulting/recipes/signal-taxonomy-workshop/2026"
  - condition: "User only needs the technical MVP build"
    use_instead: "consulting/recipes/mvp-pipeline-build/2026"
  - condition: "User only needs to run a pilot"
    use_instead: "consulting/recipes/pilot-execution-playbook/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: target_vertical
    question: "Which industry vertical is the client targeting?"
    type: text
  - key: engagement_scope
    question: "What is the engagement scope?"
    type: choice
    options: ["signal audit only", "audit + taxonomy + MVP", "full lifecycle (audit to flywheel)", "platform extraction (post-vertical #1)"]
  - key: data_budget
    question: "What is the monthly budget for data sources?"
    type: choice
    options: ["$0 (public data only)", "$500-$2K/month", "$2K-$5K/month", "$5K+/month"]
  - key: sales_team_size
    question: "How many salespeople will consume the dossiers?"
    type: choice
    options: ["1-3 (founder-led)", "4-10 (small team)", "10-25 (mid-market)", "25+ (enterprise)"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Target vertical definition"
      source: "client/strategy"
      format: "document"
    - name: "Current sales process baseline"
      source: "client/sales"
      format: "spreadsheet"
    - name: "CRM export with conversion metrics"
      source: "client/CRM"
      format: "CSV"

  outputs:
    - name: "Signal Audit Report"
      format: "document"
      description: "Scored inventory of all available signal sources for the target vertical"
    - name: "Signal Taxonomy"
      format: "JSON schema + document"
      description: "Hierarchical classification of intent signals with scoring weights"
    - name: "MVP Pipeline"
      format: "deployed code + cron schedule"
      description: "Functional data pipeline producing enriched dossiers"
    - name: "Pilot Results Report"
      format: "PDF + dashboard"
      description: "Conversion metrics, taxonomy refinements, ROI calculation"
    - name: "Platform Architecture"
      format: "technical specification"
      description: "Reusable engine design separating generic from vertical-specific components"

  tools_required:
    - name: "Python + LLM API"
      purpose: "Signal classification and dossier generation"
      tier: "paid"
      cost: "$200-$500/month (API costs)"
      alternatives: ["Claude API", "GPT-4 API", "Local LLM (Llama)"]
    - name: "Clearbit/Apollo"
      purpose: "Company and contact enrichment"
      tier: "paid"
      cost: "$99-$499/month"
      alternatives: ["Hunter.io", "ZoomInfo", "manual LinkedIn research"]
    - name: "Cron scheduler"
      purpose: "Automated daily data pulls"
      tier: "free"
      cost: "$0"
      alternatives: ["GitHub Actions", "Railway cron", "AWS EventBridge"]

  credentials_needed:
    - service: "LLM API"
      type: "API key"
      where_to_get: "https://console.anthropic.com or https://platform.openai.com"
      free_tier_limits: "Varies — budget $200-$500/month for classification volume"
    - service: "Enrichment API"
      type: "API key"
      where_to_get: "https://clearbit.com or https://apollo.io"
      free_tier_limits: "50-100 lookups/month on free tiers"

  estimated_duration: "12-20 weeks (full lifecycle)"
  estimated_cost: "$15K-$40K (consulting) + $500-$2K/month (data + compute)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/consulting/recipes/signal-stack-engagement-playbook/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-29)"

# === RELATED UNITS ===
related_kos:
  depends_on: []
  feeds_into:
    - id: "consulting/recipes/platform-extraction/2026"
      label: "Platform extraction after vertical #1 succeeds"
  related_to:
    - id: "consulting/recipes/signal-source-audit/2026"
      label: "Signal audit sub-recipe (Phase 1)"
    - id: "consulting/recipes/signal-taxonomy-workshop/2026"
      label: "Taxonomy workshop sub-recipe (Phase 2)"
    - id: "consulting/recipes/mvp-pipeline-build/2026"
      label: "MVP pipeline build sub-recipe (Phase 3)"
    - id: "consulting/recipes/pilot-execution-playbook/2026"
      label: "Pilot execution sub-recipe (Phase 4)"
    - id: "consulting/recipes/vertical-launch-checklist/2026"
      label: "New vertical launch checklist (Phase 6+)"

# === SOURCES ===
sources:
  - id: src1
    title: "Predictable Revenue"
    author: Ross, A. & Tyler, M.
    url: https://predictablerevenue.com/book
    type: industry_report
    published: 2011-08-01
    reliability: high
  - id: src2
    title: "The Lean Startup"
    author: Ries, E.
    url: https://theleanstartup.com/
    type: industry_report
    published: 2011-09-13
    reliability: authoritative
  - id: src3
    title: "Crossing the Chasm"
    author: Moore, G.A.
    url: https://www.harpercollins.com/products/crossing-the-chasm-geoffrey-a-moore
    type: industry_report
    published: 2014-01-28
    reliability: authoritative
  - id: src4
    title: "Platform Revolution"
    author: Parker, G., Van Alstyne, M. & Choudary, S.
    url: https://platformrevolution.com/
    type: academic_paper
    published: 2016-03-28
    reliability: high
  - id: src5
    title: "Obviously Awesome — Product Positioning"
    author: Dunford, A.
    url: https://www.aprildunford.com/obviously-awesome
    type: industry_report
    published: 2019-05-01
    reliability: high
---

# Signal Stack Engagement Playbook

## Purpose

This recipe executes the full Signal Stack consulting lifecycle: from identifying raw intent signals in a target industry through building an automated intelligence pipeline that converts those signals into qualified sales dossiers. The end state is a self-reinforcing flywheel where each delivered dossier generates feedback data that improves signal classification accuracy. [src1, src2]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **Target vertical** defined with at least 1,000 addressable companies
- [ ] **Sales baseline** available — current conversion rates, average deal size, sales cycle length
- [ ] **CRM access** with historical conversion data for at least 6 months
- [ ] **Budget** confirmed for data sources ($500-$2K/month) and LLM API costs ($200-$500/month)
- [ ] **Sales team** identified who will consume and act on delivered dossiers

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. Violating these = broken output or legal risk. -->

- All data sources must be publicly accessible or properly licensed. No scraping behind authentication without explicit legal agreement. [src2]
- Human-in-the-loop validation required for first 100 dossiers per vertical — no fully automated delivery before validation.
- No platform extraction work until 3 paying customers confirm value in vertical #1. This is a hard gate. [src3]
- GDPR, PECR, and CAN-SPAM compliance mandatory before any outreach delivery begins.
- Minimum viable pilot: 10 dossiers/week for 4 consecutive weeks. Shorter pilots lack statistical significance.

## Tool Selection Decision

```
Which path?
├── Client has existing sales data + CRM
│   └── PATH A: Data-enriched pipeline — CRM integration, enrichment APIs, automated scoring
├── Client has target vertical but no CRM data
│   └── PATH B: Signal-first pipeline — public data only, manual enrichment, build CRM from scratch
├── Client needs multiple verticals simultaneously
│   └── PATH C: Platform-first — only if 3+ paying customers already exist in vertical #1
└── Client unsure about vertical selection
    └── PATH D: Discovery engagement — audit + taxonomy + viability scoring before any build
```

| Path | Tools | Cost | Speed | Output Quality |
|------|-------|------|-------|---------------|
| A: Data-enriched | CRM + Clearbit/Apollo + LLM | $1K-$3K/month | 8-12 weeks | Excellent — personalized, scored |
| B: Signal-first | Public data + LLM + manual | $200-$500/month | 10-16 weeks | Good — requires manual enrichment |
| C: Platform-first | Reusable engine + config | $2K-$5K/month | 4-6 weeks per vertical | Excellent — scalable |
| D: Discovery | Research + workshops only | $0-$500 | 3-4 weeks | Assessment only — no pipeline |

## Execution Flow

### Phase 1: Signal Audit (Weeks 1-2)

**Duration**: 5-10 days
**Tool**: Web research + structured scoring framework

Execute full signal source audit for the target vertical. See [Signal Source Audit](/consulting/recipes/signal-source-audit/2026) for detailed sub-recipe.

Inventory every available data source: regulatory databases, behavioral signals (job postings, DNS changes, review patterns), visual signals (satellite/street imagery if applicable), and unstructured media. Score each source on accessibility (1-5), cost (1-5), refresh rate (1-5), and signal-to-noise ratio (1-5). [src1]

**Verify**: Signal audit report delivered with minimum 15 scored sources across 3+ signal categories.
**If failed**: Vertical may have insufficient signal density. Run viability scoring before proceeding — if total weighted score < 12/20, recommend alternative vertical.

### Phase 2: Taxonomy Workshop (Weeks 2-3)

**Duration**: 2 days (workshop) + 3 days (validation)
**Tool**: Workshop facilitation + live data testing

Execute signal taxonomy workshop. See [Signal Taxonomy Workshop](/consulting/recipes/signal-taxonomy-workshop/2026) for detailed sub-recipe.

Day 1: domain expert interviews, data source deep-dives, trigger event brainstorming. Day 2: signal strength scoring, false positive threshold calibration, compound signal design, taxonomy validation against live data samples. [src5]

**Verify**: Taxonomy document with weighted scoring model validated against at least 50 real-world examples. False positive rate < 30% on test set.
**If failed**: If false positive rate > 30%, add qualifying signals or tighten scoring thresholds. Revalidate against fresh sample.

### Phase 3: MVP Pipeline Build (Weeks 3-6)

**Duration**: 2-4 weeks
**Tool**: Python + LLM API + enrichment APIs + cron scheduler

Execute MVP pipeline build. See [MVP Pipeline Build](/consulting/recipes/mvp-pipeline-build/2026) for detailed sub-recipe.

Build minimal viable pipeline: cron job pulling public data, Python script with LLM classification using taxonomy from Phase 2, enrichment via Clearbit/Apollo, document generation (dossier as PDF), email delivery with open/click tracking. No UI required. [src2]

**Verify**: Pipeline producing 10+ dossiers/week with < 5% error rate on classification. End-to-end automation working on schedule.
**If failed**: If classification accuracy < 70%, return to taxonomy and retrain. If enrichment coverage < 60%, add alternative data sources.

### Phase 4: Pilot Execution (Weeks 6-10)

**Duration**: 4 weeks
**Tool**: Pipeline + tracking + weekly iteration

Execute pilot program. See [Pilot Execution Playbook](/consulting/recipes/pilot-execution-playbook/2026) for detailed sub-recipe.

Select 2-3 pilot customers with measurable baselines. Deliver 10-20 qualified dossiers/week per customer. Track conversion rates against baseline. Iterate taxonomy weekly based on sales team feedback. Human validates every dossier for first 100 deliveries. [src1, src3]

**Verify**: At least 2x conversion rate improvement vs cold outreach baseline after 4 weeks. Minimum 3 pilot customers still engaged.
**If failed**: If < 1.5x improvement, problem is either signal quality (return to taxonomy) or dossier format (A/B test delivery formats). If pilot customers churning, interview for root cause before proceeding.

### Phase 5: Platform Extraction (Weeks 10-14)

**Duration**: 3-4 weeks
**Tool**: Software architecture + refactoring

Execute platform extraction. See [Platform Extraction](/consulting/recipes/platform-extraction/2026) for detailed sub-recipe.

**Hard gate**: Do not begin until 3 paying customers confirmed in vertical #1. Refactor vertical #1 codebase into reusable engine (data ingestion, LLM classification, enrichment, delivery) + vertical-specific config layer (signal sources, taxonomy, templates, compliance rules). Target: each subsequent vertical requires < 50% of vertical #1 effort. [src4]

**Verify**: Second vertical launched using platform + config approach in < 50% of vertical #1 timeline.
**If failed**: If second vertical takes > 60% of original effort, platform abstraction is insufficient. Identify tight-coupled components and refactor before attempting vertical #3.

### Phase 6: Vertical Scaling (Weeks 14-20)

**Duration**: 4-6 weeks per additional vertical
**Tool**: Platform + vertical-specific config + domain advisors

Launch additional verticals using the platform. See [Vertical Launch Checklist](/consulting/recipes/vertical-launch-checklist/2026) for each new vertical.

For each vertical: recruit domain advisor, verify data sources, build classifier rules, design outreach templates, identify 5-10 pilot customers, ensure compliance, set conversion tracking. [src3, src5]

**Verify**: Each new vertical achieves > 1.5x conversion improvement within first 4-week pilot.
**If failed**: If vertical underperforms after 4 weeks, evaluate whether signal density is sufficient. Some verticals are not viable — kill quickly rather than investing further.

## Output Schema

```json
{
  "output_type": "signal_stack_engagement",
  "format": "multi-deliverable",
  "sections": [
    {"name": "signal_audit", "type": "object", "description": "Scored inventory of data sources with accessibility/cost/refresh/SNR ratings", "required": true},
    {"name": "signal_taxonomy", "type": "object", "description": "Hierarchical classification schema with weighted scoring model", "required": true},
    {"name": "mvp_pipeline", "type": "object", "description": "Deployed pipeline specification with cron schedule and monitoring", "required": true},
    {"name": "pilot_results", "type": "object", "description": "Conversion metrics, ROI calculation, taxonomy refinements", "required": true},
    {"name": "platform_architecture", "type": "object", "description": "Reusable engine design with config layer specification", "required": false},
    {"name": "vertical_playbooks", "type": "array", "description": "Per-vertical launch configurations", "required": false}
  ],
  "expected_sections": "4-6",
  "sort_order": "chronological by phase"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Signal sources identified per vertical | > 15 | > 25 | > 40 |
| Taxonomy false positive rate | < 30% | < 20% | < 10% |
| Dossier delivery rate | 10/week | 20/week | 50+/week |
| Conversion rate vs cold outreach | > 1.5x | > 2x | > 3x |
| Time to launch new vertical | < 6 weeks | < 4 weeks | < 2 weeks |

**If below minimum**: Stop and diagnose. Signal density may be insufficient for the vertical, or taxonomy needs recalibration with domain expert input.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Signal audit finds < 10 viable sources | Vertical lacks public data density | Pivot vertical or supplement with paid data sources |
| Taxonomy false positive rate > 40% | Signals too noisy or taxonomy too broad | Add qualifying signals, tighten thresholds, revalidate with domain expert |
| Pipeline delivery failures > 10% | API rate limits or data source changes | Add retry logic, monitor source availability, maintain backup sources |
| Pilot conversion < 1x (no improvement) | Wrong signals or wrong audience | A/B test dossier formats, interview sales team, reassess signal relevance |
| Platform extraction takes > 2x estimated | Tight coupling in vertical #1 code | Invest in decoupling before adding verticals — technical debt compounds |

## Cost Breakdown

| Component | Lean ($15K-$25K) | Standard ($25K-$40K) | Enterprise ($40K+) |
|-----------|-------------------|----------------------|-------------------|
| Signal audit | $2K-$3K | $3K-$5K | $5K-$8K |
| Taxonomy workshop | $3K-$5K | $5K-$8K | $8K-$12K |
| MVP pipeline build | $5K-$8K | $8K-$12K | $12K-$18K |
| Pilot execution (4 weeks) | $3K-$5K | $5K-$8K | $8K-$12K |
| Platform extraction | $0 (deferred) | $5K-$10K | $10K-$15K |
| **Total engagement** | **$15K-$25K** | **$25K-$40K** | **$40K-$65K** |
| **Monthly data/compute** | **$500-$1K** | **$1K-$2K** | **$2K-$5K** |

## Anti-Patterns

### Wrong: Building the platform before proving vertical #1
Investing in reusable architecture before confirming product-market fit with paying customers. Result: over-engineered system that nobody uses, $50K+ wasted on infrastructure that solves the wrong problem. [src2, src3]

### Correct: Prove value with ugly code first
Build the simplest possible pipeline for vertical #1. Hardcode everything. Only extract a platform after 3 paying customers confirm the value proposition.

### Wrong: Skipping human-in-the-loop validation
Automating dossier delivery from day one without human review. Result: first batch contains false positives and irrelevant signals, destroying credibility with pilot customers permanently. [src1]

### Correct: Human validates first 100 dossiers per vertical
Every dossier gets human review for the first 100 deliveries. This calibrates the taxonomy, catches edge cases, and ensures quality before scaling.

### Wrong: Launching multiple verticals simultaneously
Trying to prove the model in 3 verticals at once to speed up platform justification. Result: none get enough attention, all produce mediocre results, no clear signal on what works. [src3]

### Correct: Sequential vertical execution
Fully prove vertical #1 (3 paying customers), extract platform, then launch vertical #2. Each vertical informs the next.

## When This Matters

Use when an agent needs to plan or execute a full Signal Stack consulting engagement — from identifying intent signals in a target industry through building an automated intelligence pipeline. This is the master recipe orchestrating signal audit, taxonomy design, MVP build, pilot execution, platform extraction, and vertical scaling into a cohesive engagement lifecycle. Requires defined target vertical and sales baseline data as prerequisites.

## Related Units

- [Signal Source Audit](/consulting/recipes/signal-source-audit/2026)
- [Signal Taxonomy Workshop](/consulting/recipes/signal-taxonomy-workshop/2026)
- [MVP Pipeline Build](/consulting/recipes/mvp-pipeline-build/2026)
- [Pilot Execution Playbook](/consulting/recipes/pilot-execution-playbook/2026)
- [Platform Extraction](/consulting/recipes/platform-extraction/2026)
- [Vertical Launch Checklist](/consulting/recipes/vertical-launch-checklist/2026)