Return of the Guru

Doing More with Less: It's Not Just for Insurers

Ara Trembly
Insurance Experts' Forum, September 7, 2010

Recently I had the opportunity to listen in on some conversations between a major policy administration system vendor and an analyst regarding the vendor’s current and future offerings.

While confidentiality prohibits me from sharing details, I was struck by the fact that the vendor in this case wasn’t just interested in who would buy their current offerings or their planned future products. Instead, both parties were talking about extracting every bit of value from the vendor’s new and existing products—even those that already promise to meet stated business needs.

So what I am talking about? Simply this: Since 2008, we have heard nothing more clearly than that insurers operating in this tight market and sickly economy need to do more to sustain competitive advantage and position themselves for growth—and they need to do it with fewer resources—both monetary and human. Technology vendors, however, are subject to the same market forces and general economic decline that have put insurers, agents and others between a rock and a hard place. Vendors, too, must figure out ways to do better using the reduced resources available.

But, how does a technology provider go about doing more with less? Vendors make their money in two primary ways—providing new products and maintaining existing ones. Getting new products out there seems pretty straightforward: Find an area of need and fill it. But today’s economic climate demands a further step and an expanded way of thinking about the market.

Instead of just developing a product that satisfies a need in one market, why not put together something that meets a need in two or more markets? Alternately, a vendor could develop a product that meets more than one need in a market. This kind of thinking could be carried further, perhaps to find a new need for an existing product in the same market and/or in several markets.

Perhaps you’re a vendor who is developing a new product line for a well-defined market like insurance. But could that product be adapted to serve equally well in another industry? Or could a module or part of your new product be offered in conjunction with a competitor’s product in order to yield a “best of breed” solution that benefits you and your competitor? Maybe you could develop your new product line in such a way that the individual parts can be sold alone, marketed to other vendors, or packaged with some other product in a cooperative venture.

This same kind of creativity could be applied to the other major function vendors provide—product maintenance. Let’s say your company is really good at maintaining your products; could you expand into maintaining similar products elsewhere? Could you provide integration services for the many enterprises that mix multiple platforms and/or product lines?

I’ve asked a lot of questions here, and your answer to many of them may be in the negative. Then again, perhaps there is an idea or two that seems within the realm of possibility. Making the most out of a bad situation is a matter of creativity, and it’s the creative vendors who will come out smelling like a bouquet of roses when this economic mess finally resolves itself.

Ara C. Trembly ( is the founder of Ara Trembly, The Tech Consultant, and a longtime observer of technology in insurance and financial services.

Readers are encouraged to respond to Ara using the “Add Your Comments” box below. He can also be reached at

This blog was exclusively written for Insurance Networking News. It may not be reposted or reused without permission from Insurance Networking News.

The opinions of bloggers on do not necessarily reflect those of Insurance Networking News.

Comments (1)

The concept of "More with Less" has about run it's course. It was so beaten to death, in the insurance industry, even before the recession, that it is not applicable, now that it might be needed.

In real terms it usually means cutting or letting attrition cut the staff. It really means someone or several someones have to work harder, longer and for the same or less money. As a short term solution it was feasable but, as usual, it was over used and over extended by too many employers.

In the end you can cause your service to suffer. In the extreme you can loose so much business, or key employees, that the entire enterprise suffers. During this time of many well seasoned and intelligent employees in the job market, it would seem a great time to seek and hire the best, pay them a reasonable amount and improve your service and product delivery. There are many "bargains" out there, time to "buy" and improve from the investment.

Posted by: elevans66 | September 13, 2010 4:28 PM

Report this Comment

Add Your Comments...

Already Registered?

If you have already registered to Insurance Networking News, please use the form below to login. When completed you will immeditely be directed to post a comment.

Forgot your password?

Not Registered?

You must be registered to post a comment. Click here to register.

Blog Archive

The Other Auto Insurance Telematics Shoe Drops

Progressive's decision to charge Snapshot drivers more if their driving data indicates higher risk has started the industry down a road of data-driven adverse selection.

Core Transformation – Configuring in the Rain

The whole point of core transformation is that changes at the micro level can be used as a stimulus for changes at the macro level.

6 Ways to Develop a Productive IT-Business Dialog

Relationship management 101 for keeping IT and business on the same page.

Unified Digital Strategy: Succeeding in the Digital Revolution

A unified digital strategy recognizes that all business strategies and technologies touch the customer in some way and that a one-size-fits-all channel model is obsolete.

Agile and Continuous Delivery in a Regulated Environment

Just because a development team is doing continuous delivery or packaging releases into two-week sprints doesn’t mean that code is being moved to production.

Dealing with the COBOL Brain Drain

Documentation on aging systems often is akin to tribal knowledge, and the potential for things to go bump in the night increases as these environments face generational transition.