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

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

Early Renewal or Prepayment: aqua 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 aqua is generally a strong, cost‑effective choice for teams that want structured, scalable QA with modern AI support.

From what Spendbase clients share with us, the main strengths cluster around:

• Ease of setup and daily use
• Fast onboarding, “office-like” UI
• Intuitive test case, test scenario, and bug workflows

• Clear structure for requirements → test cases → scenarios → defects

• AI and productivity

• AI test case generation is a standout: many clients say test cases from requirements need little to no editing

• Smooth path from manual to automated testing, especially when combining aqua with external automation tools

• Reporting and visibility

• Real‑time dashboards and flexible reports
• Better transparency for QA and dev: developers can see coverage and failing tests tied to bugs

• Good basis for management decisions and process optimization

• Integrations and flexibility

• Jira integration praised frequently
• Open API and ability to connect multiple tools

• Both desktop and web clients, plus Chrome extension for quick bug capture

• Support and pricing

• Very fast, helpful support called out again and again
• Pricing seen as fair, with options for smaller teams and externals

At the same time, our data also highlights recurring friction points:

• Integrations and automation
• Some missing or harder‑to‑implement integrations (e.g., Confluence, certain automation setups)

• No built‑in automation engine; you rely on external tools and integrations

• UI / UX consistency

• Web client sometimes lags behind desktop in features and admin options
• Navigation and user guidance can feel inconsistent or complex at first

• Building complex test scenarios and release-based sets can be a bit tricky

• Onboarding and documentation

• Manual and SSO documentation can be dense or outdated
• Clients would like more onboarding videos and clearer guides

In Spendbase terms, aqua tends to deliver high functional value per dollar for teams that:
– Care about strong test management and reporting
– Are ready to rely on integrations for automation
– Can tolerate a learning curve in exchange for depth of features

If you’re negotiating or rightsizing licenses, the biggest value levers are usually AI usage, number of power-users vs. light defect-only users, and which integrations you really need enabled.