How companies using Jam are saving six figures annually

While we've always been delighted to hear from customers that Jam makes debugging faster and easier, we wanted to put concrete numbers behind Jam’s impact to make sure we’re building a product that really makes a meaningful difference for them. We worked closely with our customers to investigate their engineering velocity data before and after deploying Jam, and we’ll share with you the results today.

We worked with customers to measure how quickly high priority tickets were fixed if a Jam was attached vs one where no Jam was attached. They found tickets with a Jam attached were fixed 12 hours faster. This makes sense–– without a Jam, engineers have to manually investigate issues from scratch and wait for back-and-forth communications to gather necessary debug info.

One company found that after deploying Jam, bugs were fixed in a single day instead of 4-5 days. which led to a reduction of 88% bugs reported. In addition, they required 84% fewer troubleshooting calls, instead relying on a Jam – saving both their customers and their engineers from more meetings in the day.

But what does this mean in dollars and cents? First, we’ve found that each Jam saves a minimum of 35 minutes of engineering investigation time. This is actually quite conservative based on our data, but we wanted to err on the side of caution. We then assumed each developer handles roughly three bugs per week.

Taking a mid-level engineer's salary in the US ($175k) and factoring in benefits and taxes ($225k total), we arrived at about $1.80 per minute of engineering time. This means each Jam saves approximately $63 in engineering time (35 minutes × $1.80).

For a single engineer over a year, this adds up to $9,072 in savings, only accounting for direct engineering time saved. We’ve also found it saves companies around $3,000 per PM based on how quickly they can triage & communicate these issues. We haven't calculated in the revenue impact of reduced customer churn from having fewer longstanding issues, or the revenue impact of being able to deliver more new features, though certainly operational efficiency and product quality directly correlate to customer revenue beyond time saved.

Just purely in engineering costs, Jam saves companies $9,000+ per engineer per year. Let's say you have a workforce of 50 engineers, that's a total saving of deploying Jam of $453,600. You can use this ROI calculator to measure the savings you can reliably expect by deploying Jam in your own organization.

If you’re interested in learning more about how other enterprises are using Jam wall to wall, saving their teams $1M for every 110 engineers on their team, you can book a demo.

Thanks for being a part of Jam. We’re really excited about making it a lot faster to develop software because that’s how the future can arrive sooner for everyone. Appreciate you being on the journey with us to make engineering a lot more productive, one Jam at a time.