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

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

Early Renewal or Prepayment: ActiveControl 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 ActiveControl tends to score solidly in functionality, but the day‑to‑day experience depends a lot on development style and process maturity.

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

• Governance & compliance
• Strong SOX controls and audit trails out of the box
• Clear visibility of who moved what, where, and when

• Testing steps embedded into the change flow, which reduces compliance risk

• User experience & integrations

• A noticeably simpler UI compared to traditional SAP tools like Solution Manager

• Native linkage with tools like Jira, helping align SAP changes with broader IT workflows

• Change automation

• Automated handling of transports once rules are in place
• Good fit for environments with many small change requests and continuous delivery patterns

However, our internal data also highlights recurring pain points:

• Developer experience
• Some technical teams feel they “lose control” over transports, since releases are forced through ActiveControl instead of SAP GUI/Eclipse

• When issues are found, developers must jump back into SAP to rerun ATC/unit tests, which can feel repetitive

• Performance & scalability

• Analysis runs can be slow on very large transport bundles (e.g., monthly releases with thousands of objects)

• This leads some clients to question suitability for classic, heavy waterfall releases unless processes are tuned

• Technical flexibility

• Lack of a RESTful API is a common complaint from more modern engineering teams that want tighter CI/CD integration

From a Spendbase savings and value perspective, clients who get the best ROI typically:

• Use ActiveControl to push smaller, more frequent releases
• Invest a bit of time upfront to tailor workflows (e.g., when analyzers run, how approvals are structured)
• Align dev practices with the tool instead of trying to mimic legacy, manual transport handling

In short, ActiveControl tends to deliver strong compliance and automation value, but you’ll want to factor in developer sentiment, release patterns, and integration needs when negotiating pricing and planning adoption.