When enterprise security puts the product to the test: LifeCell and Mera Work

LifeCell put Mera Work through a demanding technical and security evaluation in its real environment before deciding to move forward.

Talk to Our Team Book a Free Demo

First stepA detailed evaluation in its real environment
The testTechnical compatibility, security and reporting
The outcomeApproval, procurement and implementation

About LifeCell

LifeCell was not looking for a proof of concept that worked only under ideal conditions. The team wanted to see how Mera Work would perform inside its actual enterprise environment, alongside existing security controls, across different operating systems and with the reporting requirements its teams would eventually rely on.

So they tested it properly. Technical issues surfaced. Security questions followed. Some troubleshooting approaches were challenged. Rather than rushing towards a decision, both teams kept working through the details.

The evaluation

Testing Mera Work in the real environment

From the beginning, the evaluation reflected LifeCell's actual technology landscape. The team evaluated Mera Work across Windows, macOS and Linux, while also looking at attendance, dashboards, screenshots, alerts, user roles, bulk uploads and centralised deployment.

Different groups needed different ways of interacting with the platform. Management and reporting teams needed access to dashboards and workforce information.

This was not simply about seeing whether the features worked. It was about seeing whether Mera Work fitted into the environment where it would actually be used.

The challenge

When the environment became part of the test

During the evaluation, some Windows systems experienced issues with data recording. The behaviour was not consistent across devices, which made the investigation more complex. Both technical teams reviewed logs, certificates, SSL behaviour, endpoint security and network configuration.

The evaluation was extended so there was enough time to understand what was happening rather than forcing a decision around the original timeline. By then, the question was no longer whether Mera Work works in a demo. It was whether Mera Work can work within the realities of an enterprise environment.

The security standard

Security was not something to work around

During certificate troubleshooting, a temporary diagnostic approach raised concerns within LifeCell's IT team because it involved bypassing certificate validation. LifeCell pushed back. The team wanted the underlying problem addressed without weakening its security protocols.

That set a clear expectation: Mera Work needed to work within LifeCell's security standards, not around them. The investigation continued, a certificate chain issue was identified on the Mera Work side, and the certificate configuration was changed. LifeCell tested again, and the affected functionality was validated on a test system.

The reporting

Reporting had to make sense too

LifeCell also wanted the workforce information to reflect the way its teams actually worked. The team looked closely at productive, unproductive, idle and neutral time, together with employee level and department level reporting.

That led to a practical question: what should actually count as productive work at LifeCell? The answer depended on the tools its teams genuinely used. LifeCell shared relevant development, engineering, collaboration, cloud and AI applications, and the productivity classifications were adjusted accordingly.

Approval

Enterprise readiness had to be earned

LifeCell did not move directly from technical testing into procurement. There were management, audit and internal approval requirements to work through too. Mera Work had been examined from several angles: technical compatibility, security, deployment, workforce reporting and management requirements.

Only after those areas had been worked through did LifeCell move into approval, procurement and implementation. Once it did, the team began working with views such as team visibility, Dashboard reporting, screenshots, time tracking, activity information and Productivity Breakdown. The technical conversation continued after implementation, with LifeCell's IT team working with Mera Work's Customer Success and technical teams whenever environment specific questions needed closer attention.

The journey

Each step was tested, questioned and worked through before the next.

Evaluate

A detailed evaluation across a mixed technology environment.

Challenge

Technical and security questions raised.

Investigate

Both teams reviewed logs, certificates and network configuration.

Resolve

The certificate configuration was changed.

Validate

The affected functionality was tested again.

Configure

Productivity classifications aligned with LifeCell's tools.

Approve

Management, audit and internal approvals.

Implement

Moved into everyday use.

The journey at a glance

The starting point: A detailed enterprise evaluation across a mixed technology environment.
The evaluation: Technical compatibility, security, deployment and workforce reporting.
The challenge: Real technical issues surfaced when Mera Work met the enterprise environment.
The security standard: LifeCell challenged an approach that did not meet its security expectations.
The resolution: Both teams investigated, tested and worked through the issues.
The reporting context: Productivity classifications aligned more closely with the tools LifeCell's teams use.
The everyday use: Different workforce views became part of the experience after implementation.
The decision: The evaluation progressed through internal approval into implementation.
The ongoing relationship: Technical collaboration continued after implementation.

Find the visibility that fits your environment

Mera Work is built to be tested against your own systems, security standards and reporting needs. Start free with your team and see how it fits.

Start Free with Your Team Book a Free Demo Talk to Us