Grizz Company Enrichment API vs OpenGTM

Grizz Company Enrichment API accepts a company name or domain and returns enriched company information. Documented fields include company name, domain, NAICS code, location, ERP and ATS signals, and, when available, employee range, address, phone, email, LinkedIn URL, and an AI-generated description. Existing database matches return immediately; unknown domains are scraped and classified with AI, typically within 60 seconds. Requests use an asynchronous submit, status-polling, and results-fetch workflow, with a bulk endpoint for completed unretrieved requests. Organizations have a monthly call limit set by Grizz, and the bulk endpoint returns up to 100 records by default, with 500 as the maximum. The API is in beta, so endpoints, fields, and rate limits may change. It is aimed at construction technology sales and marketing teams, tracks more than 100 construction technologies, and refreshes technology signals weekly.

OpenGTM is an open-source, self-hosted workspace for go-to-market teams and their agents. It handles lead sourcing and enrichment, AI research with cited answers, buying-intent tracking and sending qualified records to other tools. Workbooks combine imports, formulas, HTTP columns, enrichment waterfalls, AI research and output columns, with estimated spend visible before runs. Teams can segment live audiences, monitor hiring and buying signals, and schedule refreshes and automations. Listed activation destinations include HubSpot, Salesforce, Slack, Sheets, Airtable, Instantly, Smartlead, webhooks, warehouses and consent-gated ad audiences. The workspace is also available through REST, webhooks and an auditable MCP server with scoped read and write access. The project says data remains on the user's infrastructure and external calls use provider keys selected by the user. Teams can set workbook budgets to stop paid calls at a ceiling, although provider charges may apply. The software is free under AGPL-3.0. Installation requires Git, Docker with Compose v2 and roughly 4 GB of RAM. The project is pre-1.0; public multi-tenant hosting needs further work beyond team-controlled Compose deployment.