How to Use This Guide
This guide breaks down the four most common tactics vendors are using to apply AI-driven price increases. For each one, you'll find what it looks like in a proposal, why the vendor is using it, what it costs you, and how to counter it.
Keep this handy during renewal season. Share it with your negotiation team. Once you can name the tactic, you can push back on it.
Tactic 1: Forced SKU Migration
What It Looks Like
Your vendor announces that your current plan is being "sunset" or "consolidated" into a new product tier. The new tier includes AI features you didn't ask for — and costs 20–40% more. There's no option to renew at your current plan and price. The old SKU simply doesn't exist anymore.
You'll hear language like: "We've simplified our packaging to better serve customers like you" or "Your plan is being upgraded to include our new AI capabilities."
Why the Vendor Does It
SKU migration is the cleanest way to raise prices without calling it a price increase. By eliminating the old plan, the vendor removes your benchmark. You can't compare new pricing to old pricing if the old product technically no longer exists. It also lets the vendor apply the increase to their entire customer base at once, rather than negotiating one-off renewals.
What It Costs You
The immediate cost is the price difference between your current plan and the new one — typically 20–40%. But the hidden cost is the loss of your pricing anchor. Once you accept the new SKU, that becomes your new baseline, and future increases stack on top of it.
How to Counter It
- Pull your last 2–3 invoices and document your current effective rate per user (or per unit of value).
- Identify what features you actually use vs. what's being added. If the AI features don't serve your use case, you shouldn't be paying for them.
- Request legacy pricing as your benchmark. Even if the old SKU is gone, you can negotiate the new one down to your previous effective rate plus a reasonable uplift (3–5%).
- Ask for a transition period. Propose a 6–12 month ramp where you pay your current rate, then step up to the new pricing gradually.
- Push for a price cap on the new SKU. If you accept the migration, lock in the new price with a contractual cap on future increases.
- Negotiate the AI features as optional. Ask whether you can stay on a version of the new tier that excludes the AI add-ons and the corresponding premium.
"We understand you're updating your packaging, but the AI capabilities in this new tier don't align with our current needs. We'd like to discuss a pricing structure that reflects the value we're actually using — starting from our current effective rate as the baseline."
Tactic 2: Unbundling-Then-Rebundling
What It Looks Like
Your vendor takes what used to be an all-in-one product and splits it into multiple separate SKUs. Features that were previously included — reporting, integrations, automation, advanced search — get reclassified as standalone modules. AI features are positioned as a premium add-on.
To get back to the same functionality you had before, you now need to purchase two or three products instead of one. The combined price is higher than what you were paying.
You'll hear language like: "We've modularized our platform to give you more flexibility" or "You can now choose exactly the capabilities you need."
Why the Vendor Does It
Unbundling creates the illusion of choice while extracting more revenue. The vendor can point to a lower base price (since features have been removed) while knowing most customers will need the add-ons to maintain their existing workflows. It also lets them charge AI-specific premiums that would be harder to justify inside an all-in-one price.
What It Costs You
The direct cost is the gap between your previous all-in price and the new total with add-ons. But the strategic cost is larger: every module is now a separate negotiation, a separate renewal, and a separate price increase. Complexity is the vendor's friend and your enemy.
How to Counter It
- Document your current feature set in detail — every feature, integration, and capability you use today. Do this before the vendor's packaging change takes effect, so you have a clear record of what "included" used to mean.
- Calculate the true cost of the new model. Add up the base price plus every add-on you'd need to replicate your current functionality.
- Challenge the framing. This isn't "more flexibility" — it's a restructuring that increases your total cost. Name it directly.
- Negotiate a bundle price that matches or is close to your current spend. If the vendor wants you on the new model, they should make the transition cost-neutral (or close to it).
- Lock in the bundle. If you agree to purchase multiple modules, negotiate them as a single contract with a single renewal date and a single uplift cap — not as separate agreements that can be renegotiated independently.
- Ask for a grandfathering period. Request 12–24 months at your current effective rate while you evaluate whether the modular model works for you.
"We've mapped our current feature usage to your new packaging, and the total cost to maintain the same functionality is [X]% higher. We're not opposed to the new model, but we need the economics to reflect our existing relationship, not a net-new purchase."
Tactic 3: Credit-Based Obfuscation
What It Looks Like
Your vendor moves from predictable per-seat or flat-fee pricing to a credit or consumption model. Instead of paying $50/user/month, you buy a pool of credits. Every action — API calls, AI queries, document processing, report generation — consumes credits at rates that may vary by feature, time of day, or model version.
You'll hear language like: "Our new pricing model gives you more control over costs" or "You only pay for what you use."
Why the Vendor Does It
Credit-based pricing solves two problems for the vendor. First, it shifts cost risk to the buyer — if your team uses more than expected, you pay more, and the vendor doesn't have to negotiate. Second, it makes benchmarking nearly impossible. When every vendor defines "credits" differently, you can't compare prices across competitors. The vendor knows this.
What It Costs You
The immediate risk is cost unpredictability. Finance teams that are used to forecasting software spend based on seat count suddenly have a variable line item that fluctuates month to month. The long-term risk is overage exposure — teams adopt AI features faster than expected, credits get consumed, and an unexpected invoice lands at the end of the quarter.
How to Counter It
- Ask the vendor to model your expected costs in dollars, not credits. Have them show what a typical month of usage looks like for a company your size, with specific dollar amounts.
- Request historical usage data from your own account (if this is a renewal) to understand your actual consumption patterns.
- Demand a cost-per-outcome metric. Instead of negotiating on credit price, negotiate on what matters: cost per report generated, cost per document processed, cost per user per month. This creates a benchmark you can track and compare.
- Negotiate a spend cap. Set a contractual maximum monthly or quarterly spend. If usage exceeds the cap, the vendor should notify you and pause consumption until you approve additional spending.
- Build in quarterly true-up clauses. Instead of committing to an annual credit volume, negotiate quarterly check-ins where you can adjust your commitment based on actual usage.
- Require a usage dashboard as a contract term. If the vendor doesn't provide real-time visibility into credit consumption, you're flying blind. Make the dashboard a contractual deliverable, not a nice-to-have.
- Lock the credit-to-dollar rate for the contract term. Credit costs should be fixed, not variable. If the vendor can change credit prices mid-contract, you have no cost predictability at all.
"We need to understand this in dollars, not credits. Can you model three scenarios — conservative, expected, and high usage — with actual dollar amounts based on our team size? And we'll need a spend cap and a dashboard written into the contract before we commit to a consumption model."
Tactic 4: Conditional Discounts
What It Looks Like
The vendor offers you a discount on your base product renewal — but only if you agree to purchase their new AI add-on. The AI product is framed as something you're getting a deal on because of your existing relationship. The discount on the base product is presented as a savings, not as a pressure tactic.
You'll hear language like: "Because you're a valued customer, we can offer you 15% off your current plan — if you add our AI suite" or "We have a special bundle rate for existing customers that includes AI."
Why the Vendor Does It
Conditional discounts let the vendor land AI revenue from their existing customer base without a separate sales cycle. By tying the discount to the AI purchase, they create urgency ("this pricing is only available if you add AI now") and reframe a spending increase as a savings. It also drives AI adoption metrics that the vendor can report to investors and the market.
What It Costs You
The obvious cost is the AI add-on itself — you're spending more money total, even if the base product costs less. The hidden cost is that you're now locked into an AI product you may not have evaluated properly. If it doesn't deliver value, you're stuck with it for the contract term. And the "discount" on the base product becomes the new baseline — at renewal, the vendor will price the base product at the discounted rate plus uplift, but the AI add-on will have its own renewal and its own price increase.
How to Counter It
- Separate the two conversations in your own mind before the vendor combines them. The base product renewal and the AI add-on are two different purchasing decisions with two different value propositions.
- Evaluate the AI product on its own merits. Does your team need it? Has it been piloted? Can you quantify the ROI? If the answer to any of these is "no," you don't need it at any price.
- egotiate the base renewal first, independently. Tell the vendor you want to finalize the base product terms before discussing any add-ons. If they push back, that confirms the "discount" is a tactic, not genuine value.
- Challenge the discount framing. Ask: "What's the renewal price for the base product without the AI add-on?" If the answer is significantly higher, the vendor is using the AI purchase as a subsidy, not offering you a deal.
- If the AI product has real value, negotiate it separately. Get the best price on the base product, then evaluate the AI add-on as a standalone purchase with its own pilot period, success criteria, and walk-away clause.
- Push for a trial before commitment. If you're interested in the AI product, ask for a 60–90 day pilot at no additional cost, with the option to add it to your contract at a defined price if the pilot meets agreed-upon success criteria.
"We'd like to renew the base product on its own terms first. We're interested in learning more about the AI add-on, but we want to evaluate it separately and potentially pilot it before we commit. Can you share the base renewal pricing without the AI bundle attached?"
Quick Reference: All Four Tactics at a Glance
| Tactic | What Changes | Vendor's Goal | Your Top Counter Move |
|---|---|---|---|
| Forced SKU Migration | Old plan eliminated, new AI-inclusive plan costs more | Remove your pricing anchor | Use current rate as benchmark, cap the new SKU |
| Unbundling-Then-Rebundling | All-in-one product split into modules + AI add-ons | Charge more through complexity | Document current features, negotiate bundle parity |
| Credit-Based Obfuscation | Per-seat pricing replaced with credit/consumption model | Shift cost risk to buyer, block benchmarking | Demand dollar-based modeling, cap spend, lock credit rates |
| Conditional Discounts | Base product discount tied to AI add-on purchase | Land AI revenue without a separate sales cycle | Separate the negotiations, evaluate AI independently |
Tips for Using This Guide
- You don't need to accuse the vendor of using a "tactic". Just use the counter-strategies. The goal is to negotiate a better outcome, not to win an argument.
- Tactics often stack. A single renewal proposal can include SKU migration and conditional discounts at the same time. Read the full proposal before responding.
- Start the conversation early. These tactics work best (for the vendor) when you're under time pressure. Begin renewal conversations 90+ days before the deadline.
- Pair this with the AI Contract Review Checklist (Asset 1 in this toolkit) to ensure the final contract reflects the terms you negotiated, and the AI Spend Forecasting Worksheet (Asset 3) to model the long-term cost impact of whatever deal you agree to.