The Hog GTM brain

category

market profile

• text: Agent builders often combine separate web search, scraping and data enrichment providers to ground workflows in current information.
• text: The product is in a full beta with a waitlist, so published self-service terms do not guarantee immediate access.

personas

• title: AI agent engineer
  pains:

  • Maintaining multiple data APIs slows product development
  • Stale or unstructured web data degrades agent output
• title: GTM engineer or revenue operations lead
  pains:

  • Account and contact enrichment are spread across tools
  • Sales signals change before static prospect lists are refreshed
• title: Head of growth at a B2B startup
  pains:

  • Small teams cannot manually monitor every target account
  • Research and data subscriptions add costs and handoffs

icp

• text: Software and AI companies building production agents or workflows that require live web, people and company context.
• text: Lean B2B growth teams needing enrichment and account monitoring; enterprise teams may require security review and dedicated capacity.

message pillars

• text: Consolidate search, enrichment and monitoring in one integration.
• text: Equip agents with current context.
• text: Deliver structured outputs that agents can use.
• text: Control API consumption with metered rates.

objections

• objection: Will data coverage and freshness beat our current providers?
  response: Benchmark target accounts and key endpoints against existing sources, measuring match rate, freshness and latency.
• objection: Could agent usage create unpredictable costs?
  response: The pricing page describes endpoint rates and a configurable monthly spend cap; model expected workload before deployment.
• objection: Can we start immediately?
  response: The site says the beta is full and invites users to the waitlist; confirm access timing directly.

competitors

• name: Exa
  why: Search and entity retrieval API for AI agent research.
• name: Tavily
  why: Agent-focused web search and extraction API.
• name: Apollo
  why: People and company search and enrichment overlap the GTM data endpoints.
• name: Clay
  why: Enrichment waterfalls and workflows address related GTM data aggregation needs.

influencers

• name: Hudson Liao
  url: https://www.linkedin.com/posts/hudsonliao_what-a-way-to-launch-our-api-to-the-world-activity-7463310638489165825-3nh8
  why: Co-founder and CEO explaining the API launch and positioning.

keywords

• web intelligence API
• AI agent web search API
• company enrichment API
• people data API
• real time sales signals API
• web scraping and monitoring API
• GTM data waterfall

voice

• developer-oriented
• direct and pragmatic
• growth-focused

signals

• text: A team is building agents and integrating several search, scraping and enrichment providers.
• text: A GTM team is launching account monitoring or signal-based outbound and needs current structured data.

stack

• REST API
• JSON

pricing

motion

channels

• developer documentation
• LinkedIn
• launch content
• website waitlist

confidence

Founders

• name: Hudson Liao
  title: Founder/CEO
  role: CEO
  bio: Hudson Liao is a growth operator with nearly 15 years in GTM and a 5× first growth and marketing hire. He took one startup from ~$900k to $7M+ ARR in 3 months, led another from two months of runway to profitability, and built repeatable playbooks across search, social, outbound, partnerships, and product-led motions. He is the GTM person you call when outcomes matter.