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

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

Early Renewal or Prepayment: Jam 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 Jam is especially loved by product and QA teams who need to pass clear bug context to engineers with almost no friction.

From what our Spendbase clients share, the strongest points are:

• One-click capture
• Rich technical diagnostics included automatically
• Faster handoff between non-technical and technical teams

Key strengths our clients highlight:

1. Ease of use
   – Simple browser extension, minimal onboarding
   – “1 click” to start capturing issues
   – Very low barrier for non-technical teammates

2. Quality of bug evidence
   – Console screenshots are a big win for engineers
   – Automatic capture of:

   • Network requests
   • Browser details
   • Reproduction steps
   • Ability to download videos for documentation or demos
   • Option to speed up videos is handy for presentations and quick internal reviews

3. Collaboration & communication
   – Sharing one link with full context cuts back-and-forth dramatically
   – Helps align product, support, and engineering around the exact same bug scenario

Areas where our clients see room for improvement:

1. Human presence in recordings
   – The most common ask: support for including the person in the video (similar to tools like Loom)
   – Our clients believe face or camera bubbles could:

   • Increase engagement
   • Make async communication more personal
   • Help with stakeholder presentations or customer updates

2. Advanced communication features
   – Some teams would benefit from richer annotation and commenting inside the recording
   – A few would like more control over editing or trimming clips without exporting elsewhere

How this translates into savings (our Spendbase angle):

• Fewer engineering cycles wasted reproducing bugs
• Less meeting time needed to “walk through” issues live
• Faster time-to-fix means less risk of churn from unresolved bugs

In short, our internal data shows that Jam is a high-impact, low-friction tool for bug reporting, with standout diagnostic capabilities. The main gap is around more “human” video features for teams that want both technical depth and personal async communication.