Clear project boundaries before work begins.

IrwellCore is an independent, founder-led IT consultancy focused on defined projects. Direct clients can engage IrwellCore for cloud, endpoint, rollout and site-delivery work. MSPs can use the same capability as a white-label delivery partner for larger or time-bound projects.

No. IrwellCore does not sell unlimited end-user support or imply always-on availability. Projects can include stabilisation, documentation and handover, but ongoing incidents should remain with the client’s internal team or nominated MSP.

Yes, where the scope and commercial arrangement are suitable. We agree whether delivery is customer-facing or behind the scenes, how communication will work, and where responsibility returns to your service desk after handover.

Typical work includes Microsoft 365 and Entra ID setup, tenant configuration and migration, Intune and Autopilot projects, identity and access improvements, endpoint baselines and documented remediation. Final scope depends on access, complexity and available capacity.

Yes. Scheduled site visits are available across Greater Manchester for rollout days, equipment changes, checks, evidence capture and vendor-directed tasks. Travel, access requirements and the onsite runbook are agreed before the visit.

Remote project delivery is available across the UK. Onsite work is centred on Greater Manchester, with travel beyond the area considered when the scope and schedule justify it.

Work is proposed as a fixed scope, booked engineering days or a reserved project-capacity block. The proposal separates delivery, travel, licences, third-party costs and anything explicitly outside scope.

Share the required outcome, current environment, user or device volume, locations, target date, known dependencies and the constraint blocking your team. Estimates become more reliable when access and decision-makers are identified early.

Projects use customer-controlled accounts, MFA and least-privilege access wherever the platform permits. Required roles, access duration and removal at handover are agreed with the customer or MSP.

The agreed outcome is validated, configuration and decisions are recorded, outstanding risks are listed and responsibility returns to the nominated internal team or MSP. Any stabilisation period is stated in the proposal.

If the work fits the services and available capacity, the next step is a focused scoping conversation. Written assumptions and a suitable engagement model follow before delivery dates are committed.