Break the buy-a-tool reflex in three steps. First, default to what you already own and extend it before buying. Second, require a business case that names the missing capability and the revenue it gates. Third, run competitive proofs of concept, not vendor demos. This is a procurement discipline, applied from your next decision onward, not a project.
The reflex to solve every gap with a purchase built a 10,000-tool market and the 49% utilisation rate behind it. You cannot un-buy the tools you already own. You can stop the next reflex buy, and get value from the ones sitting idle. This playbook is the operating sequence for both.
Step 1: default to what you already own
Before any vendor search, run an owned-capability audit. This is the step teams skip, and it is the one that closes most gaps for free.
List every tool you pay for. Next to each, write what it can do, not what your team currently uses it for. The gap between those two columns is your idle capability. Marketers are routinely over-bought and cannot show value for what they hold (AlixPartners via Marketing Week), and this audit is where that hidden value surfaces.
Then match the new gap against that list. Nine times out of ten, a feature you already pay for covers it, or a tool one team runs can serve another. Extend before you buy. If the gap is genuinely unowned, you have now proven it, which is the entry condition for Step 2.
Owner: a named person in marketing operations, working with whoever owns the martech stack. Measure: number of gaps closed with owned tools versus new purchases, tracked each quarter. A healthy ratio bends toward owned.
Step 2: require a business case that names the revenue
If the audit proves the gap is real and unowned, the purchase still has to earn its place. The filter is a business case, and it has three mandatory parts.
One, the specific capability missing, stated plainly. Not “better analytics” but “match rate on anonymous web sessions to known contacts”. Two, proof from Step 1 that no owned tool covers it. Three, the revenue the capability protects or grows, with a number attached.
That third part is the one that kills reflex buys. Most cannot survive it, because most were never tied to a result. If nobody can name the revenue at stake, the purchase is not ready, and you have just saved the licence, the integration work, and the overlap.
Owner: the budget holder signs, but the requesting team writes the case. Measure: every purchase above a set threshold has a named revenue line before it reaches a contract. No case, no buy.
Step 3: run competitive proofs of concept, not demos
A vendor demo is theatre. It runs on the vendor’s data, follows the vendor’s script, and is built to hide the tool’s weak points. You learn nothing about whether it works for you.
Replace it with a competitive proof of concept. Shortlist two or three tools. Give each the same real slice of your data and the same real task, the one from your business case. Score them on outcomes you define in advance: match rate, time to first result, fit with the tools you already run. Set a time box of two to four weeks so it does not drift.
Buy the tool that produced the result, not the one that presented well. Running two or three in parallel costs a little more upfront and saves you from a multi-year contract on the wrong choice. It also surfaces integration cost early, before you have signed, which keeps you off the integration debt treadmill.
Owner: marketing operations runs the proof; the requesting team scores it. Measure: purchase decisions backed by a hands-on test on your own data, not a demo.
How to train your team to hold the fix
A discipline that lives in one person’s head dies when that person is busy. Make the three steps the default path, so following them is easier than skipping them.
Put the business case template where purchases start. If a request cannot fill in the three parts, it does not move. That turns the filter from a person saying no into a form that will not submit.
Reframe what good looks like. The reflex rewards visible buying, so reward the opposite out loud. When someone closes a gap by turning on an owned feature or extending a tool, name it in the same forum where purchases usually get the applause. People repeat what gets recognised.
Run a quarterly owned-capability review. Thirty minutes, every tool owner in the room, one question each: what does your tool do that we do not use. This keeps the audit alive and keeps idle capability visible, so it gets used instead of duplicated by the next buy.
Give the discipline air cover. Procurement discipline slows the person who wants to buy today, and that person needs a leader to back the delay. Without that backing, the reflex wins on urgency every time.
Where Morphy helps
We run a four to eight week engagement that installs this discipline and pays for itself on the first avoided purchase.
We start with the owned-capability audit: every tool you pay for, mapped against the jobs you need done, with the idle capability surfaced and a shortlist of gaps you can close without buying. Then we set up the business case filter and the competitive proof of concept format, and run the first one live with your team so the method sticks.
The metric we hold ourselves to is simple and honest: gaps closed with tools you already own, and reflex purchases stopped before contract. We do not promise a fixed saving, because it depends on your stack. We do promise you will leave able to run this without us, from your next tool decision onward.
Go deeper on customer data maximization
Three ways forward. Pick the one that fits where you are.
- Get the playbook. Practical notes on turning the customer data you already own into revenue, straight to your inbox. Join the newsletter at the foot of this page.
- Take the assessment. Score your customer data maximization in four minutes and see your top revenue blockers. Start the assessment →
- Book a meeting. Bring your data problem. Leave with a prioritised fix, not a platform pitch. Book a call →
The playbook companion to Stop buying a tool for every gap. Use what you already own first. Post 20 of 25 in the Customer Data Maximization series.
Frequently asked questions
How do you audit martech capability you already own?
List every tool you pay for, then map its features against the jobs your team actually needs. Ask each tool owner what it can do that nobody uses. Most gaps close here. Marketers are routinely over-bought and cannot show value for what they hold (AlixPartners via Marketing Week).
What must a martech business case include?
The specific capability missing, proof that no owned tool covers it, and the revenue the capability protects or grows. If nobody can name that revenue, the case is not ready. This is the single filter that stops most reflex purchases before they reach a contract.
How do you run a competitive proof of concept?
Shortlist two or three tools, give each the same real data and a real task, and score them on outcomes you define in advance. Set a time box of two to four weeks. Buy the one that produced the result, not the one that presented best in a scripted demo.
Is fixing the buy-a-tool reflex a big project?
No. It is a procurement discipline, applied from your next decision onward. There is no platform to install and no rip-and-replace. You add three rules to how you buy, and the savings and reduced integration debt start with the very next tool decision you face.