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

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

Early Renewal or Prepayment: Raygun 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 Raygun is generally well liked by engineering teams, but there are a few important caveats you’ll want to factor in before renewing or expanding licenses.

Overall sentiment
– Most Spendbase clients rate Raygun highly for day‑to‑day debugging and monitoring.
– A smaller but vocal group is unhappy mainly around pricing and pricing changes, not the core tech.

What Spendbase clients like most
– Fast value from setup
– “Two lines of code” type integrations for .NET, Xamarin and other stacks
– Easy to roll out across multiple apps and environments
– Strong debugging capabilities
– Pinpoints exact line of code and stacktrace
– Rich context: user info, environment, version, history of an error
– Helpful for catching edge cases that QA misses and for being proactive before users complain
– Productivity gains
– Centralized place for all exceptions
– Good for onboarding new devs with historical error context
– Integrations with Slack, Jira and others to streamline workflows

Where friction appears
Our internal feedback clusters into a few recurring pain points:

• Pricing & billing
• Multiple clients mention Raygun feeling expensive for small teams.
• One major complaint centers on plan changes:
  • Automatic jump to higher event tiers
  • 10x price increase without sufficiently clear communication

• Limited flexibility for lower‑usage teams who don’t need huge event volumes.

• Usability gaps

• Error grouping sometimes inaccurate; breaks when stacktraces change
• Filtering and search are too basic for complex queries
• Hard to navigate large numbers of exceptions; desire for better snapshots and time‑based views

• Occasional slow UI at high activity times

• Feature wishes

• More concise issue overviews
• Better notification controls (less spam, more targeted alerts, reoccurrence alerts)
• Stronger user behavior/usage insights on top of errors

How we usually optimize Raygun spend
Given this mix, our discount playbook for Raygun often focuses on:
– Right‑sizing event volumes to actual usage (many teams overpay for unused events)
– Negotiating safeguards around future plan changes and auto‑upgrades
– Leveraging contract length and multi‑product commitments to secure better per‑event pricing
– Ensuring you’re not duplicating APM/RUM capabilities you already own in tools like Datadog or New Relic

If you share recent invoices and actual event usage, we can typically spot 20–40% optimization opportunities without reducing coverage.