GTM intelligence /0.2

Platform

An agentic platform with a conversational interface, from ICP to reporting.

/0.2.1

Orchestrator

Each client's data, organized by the people running the operation.

CLIENT DATAORCHESTRATORFDEsONTOLOGYBUILDER

    /0.2.2

    Builder

    You describe who you are looking for. The agent turns it into criteria.

    BUILDERDATASETCRMYOUR TEAM
    1. 01

      A conversation

      Describe who you are looking for, import a list or start from a saved audience. The agent turns your request into criteria and builds the dataset.

      • Natural language
      • Import a list
      • Criteria
    2. 02

      Audiences

      Reusable audience definitions, prioritized by focus. "We sell to construction companies" becomes "property and land developers in São Paulo, 5 to 200 employees, mid- to high-end", ready to start the next session.

      • Focus
      • Nice-to-have
      • Low priority
    3. 03

      Sessions

      The history of your work with the agent: every conversation, the criteria used and each dataset edition, including what changed.

      • History
      • Dataset editions
    4. 04

      For your revenue team

      Qualified accounts reach your CRM with context, signals and a contact path for pre-sales, sales and customer success. The agent handles the manual work and provides guidance; your team approves and acts.

      • Pre-sales
      • Sales
      • Customer success
      • Human in the loop
    5. 05

      Under the hood

      A supervisor delegates each step to specialized agents, with guardrails for scope, moderation and cost.

      • icp-architect
      • company-finder
      • contact-finder
      • enricher
      • qualifier
      • crm-connector

    /0.2.3

    Data & Context

    The accounts that LinkedIn-indexed tools cannot see.

    01020304050607DATA MODELINGTHE ACCOUNTSOURCES01Websearch02Public data03Receita Federal04CVM05Marketplaces06Private databases07Your CRM
    1. 01

      Sources

      Public records, marketplaces, directories, websites, maps, purchased databases and the client's CRM.

      • Receita Federal e CNPJ
      • CVM
      • Google Maps
      • Marketplaces
      • Sites
    2. 02

      Processing

      Clean, normalize, deduplicate, enrich, index and validate until the agreed fill rate is reached.

      • Fill rate
      • Deduplication
      • Enrichment
    3. 03

      Case-by-case analysis

      Agents read each account's website, social profiles, job openings and public records at scale, applying your qualification rules.

    /0.2.4

    Datasets & Analytics

    Every account with a reason. Every step with a cost.

    ICP FITCRITERION BY CRITERIONDISCARDEDWITH THE REASONWORKSPACE FUNNELFROM MAPPED TO ENRICHEDWARM AND COLDCONVERSION AND COST
    1. 01

      Datasets

      Companies discovered and evaluated against your ICP: fit against each criterion, enrichment, contacts and what has been sent to the CRM. Every filter or adjustment is recorded as a dataset edition.

      • Fit
      • Criteria
      • Enrichment
      • CRM delivery
    2. 02

      Workspace funnel

      From mapped to qualified companies, from extracted to enriched contacts, across all sessions. Every stage shows how much was discarded and why.

      • Mapped
      • Qualified
      • Contacts
      • Enriched
    3. 03

      Intelligence

      Alerts derived from the Workspace's own data, ranked by severity and each with a next step: contacts without verified email or phone, qualified accounts that have never been enriched.

      • Critical
      • Attention
      • Opportunity
    4. 04

      Warm and cold outreach

      Prospect-to-opportunity conversion by channel, throughout the funnel and session by session.

      • Conversion by channel
      • Per session
    5. 05

      Cost

      Spend per execution and acquisition cost by channel, so you know where your money goes furthest.

      • Cost per execution
      • CAC by channel

    /0.2.5

    Integrations

    Works with the stack you already have.

    DATA PROVIDERSONE WORKFLOWORCHESTRATORHUBSPOTCONNECTEDCOMING SOONSALESFORCE, PIPEDRIVE
    1. 01

      CRM

      Companies, contacts and deals synced with your CRM. HubSpot today; Salesforce and Pipedrive coming soon.

      • HubSpot
      • Salesforce (coming soon)
      • Pipedrive (coming soon)
    2. 02

      Data providers

      Data providers centralized in a single workflow instead of a fragmented stack paid for separately. The agent chooses which one to query for each account.

      • Apollo
      • Lusha
      • Clay
      • Econodata
      • BigDataCorp
      • BrightData
      • Firecrawl
    3. 03

      With context

      Every account reaches your CRM with its qualifying signal, ICP fit and contact path, ready for your team to act.

      • Signal
      • Fit
      • Contact path

    /0.2.6

    Ontology

    The agent proposes the model. Your team approves each version.

    BUYING SIGNALCUSTOMER PAINPERSONCOMPANYCAMPAIGNOPPORTUNITYCONVERSIONWORKS ATSHOWSFACESGENERATESPROPOSEDCOMPETITORAPPROVEDLOST TO
    1. 01

      Types, not records

      The Ontology is the Workspace's schema: the allowed types, what each means and how they connect. Records live in the Graph, each within its type. The account you will approach is a Company record.

      • Entities
      • Relationships
      • Graph
    2. 02

      How the agent identifies a record

      Each type declares its identifiers, such as a company's website domain. This is how the agent knows two records refer to the same entity and avoids duplicate accounts.

      • Identifiers
      • Domain
      • Email
      • URL
    3. 03

      What is known about each record

      Typed properties with rules: required fields, allowed options and value ranges. Signals and pain points are types of their own, linked to the account through relationships.

      • Properties
      • Validation
      • Relationships
    4. 04

      The agent proposes, your team approves

      Changes begin in conversation. The agent proposes new or revised definitions, and any Workspace member can approve or reject them. The Ontology screen is read-only: nothing changes without approval.

      • Proposal in the conversation
      • Approve or reject
    5. 05

      Every approval, a new version

      Approval publishes the definitions together as the next Ontology version. Records retain the definition version they were created under; no records are migrated.

      • Ontology version
      • Definition version
    6. 06

      Your operating model

      Each Workspace has its own Ontology, reflecting how you sell: campaigns, opportunities, competitors and customer pain points. It grows with each cycle and stays with you.

    /0.2.7

    Code Execution

    When no off-the-shelf tool can solve it, the agent writes the missing one.

    ISOLATED VIRTUAL MACHINESPECIALIZED SOURCESWORKSPACE DATAANALYSIS AND CALCULATIONS
    1. 01

      Process and cross-reference data

      Clean, transform and cross-reference databases beyond the reach of off-the-shelf tools, in the format your operation uses.

      • Transformation
      • Cross-referencing databases
    2. 02

      Specialized sources

      Code that retrieves data from sources unique to your market: portals, websites and APIs beyond standard databases.

      • Scrapers
      • APIs
    3. 03

      Analysis and calculations

      Custom scores, metrics and models calculated from your Workspace data.

      • Scores
      • Metrics
      • Models
    4. 04

      Isolated virtual machine

      All code the agent writes runs in an isolated virtual machine.

    /0.2.8

    Artifacts

    The client folder is the deliverable. Documents are just renderings.

    RESULTS REPORTINTERACTIVEDIAGNOSTICBEFORE AND AFTERSTRATEGYAND PLAYBOOKTHE CLIENT FOLDERTHE SAME FOUNDATION
    1. 01

      Results report

      The cycle on one page: funnel, conversion by channel, cost and generated pipeline, ready to explore and filter instead of reading a PDF.

      • Funnel
      • Conversion
      • Pipeline
    2. 02

      Diagnostic

      A before-and-after view of your market and operation: where the accounts are, what is known about each and what has changed.

      • Before and after
      • Market
      • Operation
    3. 03

      Strategy and playbook

      Where to compete, how to position by segment and how your team executes, in pages that evolve with operational feedback.

      • Strategy document
      • Positioning
      • Playbook
    4. 04

      Generated, not assembled

      Every artifact is generated from the client folder, the same source that feeds the Workspace. No one copies numbers into slides.

      • Interactive HTML
      • Shareable

    Next

    FDE Squad Service ↗