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

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

Early Renewal or Prepayment: Request Tracker 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 Request Tracker tends to attract teams that want strong help desk capabilities without enterprise price tags or lock‑in.

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

1) Overall satisfaction and value
Most clients rate RT very highly for value for money, especially compared to per‑user tools like ServiceNow or Zendesk.
Key points they highlight:
– Open source model, no per‑seat pricing
– Stable performance even at scale
– “Enterprise‑grade” capabilities without enterprise licenses

For cost optimization, this often results in:
– Lower recurring SaaS spend
– More predictable budgeting for growing teams
– Fewer surprise costs when usage increases

2) Flexibility and customization
Our internal data shows that flexibility is the main selling point:
– Highly customizable queues and workflows
– Strong automation capabilities
– Mature data model and good dashboards
– Extensions and an active community

Several Spendbase clients emphasize that a lot can be done with “zero code” configuration; deeper logic is possible with Perl, though that can require technical skills.

3) Daily operations and usability
Clients using RT as a service desk or IT support hub highlight:
– Reliable alerting and notifications
– Solid search and escalation features
– Clear request tracking for IT, HR, and internal ops

The UI is often described as “good and mature,” not flashy but dependable.

4) Technical challenges and gaps
Our internal data also surfaces some recurring pain points:
– Perl-based scripting is powerful but not always friendly for non‑developers
– SSO setup can be tricky and may require extra effort
– Out‑of‑the‑box integrations with some popular tools (like SolarWinds or Confluence) can be limited, pushing some teams toward alternatives such as Jira

5) Where Spendbase usually helps
When we work with teams using Request Tracker, the main optimization levers are:
– Comparing TCO of RT plus hosting/support vs. high‑priced SaaS tools
– Identifying overlap with other ticketing or ITSM tools still in the stack
– Evaluating whether paid add‑ons or external support contracts are sized correctly

In short, our Spendbase clients see RT as a cost‑efficient, highly flexible ticketing system that works best for organizations comfortable with some technical setup and willing to trade “polished SaaS” for control and savings.