Ansys renewals are deceptively hard to read. The quote arrives as a stack of solver seats, HPC packs, and elastic on-demand units, usually under an annual lease, sometimes under a paid-up license with a separate maintenance line. Most buyers approve the uplift because picking the line items apart takes simulation-usage data they don't have in front of them at renewal time. That's exactly where the money leaks.
This guide breaks down how Ansys actually prices, where the leverage sits, and which line items reward a hard look. It's written from the buyer's side, vendor-neutral, and reflects patterns seen across thousands of renewals — not confidential terms, and not a promise of any specific number. Treat every figure here as directional and pressure-test it against your own deployment.
Directional only. The figures below come from public Ansys pricing signals and aggregated practitioner experience across many renewals — not confidential terms, and not a guarantee of any outcome. Ansys does not publish a standard rate card for commercial solver/HPC licensing, so several items below are deliberately qualitative. Your numbers will vary with deployment size, solver mix, and history.
- Annual uplift on flat renewals: commonly lands in the mid-single to low-double-digit percent range when accepted without challenge. This is frequently negotiable — especially when usage is flat or declining.
- TECS maintenance (paid-up licenses): maintenance on perpetual software in this category typically runs a meaningful double-digit percentage of license value annually. Confirm the exact rate on your quote and scrutinize any year-over-year increase in the percentage itself.
- HPC pack spend: qualitative — pack cost scales steeply with core count and is often a disproportionate share of total spend relative to how rarely peak parallelism is actually used. High-value area to right-size.
- Low-utilization solver seats: qualitative — specialty solvers (EM, explicit dynamics) are the most common over-provisioned lines. Checkout logs usually reveal at least one seat worth dropping or down-tiering.
- Elastic/on-demand units: qualitative — value depends entirely on demand shape. Prepaid pools that don't roll over and go unused are a recurring source of waste; size to actual burn.
Use these as directions to investigate, not as targets to demand. Your license-manager data is the real benchmark.
How Ansys prices: lease, paid-up, and the TECS line
Ansys sells simulation capacity two ways, and which one you're on changes the entire negotiation:
- Annual lease (term license): the most common commercial model. You pay each year for the right to run the software; stop paying and the licenses stop working. Maintenance and support are typically bundled into the lease fee.
- Paid-up (perpetual) license + TECS: a larger upfront purchase for a license you keep, plus annual TECS (Technical Enhancement & Customer Support) maintenance to stay current on versions and support. TECS is usually quoted as a percentage of license value and recurs every year.
On top of either base, Ansys layers:
- Solver seats — the discipline-specific engines: Mechanical (structural), Fluent (CFD), HFSS (high-frequency EM), LS-DYNA (explicit dynamics), and others. These are licensed per concurrent task or per named bundle.
- HPC / parallel packs — additional licenses that unlock more CPU cores (and GPU) for a single solve. A base solver seat runs on limited cores; HPC packs are how you scale a job, and they stack multiplicatively in cost as core counts climb.
- Elastic / on-demand units — consumption-based capacity (often sold as prepaid unit pools) for burst workloads without owning more permanent licenses.
The renewal conversation is really about the mix of these four things, not the headline price. A 6–8% uplift on a bundle you've half-outgrown can hide a 20%+ saving available from re-mixing.
Where the leverage actually is
Leverage at an Ansys renewal comes from usage truth, not from asking for a discount. Before you engage, pull license-manager (FlexLM / Ansys License Manager) checkout logs for the full term. They tell you what you actually ran, by solver, by peak concurrency, by core count. That data drives every lever below.
- Solver-vs-HPC mix: teams routinely over-buy permanent HPC packs to cover a few large jobs, then run single-core or low-core the rest of the year. If peak parallel usage is rare, the packs are candidates to cut or shift to elastic.
- Elastic vs. owned for peaks: if your demand is spiky — a few crunch weeks around a design deadline — on-demand units can be cheaper than carrying owned HPC or extra seats year-round. If demand is flat and high, owned capacity wins. Model both; don't assume.
- Right-size rarely-used solvers: a seat of a discipline solver that checked out a handful of times all year is the clearest line to drop, down-tier, or move to a shared/elastic model. Named specialty solvers (EM, explicit dynamics) are common offenders.
- Lease-vs-paid-up math: compare the multi-year lease stream against paid-up + TECS over your real holding period. Paid-up can win if you'll run the software for many years and capital treatment is favorable; lease wins for flexibility and flat opex. Run the NPV, not the sticker.
- Bundling leverage: if you hold multiple Ansys product lines, consolidating the renewal into one negotiation — and timing it against the vendor's quarter/year-end — concentrates your spend into a single lever rather than several small, separately-discounted ones.
The line items and SKUs worth challenging
Go through the quote line by line and put each of these under scrutiny:
- HPC pack quantity and tier: match pack count against peak-concurrent core usage from your logs. Packs bought for a one-time large solve should be questioned or re-scoped.
- Low-utilization solver seats: any seat whose checkout hours don't justify its line. Ask whether it can be dropped, down-tiered, or covered by elastic units instead.
- TECS maintenance percentage: on paid-up licenses, confirm the maintenance rate and whether it's being applied to list or to your negotiated license value. Challenge any year-over-year creep in the percentage itself, not just the base.
- Elastic unit pools: check last year's consumption against what you prepaid. Unused units that don't roll over are pure waste; right-size the pool to actual burn plus a modest buffer.
- Auto-renewal and uplift clauses: standing annual increase language (CPI-plus, or a fixed %) is a line to negotiate down or cap, not accept as boilerplate.
- Bundle repackaging: vendors periodically re-bundle SKUs (e.g., into suites or unified platforms). When a renewal moves you to a new package, verify you're not paying for capabilities you don't use and that your effective per-solver cost didn't rise in the repackaging.
Post-Synopsys-acquisition context
Synopsys completed its acquisition of Ansys in July 2025, with Ansys becoming a wholly owned subsidiary. That changes the negotiating backdrop in ways worth noting carefully — and without over-reading:
- Larger portfolio, more cross-sell surface: Ansys now sits inside a much bigger EDA and systems-design company. Expect more packaging and cross-product positioning over time. Keep your renewal scoped to what your team uses; resist bundle expansion you can't tie to usage.
- Integration periods favor prepared buyers: ownership transitions generally bring process change on the vendor side. A buyer who shows up with clean usage data and a defined walk-away position is better positioned during any period of commercial reorganization.
- Watch for model and packaging shifts: acquisitions can accelerate moves toward subscription/term and unified platform SKUs. If your renewal proposes a structural change to how you license, treat it as a full re-negotiation, not a rollover.
None of this is a prediction of specific pricing behavior. It's a reason to renew with more diligence, not less, during the transition.
Renewal timeline: when to start
The single biggest determinant of outcome is how early you start. A renewal worked in the last two weeks has no leverage; one started months ahead has options.
- 6–9 months out: pull license-manager usage logs for the full term. Build the utilization picture by solver, peak concurrency, and HPC core usage. Identify candidates to cut, down-tier, or shift to elastic.
- 4–6 months out: model the alternatives — lease vs. paid-up NPV, elastic vs. owned for peaks, re-mixed solver/HPC quantities. Decide your target state and your walk-away.
- 2–4 months out: engage the vendor with your data-backed counter. Time the ask against the vendor's quarter- or fiscal-year-end where you can — end-of-period is when flexibility tends to appear.
- Final weeks: finalize terms, lock the uplift cap, and confirm the SKU list line by line before signing. Never let an auto-renewal date make the decision for you.
Get the full Ansys Renewal Playbook
This guide is the shape of the problem. The $59 playbook gives you the fillable worksheets, the six-point negotiation plan, two copy-paste emails, and the full pre-renewal checklist — everything to walk into the Ansys conversation with a number and a plan.
Get the Ansys playbook — $59 → Get the free 15-point renewal checklist →Frequently asked questions
Is Ansys licensing a lease or a purchase?
Both exist. The most common commercial model is an annual lease (term license), where support is typically bundled and the software stops working if you stop paying. The alternative is a paid-up perpetual license plus annual TECS maintenance. Which you're on changes your entire negotiation — check your contract before you model anything.
What is TECS and can I negotiate the percentage?
TECS is Ansys's Technical Enhancement & Customer Support — the annual maintenance that keeps paid-up (perpetual) licenses current on versions and support. It's quoted as a percentage of license value and recurs yearly. The percentage and the base it's applied to are both worth scrutinizing, and year-over-year creep in the rate itself is negotiable.
What are HPC packs and why do they cost so much?
A base solver seat runs on a limited number of CPU cores. HPC (parallel) packs unlock more cores for a single solve, and their cost scales steeply as core counts climb. Teams often buy permanent packs to cover rare large jobs, then under-use them the rest of the year — which makes packs one of the highest-leverage items to right-size or shift to elastic.
Should I use elastic on-demand units or own more licenses?
It depends on your demand shape. Spiky demand — a few crunch weeks a year — often favors elastic/on-demand units over carrying owned capacity year-round. Flat, high demand favors owned licenses. Pull your usage logs and model both; don't assume. Prepaid elastic pools that go unused and don't roll over are a common source of waste.
Does the Synopsys acquisition change how I should renew?
Synopsys's acquisition of Ansys closed publicly in July 2025, with Ansys becoming a wholly owned subsidiary. It doesn't change the mechanics of your current licenses, but it's a reason for more diligence, not less: expect more packaging and cross-product positioning over time. If a renewal proposes a structural change to how you license, treat it as a full re-negotiation rather than a rollover.
When should I start working the renewal?
Six to nine months ahead. That's enough time to pull full-term license-manager usage data, model lease-vs-paid-up and elastic-vs-owned alternatives, and engage the vendor with a data-backed counter — ideally timed against their quarter or fiscal-year-end. Renewals worked in the final two weeks have essentially no leverage.
Key takeaways
- Know your model first: annual lease (support bundled) versus paid-up perpetual plus annual TECS maintenance changes every lever you have.
- Pull license-manager checkout logs for the full term before you negotiate — usage truth by solver, peak concurrency, and core count drives everything.
- HPC packs and rarely-used specialty solvers are the highest-leverage lines to right-size, down-tier, or shift to elastic.
- Model elastic vs. owned for peak demand and run the lease-vs-paid-up NPV over your real holding period — don't accept the sticker framing.
- Post-Synopsys, renew with more diligence: scope to actual usage, scrutinize any repackaging, and treat structural license changes as full re-negotiations.
- Start 6–9 months out and time your counter to the vendor's period-end; never let an auto-renewal date decide for you.