The Agentic Decision Framework: Build, Buy, or Platform
Building got cheap. Deciding got hard. A teardown of the (one of the) most expensive tools in your stack.
When we were kids, the rules of life were hard and fast. Don’t run with scissors. Don’t go swimming after you eat. Don’t stick metal things in the wall socket. Don’t put forks in the microwave. And don’t build your own software.
Hold our beer.
We’re about to run with the scissors straight into that wall socket. Because one of those rules just stopped being true, and most growth leaders haven’t noticed yet.
Start with the list
Before you read another word, do one thing. Open a spreadsheet. List every tool in your stack and what you pay for it. Every subscription. Every seat. Every “platform fee” you forgot you signed up for. Estimate if you have to. Nobody’s grading the math.
We call it the Grail list. It’s the most uncomfortable hour you’ll spend this quarter, and it’s the most useful.
Here’s why it works. You cannot make a single smart decision about build, buy, or anything else until you see the whole bill in one place. Most leaders never do. The spend is scattered across departments, buried in annual contracts, hidden behind names nobody remembers approving. You feel the pain at budget review. You never see the shape of it.
Make the list. Now cross off the three you can’t touch yet. Your CRM, because the whole company runs on it. Your marketing automation platform, because unwinding it is a year of your life. Your data provider, the ZoomInfo line because you haven’t fully deployed Cannonball GTM yet (clears throat).
What’s the next biggest number?
For most revenue teams, it’s the conversation intelligence line. It’s Gong. Ouchie.
What you’re actually paying
Gong doesn’t publish pricing. There’s no self-serve plan. No sandbox. Every deal runs through a sales cycle, and what shows up at the end is a three-part bill most buyers never saw coming.
A per-user license. A platform fee that doesn’t care how big your team is. And an implementation charge.
Run the math for a 50-person revenue team. Licenses land around $76,000. The platform fee adds up to $50,000 on its own. Onboarding, another $15,000. Year one comes in around $140,000. Go for the full stack with Forecast and Engage bundled in, and you’re north of $200,000.
That’s $235 per user per month, before anyone has booked a single meeting off it. And the contract locks you in for two to three years, with an auto-renewal uplift baked in so the number only goes up.
That’s what you’re paying. Now look at what it does.
What Gong actually is
Strip away the category language and the revenue-intelligence branding. At its heart, Gong is three things.
It records and transcribes your calls. It dumps those transcripts into a repository. And it reads them against a sales methodology to tell your reps what they missed.
That’s the product. A transcription service, a place to put the transcripts, and a coaching layer on top.
Here’s the part that should make you angry. The one thing Gong should be brilliant at, asking the whole pile of conversations a hard question, is the thing it’s worst at. Try to query a Gong database for the common pains your buyers raised last quarter. Good luck. The metadata is thin. The trends are buried. You’re paying $140,000 for a system that captures everything and tells you almost nothing about the pattern.
So we asked the obvious question. What would it cost to build it ourselves?
The rebuild
We’re going to walk this in three steps, lazy to sophisticated. Watch the cost.
The lazy version. Granola for transcription, fourteen dollars a month. Claude to do the reading. Your existing CRM to hold the output. You build a small coaching component that takes the transcript, checks it against whatever methodology you run, MEDDIC, BANT, SPICED, whatever, and tells the rep what they should have said. Three tools. It runs in perpetuity. It’s janky. For a small team, it works.
The real version. Now you add a database so you’re not capped, Supabase or Mongo, somewhere to actually keep the transcripts at volume. You add a workflow step that moves the data automatically. And you have Claude read across every transcript to build pain footprints and keyword maps, the trend layer Gong never gave you.
The sophisticated version. Add a vector layer, Pinecone or similar, so you can ask the whole corpus real questions and get real answers. Add structured analysis that gets better over time instead of starting cold every run. This is the part that beats Gong at the exact thing Gong is bad at.
And here’s the kicker. You don’t need a frontier model for any of this. “Did this rep follow the methodology” is a Haiku-class question. The cheapest, dumbest model on the menu does it fine. A guy named Bernie in a back room could run it.
So what does it cost? For a normal team, somewhere around $700 a month. Push it to the most fantastical scenario, big team, sloppy token use, nothing optimized, pure jank, and maybe you hit $1,000 to $1,500 a month.
Fifteen hundred a month against a hundred and forty thousand a year. That’s the gap. That’s the whole post.
Now the part nobody selling you a weekend build will say
We are not telling you to go build Gong. Read that twice.
The cost of building collapsed. The cost of maintaining did not. The moment you build that system, you own it. When it breaks, you fix it. When the API changes, you fix it. When the person who built it leaves, and it lived in their head, you’re stuck holding a system nobody understands. We can build almost anything now. The question that still matters is the old one: how well does it actually work for the people who have to use it every day?
And there’s a real reason to buy Gong, a reason that has nothing to do with the technology. Governance. Security. Support. A vendor on the hook when it fails. A system that doesn’t walk out the door when one person quits. For a lot of companies, that’s worth six figures. For a lot of others, it absolutely is not.
That’s the decision. Not “can I build it.” You can. It’s “should I own this, or should I rent the governance.”
The three questions that fall out of this
You don’t need a Gong teardown for every tool on your Grail list. You need the pattern. Three questions answer most of it.
How complex is the motion? Simple, repeatable motions, the kind packaged software automates, are the easiest to rebuild. The more sophisticated and specific your motion, the more the math tips toward owning it, because no vendor flexes to fit you.
What’s the gap between replacement cost and replaced cost? If you can rebuild it for a fraction of the annual license, the vendor isn’t selling you technology. They’re selling you a pricing model. Gong fails this test by a mile.
How good is your source of truth? This is the one that humbles everyone. Clean data and a real source of truth raise your ceiling, you can build almost anything. A fragile, duct-taped source of truth caps you, and forces you to either buy your way out or accept lag you build around. Most teams are worse off here than they think, and it’s the thing that decides what’s actually possible.
Run the list
The rule we grew up with, don’t build your own software, was true for thirty years. It isn’t anymore. Building got cheap. Deciding got hard. The value moved from the building to knowing what’s worth owning in the first place.
So make your Grail list. Find your Gong. Do the math on the gap. And before you build a thing, ask the question that actually matters now, the one about governance, because that’s where the next decision lives.
That’s the next post.
—-------------------------------------------------------------------
New to Cannonball GTM? We help growth leaders find hidden buyers using publicly available data and figure out which tools, agents, and platforms are actually worth your money. Start with our most-read posts:
The Beginner’s Guide to Cannonball GTM — Start Here
Keep reading
This post is part one of a series on building, buying, and surviving the agent era.
Start at the beginning with The Agent Landscape for Growth Leaders, the rubric, and the decision table that maps fifteen use cases against build it yourself, build it on a platform, or buy it.
Next up: The Pragmatist’s Guide to Governance, where we get into the real reason to buy instead of build, and how to keep a system you built from walking out the door when the person who built it quits. [Coming soon]
 | A guest post by
|