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

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

Early Renewal or Prepayment: MBS 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 feedback on MBS is generally positive, especially around billing flexibility and multi-market management, while there are some clear usability gaps around account structure and identifiers.

From what Spendbase clients share with us, the strongest points are:

• Easy-to-follow billing workflows
• Clear write-off processes
• Ability to manage multiple markets within a single billing system
• Robust feature set for complex telecom billing (including BDS, Special Access, Ethernet, and Interconnection)

Clients especially like that MBS can handle many different billing scenarios in one place. That consolidation often helps reduce the number of tools they pay for, which in turn creates a good basis for Spendbase to negotiate or optimize license and support costs.

However, our internal data also shows some recurring pain points:

• Too many numerical identifiers:
• Subscriber number
• Guarantor number
• Account number
• High risk of misposting payments to the wrong account
• Confusion for both finance teams and end customers when referencing the “right” number

This complexity leads to extra support tickets and manual corrections, which indirectly increases the total cost of ownership. When we work on discount strategies for MBS, we often factor in:

• Extra admin effort required due to identifier confusion
• Training or documentation needs for billing teams
• Potential add-ons or configuration work to streamline account structures

In terms of outcomes, Spendbase clients typically look for:

• Cost reductions through:
• Consolidation of markets onto one MBS instance
• Volume-based or multi-year discounts
• Support and training bundles negotiated into the main contract
• Efficiency gains via:
• Simplified account-reference rules
• Clearer mapping between customer-facing IDs and internal IDs

Overall, our internal data shows that MBS is viewed as a solid, flexible billing engine, especially for complex telecom environments. The main opportunity lies in simplifying how accounts and numbers are presented and managed. When we negotiate on behalf of clients, we often push not only for better pricing, but also for configuration and support concessions that reduce those day-to-day friction points.