--- # === IDENTITY === id: consulting/recipes/vertical-launch-checklist/2026 canonical_question: "What is the checklist for launching a new Signal Stack vertical?" aliases: - "Signal Stack new vertical launch process" - "How to add a new industry vertical to Signal Stack" - "Vertical expansion checklist for signal-based outreach" entity_type: execution_recipe domain: consulting > recipes > Vertical Launch Checklist 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 vertical launch methodology v1.0" next_review: 2026-09-25 change_sensitivity: high # === CONSTRAINTS === constraints: - "Platform extraction must be complete before launching vertical #2+ — do not launch on bespoke code" - "Each vertical requires a domain advisor (even part-time) — never launch without signal taxonomy validation from an industry expert" - "GDPR/PECR/CAN-SPAM compliance review mandatory before any outbound delivery in the new vertical" - "Minimum 5 pilot customers identified before build begins — do not build speculatively" - "New vertical config must produce first dossier within 2 weeks of build start — if longer, the platform abstraction failed" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User has not yet completed platform extraction" use_instead: "consulting/recipes/platform-extraction/2026" - condition: "User is still running the first vertical pilot" use_instead: "consulting/recipes/pilot-execution-playbook/2026" - condition: "User needs Signal Stack theory, not execution" use_instead: "consulting/signal-stack/five-layer-pipeline-architecture/2026" # === AGENT HINTS === inputs_needed: - key: target_vertical question: "Which industry vertical is being launched?" type: text - key: platform_status question: "Is the platform extraction complete (generic engine + config layer)?" type: choice options: ["yes — platform extracted and tested", "partially — extraction in progress", "no — still on bespoke code"] - key: domain_advisor question: "Has a domain advisor been recruited for this vertical?" type: choice options: ["yes — advisor engaged", "identified but not engaged", "no advisor yet"] - key: pilot_customers question: "How many pilot customers have been identified for this vertical?" type: choice options: ["0 (none yet)", "1-4", "5-10", "10+"] # === EXECUTION METADATA === execution: required_inputs: - name: "Extracted platform (generic engine + config schema)" source: "Platform extraction output" format: "code repository" - name: "Target vertical selection rationale" source: "Strategy/BD" format: "document" - name: "Domain advisor agreement" source: "BD/recruitment" format: "contract or LOI" - name: "5-10 pilot customer leads" source: "Sales/BD" format: "CRM list" outputs: - name: "Vertical Config File" format: "JSON/YAML" description: "Complete vertical configuration for the platform engine: sources, triggers, targets, templates, delivery, conversion definitions" - name: "Signal Taxonomy Document" format: "document" description: "Domain-advisor-validated taxonomy of signal sources, trigger events, strength scoring, and false positive exclusions" - name: "Compliance Clearance" format: "document" description: "GDPR/PECR/CAN-SPAM review confirming outbound delivery is legal in target jurisdictions" - name: "Pilot Launch Package" format: "operational pipeline + tracking" description: "Working pipeline producing dossiers for pilot customers with conversion tracking active" tools_required: - name: "Platform engine (from extraction)" purpose: "Reusable 5-layer pipeline" tier: "internal" cost: "$0 (already built)" alternatives: [] - name: "Data source APIs/scrapers" purpose: "Vertical-specific signal ingestion" tier: "varies" cost: "$100-500/month depending on sources" alternatives: ["RSS feeds", "Manual monitoring", "FOIA requests"] - name: "Enrichment API (Clearbit/Apollo)" purpose: "Firmographic enrichment for new vertical targets" tier: "paid" cost: "$100-300/month" alternatives: ["LinkedIn Sales Navigator", "Hunter.io"] - name: "Legal review" purpose: "Compliance assessment for outbound delivery" tier: "paid" cost: "$1K-3K one-time" alternatives: ["Internal compliance team", "Template-based self-assessment (higher risk)"] credentials_needed: - service: "Vertical-specific data sources" type: "API keys or scraping access" where_to_get: "Varies by vertical — identified during signal audit" free_tier_limits: "Varies — budget $100-500/month" estimated_duration: "2-4 weeks (checklist through pilot launch)" estimated_cost: "$15K-25K (first engagement in new vertical)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/consulting/recipes/vertical-launch-checklist/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-29)" # === RELATED UNITS === related_kos: depends_on: - id: "consulting/recipes/platform-extraction/2026" label: "Platform must be extracted before launching new verticals" - id: "consulting/signal-stack/five-layer-pipeline-architecture/2026" label: "The five-layer signal pipeline — Ingest, Detect, Enrich, Generate, Deliver" feeds_into: - id: "consulting/recipes/pilot-execution-playbook/2026" label: "New vertical enters pilot execution after launch checklist is complete" related_to: [] # === SOURCES === sources: - id: src1 title: "Signal Stack — A Unified Signal-family Platform" author: "Internal methodology" url: https://knowledgelib.io/consulting/signal-stack/signal-stack-architecture/2026 type: primary_research published: 2026-03-09 reliability: high - id: src2 title: "Signal Stack Consulting-as-a-Service — Strategic Intelligence Report" author: "Internal methodology" url: https://knowledgelib.io/consulting/signal-stack/signal-stack-caas/2026 type: primary_research published: 2026-03-29 reliability: high - id: src3 title: "Stop Cold Emailing and Start Reading the Exhaust Fumes" author: "Internal research" url: https://knowledgelib.io/consulting/signal-stack/exhaust-fumes-thesis/2026 type: primary_research published: 2026-03-01 reliability: high - id: src4 title: "GDPR and Direct Marketing: A Practical Guide" author: "ICO (UK Information Commissioner's Office)" url: https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/ type: official_docs published: 2024-01-01 reliability: authoritative --- # Vertical Launch Checklist ## 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 setup, and success metric definition. Each new vertical should take less than 50% of the effort of vertical #1. [src1, src2] ## Prerequisites - [ ] **Platform extraction complete** — generic engine + declarative config layer operational with at least one vertical - [ ] **Vertical #1 has 3+ paying customers** — the platform is commercially validated - [ ] **Target vertical selected** — rationale documented (data source overlap with existing verticals, buyer willingness to pay, market size) - [ ] **Budget allocated** — $15K-25K for first engagement in new vertical - [ ] **Sales pipeline** — at least 5 potential pilot customers identified in target vertical ## Constraints - Platform extraction must be complete before launching. Do not launch a new vertical on bespoke code — that defeats the platform economics. [src1] - Every vertical requires a domain advisor who validates the signal taxonomy. Industry expertise cannot be faked by LLMs alone. [src2] - GDPR/PECR/CAN-SPAM compliance review is mandatory before any outbound delivery. Different verticals may operate in different regulatory environments. [src4] - Minimum 5 pilot customers identified before build begins. Do not build speculatively — demand must precede supply. [src3] - First dossier must ship within 2 weeks of build start. If longer, the platform abstraction has failed and needs refactoring. [src1] ## Tool Selection Decision ``` Which path? ├── New vertical shares data source types with existing vertical │ ├── Same regulatory/public data sources │ │ └── PATH A: Config-only launch — reuse existing scrapers, new classifier rules │ └── Same source type but different APIs │ └── PATH B: Light integration — new API connector + config ├── New vertical requires entirely new data source type │ ├── Structured data (APIs, databases, filings) │ │ └── PATH C: New connector development — build ingestion + config │ └── Unstructured data (imagery, documents, media) │ └── PATH D: New capability — requires engine extension + config └── New vertical is regulatory-heavy └── PATH E: Compliance-first — legal review before any technical work ``` | Path | Approach | Duration | Cost | Best For | |------|----------|----------|------|----------| | A: Config-only | New classifier rules + templates | 1-2 weeks | $5K-10K | Adjacent verticals | | B: Light integration | New API connector + config | 2-3 weeks | $10K-15K | Same source type | | C: New connector | Build ingestion + config | 3-4 weeks | $15K-20K | New structured data | | D: New capability | Engine extension + config | 4-6 weeks | $20K-30K | Imagery/unstructured | | E: Compliance-first | Legal review then build | 3-5 weeks | $15K-25K | Regulated industries | ## Execution Flow ### Step 1: Recruit Domain Advisor **Duration**: 3-5 days **Tool**: LinkedIn outreach + advisor network Identify and engage a domain advisor for the target vertical. The advisor validates signal taxonomy — they know which data sources exist, which events are genuine buying triggers, and which are noise. Minimum qualifications: 5+ years in the target industry, direct experience with the buying process you are targeting. [src1, src2] Compensation: $2K-5K per engagement (fixed fee), or ongoing advisory at $500-1K/month. Structure as a fixed deliverable: "validate the signal taxonomy and review first 10 dossiers." **Verify**: Advisor agreement signed with deliverables and timeline defined. **If failed**: If no advisor available within 1 week, assess whether the team has sufficient domain knowledge to proceed. If not, do not launch this vertical — 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 identified in the target vertical, verify: (1) the data is actually accessible (API exists, scraping is legal, FOIA response time is acceptable), (2) the cost is within budget ($100-500/month total for all sources), (3) the refresh rate supports the required detection speed, (4) data quality is sufficient for reliable classification. [src1] Build a source scorecard: source name, accessibility (1-5), cost/month, refresh rate, signal-to-noise estimate, redundancy (alternative sources if primary fails). **Verify**: At least 3 viable sources scored and budgeted. Total source cost < $500/month. **If failed**: If fewer than 3 viable sources exist, the vertical may not have sufficient signal density. Consider merging with an adjacent vertical or deprioritizing. ### Step 3: Build Vertical-Specific Classifier Rules **Duration**: 3-5 days **Tool**: Config file authoring + LLM prompt engineering Create the vertical-specific configuration for the classification layer: define trigger events (what counts as a buying signal), strength scoring (how to weight different signal types), compound signal logic (which signal combinations increase confidence), and false positive exclusion rules (what looks like a signal but is not). [src1, src3] Have the domain advisor review and validate the taxonomy. Iterate based on their feedback — they catch false positive patterns that data alone misses. [src2] **Verify**: Domain advisor signs off on the signal taxonomy. Test classification on 20+ historical examples from the vertical with > 60% precision. **If failed**: If precision < 60%, the taxonomy is too broad. Have the advisor identify the top 3 false positive categories and add explicit exclusion rules. ### Step 4: Design Outreach Package Templates **Duration**: 2-3 days **Tool**: Template engine (Jinja2 or similar) + domain advisor review Design the dossier template for this vertical. Every dossier needs: (1) signal evidence section — the specific data points that triggered the alert, (2) company context — enrichment data making the case relevant, (3) proof pack — the falsifiable evidence supporting the signal (the "Doctor-with-Lab-Report" approach), (4) recommended action — what the recipient should do, (5) call to action — clear next step. [src3] The template must be vertical-specific: an insurance broker receives a different dossier format than a cybersecurity MSSP. Have the domain advisor and at least one pilot customer review the template. **Verify**: Template reviewed by domain advisor and at least 1 pilot customer. Feedback incorporated. **If failed**: If pilot customer feedback is negative, redesign the proof pack structure — this is usually the section that either builds or destroys credibility. ### Step 5: Identify 5-10 Pilot Customers **Duration**: 3-5 days (can run parallel to Steps 2-4) **Tool**: CRM + outreach Identify and recruit 5-10 pilot customers in the target vertical. Selection criteria: (1) currently doing outbound (has a baseline to compare against), (2) deal size > $50K ACV (justifies the investment), (3) willing to share conversion data, (4) accessible decision-maker (VP Sales/CRO). [src2] Offer pilot terms: discounted rate ($15K-25K vs. full $50K implementation) in exchange for detailed conversion tracking and case study rights. **Verify**: At least 5 pilot customers confirmed with signed agreements. **If failed**: If fewer than 5, extend recruitment by 2 weeks. If still fewer than 5 after 4 weeks total, reconsider vertical selection — demand must exist before supply. ### Step 6: GDPR/PECR/CAN-SPAM Compliance Review **Duration**: 3-5 days **Tool**: Legal review + compliance checklist Conduct compliance review for outbound delivery in the new vertical. Cover: (1) which jurisdictions are the target companies in, (2) what consent basis exists for outbound contact (legitimate interest, soft opt-in, prior relationship), (3) are there industry-specific regulations beyond general data protection (e.g., HIPAA for healthcare, FINRA for financial services), (4) what opt-out mechanism is required, (5) what data retention limits apply. [src4] Produce a compliance clearance document specifying: permitted delivery channels, required disclosures, opt-out requirements, data retention policy, and any industry-specific restrictions. **Verify**: Compliance clearance document signed by legal counsel or compliance officer. **If failed**: If compliance is unclear, default to opt-in only delivery (highest compliance bar). Engage external legal counsel if internal expertise is insufficient. ### Step 7: Set Conversion Tracking and Feedback Loop **Duration**: 1-2 days **Tool**: Platform config + CRM integration Configure the conversion tracking for the new vertical in the platform config: define what counts as each funnel stage (dossier delivered, opened, replied, meeting booked, proposal sent, deal closed), set up feedback loop (which outcome data feeds back into classification improvement), and establish reporting cadence (weekly dashboard). [src2] Ensure the feedback loop is bidirectional: not only does outcome data improve classification, but pilot customer rejections ("this signal was irrelevant") directly update false positive exclusion rules. **Verify**: Tracking operational — test event flows through all funnel stages. Feedback loop confirmed with at least one test rejection. **If failed**: If CRM integration is blocked, fall back to manual tracking spreadsheet. Automate in next iteration. ### Step 8: Define Success Metrics and Phase 1 Exit Criteria **Duration**: 1 day **Tool**: Strategy document Define the success metrics for this vertical's Phase 1: - **Signal precision**: target > 70% by week 4 (higher than initial vertical because platform is proven) - **Dossier volume**: target 10-20 per week per pilot customer - **Conversion vs. baseline**: target > 2x pilot customers' cold outreach conversion rate - **Customer retention**: target 4/5 pilot customers continuing after pilot - **Unit economics**: cost per qualified dossier < $50, cost per meeting booked < $500 - **Phase 1 exit criteria**: 3 paying customers in this vertical [src1, src2] **Verify**: Success metrics document shared with team and pilot customers. **If failed**: If team disagrees on metrics, align with domain advisor on what is realistic for this vertical's sales cycle length and deal size. ## Output Schema ```json { "output_type": "vertical_launch_package", "format": "config files + documents", "sections": [ {"name": "vertical_config", "type": "object", "description": "Complete platform config for new vertical", "required": true}, {"name": "signal_taxonomy", "type": "object", "description": "Domain-advisor-validated taxonomy", "required": true}, {"name": "source_scorecard", "type": "array", "description": "Data source accessibility, cost, and quality scores", "required": true}, {"name": "dossier_template", "type": "object", "description": "Vertical-specific outreach package template", "required": true}, {"name": "compliance_clearance", "type": "object", "description": "Jurisdiction-specific compliance review", "required": true}, {"name": "success_metrics", "type": "object", "description": "Phase 1 exit criteria and KPIs", "required": true} ], "expected_sections": "6", "sort_order": "checklist step order" } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Time from start to first dossier | < 3 weeks | < 2 weeks | < 10 days | | Effort vs. vertical #1 | < 60% | < 50% | < 40% | | Engine code changes required | < 3 | 1 | Zero | | Signal precision on test data | > 60% | > 70% | > 80% | | Pilot customers recruited | >= 5 | >= 7 | >= 10 | | Compliance clearance time | < 2 weeks | < 1 week | < 3 days | **If below minimum**: The vertical either lacks sufficient signal density, or the platform abstraction needs refactoring. Reassess before investing further. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | No domain advisor available | Niche vertical or insufficient network | Post on industry-specific communities, offer higher compensation, consider fractional advisor | | Data sources inaccessible or too expensive | Regulatory restrictions or paywalled data | Look for alternative sources (FOIA, proxy signals, aggregator APIs), reassess vertical viability | | Signal precision < 60% after advisor review | Signals in this vertical are inherently noisy | Add compound signal requirement, narrow to highest-quality sources only | | Fewer than 5 pilot customers after 4 weeks | Weak demand or wrong positioning | Pivot messaging, test different buyer persona, or deprioritize vertical | | Compliance blocks outbound delivery | Industry-specific regulation (HIPAA, FINRA) | Switch to opt-in only model, or deliver via partner channel instead of direct outbound | | First dossier takes > 2 weeks | Platform config schema insufficient for vertical | Identify missing config parameters, extend schema, file as platform improvement | ## Cost Breakdown | Component | Adjacent Vertical ($15K) | New Source Type ($20K) | New Capability ($25K) | |-----------|--------------------------|------------------------|-----------------------| | Domain advisor | $2K-3K | $3K-5K | $3K-5K | | Data source setup | $1K | $3K-5K | $5K-8K | | Classifier config | $2K-3K | $3K-4K | $4K-5K | | Template design | $1K-2K | $2K-3K | $2K-3K | | Compliance review | $1K-2K | $2K-3K | $2K-3K | | Pilot recruitment | $1K | $1K-2K | $1K-2K | | Tracking setup | $500-1K | $1K | $1K-2K | | **Total** | **$10K-15K** | **$15K-22K** | **$18K-28K** | | **vs. Vertical #1 ($50K)** | **20-30%** | **30-44%** | **36-56%** | ## Anti-Patterns ### Wrong: Launching without a domain advisor Building the signal taxonomy using LLM-generated industry knowledge alone. Result: false positive rate exceeds 50%, dossiers contain industry-inappropriate framing, pilot customers lose confidence after 2 weeks. [src1, src2] ### Correct: Domain advisor is non-negotiable Even a part-time advisor ($2K-5K) catches taxonomy errors that would otherwise take 4-6 weeks of pilot iteration to discover. The advisor pays for themselves in avoided false positives. ### Wrong: Building before confirming demand Constructing the vertical config and dossier templates before identifying pilot customers. Result: you build for an imagined buyer, not a real one. Template feedback from actual prospects is 10x more valuable than internal assumptions. [src3] ### Correct: Recruit pilot customers before building Identify 5-10 pilot customers first. Their feedback shapes the signal taxonomy and dossier format. If you cannot find 5 willing pilot customers, the vertical is not ready. ### Wrong: Skipping compliance review for speed Launching outbound delivery without jurisdiction-specific compliance assessment. Result: one complaint triggers regulatory investigation, damages brand reputation across all verticals, and potentially generates fines. [src4] ### Correct: Compliance review runs parallel to build Start the compliance review on day 1, parallel to domain advisor recruitment and data source verification. It should complete before the first dossier ships, not after. ## 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. It prevents the two most common vertical launch failures: building without demand and shipping without compliance. ## Related Units - [Platform Extraction](/consulting/recipes/platform-extraction/2026) - [Pilot Execution Playbook](/consulting/recipes/pilot-execution-playbook/2026) - [Signal Stack Architecture](/consulting/signal-stack/signal-stack-architecture/2026)