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

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

Early Renewal or Prepayment: Acunetix 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 Acunetix is generally well‑liked, but there are some clear patterns our clients care about when negotiating price and fit.

Overall sentiment
– Roughly 3 out of 4 Spendbase clients rate Acunetix 4–5/5.
– The remaining segment flags product limitations and, more often, licensing and sales issues.

What Spendbase clients like most
– Ease of use and UX
– Very often described as “point and shoot” and friendly even for less technical users.
– Strong reporting
– Separate reports for management, boards, and developers.
– Good vulnerability descriptions, remediation steps, and severity breakdown.
– Automation
– Scheduling (daily/weekly/monthly) and continuous scanning support common DevSecOps workflows.
– Coverage and depth
– Broad vulnerability coverage, including compliance-style outputs (OWASP Top 10, PCI, HIPAA).
– Helpful developer-oriented features like AcuSensor and crawl quality.

Typical use cases we see
– Security baselines for new applications before production.
– Continuous scanning of key web assets for smaller security teams.
– Developers self-testing their own apps.
– Education and training in DAST concepts.

Key pain points Spendbase clients report
– Licensing and pricing
– Per‑target pricing becomes expensive as scope grows.
– Licensing model changes mid‑term caused unexpected cost increases and reduced perceived value.
– Pentest/consulting-style use (many one‑off apps) is poorly aligned with current licensing.
– Feature and configuration gaps
– Fewer low‑level tuning options compared to older versions or tools like Nessus.
– Some removed or moved features (manual tools, network scanning) frustrate long‑time users.
– Issues with complex apps, multi-domain targets, and some login flows.
– Quality and coverage concerns
– In a minority of cases, important issues were missed or there were noticeable false positives.
– Support and sales experience
– Slow or unhelpful support responses in several cases.
– At least one notably negative interaction with the sales team around trial access.
– Performance
– Long scan times on large or complex sites.
– Limits on concurrent scans for some license tiers.

How we typically advise clients from a discount perspective
– Push for clarity and stability on licensing terms over the entire contract (especially per‑target definitions).
– Leverage concerns about removed features, support response times, and pricing vs. competitors to negotiate discounts.
– If you’re a pentest/consulting shop or have many short‑lived apps, aim for a tailored licensing structure rather than standard continuous-scanning pricing.