Whether it was a home remodeling job or the deployment of new technology for a business, we all have stories to tell about the project we wish we’d never started in the first place. When purchasing or replacing a Risk Management Information System (RMIS), choosing Origami Risk means you won’t repeat the experience.

Origami Risk was founded a decade ago by industry veterans who recognized that improvements in the development, delivery, and support of RMIS technology were long overdue. A central component of the changes they introduced, and that we’ve continued to refine, is an approach to implementation and ongoing support that is different by design.

This approach is made up of four key elements:

• Collaborative expertise
• Iterative delivery
• Flexible technology and system accessibility
• Consistency and autonomy

In combination, these elements enable Origami Risk and our clients to implement RMIS software efficiently and with fewer headaches.

A collaborative process, guided by experts

The Origami Risk service team is made up of the most experienced professionals in the industry. With degrees from top-rated risk management programs and experience accumulated over years in the risk and insurtech industries, our team brings a combination of business knowledge and technical skills to each client implementation. Although their resumes and backgrounds are unique, members of our team have the following trait in common: each is a problem solver looking for the “why,” not just the “what.”

Rather than simply recreate the old, Origami Risk sees RMIS implementation as an opportunity to collaborate with our clients and improve their overall risk management efforts. Part of this approach is taking an in-depth look at data, reports, and workflows in an effort to ensure each supports your business objectives. This can only be accomplished with a team that combines an understanding of insurance and technology experience.

An iterative delivery process promotes communication and engages users

In the past, implementations of legacy RMIS technology commonly included gaps in communication that could last for weeks. While the vendor was coding and customizing, clients were left to wonder if their requests were understood and would be incorporated. Too often, this was not the case. Delays, cost overruns, and changes in scope were not uncommon, to say nothing of the frustration and frayed nerves on both sides.

Origami Risk changes this paradigm using a process that involves not only weekly meetings, but continual communication in the form of emails, phone calls, and—when possible—face-to-face conversations. The reason is simple: implementing a RMIS is a complex undertaking. One size does not fit all. Constant communication is key to getting it right the first time.

Starting week one, there are deliverables for you to review and follow-up for the week ahead. Results and feedback are gathered and distributed in advance of regular meetings that continue throughout the entire implementation. This enables us to pivot to a more optimal solution, should one arise. It also acts as an additional form of training that prepares users for go-live well before the arrival of the go-live date. Just as you depend on us to get your system set up, the Origami Risk team depends on you to help us get it right.

Flexible technology and system accessibility help streamline the process

Origami Risk was built from the ground up by our founders, who set out to build the RMIS they’d always wanted:

• one built on a scalable platform that is easy to maintain and to which functionality can be added within the base code,
• one that interfaced well with the third-party systems on which clients depend, and
• one that empowers clients to take control if they feel comfortable doing so.

Why build a system from scratch? While choosing to build upon an existing third-party software platform would have meant a quicker move to market, doing so would have imposed constraints that, ultimately, might prevent Origami Risk from fully serving our clients.

In the Origami Risk system, making changes to fields, labels, forms, data mappings, batch import or export processes, point-in-time reports, loss triangles, notifications, alerts and security permissions can all be done through the front end. No custom code required.

During implementation and as part of ongoing support, this means that changes are often accommodated during the call in which it is outlined. Additionally, with system updates every 6-8 weeks, you don’t wait months to use new functionality. Origami implementations move quickly because our technology doesn’t require a large-scale project or the updating of roadmaps when you see different and better ways of doing things.

Consistency and autonomy contribute to better implementations and ongoing support

Arriving at “go-live” with a system that meets all of the points laid out in a Statement of Work is the very definition of success. It is, of course, not the ultimate goal. Like our approach to system implementations, the Origami Risk service model is different by design. Rather than handing you and your system off to a random member of another support team— one not involved in the implementation—or pushing you toward a call center, your implementation team continues to work with you. There is no handoff. The team that implements your RMIS is the team that supports you on a go-forward basis.

As RMIS experts, solving problems and contributing to the success of our clients is why we do what we do. Navigating a bureaucratic system of sign-offs? Not so much. Because we hire experts that we trust, your senior client executive has the authority to make the change you request. There’s no need to escalate an issue or schedule a meeting with their team lead to get permission. Instead, they roll up their sleeves and get to work. As a result, people want to work here. This is underscored by the fact that we’ve consistently been voted one of Business Insurance’s Best Places to Work in Insurance.

This means that when you pick up the phone with a question or request, you’ll be talking to the person with whom you’ve worked for months or years—someone who not only knows the system, but understands your business objectives.

Elevate your approach to identifying, managing, and reducing risk

For those evaluating their options for moving on from spreadsheets or leaving behind the limitations of a legacy RMIS system, a question seldom asked during initial conversations and system demos is this, "Will moving from our old system wreak havoc on me and my team for the next twelve months?"

We understand that fear. We designed a different approach to RMIS implementation for just that reason. If you’d like to have a thoughtful conversation, we’re ready to listen.