An on premises deployment built around the customer

MedCare MSO needed control over where the solution would run and where its data would live. Instead of fitting them to a SaaS first model, the two teams designed a customer managed deployment together.

  • Starting pointA first group, on premises
  • DeploymentCustomer managed, on premises
  • MilestoneFirst on premises customer

About MedCare MSO

MedCare MSO operates in healthcare revenue cycle management, combining healthcare expertise with intelligent automation and AI enabled workflows.

When its team began exploring Mera Work, the requirement was clear: greater control over where the solution would run, where its data would reside, and how it would fit within its own technology environment.

01

Listening first

Starting with what would work for them

Mera Work's usual SaaS first approach was not what MedCare MSO needed, and that was fine. Instead of asking the team to adapt to the way the product was normally delivered, Mera Work started by understanding what would work for them.

Together, the two teams began shaping a customer managed, on premises approach around MedCare MSO's own environment.

The best customer relationships often start with listening, not selling.

02

The right fit

Requirements as the starting point

For MedCare MSO, the deployment model mattered. So rather than treating its requirements as limitations, Mera Work made them the starting point.

The journey began with an on premises approach designed around MedCare MSO's infrastructure. It was new territory for Mera Work too: MedCare MSO became its first on premises deployment customer, and an important step into the US market.

03

Deployment

Making it work together

The real test of enterprise technology begins when it enters the customer's own environment. As MedCare MSO tested Mera Work, both teams met implementation challenges that had to be worked through. The customer's technical team kept testing and sharing feedback, and the Mera Work team investigated, shared updates and worked alongside them.

It was not a perfectly straight road. It was test, learn, fix, then test again, and gradually the deployment moved forward.

A strong enterprise partnership is not one where challenges never happen. It is one where both teams stay committed to solving them together.

From a requirement to an ongoing relationship

As MedCare MSO's existing licence approached expiry, its team reached out to talk about renewal.

01

Listen

Understand the requirement before proposing a model.

02

Design

Shape a customer managed approach around their environment.

03

Deploy

Begin on premises with a first group of users.

04

Support

Test, fix and test again, side by side.

05

Continue

A renewal conversation as the licence neared expiry.

04

What we learned

Meeting the customer where they are

Some customers help you improve a feature. Others make you think differently about your product. MedCare MSO's requirements encouraged Mera Work to look beyond its SaaS first approach and consider how it could serve organisations that need more control over their infrastructure and deployment environment.

The biggest lesson was not technical. MedCare MSO came with requirements that did not fit neatly into the standard model, and instead of treating that as a barrier, the two teams found another way forward. Sometimes being customer first means rethinking how you deliver, not just listening to what customers want from the product.

Your environment is different. Your solution can be too.

Every organisation has its own technology, security and deployment requirements. If the standard approach does not fit yours, let's explore what will.

Rated by customers on independent review sites

300+ organisations worldwide that run on Mera Work

Read their stories See all clients