Detailed specs, pseudo-config, and workflows that sit under the public GTM blueprint.

1. Stack Specs

1.1 Data Layer (Spec)

• Deterministic ICP filters (industry, headcount, funding, stack, geo).
• Enrichment (role, seniority, signals like hiring / tech stack / content).
• De-duplication against CRM and current pipeline.
• Output: a clean table for downstream workflows.

# Example ICP filter (pseudo-spec)
WHERE
  company_industry IN ("AI", "SaaS") AND
  employee_count BETWEEN 5 AND 200 AND
  title ILIKE '%Founder%' OR '%CEO%' OR '%Head of GTM%'

1.2 Messaging Layer (Spec)

• Segment → narrative → primary offer mapping.
• Modular blocks: openers, value props, proof, CTAs.
• Outbound sequences assembled from blocks, not one-off copy.
• Versions promoted or deprecated based on performance.

# Example message block
SEGMENT: AI Founder (5–50 team, active on LinkedIn)
TYPE: OPENER
COPY:
"Saw your recent build-in-public post on [topic]. Most AI teams stall when GTM infra lags behind the product. We fix the infra layer so your outbound is deterministic, not random experiments."

1.3 Sending Layer (Spec)

• Domain warmup and routing per mailbox.
• Sequences mapped to the right sender identity.
• Volume throttling based on bounce and spam thresholds.
• All replies and meetings routed to CRM / Notion.