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

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

Early Renewal or Prepayment: IncidentMonitor 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 IncidentMonitor tends to shine for teams that care about flexibility and cost-efficiency, but it does have some trade-offs around UI modernity and learning curve.

From what Spendbase clients tell us, the main strengths are:

• Exceptionally responsive support
• Many clients call out the professionalism and speed of the vendor’s support team.

• Direct access to knowledgeable people is a recurring theme.

• High configurability with no-code tools

• Workflow designer and form designer are repeatedly praised.
• Clients like that they can:
  • Build and adapt ITIL-based processes
  • Configure complex approvals
  • Design custom self-service portals (even per customer/department)
  • Host multiple help desks in one environment

• Our internal data shows that this self-configuration cuts down on paid professional services and long change cycles.

• Value for money

• IncidentMonitor is often perceived as “enterprise features at SMB pricing.”

• All modules included, no surprise add-ons, is seen as a key budget advantage.

• Functionality depth

• Out-of-the-box ITIL templates
• Email integration and automatic ticket creation
• Knowledge base integration
• Dashboards, document linking, architectural modeling
• Multilingual capabilities and integration via web services/XML

At the same time, Spendbase clients highlight some consistent drawbacks:

• Aging technology and UI
• Several comments point to an “older” look and feel and underlying Microsoft framework.

• One client explicitly compares it to much older-style interfaces, which can impact user adoption.

• Feature overload and learning curve

• There is so much possible that it takes time to understand and fully leverage.

• Our internal data shows that without a clear rollout plan, teams may end up underusing capabilities they’re paying for.

• Minor usability gaps

• Inconsistent support with older browsers (like IE8).
• Visual aspects such as not being able to color-code projects can make navigation confusing in complex setups.
• Outdated public feature lists vs actual capability.

In Spendbase terms:
If your priority is a highly customizable ITSM tool with strong support and good pricing, IncidentMonitor can be a very cost-effective fit. Just be prepared to invest a bit in onboarding, UX training, and internal governance so your team doesn’t get lost in the power it offers.