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

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

Early Renewal or Prepayment: BotCity 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 BotCity tends to deliver strong value for Python‑centric automation teams that care about cost, control, and flexibility.

From what our Spendbase clients share most often, a few themes stand out:

1) Cost structure and ROI
– Many clients highlight the ability to cut costs versus traditional low‑code RPA while keeping enterprise features.
– Savings usually come from:
– No expensive per‑bot licenses
– Using existing Python talent instead of niche RPA skill sets
– Running bots on cheaper infrastructure (VMs, containers, serverless)

2) Technical flexibility
Our internal data shows that technical teams consistently appreciate:
– Full Python access and compatibility with a huge package ecosystem
– Freedom from vendor lock‑in and easier migration from legacy RPA tools
– Support for complex environments (Citrix, SAP, Windows, Linux) without a lot of hacks

3) Orchestration and governance
Spendbase clients often call out the orchestrator and governance layer as a key reason to choose BotCity:
– Central control of bots, schedules, credentials, and logs
– Clear execution history and auditability that finance, risk, and IT can all live with
– Real‑time monitoring and insights that help track hours saved, failures, and infrastructure usage

4) Speed of delivery
Our data shows that development teams usually ship automations faster once they are past the initial learning curve:
– Direct coding in Python speeds complex scenarios
– Reuse of components across processes
– Easier scaling from a few bots to dozens or more

5) Support and learning curve
– Clients generally rate support and documentation as responsive and “hands‑on”.
– One trade‑off we see: non‑technical business users may struggle compared to classic drag‑and‑drop tools, so it fits better when you already have developers or a tech‑driven CoE.

Summary for procurement and discount planning
– Best fit: organizations with in‑house Python skills, desire to avoid lock‑in, and significant legacy/desktop systems to automate.
– Savings drivers: lower platform cost, consolidation of legacy RPA spend, better infra utilization, and fewer re‑work hours thanks to governance and observability.
– Risk: if a company expects pure citizen‑developer RPA, BotCity may require more upskilling than they planned, which we factor into our negotiation and ROI modeling at Spendbase.