Mango GTM
AI-powered GTM execution: Product Advisor chat, demo routing, lead scoring, and CI-grounded prospecting.
MangoApps
Overview
Mango GTM owns the revenue-side lifecycle β Product Advisor conversations on the marketing site, Book-a-Demo requests with HubSpot sync and geo-based routing, deterministic lead scoring with LLM rationale, and a Prospecting Agent that drafts outbound email grounded in Mango IQ battle cards and content briefs. Mango IQ sees the market; Mango GTM acts on it.
Highlights
Capabilities
Inbound Intelligence
-
Product Advisor chat conversations (visitor-facing on marketing site)
-
Cross-session visitor history with ZoomInfo company enrichment
-
Automatic CI context extraction (competitor, content gap, feature comparison, market theme)
-
Buying-intent detection from conversation patterns
-
Nano-tier LLM topic gate filters off-topic/jailbreak attempts before RAG cost
-
CI context extractor model tier: Nano (fast, cheap) with heuristic fallback
Demo Request Management
-
Public Book-a-Demo form with honeypot and rate-limit protection
-
Full lead lifecycle stages (new β contacted β qualified β demo β proposal β closed)
-
HubSpot Form API sync with retry and failure notifications
-
IP-based geo resolution (country, continent) cached 7 days
-
Auto-assignment via priority-ordered routing rules
-
Round-robin, least-busy, or specific-admin assignment modes
-
CSV bulk import with field validation
-
High-priority flag auto-set from Product Advisor buying intent
Lead Scoring & Prioritization
-
Deterministic numeric score (0β100) with tiered banding
-
Scoring signals: buying intent, visitor profile, CI context depth, company size, geo, routing match
-
LLM-generated score rationale (prose, not numeric)
-
Similar-prospect search via pgvector over visitor extracted data
-
Scoring provider: Deterministic (reproducible across reruns)
-
Rationale model: Medium tier (OpenAI via RubyLLM)
Prospecting Agent
-
Natural-language chat interface for GTM workflows
-
Outbound email drafting grounded in CiCompetitorProfile battle cards
-
Follow-up drafting referencing visitor journey (pages viewed, questions asked, competitor mentioned)
-
Hook types: feature_gap, competitor_win, content_topic
-
Outreach channels: email, linkedin
-
All drafts persist with full generation audit trail (model, prompt, rationale)
-
Automatic publishing to HubSpot v1: internal "mark published" flag only; HubSpot Engagement write-back on roadmap
GTM Activity & Reporting
-
Unified timeline of advisor conversations + demo requests
-
Filter by competitor, content gap, feature comparison, market theme, buying intent, high priority
-
Admin dashboard with lead funnel analytics
-
My Leads view for individual assigned reps
Integrations & Platform
-
Reads Mango IQ canonical data (CiCompetitorProfile, CiFeatureComparison, CiContentGap, market themes)
-
Reuses Mango IQ BriefBacklogService for outreach hooks
-
Reuses Mango IQ EvidenceBundleService for testimonials/case studies
-
HubSpot Form API (portal-configurable)
-
Anthropic Claude and OpenAI via RubyLLM / LlmConnectionManager
-
Apollo / Clay / Clearbit external contact discovery Seam defined; integration deferred to a future release
Use cases
FAQ
Mango IQ observes and analyzes the competitive market (competitors, feature matrix, content gaps, keyword opportunities). Mango GTM acts on it β owning the revenue-side lifecycle from anonymous visitor chat through demo request, scoring, and outbound prospecting.
No. The Product Advisor widget and the Book-a-Demo form on www.mangoapps.com are unchanged, along with all submission endpoints. Mango GTM only adds admin-side surfaces and agent tools.
Mango GTM runs without Mango IQ, but loses most of its value without competitive context. The Prospecting Agent, CI context filtering, and score signals all pull from Mango IQβs canonical services.
v1 persists all drafts as CiProspectOutreach records with an internal "Mark Published" flag. Direct HubSpot Engagement write-back and automated sending are on the roadmap.
The interface seam (ExternalProspectProvider) is in place for Apollo/Clay/Clearbit-style integrations. Integration work is deferred until v1 dogfooding validates the inbound-first workflow.
Access is role-gated via the "mango-gtm" app admin permission. Super admins implicitly have access. Non-admin reps can see their assigned leads (My Leads) but not routing rules or outreach generation.