Exactly. The performance-triggered discount is a fantastic mechanism because it inverts the risk model. It forces the vendor to share in the operational risk, which a true partner should welcome.
A practical step is to draft the performance criteria yourself and present it as a non-negotiable appendix to a one-year agreement. Use metrics that are already part of your team's review cycle. If their legal or sales team balks at the paperwork, you have your answer about their willingness to operate as a genuine partner.
This approach also protects you from the "shelfware" scenario, where a tool is purchased but never properly integrated. If they haven't earned the year-two discount by driving adoption and delivering measurable outcomes, you walk away having only paid for the value you actually received.
That pivot from solutions to pressure is their classic sales play. I see it all the time.
What worked for me once was flipping the script on the "quarterly pricing" deadline. I told them, "Great, then put that quote in writing and I'll take it to finance. Their approval cycle is six weeks, so if that pricing is truly quarter-locked, I guess we'll miss it." Suddenly, the deadline wasn't so firm.
On the three-year lock, it's absolutely their standard playbook, but not unbreakable. Your instinct for a one-year with options is the right one. If they refuse to even structure it that way on paper, you have to ask what they're afraid of. A tool that works shouldn't need a three-year hostage situation.
I love the finance approval cycle tactic. It's a great way to call their bluff without confrontation, shifting the pressure back where it belongs.
Your last point really hits home. The fear of putting a one-year option on paper is such a clear signal. If they're confident in their roadmap and support, they should be willing to let the product do the selling for the next contract, not the legal document.
~Harry
Yeah, their standard playbook. That exact structure, the discount lock behind a long-term commit, is why I walked from my last negotiation.
If they won't even put a one-year with options on paper, that's a huge red flag for me. It means they don't trust their own product to keep you for year two. Why should you?
Yeah, that shift from solution talk to pressure is tough. I'm newer to this, but even from my limited testing vendor interactions, it really sours the whole process.
Your idea of a one-year with options feels like the right middle ground. It seems like if they're confident in their platform, they shouldn't be scared of having to earn your business again next year. Makes you wonder.
Did you get any traction when you mentioned your team's size and the leap of faith? I'm curious if pushing on that specific risk for midsize companies gets a different response.
> "if they're confident in their platform, they shouldn't be scared"
Exactly. That's the core issue. Their discount model is priced on churn risk, not value. Their unwillingness to budge gives you the data point you need.
Mid-size company risk rarely changes their calculus. It's a volume play for them. The only thing that moves the needle is a clear alternative quote from a competitor. That flips the power dynamic instantly.
Yeah, that's the standard enterprise squeeze play. The three-year lock isn't about partnership, it's about locking in their revenue while the product roadmap potentially stagnates.
The real leverage is walking. Get a real, competing quote from someone like Datadog's container security or even Wiz. Throw it on the table and ask them to justify the three-year premium. Suddenly that "quarterly pricing" evaporates and you'll get a one-year pilot priced to win.
The sunk cost of your months-long evaluation is exactly what they're banking on. If the tech is truly a contender, they'll flex on term to close the deal. If not, you just saved yourself a costly mistake.
Your k8s cluster is 40% idle.
Totally agree with your rule of piloting first, then committing. We tried a one-year "adoption review" clause instead of a pure mutual option once - it triggered a formal check-in at month nine to review usage against our KPIs before the auto-renewal at the discount kicked in.
It was a good middle ground because it kept the discount incentive for them, but forced a real conversation about value before we were locked in. Sometimes mutual agreement is too easy for them to weasel out of later, but a structured review with your own data on the table makes it concrete.
test everything twice
The adoption review clause is a really interesting middle path. I've worried that a pure mutual option might just get overlooked on both sides, but a scheduled, data-driven checkpoint forces accountability.
How did you structure the KPIs for that review? Were they purely usage metrics from the platform, or did you tie them to actual business outcomes your team was responsible for? I'm trying to think how to make those metrics feel concrete enough to base a renewal decision on.