The Operator Manifesto
Bespoke beats opinionated.
What we believe about how go-to-market should be built, run, and owned.
Never be forced into someone else's paradigm.
Modern GTM runs on a pile of expensive, opinionated tools that do not work together. The systems a team actually needs sit stuck behind vendor limits, engineering backlogs, and brittle workarounds — and nobody can see or control the whole thing. Teams pay more every year for a motion they run less of.
Your go-to-market is unique. You should be able to build and run the exact systems your business needs, bespoke to you, on top of the tools and data you already have — without becoming an engineer. Keep the point tools you like, replace the expensive opinionated layer on top with one built for you, and the whole motion starts working as one system your team can actually see, use, and control.
The buy vs build line is shifting.
For decades the answer to any GTM problem was buy a tool or file an engineering ticket, and both paths fail operators now: shelf software was not built for your business, engineers are a backlog you cannot jump, and for plenty of problems there is nothing to buy at all — so they simply go unsolved while everyone tinkers with AI on the side.
Teams now get better outcomes building custom solutions than buying off-the-shelf, because the operator who understands the motion can be the builder. When a problem comes up, the move is no longer find a tool or file a ticket. It is build the exact solution, on the fly, as real production-grade software, centralized where the whole team can use it. Not everything should be built — software that fits perfectly is still worth buying — but the default is flipping, and the teams that learn to build will out-execute the ones that wait.
Tinkering proves the appetite. Shipping proves the value.
AI put building within everyone's reach, and now every GTM team has people tinkering: twelve people building twelve different things in chats, scripts, and no-code. None of it production-grade, none of it visible, and none of it surviving its builder leaving.
The tinkering proves the appetite, but differentiation comes from shipping. Centralize the building in one place — shared context, shared components, every project visible and controlled — or the energy never compounds. The teams that turn their tinkerers into a system will pull away from the ones that stay a collection of side projects.
Every team needs a GTM brain.
Every team's GTM knowledge and data live scattered across tools, docs, and people's heads. Reps improvise, AI output comes back generic and off-brand, and nothing built on top of it can be trusted or scaled. Generic in, generic out.
Every team needs a GTM brain: all the strategy — positioning, messaging, ICP, target lists — and all the data from across the stack in one place, feeding every workflow, every rep, and every AI. It should not take a GitHub repo or a $10,000-a-month consultant to build one. Get the brain in place and everything downstream gets sharper.
The motion is bigger than any tool.
Go-to-market work spans a dozen tools that do not talk to each other, and the workflows that connect them are trapped inside opinionated platforms or brittle no-code chains. Handoffs fall through the cracks and data goes stale between systems.
Every platform claims AI GTM orchestration, but it is orchestration inside their own walls, limited to what that one tool can do. True orchestration runs across the entire stack, on your terms: trigger off anything, act on anything, route, enrich, sync, and automate the whole motion end to end. The motion is bigger than any one tool, and the workflows should be too.
Built for the seat, not the vendor.
Teams will not adopt another vendor's interface, and reporting to leadership still means pulling exports and stitching data together by hand. Good systems go unused and leaders cannot see what is working.
If your team has to learn someone else's tool, they will not use it. The interface should be built around each seat and your motion: give the SDR a clean daily queue, the AE and CSM their pipeline views, and the founder one-look reporting — each shaped for how that person actually works — and adoption stops being a fight. Reporting stops being a scramble, because the systems present themselves.
See it. Cost it. Control it.
GTM now runs on twenty-plus tools and countless workflows, and nobody can see what is running, what is breaking, or what it all costs. Automations fail silently for weeks, AI and data spend creeps with no owner, and the team finds out when the number is off.
If it runs your go-to-market, you should be able to see it, cost it, and control it from one place — the way ops and finance expect of anything else that matters: every system visible, cost tracked per project, failures caught, changes reversible. That visibility is what turns a sprawl of automation into an operation leadership can actually trust and fund.
The test is not the demo. It is month three.
Every tool eventually hits a wall on something unique to your business: it demos well, then two weeks in you hit a limit that matters, and you are stuck waiting on a vendor roadmap or ripping and replacing.
Your GTM is unique, so the layer you run it on has to bend to you: adapt to any use case and extend to any tool, API, or data source, so the system grows with the business instead of capping it. The test of any platform is not the demo — it is month three, when your weirdest, most valuable use case shows up.
Fit the team, not the other way around.
The hardest part of any GTM system is not buying or building it. It is getting the team to actually use it: the contract gets signed or the build ships, adoption stalls, and the investment quietly dies.
A GTM system only creates value when the people in the seat use it, so it has to be easy and built around how they already work, with no engineering skills required to run it or improve it. Make the system fit the team instead of training the team to fit the system, and usage becomes the default instead of the fight.
If you believe it too.
We're building the layer this manifesto describes. Join the waitlist and build it with us.