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

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

Early Renewal or Prepayment: Axosoft 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 Axosoft is generally well liked by product and engineering teams, especially those running Scrum, but it does come with a learning curve and some UI friction.

Overall sentiment
– Most Spendbase clients rate it positively (4–5 stars are common).
– A smaller but notable group feels it’s “okay but not great” and sometimes move to other tools when they need deeper visibility or smoother UX.

What Spendbase clients like most
Our data consistently highlights these strengths:

• Agile & Scrum support
• Strong fit for Scrum teams: sprints, releases, backlogs, burndown charts.

• Kanban / Card View is often used during stand‑ups and planning.

• Time tracking & reporting basics

• Teams track effort per task/defect/feature and use burndown charts to validate estimates.

• Helpful for R&D write‑offs, billing, and understanding where time is spent.

• Customization & flexibility

• Custom fields, workflows, categories, and security options help adapt Axosoft to different processes.

• Ability to organize by projects/releases and create saved views for management reporting.

• Support / ticketing capabilities

• Email‑to‑ticket and the customer portal are seen as big wins.
• Several clients successfully use it as both dev tracker and support tool.

Key pain points
Our internal data also surfaces recurring concerns:

• User interface and usability
• Described as crowded, cluttered, and not always intuitive.
• Filters and search are common pain points; items can “disappear” because of filters.

• New users need training; some mention a steep learning curve.

• Reporting & dashboards

• Dashboards are useful but considered less powerful than expected.

• Building advanced/custom reports can be cumbersome or require extra tools.

• Stability and performance (for some environments)

• A minority reports lag, CSS not loading, crashes, and stuck loading screens.

• On‑premise setups sometimes need server restarts.

• Workflow limitations

• Limited sub‑task / multi‑level nesting options.
• Some workflow logic (especially around testing) is missing or must be handled via text fields.
• Time tracking per work type (e.g., Dev vs QA vs Docs) is not granular enough for certain teams.

How this ties to cost optimization
From a Spendbase perspective, Axosoft tends to deliver strong value when:
– You actively use Scrum features, time tracking, and customization.
– You invest a bit in onboarding and UI simplification.

Costs become harder to justify when teams mainly need lighter ticketing or struggle with the UI and reporting, as they underuse the advanced capabilities they are paying for.