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

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

Early Renewal or Prepayment: monosign 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 monosign is seen by Spendbase clients as a strong, flexible core for identity and access management, especially in environments with many internal and external services.

Based on what our clients tell us, the main strengths look like this:

• Excellent customer support
• Fast response times for incidents, questions, and change requests
• Willingness to implement minor product changes quickly

• Support team perceived as accessible and collaborative

• High flexibility and scalability

• Works well as a central single sign-on hub across dozens of apps
• Handles both internal and external services reliably
• Can ingest user data from multiple sources (e.g., AD plus bespoke systems)

• Fits complex, hybrid environments rather than just “standard” setups

• Security positioned at the center

• Clients use monosign as a core security layer, not just an SSO tool
• Good fit for organizations wanting tighter control over access flows and user lifecycle

At the same time, our internal data shows a few recurring friction points:

• Error handling and transparency
• When there is an issue, error messages can be too generic

• Troubleshooting sometimes requires more back-and-forth with support than ideal

• Learning curve / admin experience
  (common in IAM tools, and consistent with what we see in this category)

• New admins may need time to fully understand advanced configuration
• Some Spendbase clients would like clearer guidance and more “self-service” diagnostics

From a Spendbase discount and optimization perspective, our clients typically:

• Consolidate multiple access tools into monosign to reduce license overlap
• Use it to standardize SSO for a growing app portfolio, which improves both security and IT efficiency
• Get higher ROI when they:
• Centralize as many apps as possible under monosign
• Integrate all major identity sources early (AD, HR systems, custom user stores)
• Involve security and IT ops together in the rollout

In short, Spendbase clients see monosign as a flexible, support-backed IAM and SSO platform that scales well, with the main opportunity for improvement in clearer error messaging and admin self-service.