Field notes
The most expensive tool is the one you bought two years too early.
What to buy at pre-seed, seed and Series A, and what to refuse. A tool does not give you a process - it hard-codes whichever one you had. Buy for the stage you are in.
Buy tools for the stage you are in, not the one you are hoping for. At pre-seed and seed you need little beyond a CRM and a way to talk to customers; a tool bought too early just hard-codes a process you have not figured out yet.
On this page
The most expensive mistake in early go-to-market is not the tool you are missing. It is the tool you bought two years too early, that quietly designed your process for you.
A tool does not give you a process. It hard-codes whichever one you had when you bought it - including no process at all.
Buy for the stage you are in, not the one on the pitch deck
Pre-seed. A CRM on the free tier. A shared inbox. A spreadsheet. That is genuinely enough to sell your first twenty deals, and every hour spent configuring a bigger stack is an hour not spent talking to a buyer. The goal here is learning, not infrastructure.
Seed. The CRM starts paying its way, plus the first automation - the busywork that is stealing selling time. Enrichment so a record fills itself. Sequencing if the motion is outbound. Buy each of these only when the manual version is provably the bottleneck, not before.
Series A. Now the stack earns real budget: attribution you can defend, a customer-success platform, data warehousing, AI where it beats a rule. By this point you should know your motion cold, so the tools serve it instead of shaping it.
The one rule that keeps a stack from rotting
Your CRM is the system of record. Everything else either writes to it or reads from it. If a tool holds data your CRM never sees, it is not part of your go-to-market - it is a private spreadsheet with a login and a monthly bill.
Every tool you add is another place data enters, another sync that breaks, another field that means something slightly different to someone else. That is how a stack becomes a Franken-stack - not through one bad decision but through ten reasonable ones nobody wrote down.
The test before you buy
Ask one question: what is the current tool provably failing to do? If you cannot answer with a specific, measured failure, you do not need the new tool. You need to use the one you have.
Boring stacks win. A small number of tools that talk to each other beats a large number that argue.
This is one of ten decisions in the GTM blueprint - the go-to-market system we build for B2B SaaS clients, free and written down.
The stack is the third decision in the blueprint - after the ICP and the motion that should drive it.
Get the next one
New field notes twice a month. We don’t do newsletters, follow RevOps XL on LinkedIn instead.
Follow on LinkedIn ↗