Model for the token, not the table

A dbt blog post argues that enterprises should avoid using Gong’s transactional API as a high-volume AI context source and instead ingest call data into a warehouse, model and compress it with dbt and warehouse-native AI functions, and expose the results through a dbt MCP server. Direct retrieval of dozens of raw transcripts can consume roughly 240,000 tokens per account query and rapidly exhaust Gong API limits, whereas structured summaries can reduce transcript volume by 20 times or more, with a 10,000-token call compressed to roughly 500–1,000 tokens. The post estimates that this approach can lower AI context costs substantially, citing annual savings of hundreds of thousands of dollars for large sales teams or always-on agent workflows, while also enabling joins with CRM, billing, product, and other warehouse data. It distinguishes among Gong’s official MCP for quick account briefs, an API wrapper for one-off raw transcripts, and dbt’s warehouse-based MCP for filtered, aggregated, joined, trend-based, and governed analytical questions. Although the approach requires upfront modeling work, the author presents it as a reusable pattern for other durable, token-heavy sources such as Slack logs, emails, support tickets, contracts, and marketing materials.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.