Vertical Launch Checklist — Signal Stack

Purpose

This recipe provides the complete checklist for launching a new Signal Stack vertical on the extracted platform. It covers all gates from domain advisor recruitment through pilot launch: signal taxonomy validation, data source verification, classifier rule construction, outreach template design, pilot customer identification, compliance review, conversion tracking, and success metric definition. Each new vertical should take < 50% of the effort of vertical #1. [src1, src2]

Prerequisites

• Platform extraction complete — generic engine + declarative config layer operational
• Vertical #1 has 3+ paying customers — platform commercially validated
• Target vertical selected — rationale documented
• Budget allocated — $15K-25K for first engagement
• Sales pipeline — at least 5 potential pilot customers identified

Constraints

• Platform extraction must be complete before launching. Do not launch on bespoke code. [src1]
• Every vertical requires a domain advisor. Industry expertise cannot be faked by LLMs alone. [src2]
• GDPR/PECR/CAN-SPAM compliance review mandatory before outbound delivery. [src4]
• Minimum 5 pilot customers identified before build begins. Demand must precede supply. [src3]
• First dossier must ship within 2 weeks. If longer, platform abstraction needs refactoring. [src1]

Tool Selection Decision

Which path?
├── Shares data source types with existing vertical
│   ├── Same regulatory/public data sources
│   │   └── PATH A: Config-only — reuse scrapers, new classifier rules
│   └── Same type but different APIs
│       └── PATH B: Light integration — new connector + config
├── Requires entirely new data source type
│   ├── Structured data (APIs, databases, filings)
│   │   └── PATH C: New connector — build ingestion + config
│   └── Unstructured data (imagery, documents, media)
│       └── PATH D: New capability — engine extension + config
└── Regulatory-heavy vertical
    └── PATH E: Compliance-first — legal review before technical work

Execution Flow

Step 1: Recruit Domain Advisor

Duration: 3-5 days · Tool: LinkedIn outreach + advisor network

Engage a domain advisor (5+ years in target industry) to validate signal taxonomy. Compensation: $2K-5K per engagement or $500-1K/month ongoing. [src1, src2]

Verify: Advisor agreement signed with deliverables and timeline. · If failed: If no advisor within 1 week, do not launch — domain ignorance produces unusable taxonomies.

Step 2: Verify Data Source Accessibility and Cost

Duration: 2-3 days · Tool: API testing + cost analysis

For each signal source: verify accessibility, cost (< $500/month total), refresh rate, and data quality. Build source scorecard. [src1]

Verify: At least 3 viable sources scored and budgeted. · If failed: Fewer than 3 sources means insufficient signal density — deprioritize or merge with adjacent vertical.

Step 3: Build Vertical-Specific Classifier Rules

Duration: 3-5 days · Tool: Config authoring + LLM prompt engineering

Create classification config: trigger events, strength scoring, compound signal logic, false positive exclusions. Domain advisor validates taxonomy. [src1, src3]

Verify: Advisor sign-off + > 60% precision on 20+ test examples. · If failed: Add exclusion rules for top 3 false positive categories.

Step 4: Design Outreach Package Templates

Duration: 2-3 days · Tool: Template engine + advisor review

Design vertical-specific dossier template: signal evidence, company context, proof pack, recommended action, CTA. Review with domain advisor and at least 1 pilot customer. [src3]

Verify: Template reviewed by advisor and 1+ pilot customer. · If failed: Redesign proof pack structure — usually the credibility-critical section.

Step 5: Identify 5-10 Pilot Customers

Duration: 3-5 days (parallel to Steps 2-4) · Tool: CRM + outreach

Recruit 5-10 pilots: currently doing outbound, deal size > $50K ACV, willing to share conversion data. Offer discounted pilot terms ($15K-25K). [src2]

Verify: At least 5 confirmed with signed agreements. · If failed: Extend 2 weeks; if still < 5, reconsider vertical selection.

Step 6: GDPR/PECR/CAN-SPAM Compliance Review

Duration: 3-5 days · Tool: Legal review + compliance checklist

Review: target jurisdictions, consent basis, industry-specific regulations (HIPAA, FINRA), opt-out requirements, data retention. Produce compliance clearance document. [src4]

Verify: Compliance clearance signed by legal counsel. · If failed: Default to opt-in only delivery; engage external counsel if needed.

Step 7: Set Conversion Tracking and Feedback Loop

Duration: 1-2 days · Tool: Platform config + CRM integration

Configure funnel stages, feedback loop (outcome data improves classification, rejections update exclusion rules), and reporting cadence. [src2]

Verify: Test events flow through all stages, feedback loop confirmed. · If failed: Fall back to manual tracking spreadsheet.

Step 8: Define Success Metrics and Phase 1 Exit Criteria

Duration: 1 day · Tool: Strategy document

Define metrics: signal precision > 70% by week 4, 10-20 dossiers/week, > 2x baseline conversion, 4/5 pilot retention, cost per dossier < $50. Phase 1 exit: 3 paying customers. [src1, src2]

Verify: Metrics document shared with team and pilots. · If failed: Align with domain advisor on realistic targets for this vertical.

Output Schema

{
  "output_type": "vertical_launch_package",
  "format": "config files + documents",
  "sections": [
    {"name": "vertical_config", "type": "object", "description": "Complete platform config for new vertical"},
    {"name": "signal_taxonomy", "type": "object", "description": "Domain-advisor-validated taxonomy"},
    {"name": "source_scorecard", "type": "array", "description": "Data source scores"},
    {"name": "dossier_template", "type": "object", "description": "Vertical-specific outreach template"},
    {"name": "compliance_clearance", "type": "object", "description": "Jurisdiction compliance review"},
    {"name": "success_metrics", "type": "object", "description": "Phase 1 exit criteria and KPIs"}
  ]
}

Quality Benchmarks

If below minimum: The vertical lacks signal density or the platform needs refactoring. Reassess before investing further.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Launching without a domain advisor

Building taxonomy using LLM knowledge alone. Result: 50%+ false positive rate, industry-inappropriate framing, pilot churn in 2 weeks. [src1, src2]

Correct: Domain advisor is non-negotiable

A $2K-5K advisor catches taxonomy errors that would take 4-6 weeks of iteration to discover.

Wrong: Building before confirming demand

Constructing config and templates before identifying pilots. Result: you build for an imagined buyer. [src3]

Correct: Recruit pilot customers before building

Identify 5-10 pilots first. Their feedback shapes taxonomy and format. No willing pilots = vertical not ready.

Wrong: Skipping compliance review for speed

Launching outbound without jurisdiction review. Result: one complaint triggers investigation across all verticals. [src4]

Correct: Compliance review runs parallel to build

Start compliance on day 1, parallel to advisor recruitment. Must complete before first dossier ships.

When This Matters

Use when an agent needs to plan or execute the launch of a new Signal Stack vertical on an existing platform. This checklist ensures every gate is passed before resources are committed: domain expertise, data availability, compliance clearance, and confirmed demand.