Quantifying Value: Why BRMS is Like a Day at the Beach

SaMT

Sales and Marketing Teams

09/16/2013

I’m lucky enough to live in middle of the Indiana Dunes National Lakeshore, a half mile from our beautiful town beach. While I enjoy all the seasons, it’s summer I live for: as much as I can, I spend weekend afternoons on the beach. With each swim, as summer begins to fade, I wonder if this will be the last. Yesterday was one of those days, a little chilly, a day that in July would have seemed unfit for the beach. But in mid-September, such a day looks different: it looks like the last swim of the season. Can I quantify the value of this last afternoon on the beach? In fact, yes. To spend the afternoon at the beach, I had to put off work (including writing this blog) to Sunday, typically a day of rest for me. In our personal lives, we quantify the value of what we do by the trade-offs we make; the time and money we spend; how our choices affect our finances, our career, our relationships: our mind, body, and spirit; and the memories we create.

In business, we are increasingly being asked to do more with less and to quantify the return on our investments of time and money. As a marketer, I’m measured by leads and, ultimately, revenue. IT is increasingly measured in how their investments deliver business results—faster time to market, lower costs, improved quality, increased revenues.

Over the years, we’ve heard amazing stories of quantified value from our user community. Customers have shared that the quality (measured in reported bugs) of the rules-driven portion their systems is much higher than the code portion, even though it is changed more frequently. We’ve seen reduced delivery times and increased revenues. And we’ve seen our BRMS fundamentally change the nature of application development (read more in Loren Goodman’s white paper Getting to the Handshake). We’ve seen that our technology enables this change in application development and that this delivers this quantifiable value.

On Tuesday, September 17, 2013 we’ll unveil highlights of the 2013 InRule user community survey. Here’s a preview: InRule user community members saved an average of $488,059 using InRule versus hard code. They’ve reduced maintenance costs, improved quality, and are better able to react to marketplace changes. Being able to react to marketplace changes more quickly is increasingly important in this, what Forrester analyst John Rymer calls, “the Age of the Customer.” (Customers include residents and citizens of government agencies.) John has identified key technologies for delivering easily configurable, device-agnostic, easy and fun to use customer-facing applications and BRMS is central. In talking with John he said he doesn’t know how organizations can deliver these applications without BRMS.

As organizations seek to meet and exceed customer expectations and to proactively offer them products and services that best suit them, they will be making strategic decisions in the technologies they use to deliver these applications. Our user community proves that InRule delivers quantifiable value.

Today is cool, dark, and raining; I’m pretty happy with yesterday’s beach decision. My last swim of the season is like the Age of the Customer: a great opportunity that must be seized and whose value can be quantified. Organizations that seize this opportunity will see quantifiable results; they will prosper, enjoying that last swim in the lake. Those that don’t will lose customers to competitors, their costs will increase, and their revenues will decrease. The value is quantifiable. Come on in, the water is fine.; I’m lucky enough to live in middle of the Indiana Dunes National Lakeshore, a half mile from our beautiful town beach. While I enjoy all the seasons, it’s summer I live for: as much as I can, I spend weekend afternoons on the beach. With each swim, as summer begins to fade, I wonder if this will be the last. Yesterday was one of those days, a little chilly, a day that in July would have seemed unfit for the beach. But in mid-September, such a day looks different: it looks like the last swim of the season. Can I quantify the value of this last afternoon on the beach? In fact, yes. To spend the afternoon at the beach, I had to put off work (including writing this blog) to Sunday, typically a day of rest for me. In our personal lives, we quantify the value of what we do by the trade-offs we make; the time and money we spend; how our choices affect our finances, our career, our relationships: our mind, body, and spirit; and the memories we create.

In business, we are increasingly being asked to do more with less and to quantify the return on our investments of time and money. As a marketer, I’m measured by leads and, ultimately, revenue. IT is increasingly measured in how their investments deliver business results—faster time to market, lower costs, improved quality, increased revenues.

Over the years, we’ve heard amazing stories of quantified value from our user community. Customers have shared that the quality (measured in reported bugs) of the rules-driven portion their systems is much higher than the code portion, even though it is changed more frequently. We’ve seen reduced delivery times and increased revenues. And we’ve seen our BRMS fundamentally change the nature of application development (read more in Loren Goodman’s white paper Getting to the Handshake). We’ve seen that our technology enables this change in application development and that this delivers this quantifiable value.

On Tuesday, September 17, 2013 we’ll unveil highlights of the 2013 InRule user community survey. Here’s a preview: InRule user community members saved an average of $488,059 using InRule versus hard code. They’ve reduced maintenance costs, improved quality, and are better able to react to marketplace changes. Being able to react to marketplace changes more quickly is increasingly important in this, what Forrester analyst John Rymer calls, “the Age of the Customer.” (Customers include residents and citizens of government agencies.) John has identified key technologies for delivering easily configurable, device-agnostic, easy and fun to use customer-facing applications and BRMS is central. In talking with John he said he doesn’t know how organizations can deliver these applications without BRMS.

As organizations seek to meet and exceed customer expectations and to proactively offer them products and services that best suit them, they will be making strategic decisions in the technologies they use to deliver these applications. Our user community proves that InRule delivers quantifiable value.

Today is cool, dark, and raining; I’m pretty happy with yesterday’s beach decision. My last swim of the season is like the Age of the Customer: a great opportunity that must be seized and whose value can be quantified. Organizations that seize this opportunity will see quantifiable results; they will prosper, enjoying that last swim in the lake. Those that don’t will lose customers to competitors, their costs will increase, and their revenues will decrease. The value is quantifiable. Come on in, the water is fine.

InRule for JavaScript | inrule said: "[…] couple of weeks ago we announced availability of InRule® for JavaScript through an early adopter program. To our knowledge this is […]".
Dynamic Surveys in Dynamics CRM Part II: Managing Dependencies | inrule said: "[…] this post makes extensive references to my preceding post, Surveys in Dynamics CRM Part I: Don’t Be a Monkey With Your Survey. If you are the type of person who likes to get the full story, you should go back and read the […]".
Josh Elster said: "In the time since this post was published, I've added (via a PR) full Windows Containers example code, DOCKERFILEs and scripts. They share common ancestry with the GH Gists I posted earlier, but are more up-to-date and tested. Here's a direct link to that sub-folder: https://github.com/InRule/Samples/tree/master/Developer%20Samples/WindowsContainers Now that our Samples repository is public, feel free to file Issues if you have problems or features you'd like to see implemented. If you have something you'd like to contribute, then by all means do so! The contributor guidelines and process are listed in the root of the repository. Enjoy! I'll update the body of the post as well with this link.".