Number of Seats/Users: QMetry 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 QMetry 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 QMetry. QMetry reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: QMetry 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 QMetry. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: QMetry 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 QMetry is generally seen as a strong, user‑friendly test management and automation platform, especially for agile and DevOps teams, with a few recurring friction points around usability depth and integrations.

From what our Spendbase clients share, the main benefits cluster around:

• Ease of use & onboarding
• Simple to create and manage test cases and test cycles
• Accessible for both beginners and advanced QA engineers

• Easy to train non‑technical team members

• Productivity & structure

• Well‑organized test case management
• Helpful for planning releases, running test cycles, and approving releases

• Clear pass/fail tracking and visibility into QA progress

• Reporting & visibility

• Reporting is frequently cited as a strong point
• Customizable reports that help track test execution, pass/fail trends, and QA status

• Supports SAFE/agile practices by giving more visibility into QA tasks

• Integrations & ecosystem

• Strong Jira integration, including working directly from Jira
• Integrations with Jenkins and identity management tools
• Fits nicely into typical DevOps toolchains

At the same time, our internal feedback also highlights some consistent challenges:

• Information architecture & UX
• Folder structure is seen as hard to manage for teams running many sprints/releases
• Clients want more intuitive folder/release-wise organization

• The interface for complex structures is not always obvious

• Reporting learning curve

• Test report features are powerful but feel complicated

• Many options, but not always clear how to get the exact report needed

• Automation & technical limits

• Difficulty uploading automated test results from certain tools

• Issues with handling large test cases (for example, reordering many test steps)

• Pricing transparency

• Some Spendbase clients mention a lack of clear pricing information when evaluating QMetry

From a Spendbase discount perspective, this tells us:

• Teams that value Jira‑centric workflows and strong reporting tend to see high ROI with QMetry.
• Power users and large QA organizations may need extra time for setup and training around folder structures, reports, and automation result imports.
• When negotiating, the main levers our clients care about are:
• User tiers and pricing clarity
• Support/training packages to reduce the learning curve
• Ensuring automation and integration requirements are covered in contract terms.