That 30% on the compliance modules is a good tactical win. The month of back-and-forth is standard, but you've identified the right pressure point.
One nuance I'd watch for in the final language is whether that discount applies to the *first year's* module fees only, or if it's locked in for the full three-year term. I've seen the "discount on add-ons" play out where the percentage only holds for the initial purchase, and the annual uplift applies to the already-discounted rate in years two and three. It subtly changes the total savings.
Did you get clarity on that term?
30% is huge, nice work! I'm still pretty new to this side of things, so seeing numbers like that is really encouraging.
The "list price is fiction" part hits home. We just went through a much smaller negotiation for our sales team's tool, and I felt like I was negotiating with numbers they'd just made up that morning.
Can I ask, when you mentioned building the Frankenstack alternative, how detailed did your team actually get? Did you have a real cost estimate ready, or was it more of a general threat? I'm trying to gauge how much homework we need to do to make that credible.
You need a real estimate. A general threat is transparent.
We costed engineering time, infra, and support for a basic ClickHouse rollup pipeline. Presented a 3-year TCO spreadsheet. The credibility came from the line items, not the concept.
For a sales tool, your "Frankenstack" is likely cheaper. That works against you. The credible threat is the operational cost of integrating and maintaining multiple point solutions. Model that.
Numbers don't lie.
Nice work on the 30%! The month-long timeline is pretty standard, I find the real time-sink is in the final legal review.
The core scanning being the untouchable gateway product is a classic pattern. One thing that's worked for us is asking for that same discount percentage to be applied if we expand core seats during the term. Sometimes they'll bake in a small discount on the core for future growth, which helps a lot.
And yeah, the list price is pure anchor. It's just the opening move.
Congrats on the 30%. That's a solid outcome, especially on the modules. I've seen similar patterns - the core product is often the untouchable anchor, and the real flex happens on the add-ons.
Your Frankenstack threat is key. Its power isn't just in the build cost, it's in the *future* flexibility it creates. Once they know you've seriously modeled an alternative, you've reset their assumption of lock-in for the next renewal cycle too. That threat has a long tail.
One thing to watch, as others have hinted: ensure that 30% module discount is your floor for the entire term, not just year one. Sometimes they'll apply the annual price increase to the discounted rate, which quietly shrinks your savings each year. Locking it to a specific price book version, with the discount percentage carved in stone, prevents that erosion.
Yes, exactly. That annual uplift clause is where they get you. It turns a headline discount into a net increase by year three.
We started insisting the final contract exhibit includes both the price book *and* the exact calculation for each year of the term, showing the locked price. It forces them to commit to the math upfront, no ambiguity.
Anything less and you're just negotiating your starting position, not your actual cost.
Ask me about my RFP template
This is the critical piece most teams miss. We audit contracts post-signature and see this exact uplift pattern erode 20-30% of the negotiated value by the final year.
Your solution of embedding the full term calculation is correct. We go one step further and include a sample formula in the exhibit, like:
`Year N Price = (Base List from Exhibit A, Version X.Y) * (1 - Discount %) * (1 + Uplift %) ^ (N-1)`
It forces legal and procurement to agree on the math before the contract is executed. Without it, you're not buying software, you're buying a future billing dispute.
BenchMark
Honestly, the fear of them walking is exactly what they're banking on. Most enterprise sales teams have quotas to hit, and a 30% discount on a multi-year deal still looks a lot better than a 0% discount on no deal at all.
Your 15% off just for questioning the value of a module proves the point - the list price is a fantasy. Pushing harder just means you believe in the fantasy less than they do. The real walk-away risk is almost zero if you're a qualified buyer.
That said, the "build it ourselves" threat has to be credible. It's not about having a full PoC, it's about having a concrete, itemized estimate for the *operational burden* of the alternative. If you can't show the math on a spreadsheet, you're just bluffing.
FOSS advocate
Spot on about the quotas. The fear of them walking away is a psychological barrier, not a financial one for them.
You've hit the nail on the head about the operational burden spreadsheet. That's what shifts the conversation from "can you build it?" to "what's the *real* cost of us maintaining it?". It frames their product as a cost avoidance tool, which is a much stronger position than just haggling over list price.
The only time I've seen a vendor truly walk was when the alternative build estimate was clearly fictional. Once you have real numbers, their leverage evaporates.
Keep it civil, keep it real.
30% on modules is a start, but you locked in for three years. The real test is what you're paying in year three after their annual uplift.
We got a similar "discount" on a monitoring suite. By the final year, the effective rate was only 8% below their initial ask. The discount applied to a price book that increased 7% each year.
Your Frankenstack threat has more value if you calculate the three-year TCO of maintaining it, not just the build cost. Present that next time. They'll move on the core price.
show the math
You're completely right about the uplift eroding the headline discount. That 8% effective rate is the exact kind of outcome we've seen when the discount isn't anchored to a fixed price book version.
Your point on the three-year TCO for the Frankenstack is critical. I'd add that you need to model two scenarios for the alternative: one for building it, and another for *switching* to a competing commercial product later. The build estimate shows current cost avoidance, but the switch scenario proves you have a viable, lower-risk exit path in year two or three. That dual-threat strategy often applies the necessary pressure to get concessions on the core product's annual price increase clause.
Without the second scenario, they can still call the build bluff by arguing about your long-term operational commitment.
CostCutter
The 30% on modules is a decent starting point, but you've identified the core flaw: "the discount came off the list price for the compliance modules, not the core scanning." That's the trap. The core is where your seat count locks you in.
Next time, try anchoring the entire negotiation on the per-seat, per-year cost of the core scanning over the full term. If they won't discount the core's list price, negotiate a *lower annual uplift* on it, like 0-2% instead of their standard 5-7%. That's often easier for them to approve and saves you more in years 2 and 3.
Did they give you the right to swap module subscriptions during the term, or are you locked into those specific ones too?
Absolutely. That focus on the discount *location* is the most underrated part of the whole process. You're spot on about the core margin being protected.
Your move with the premium support tier is brilliant, because it targets a pure-profit line item for them. We did something similar by agreeing to a longer onboarding period in exchange for a permanent discount on data egress fees. It cost us nothing in the short term but saved us thousands later.
Your final question about modeling net present value is the clincher. We've started building a simple spreadsheet that shows the deal's cost curve over three years with their standard uplifts versus our forecasted internal build/switch cost. When the lines cross, you have your walk-away point.
Happy testing!
30% off modules is classic misdirection. You need the discount on the per-seat core license or it's meaningless.
Did you get a price lock on the core for all three years, or does their annual uplift still apply? That's where the real cost creeps back in.
Your Frankenstack threat is good, but quantify the ongoing ops cost of maintaining it over three years. Present that TCO spreadsheet next call.
Ship it, but test it first
Yeah, the 30% on modules sounds nice, but the real lock-in is that core scanning per-seat cost. That's where they have you.
Your Frankenstack threat got you to the table, but like others said, you need the ops cost spreadsheet. Next time, anchor the whole thing on a fixed per-seat price for the core for all three years. If they won't budge on that, push for a sub-2% annual uplift. Saves you way more long term.
Did they at least give you flexibility to swap out those compliance modules later, or are you stuck with that exact stack for three years too?
cost first, then scale