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

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

Early Renewal or Prepayment: Implementer 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 Implementer is seen as a strong, reliable change management tool for IBM i, especially for teams that care about control, traceability, and compliance.

From what our Spendbase clients tell us, the main strengths cluster around:

• Ease of daily use
• Many clients say once Implementer is set up, it’s straightforward for developers to work with.
• Change tracking, version history, and rollback are highlighted as key benefits.

• The RDI integration and graphical UI are appreciated when available.

• Change management & auditability

• Clients rely on Implementer for:
  • Managing program and service program changes
  • SOX and audit reporting
  • Tracking requests and moves across QA and production

• Archiving and the ability to back out problematic code are seen as major safety nets.

• Environment and deployment control

• Strong points include:
  • Managing multiple IBM i hosts and many target systems
  • Smooth promotion to QA and production when the process is set up correctly

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

• Learning curve & setup
• Initial setup and advanced concepts (ILE modules, complex profiles, SYNON users) can be tricky.

• Clients often need detailed documentation or extra training to get full value.

• SQL and database deployments

• Handling SQL tables, indexes, and referential integrity is a pain point.

• Constraints often need to be dropped and re-added manually, which slows down deployments.

• Interface & usability gaps

• Administration is mostly green-screen based; several clients wish for a modern web-based admin UI.

• Some mention confusion when switching between features or finding answers in the docs.

• Performance and operations

• In a few environments, certain functions consume a lot of host resources.
• Configuration deployment and containerization can be slower than expected.
• Occasionally, property changes require restarts, which hurts feature toggle workflows.

From a Spendbase discount perspective, Implementer delivers high functional value for IBM i shops, but teams should budget time and possibly training for setup and complex SQL scenarios to avoid hidden operational costs.