Alongside
your team

Your team keeps strategy, architecture and the systems that run the business. Menshen operates the platform functions you contract, each with a documented scope, an SLA and its own reporting. In practice: the decisions stay on your side, the day-to-day operation of each contracted service moves to ours, and the boundary between the two is written into each service contract rather than left to be re-agreed every month.

With the same discipline we apply to our own Microsoft 365 tenant. Access is granted on least privilege, with no standing Global Administrator roles, using Privileged Identity Management (PIM) wherever licensing allows. Any change to privileged roles is logged and communicated to your designated approver before execution; a change without a matching record is treated as an incident. The state of privileged access is reported monthly, in its own section of the service report: changes in the period, how many carried a matching record, and any drift against the baseline agreed at onboarding. A month with no changes is reported all the same, with the indicators at zero. Access is granted by your organisation and revocable by it at any time.

Yes. The catalogue is a-la-carte by construction: each service carries its own scope, SLA and price, and is contracted independently. Many organisations start with one function (Microsoft 365 backup, or patch management) and add others once the model has proven itself in their environment.

Each service carries its own documented scope, which defines what is continuous operation and what is a project. Out of scope, and quoted separately: new projects (Microsoft 365 tenant migration, a new VPN, a new server), scope expansions, and hardware or new licence purchases.

No, and be wary of anyone who does. No IT model eliminates risk; this one is structured to minimise it, with a rigorous security baseline, continuous monitoring, low probability on the most damaging events, and predictable recovery when something does get through. The difference between models is not "zero risk" vs "some risk": it is "risk actively managed by a team with tested procedures" vs "waiting for the next incident".

An assessment of your current environment, with no obligation. We audit the functions you are considering handing over, document the state they are in and identify risks. Then a proposal per service, with scope and SLA defined. Onboarding of the contracted service follows, then the steady state: operational reporting and periodic review.