Files
skills/public/b2b-prospecting.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

4.8 KiB
Raw Permalink Blame History

B2B Prospecting Reference

For when the user sells to non-SaaS B2B — services, agencies, manufacturers, mid-market and enterprise companies, professional services firms.


ICP Signals That Matter (B2B branch)

Firmographic signals

  • Industry / vertical — NAICS or SIC codes if precision matters
  • Company size — headcount band, revenue band, location count
  • Geography — relevant for time zones, regulations, on-site requirements
  • Business model — service vs product vs distribution; B2B vs B2B2C
  • Ownership — independent, PE-backed, public, family-owned — affects buying motion

Buying signals

  • Trigger events: new C-level hire, recent acquisition or divestiture, IPO/funding, opening a new location, recent rebrand, expansion announcement
  • Vendor signals: posting RFPs publicly, switching costs in last quarterly report, contract renewal windows
  • Operational signals: recent layoffs (cost pressure) or rapid hiring (capacity pressure)
  • News mentions: launching new initiative, entering new market, regulatory change forcing action
  • PR / press: anything that signals "this company is changing right now"

Decay signals

  • Multiple bankruptcies or PE-stripped operations
  • Negative growth + cost-cutting headlines
  • Ownership stagnation (small family-owned, no growth incentive)
  • Buyer turnover (3+ Marketing Directors in 2 years)

Discovery Sources (B2B branch)

Tier 1 — primary discovery

  • Apollo: best general B2B firmographic + contact discovery
  • ZoomInfo: enterprise B2B + intent signals (mid-market+)
  • LinkedIn Sales Navigator: industry + role + signal search; the gold standard for decision-maker mapping (manual)
  • Clay: when you need custom waterfall lookups (e.g., enrich Apollo records with Hunter + Clearbit)

Tier 2 — industry-specific directories

  • Crunchbase / Pitchbook: funded businesses
  • D&B Hoovers: large traditional B2B firmographics
  • State / national business registries: for verified incorporation data
  • Industry association membership rosters: trade groups often publish member lists
  • Trade show exhibitor lists: signals active participation in a vertical
  • Procurement databases (Procore for construction, e.g.): vertical-specific signals

Tier 3 — trigger event monitoring

  • Google Alerts / Feedly: trigger keywords ("acquired," "hires," "expansion," "raises," "announces")
  • PR Newswire / Business Wire: company-controlled announcements
  • SEC filings (public companies): material change disclosures
  • State filings: new entity formation, dissolution

Qualification Checklist (B2B branch)

  • Industry / vertical matches ICP (use a recognized classification if possible)
  • Company size within range (employees or revenue)
  • Geography fits
  • At least one trigger event in last 90–180 days
  • Decision-maker role exists (CEO, COO, VP Operations, Director of X — match buyer profile)
  • Email contact verifiable (named role > info@ catchall)
  • Source URLs captured for firmographic claims
  • No disqualifiers (closed, acquired-paused, multi-bankrupt, off-ICP)

Output Columns (B2B branch)

Recommended CSV columns:

score,company,domain,industry,naics_code,size_band,revenue_band,country,city,trigger_event,trigger_date,contact_name,contact_title,contact_email,email_status,linkedin_url,source_urls,why_prospect,confidence,verified_date,notes

For chat table, condense to: Score | Company | Industry | Size | Trigger | Contact | Email status | Confidence.


Top Outreach Targets Selection (B2B)

Prioritize for the top 3–5 hot leads:

  1. Trigger event recency — 30 days beats 6 months
  2. Trigger event specificity — new CMO hire in your buyer's role beats "company in the news"
  3. Decision-maker access — named contact with verified email + LinkedIn beats role-only
  4. Vertical fit precision — exact NAICS match beats "adjacent industry"

Each top target rationale names the trigger and decision-maker: "Hired new VP of Marketing 14 days ago; verified email; mid-market manufacturer matching ICP."


Common Mistakes (B2B)

  1. Treating B2B like SaaS — funding rounds matter less; PE ownership and acquisition activity matter more.
  2. Trying to verify private company revenue precisely — most public databases approximate. Use size bands, not point estimates.
  3. Ignoring procurement complexity at enterprise scale — your prospect contact list may not include the actual approver.
  4. Cold-emailing executive assistants — they're not the buyer and they will flag your outreach as spam.
  5. Source URL hygiene — without source lineage, you can't defend a contact under GDPR DSAR or CAN-SPAM challenge.
  6. Stopping at one source — Apollo can be 60% accurate on small businesses. Cross-verify with LinkedIn or the business website.