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

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

Early Renewal or Prepayment: TestingBot 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 TestingBot generally delivers strong value for teams that need broad browser and device coverage, but there are a few patterns worth knowing before you commit budget.

Overall sentiment
Most Spendbase clients rate TestingBot positively, especially for:

• Large choice of browsers, OS versions, and real devices
• Stable automated testing (Selenium, Appium, Playwright, etc.)
• Fast onboarding and intuitive basic workflow

Key strengths our clients highlight

1) Coverage and capabilities
– Very wide range of browsers and OS combinations
– Good fit for both web and mobile testing (manual + automated)
– Helpful tools like inspectors and video recordings to debug issues

2) Ease of use
– Many clients say they were productive within minutes
– Interface is “simple” and “straightforward” once you learn the basics
– Especially appreciated by teams that just need quick Safari or iOS checks

3) Cost-effectiveness at scale
– Automated tests with high concurrency are seen as good value
– For teams using it as a “cloud computer lab,” pricing feels reasonable

Main pain points our clients report

1) Performance and latency
Some Spendbase clients on lighter plans experience:

• Slow or laggy sessions, especially on:
• Older or free-tier devices
• Certain iOS devices and simulators
• Occasional black screens or unusable sessions

2) Pricing structure
A recurring theme from our clients:

• Great for ongoing/testing-heavy teams
• Less ideal for:
• One-off, short projects
• Users who just need a couple of hours every few months
• Multiple clients specifically wish for:
• Pay-per-hour / pay-as-you-go options
• Clearer differentiation between free vs paid device performance

3) UX and clarity
– Some confusion around:
– Time limits on free plans
– Why devices are slow or limited on certain tiers
– iOS quirks (e.g., needing iCloud sign-in, native app vs simulator limits)

How we advise Spendbase customers

When we optimize TestingBot spend, we usually recommend:

• Use it if you:
• Run regular automated test suites across many environments
• Need consistent cross-browser/device coverage
• Be cautious if you:
• Only need rare, ad-hoc manual tests
• Are highly sensitive to UI latency on remote devices

With the right plan and usage pattern, our internal data shows TestingBot can be a cost-efficient part of a broader testing stack, but it benefits from careful rightsizing of seats, concurrency, and plan type.