Managed IT services or project-based consulting: which do we need?

Key facts

• Projects deliver a defined outcome; managed services deliver ongoing operations.
• A project should end with documentation and knowledge transfer, not dependency.
• Recurring work billed as one-off projects usually costs more and gets less attention.
• Large changes inside a managed contract are usually scoped as separate projects.
• The best order is often project first, to set a baseline, then managed service.

The basic difference

Project-based consulting is paid to change something. It has a scope, a timeline, a fixed or estimated price and an end point. Examples include moving from Google Workspace or Exchange Server to Microsoft 365, consolidating tenants after an acquisition, rolling out Intune and Autopilot, deploying Conditional Access or building a SharePoint intranet.

Managed IT services are paid to keep something running. They cover recurring tasks: onboarding and offboarding, license changes, security alert review, device compliance, Windows update rings, backups, Microsoft change tracking and user support. The value is consistency, not a single outcome.

Signals you need a project

• There is a deadline: Exchange Server end of support, Windows 10 retirement, an acquisition close date or a cyber insurance renewal.
• You are moving data, mailboxes, identities or devices from one platform or tenant to another.
• An assessment found gaps that need design work, such as no Conditional Access or wide-open SharePoint sharing.
• You want a new capability: Teams Phone, Power Apps, Copilot or Claude, Autopilot.
• Your internal team can run the environment but has never done this specific change.

Signals you need a managed service

• Routine admin tasks pile up or get done inconsistently.
• Nobody reviews Defender alerts, risky sign-ins or Secure Score regularly.
• Offboarded staff still have licenses, active sessions or mailbox access.
• Microsoft Message Center changes surprise you after they reach users.
• You have no internal IT staff, or one generalist who is stretched thin.

Why many organizations need both

A managed service inherits whatever state the tenant is in. If admin roles, Conditional Access and sharing settings were never designed, the provider spends months firefighting. A short project first, such as a tenant health check or security hardening, gives the managed service a documented baseline.

The reverse also applies. A project that ends without anyone to maintain the result tends to drift. Policies get exceptions, new sites ignore the governance model and nobody tracks Microsoft changes. Pairing the project with a managed service, or with a well-trained internal owner, protects the investment.

Cost drivers for each model

Project cost is driven by scope: number of users, mailboxes, data volume, sites, devices, locations, integrations, cutover windows and how much documentation and training you need. A fixed price set after discovery reduces surprises, because the unknowns are found before the number is agreed.

Managed service cost is driven by headcount, device count, the breadth of tasks included, response targets, coverage hours and how much proactive review is in scope. Compare providers on the written scope, not just the monthly figure.

Watch for the hidden cost of the wrong model. Running a migration through a managed help desk often means it is done in spare hours and drags on. Paying project rates for routine admin every month wastes budget.

How to decide

List the work you need over the next 12 months. Put each item into one of two columns: changes with an end point and tasks that repeat. If most items repeat, start with a managed service and scope projects as needed. If the list is led by one or two big changes, start with a project and decide on ongoing support once you see the finished state and the handover documentation.

How Accred Consulting approaches it

Accred Consulting delivers both models. Projects follow a set process: Discovery, then a Proposal with clear scope, fixed price and timeline, then Delivery with structured check-ins and a Handover with documentation and knowledge transfer. After handover, clients can keep the work in-house or choose an optional Support retainer for ongoing administration and review. Either way, you work directly with the US-based specialists assigned to the engagement, with no offshore handoffs. Accred has delivered 475+ client projects and can scope a baseline project first, then a retainer that maintains it.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions