Your Vendor Says You'll Need It Later. Here's How to Know.

Apply a 3-part timeline test: name the specific feature, set a concrete activation date, and define the success metric. If any component is missing, you’re not preserving strategic headroom. You’re funding hope.

The Objection Nobody Challenges

Your DXP contract is up for renewal. Personalization was a key selling point when you signed: behavioral targeting, audience segmentation, content variants served by visitor profile. Fourteen months in, nobody’s configured a single personalization rule. No audience segments built. No content variants live. It’s $35K on the annual license. The room is ready to cut it. Then a director says: “We’ll need that when we launch the redesign next year.”

The conversation ends. The personalization module stays on the contract. And nobody asks the 3 questions that would change the outcome: Which personalization rules, specifically? When will the team build and activate them? And what lift in conversion or engagement justifies keeping $35K on the license for another year?

KPMG’s 2026 Global Tech Report surveyed 2,500 technology executives across 27 countries and found that 56% say their tech plans become outdated before implementation [1]. When more than half of all technology strategies are obsolete before they ship, the “you’ll need it later” defense sounds reasonable. Plans change. Requirements shift. Keeping options open feels like prudent risk management.

It isn’t. It’s the absence of a decision disguised as the presence of a strategy.

The Foresight Illusion

The assumption behind every “you’ll need it later” argument is that retaining unused capability equals strategic preparation. It doesn’t. Preparation requires specificity. Retaining everything requires nothing but a larger budget.

PwC’s 2026 Digital Trends in Operations Survey makes the cost of that assumption visible: 89% of operations leaders report that their tech investments haven’t fully delivered expected results [2]. That’s 767 executives at companies generating $100 million or more, surveyed in early 2026, confirming that the gap between technology promise and technology performance is standard operating reality. The causes vary: poor integration, misaligned processes, insufficient training. But unused capability is a recurring contributor, and it’s the one that hides most easily behind strategic language.

The same survey found that 85% of those leaders believe they’re ahead of competitors in digital transformation. The math doesn’t reconcile. You can’t be winning the race and disappointed in the car at the same time. What’s happening is that organizations conflate having technology with using technology, and the “you’ll need it later” argument exploits that confusion by converting unused capability into a talking point instead of a cost.

The Missing Test

The root cause is straightforward: nobody demands specificity.

Darrell Alfonso put it directly in his Substack earlier this year: most martech strategies are “a list of tools in a trench coat pretending to be a plan” [3]. When the strategy document is a tool inventory, there’s no mechanism to stress-test whether a future-state capability belongs on the roadmap or the wish list.

The test that’s missing has 3 components.

Name the feature. Not the platform. Not the category. The specific capability you’re preserving access to. “Advanced personalization” is a brochure term. “Real-time behavioral triggering based on cross-session intent signals” is a feature. If you can’t name it at that level of specificity, the need is hypothetical.

Set the activation date. Not “when we’re ready.” A quarter. A campaign launch. A business milestone tied to a revenue event. The activation date forces an honest reckoning: does the organization have the operational maturity, the data foundation, and the trained staff to use this capability when the time comes?

Define the success metric. What changes in the business when this feature goes live? If the answer is “we’ll figure that out when we get there,” you’re not preserving strategic optionality. You’re warehousing cost.

When a capability passes all 3 components, it’s a strategic bet worth defending in the budget. When it fails any of them, it’s hope dressed up as foresight.

What the Test Reveals

Applying these 3 questions changes conversations in predictable ways.

In vendor evaluations, the “you’ll need it later” objection collapses under specificity. Vendors who can’t help you name the feature and the activation date are selling optionality they can’t deliver. The ones who can are partners worth keeping on the shortlist.

In internal business cases, the test exposes a pattern that repeats across organizations: teams requesting capability they don’t have the operational infrastructure to activate. The constraint isn’t in the platform. It’s in the organization. Eighteen months later, the contract renews and the capability still sits dormant because nobody built the workflow, trained the team, or connected the data sources that would make the feature operational.

At the corporate level, the consequences compound. When EverCommerce divested its entire Marketing Technology Solutions business in Q3 2025, the forward guidance excluded that unit entirely [4]. Divestitures happen for many reasons, but the pattern is consistent: technology assets without clear activation plans become the first candidates for the cut.

From Hope to Homework

The timeline test doesn’t eliminate strategic bets. It elevates them. A bet that survives the test earns its place on the roadmap and its share of the budget with evidence attached. A bet that can’t clear the bar gets reclassified as what it is: an expense without a plan.

The distinction matters because the organizations that separate headroom from hope are the same ones that can defend their technology investments under scrutiny. They’re not spending less on martech. They’re spending on capability they can name, date, and measure.

The next time someone in your organization says “we’ll need that in 18 months,” don’t argue. Ask 3 questions. The answers will tell you whether you’re looking at headroom or hope. And the difference between the two is the difference between a strategy and a line item.