👋 Hi, it’s Rick Koleta. Welcome to GTM Vault - a breakdown of how high-growth companies design, test, and scale revenue architecture. Join 27,000+ operators building GTM systems that compound.
This episode in the Library: the written playbook, the stack and the full transcript, free and open. Open it at pro.gtmvault.co.
Someone gave every rep a Claude license. Every team built its own ChatGPT project. Now the same question gets two different answers depending on who you ask. One customer had a rep pitch a product line that did not exist because ChatGPT made up SKUs the company had never sold. The model was not the problem. The agent was not the problem. The architecture underneath was.
Alex Bilmes built Endgame to fix that architecture. Alex was the first hire at CloudAbility (acquired), founded Reflect (acquired), and ran one of the early product-led sales CRMs with customers like Figma, Loom, Calendly, and LaunchDarkly. He has raised over $47M for Endgame, with customers including Braze, Scale AI, BetterUp, and Monte Carlo. Monte Carlo reached 80% AI adoption across its GTM team running on the platform.
Endgame is a context graph for go-to-market. It pulls everything (CRM, Gong, email, Slack, methodology, enablement, policy docs) into one source of truth and pre-processes that data upstream of any agent or human asking a question. It runs fact extraction and compression, builds dense one-pagers per account, and serves the graph through a single MCP server that any tool can plug into. The architectural premise is direct. Most AI GTM stacks fail because every agent makes a different set of tool calls at read time. Accuracy is low, cost is high, answers are inconsistent. The fix is not better agents. It is a unified context layer underneath them that does the synthesis once and serves it to everyone.
In GTM 46, Alex breaks down why revenue is the GTM function furthest behind on AI despite being the function that makes the money, why the investment mix on what to do versus doing it is 80-20 in favor of knowing what to do, and the new function that controls how every rep sells. He explains why agentic hellscape is the default state of most enterprises right now, why revenue per employee is the metric every CRO is laddering to, and why the best leaders are now the ones spending nights and weekends building with AI on their own accounts.
This is not a conversation about better AI tools. It is a conversation about the architecture that determines whether every tool you bought produces leverage or sprawl.
Inside this episode
This episode maps the structural gap between how most enterprises adopted AI in GTM and what the architecture has to become when every team is shipping agents, every rep is using ChatGPT and Claude, and the same question is producing different answers across the org.
Alex starts with the pattern he keeps seeing inside enterprise customers. Someone gave every rep a Claude license. Every team built its own ChatGPT project. Marketing has its own context, sales has its own, customer success has its own, and none of them share. The result is what he calls agentic hellscape. The same question gets two different answers depending on which department you ask. One of his customers had a rep pitch a product line the company did not sell because ChatGPT, working with nothing connected to it, fabricated SKUs the rep then pitched to a real customer. The fabrication is not a model bug. It is the predictable output of an agent with no context.
We go deep on why revenue is structurally the hardest GTM function to automate. Engineering is the furthest ahead. Teams are running Cursor and Claude Code with agents writing most of the code. Legal moved fast through Harvey and Legora. Support has Sierra and Decagon running autonomous workflows. Revenue lags every other function because the context to sell to a single account lives in Salesforce, Gong, email, Slack, methodology playbooks, pricing rules, packaging, and policy contradictions all at once. The data is not just fragmented. It is also messy, contradictory, and updated by different people at different cadences. No model can reason its way through that without a synthesis layer underneath it.
We cover why connecting Claude directly to MCP servers does not solve the problem. If the agent has to query Salesforce, Gong, email, and Slack at read time for every question, three things go wrong. Accuracy degrades because the agent is doing needle-in-a-haystack search across fragmented sources. Token costs blow up because every question pre-loads massive context. Consistency collapses because two reps asking the same question get different answers depending on how the agent navigated the tool calls. Endgame’s architectural play is to move all of that upstream. Run fact extraction once. Build a dense, fact-checked one-pager per account. Serve the same compressed context to every agent and every human. The agent stops searching. It starts reading.
We go into the function Alex calls the most slept-on opportunity in AI for go-to-market. Whoever curates the context layer controls how every rep sells. He half-jokes the title is chief propaganda officer. The joke is funny. The function is real. This is the person who teaches the agent what plays to run, what discounts apply under which conditions, what the methodology is, what the company will not do. Most knowledge bases contain contradictions on basic policy questions. Do we allow this discount? It depends on segment, contract size, and quarter. The function pre-processes those contradictions into directives the agent can act on. Some of his customers run it through enablement. Some through ops. One customer just created a new AI go-to-market leader role and staffed it from solutions architecture. The title is fluid. The function is not. In a world where every rep asks the agent before talking to a customer, whoever feeds the agent is shaping the entire sales motion.
We cover what AI is actually doing to GTM org design. Smaller teams. Flatter orgs. Fewer specialists, more generalists. Full-cycle AEs replacing land-and-expand handoffs because the agent does the prep and analysis work that used to require a separate role. One of his customers replaced most of their SDR function with a go-to-market engineer, the Endgame MCP, and a handful of approval loops. A few people now review the agent’s output and click send. Alex is direct that this is not a one-to-one headcount swap. It is a structural compression. The metric every CRO is laddering to underneath all of this is revenue per employee. Revenue per employee is the new endgame.
We go into the structural argument underneath the entire AI GTM conversation. Doing stuff is easy with software. Doing the right thing is very, very hard. The current narrative is that agents should do more, autonomously, faster. Alex thinks that is missing the point. The investment mix on what to do versus doing it should be 80-20 in favor of knowing what to do. Most teams have it inverted. They scale autonomy on top of bad instructions and end up shipping faster against the wrong assumptions. His example: you buy an AISDR, you send 10 million emails, you get no conversion, you burn your domain, and your competitors still win. Doing more is not the same as doing the right thing. Architecture decides which one happens.
We go into build versus buy. The shape of the question changed. Six months ago, building meant standing up a custom data pipeline and a fine-tuned model. Today building means a forward-deployed engineer connecting Claude to a few MCP servers. Alex’s argument is that the connect-and-ask approach works for one rep on one question. It collapses the moment a team tries to scale it because everything happens at read time. His honest answer on what to buy: almost nothing. Maybe payroll. Maybe a database. Maybe a context graph (because building one requires data engineering, applied AI, and domain expertise compounded over years). And maybe a f…
This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.gtmvault.co/subscribe
Altri episodi di "GTM Vault"



Non perdere nemmeno un episodio di “GTM Vault”. Iscriviti all'app gratuita GetPodcast.








