Number of Seats/Users: Tricentis Testim offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Tricentis Testim that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Tricentis Testim. Tricentis Testim reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Tricentis Testim offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Tricentis Testim. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Tricentis Testim often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Tricentis Testim tends to deliver strong value, especially for teams trying to scale UI automation without a big in‑house framework effort.

From what our Spendbase clients tell us, the main upsides are:

• Fast onboarding and creation of tests
• Non-technical QA and product folks can get useful flows running in days.
• Record-and-play plus predefined steps and shared steps are used heavily.

• Many teams report cutting regression cycles from days/hours to under an hour.

• Stability and AI-based maintenance

• Smart Locators noticeably reduce flaky tests when the UI changes.

• Parallel and cross-browser runs are considered reliable enough for CI/CD gates.

• Flexibility for mixed-skill teams

• Codeless flows for most use cases, with JavaScript for edge cases and custom validations.

• Branching, parameterization, reusable/shared steps are used to keep suites maintainable.

• Support and enablement

• Live chat and onboarding are repeatedly called out as a real differentiator.
• Clients like the cadence of new features and best-practice guidance.

At the same time, our data also surfaces some consistent friction points:

• Learning curve & UX
• Basic recording is simple, but concepts like grouping, dynamic data, and advanced JS steps can feel steep.

• Navigation and usability inside the platform are sometimes described as confusing or slow on large suites.

• Reporting & debugging

• While screenshots and logs help, some teams want richer failure insights and easier diffing of expected vs actual.

• Platform gaps

• Mobile is mostly simulated; native devices and tablet coverage are common asks.

• Some limitations/asks around: copying steps/tests across projects, scheduling by minutes, more granular test logs.

• Pricing & planning

• A few clients struggled early to map their own test volume and define a “test” for licensing.
• For teams that fully adopt shared steps and CI integration, perceived ROI is high; partial adopters feel less upside.

From a Spendbase discount perspective, Testim tends to pay off best when:
– You have many manual UI regressions today.
– You’ll empower non-engineers to author tests.
– You’re ready to invest a bit in best practices, not just record-and-play.