Meshimer was designed as a multi-tenant SaaS platform enabling centralized control over diverse edge devices, including network appliances, Windows agents, and mobile devices. The platform required:
Despite strong technical architecture, execution inefficiencies hindered progress
Meshimer is an emerging Software-as-a-Service (SaaS) platform designed to deliver integrated web content security and mobile device management (MDM) solutions for modern enterprise environments. The platform enables organizations to centrally manage, monitor, and secure a wide range of connected devices, including network appliances, Windows-based agents, and mobile devices, through a unified administrative interface. Its core value proposition lies in combining robust security controls with ease of use, allowing organizations to enforce real-time web filtering policies, monitor device health and activity, and generate actionable insights through comprehensive dashboards. Built on a multi-tenant architecture, Meshimer ensures scalability while maintaining strict data isolation across clients using role-based access control (RBAC) mechanisms and end-to-end encryption protocols for data both in transit and at rest. The platform integrates key capabilities such as URL filtering, threat monitoring, device enrollment and tracking, remote configuration, compliance enforcement, and advanced analytics, making it particularly relevant for mid-to-large enterprises operating in security-sensitive industries such as IT services, finance, education, and telecommunications. Positioned at the intersection of cybersecurity, endpoint management, and enterprise SaaS solutions, Meshimer differentiates itself through its integrated approach to security and device management, coupled with a strong emphasis on usability and real-time visibility. At the time of this case, the platform was in an active development phase, with cross-functional teams working across frontend, backend, UI/UX, quality assurance, and architecture to build a scalable and commercially viable product. The organization’s strategic priorities included strengthening system reliability, enhancing user experience, ensuring high standards of data security, and improving delivery efficiency to support long-term growth and competitive positioning.
Upon taking charge, the project manager identified three systemic breakdowns:
Fragmented Communication and Misaligned Requirements
Cross-functional teams operated in silos, leading to:
There was no centralized “single source of truth.”
Misuse of Agile Infrastructure
Although Azure DevOps was in place, it was reduced to a task tracker. Thereby, there was no backlog management, no sprint planning, or estimation and specifically no release coordination
Work allocation was reactive rather than strategic, resulting in inconsistent delivery
Lack of Performance Visibility
Stakeholders lacked transparency due to the absence of KPIs, no progress dashboards and very limited structured reporting. This led to declining confidence and weak governance
A three-pronged transformation strategy was implemented:
To eliminate silos and improve alignment:
Impact:
Communication shifted from fragmented and reactive to transparent, traceable, and proactive
The project transitioned from ad hoc execution to structured Agile delivery:
A structured workflow was introduced:
As a result the delivery became predictable, measurable, and scalable
To rebuild stakeholder trust:
The impact was seen in Decision-making, which shifted from intuition to data-driven governance
Operational Efficiency
Predictability and Planning
Stakeholder Confidence
Leadership Leverage
Structure Enables Speed
Communication Is a System, Not an Activity
Data Builds Trust
Planning Reduces Complexity
Despite significant improvements, the project team faces several forward-looking questions:
This case is best suited for courses in Project Management, Agile & Digital Transformation and Operations Management. It enables discussion on agile implementation in real-world contexts, and change management in technical teams and the role of data in leadership and governance
Exhibit 1: Pre- vs. Post-Intervention Operating Model
Exhibit 2: End-to-End Delivery Workflow
Exhibit 3: Dashboard Metrics Introduced
Exhibit 4: Root Cause Analysis of Initial Challenges
Exhibit 5: Time Allocation Shift (Project Manager)
Insight: Agile systems reduced operational burden, enabling strategic leadership
Exhibit 6: Value Creation Pathway
Imran Ali Khan and Zeeshan Ali Khan were two brothers.