Zevenue
OrganizationHeadless GTM: the full outbound chain as Claude Code and Codex skills on raw vendor APIs.
Categories
Indexed Skills (17)
00-gtm-router
Plan and run the full API-first GTM chain - the orchestrator (step 00) that turns an ICP description plus optional budget, volume, and urgency into the right discovery -> qualification -> extraction -> signals -> judgment -> email-resolution sequence, with per-step cost estimates and rationale, then executes it skill-by-skill after a go-ahead. Use whenever a request spans more than one chain step or the user asks which tools or skills to use, in what order, or what it will cost - e.g. "plan a campaign for this ICP", "build me a list end to end", "we're targeting X, what's the play", "what would it cost to go after Y", "new client kickoff", "run the whole chain" - or when they hand over an ICP or client brief and want prospects with verified emails out the other side. Also use when partial data exists (a company list without signals, contacts without emails) to pick the right entry point mid-chain. For a true cold start - "first campaign", "never run a campaign", "no CRM", nothing to analyze yet - route to run
01-icp-qualify
The qualification gate of the GTM chain - judges every discovered company against the client's ICP before any paid enrichment, so credits are spent only on companies that could actually buy. Works for any client and any vertical: it studies the client first, then compiles client-specific qualification criteria and applies them. Use whenever a prospect list needs cleaning before outreach or enrichment - "qualify this list", "remove non-ICP companies", "which of these fit the ICP", "filter this lead list", "clean the list before enriching" - and always between discovery and any credit-spending skill when running as part of the chain. Also use when the user has a CSV/JSONL of companies and asks which ones are worth pursuing, even if they never say the word "qualify". Runs on model judgment by default - no API keys required.
01-prospeo-discover
B2B company discovery and list building via the Prospeo search API. Use when the user wants to find companies from an ICP, build a prospect or TAM list, search by ICP, or size a market - e.g. "build a list of B2B SaaS in the US", "how many companies match this ICP", "TAM sizing", "company search", or any mix of industry + location + headcount + funding filters. Handles seed-based "similar to X" requests too by building an ICP from the seeds; 01-prospeo-lookalike is the deeper specialist when you want the matches themselves returned and ranked.
01-prospeo-lookalike
Seed-based B2B company discovery via the Prospeo company-lookalike API. Use when the user has example companies and wants more like them - "find companies similar to X", "companies like Stripe and HubSpot", "lookalikes of these domains", "we closed these 20 logos, find more", "expand this seed list", or hands over closed-won accounts / a competitor / a customer list and wants similar firmographic matches. Turns seed domains or an ICP description into a ranked list of similar companies, and can also hand a pattern-built ICP to prospeo-discover for a broader search.
02-apify-maps-discover
Find local-business (SMB) prospects via Google Maps using the Apify Compass actor. Use for Zevenue Step-2 Discovery (Vertical) when the ICP is Maps-addressable - laundromats, salons, HVAC, yoga studios, gyms, clinics - and you need a normalized list of name, domain, address, phone, rating, and review count ready for enrichment. Estimates cost and prompts before any run over $10. Requires APIFY_API_TOKEN.
03-firecrawl-research
Scrapes a company website into clean, page-typed markdown using Firecrawl map + scrape + extract. Triggers on: "scrape this company", "read their website", "extract pages from", "research this domain", "fetch their careers page", or any URL + "scrape/extract/read". Covers single domain, batch processing, structured LLM extraction, and Google Sheets output.
04-crustdata-signals
Enriches company domains with structured signals from CrustData - funding rounds, headcount growth, department growth, and recent hires. Use when the user wants to pull company signals, enrich domains with funding/growth/hiring data, check who recently joined a company, find new hires at a domain, get headcount trends, or anything involving CrustData enrichment. Also triggers on: "run crustdata signals", "enrich these domains", "pull funding data", "who joined recently", "headcount growth for these companies", "department growth", "recent hires at", "crustdata enrich".
04-theirstack-jobs
Pulls open job postings from the TheirStack API and turns them into structured hiring signals - open roles per domain, titles, seniority, posting dates, hiring team, plus free firmographics (headcount, funding stage, industry). Step 04 (signals) of the API-first GTM chain, and the discovery entry for hiring-defined ICPs. Use when the user wants hiring signals, open reqs, job postings, "who is hiring", "which of these companies are hiring X", "find companies hiring Y right now", open-role checks on a domain list or records.jsonl, or anything TheirStack. Sizing counts bound every pull before spend - free without company filters, ~1 credit against a domain list - then 1 credit per job returned. For people who already joined - recent hires, headcount growth, funding rounds - use 04-crustdata-signals; for scoring and campaign angles, hand the records to 05-signal-builder.
05-signal-builder
Rank a prospect's outbound signals and pick the campaign approach (Pain-led / Value-led / Segment fallback) - the judgment layer (step 05) of the API-first GTM chain. Takes scraped website markdown (03-firecrawl-research), vendor signals like funding / headcount / recent hires (04-crustdata-signals), or just a URL or pasted content, and emits ranked provenance-backed signals: the exact quotable sentence, source URL, 1-10 score, and recommended approach. Use whenever the user wants to score, rank, or prioritize prospects or accounts, decide outreach angles, or asks "which of these should we email first", "what's the angle for this account", "rank these signals", or "turn this scrape into campaign angles" - and whenever a records.jsonl or enrichment output is ready for judgment before writing copy. Scoring lives here; scraping belongs to firecrawl-research, vendor pulls to crustdata-signals, email finding to resolution.
06-resolution-email-person
Turn a company domain (plus an optional person name or job title) into a verified, send-safe email address - the deliverability-first "resolution" layer of a cold-email pipeline. Use when the user wants to find or verify a work email, enrich a list or file of domains into decision-maker contacts, or resolve "who is the [title] at [company] and what's their email." Works standalone or as Layer 06 in the API-First GTM stack. Cost-ordered waterfall: AI Ark → Prospeo → Blitz → Findymail with ZeroBounce validation; a rung is skipped when its API key is absent, and it never spends enrichment credit without an explicit go-ahead.
creative-variable
Identify and spec non-obvious personalization variables for an outbound campaign - variable names, grammar forms, sources, extraction prompts, fallbacks, rendered examples. Use when building a new campaign's personalization layer or auditing existing copy against the four variable archetypes.
email-writer
Write 3-email cold outbound sequences following the Situation -> Insight -> Inquisition methodology, from signal data plus offer context and prospect info. Use to draft campaign copy after signal-builder or from enrichment data, with deliverability rules and a QA checklist enforced.
gtm-context
Set up the GTM context layer - interviews you about your offer, ICP, and engagement signals, then writes context/offer.md and context/icp.md that the other GTM skills read. Run first, once per workspace, before signal or copy work.
prospect-posts
Scrape recent LinkedIn posts from one or more prospect profiles via Apify and scan them for a theme (e.g. hiring pain, AI-first GTM). Outputs a report with matched excerpts and post links. Use for prospect or account intelligence research before outreach.
07-campaign-sheet
Turn a terminal records.jsonl into an owner-readable campaign sheet plus a HubSpot-import-shaped CSV - the chain's exit door. Use when a run is ready to hand to an owner: "build the campaign sheet", "export these for HubSpot", "who do I contact first", or as the final step of run-first-campaign. Reads whatever stage produced the records (qualified, signal-ranked, or fully resolved) and degrades gracefully on missing fields - no email column until 06 has run. Nothing sends and nothing downstream reads its output: the sheet and CSV are the human deliverable, approved on screen. To add verified emails first, run 06-resolution-email-person; to rank, 05-signal-builder.
run-first-campaign
The packaged cold-start campaign workflow - takes an owner with no list, no CRM, and no outbound history from a plain-English business description to an approved campaign sheet in one supervised pass: business context, a proposed source of record (a public directory - registry, professional college, trade association, marketplace, Maps - for local or licensed businesses, or a firmographic pull - 01-prospeo-discover, 01-prospeo-lookalike, 04-theirstack-jobs - for B2B), free ICP qualification, signal ranking, a drafted 3-email sequence, and a HubSpot-import-shaped CSV. Use when someone says "first campaign", "never run a campaign", "no CRM", "I need customers but have nothing to analyze", or wants outbound started from zero existing data. Nothing sends - the deliverables are drafts and files, and every paid step is cost-approved before it runs. For a campaign on an existing list or CRM data, use 00-gtm-router directly.
headless-gtm-shared
Reference module for the Headless GTM chain, not a skill to invoke. Holds the record contract every chain skill reads and writes (CONVENTIONS.md) plus the Python helpers they import (common.py, schema.py). Installed alongside the chain so those imports and references resolve; read CONVENTIONS.md when you need the JSONL record shape, the runs/ layout, or the cost-gate rules.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.