You're busy adding features to the Rails app you're working on. Models, controllers, views, decorators, tests, API, JavaScript, there's so much of everything.
Focusing on the code makes it very hard to control the production environment at the same time. You're not some kind of a multitasking monster. The business expects it from you, though.
This is hard.
Worse, gone are the days when you're working on one application at one time. There is this app, that is no longer in development. You need to keep an eye on it. How is it performing? Was it Rails 2 or Rails 3? How is the current app performing? Do you know how many people use it every day? Are you able to track if they can succeed with their use cases? It's almost impossible, given your focus on the quality code of the current feature.
A phone call with your client and the question:
“Hey, how many new users we're having this week?”
No time for launching the rails console. Silence. Stress. You don't know how things are performing in your projects.
What if I tell you that it's possible to know how your projects are going? Imagine that it's you who's informing your customers about the good news in the application trends, before they even ask. Imagine the phone call with them in such situations.
What if I tell you that the most important numbers can be delivered to you in a non-overhelming way, just before your morning coffee, with no effort from your side?
20-seconds scan of the email and you know everything that's important.
Think what you're going to do with the time saved by not launching the Rails console for every app, every day.
Your customers will know they can rely on you ‐ more projects, more cash.