JRebel: value calculator

What will JRebel do for my team?

You’ve probably already taken a look at the JRebel for Teams page, where we cover the most commonly asked questions about using JRebel. The three step process below will give you a good idea of the value and ROI from using JRebel on your team.

Step One: List Assumptions

Developers don't code all day - so we're going to base our time savings calculations on 5 hours of coding per day. When it comes to "full days gained" - those are 8 hour days.
4 weeks every year are considered lost, due to vacations, holidays, other interruptions.
“Turnaround” = Time spent on the Build and Redeploy phases of Java development.

“Engineers are expensive - anything we can do to improve their productivity is an easy business case.

Arnold Goldberg, LinkedIn

“I really like the quick feedback of making a change and seeing it immediately.

Tuomas Karkkaenen, Reaktor Innovations

“We were looking for a good way to improve productivity. JRebel was a quick win.

Arnold Goldberg, LinkedIn

“I'm saving about 30 minutes per day... probably more.

Tuomas Karkkaenen, Reaktor Innovations

Step Two: Input Data

Where do these numbers come from?

The Avg Turnaround Time and Avg number of App Restarts stats come from the Java EE Container Redeploy Report, which collected information from 1100+ Java EE developers.

Productivity Award

Step Three: Results

Turnaround Costs Your Team	With JRebel you get
25,000 developer-hours annually, worth 1,250,000 USD of your development budget, equivalent to 625.0 40-hour developer-weeks per year.	500.0 extra 40-hour developer-weeks per year, by saving 50 minutes per day per developer.

Your team can use this time to code new features, fix bugs, improve code quality and finish more projects delivering better software, faster. Given your developer's wages, JRebel will pay for itself in 4.54 days.