Three jobs, not three price points
Running systems, solving a defined problem and owning technology direction are different jobs. Compare the options on the job you need done, not on the rate.

Hire a managed IT provider to keep your systems running, an IT consultant to solve one defined problem, and a fractional CTO when technology decisions need an owner for months rather than weeks. Most established businesses outside the tech industry need the first two well before the third, and good founder-led technology consulting starts by telling you which one you are.
The three get confused because all of them sell help with technology. They work at different altitudes: one keeps the lights on, one fixes a problem and leaves, one decides where the business goes next. Buying the wrong altitude is how businesses end up paying strategy rates for password resets, or getting no strategy at all.
Running systems, solving a defined problem and owning technology direction are different jobs. Compare the options on the job you need done, not on the rate.
If nobody owns patching, backups and staff support, that's the gap to close. A strategist won't fix it, and shouldn't be paid to try.
The firm that sells and manages your systems has a stake in what you buy next. Keep major decisions with someone who doesn't profit from the answer.
Admin access, domains, licences and data belong in the business's name, whoever manages them. Outside help gets delegated access, never the only copy.
If staff need support and systems need care, start with managed IT. If one decision or project needs expert judgment, hire an IT consultant. If technology is central to growth and nobody senior owns it, bring in a fractional CTO.
A managed IT provider, often called an MSP, runs your technology day to day for a recurring fee: support, security, backups and updates. An IT consultant is hired for one defined problem and leaves when it's solved. A fractional CTO is a part-time technology executive who owns direction and decisions over months.
| Factor | Managed IT provider (MSP) | IT consultant | Fractional CTO |
|---|---|---|---|
| Main job | Keep systems running and secure | Solve a defined problem | Own technology direction |
| Question it answers | Is everything working today? | What should we do about this? | Where should our technology go next? |
| Engagement | Ongoing, under a service agreement | A scoped project with an end | Part-time, over months |
| Typical work | Help desk, patching, backups, devices, monitoring | Assessments, system selection, migration plans, second opinions | Roadmap, budget, build-or-buy calls, vendors, technical people |
| Accountable for | Uptime and the response times in the agreement | The quality of the recommendation | Decisions and how they turn out |
| Best when | Staff need support and systems need care | One decision or project needs expertise you don't have | Technology is central to growth and nobody senior owns it |
| Watch for | Recommending what it also sells and manages | A report nobody carries out | Paying an executive to do operational work |
A fractional CTO owns your technology decisions part-time. They set the roadmap, decide what to build, buy or retire, hold vendors and developers to account, and translate technology into budget and risk for leadership. The role earns its place when technology decisions are frequent, expensive and connected, not when you need one answer.
Ownership is the difference. A fractional CTO who only advises is a consultant with a longer contract. Ask which decisions they'll be accountable for, and who has the final say when they disagree with your team.
Many of those calls come down to whether to build custom software or buy it, and a good technology lead makes that call one system at a time.
An IT consultant brings expert judgment to one scoped problem: choosing a system, planning a migration, reviewing your security, untangling a setup that grew without a plan, or checking a vendor's quote. The engagement ends with a recommendation, a plan or a finished project. They aren't there to answer staff tickets, and they shouldn't stay longer than the problem.
The risk with consultants is the opposite of the risk with managed IT. A recommendation nobody carries out is an expensive document. Before you sign, ask who implements the plan, and whether the consultant stays through the build or hands it to someone else.
AI work has its own version of the role, with its own rules. Here's what an AI consultant actually does, and when you need one.
Managed IT services cover the ongoing operation of your technology: a help desk for staff, device and account management, security patching, backups, monitoring and outage response. You pay a recurring fee under a service agreement that should spell out response times. The provider keeps things running. It isn't set up to decide where your technology goes next.
For an established business with staff and equipment, some version of it is non-negotiable. The real questions are whether it's in-house, outsourced or a mix, and whether the agreement says plainly what happens when something breaks.
Canada's Cyber Centre publishes guidance for organizations that use managed service providers. It recommends settling security requirements, incident response times, data residency and how you get your data back before you sign, because your organization stays the data owner and remains legally responsible for its security.
Start with the gap you're trying to fill. If systems are unreliable and staff wait for help, you need managed IT. If one decision or project is beyond your team, you need an IT consultant. If technology decisions keep coming, cost real money and nobody senior owns them, you need a fractional CTO. Many businesses need two at once.
| If… | You need |
|---|---|
| Staff wait days for help and nobody owns patching or backups | Managed IT, in-house or outsourced |
| You're choosing a major system and can't judge the options | An IT consultant |
| Vendor quotes arrive and nobody can tell whether they're reasonable | An independent IT consultant |
| A project has stalled because nobody can make the technical call | An IT consultant, scoped to that project |
| Technology decisions come up every month and each one affects the next | A fractional CTO |
| You're building software or managing developers without technical leadership | A fractional CTO |
| Systems run fine and big decisions are rare | Neither yet. Bring in a consultant when the next big decision arrives |
The costly mistake is buying the most senior option for an operational problem. An executive is wasted on device management, and a help desk is wasted on strategy.
Not on its own. A managed IT provider is paid to run the systems it manages, and many also resell the hardware, software and licences inside them. Its advice can still be good, but it isn't independent. Keep major decisions with someone who doesn't profit from the answer, and let the provider carry them out.
Strategy also works at a different altitude. A provider measured on tickets closed and uptime is focused, rightly, on today. Direction means asking which systems you should stop paying for, what should connect to what, and what the business will need in three years. Those are leadership questions.
None of it makes managed IT the problem. Splitting the roles is what keeps both honest: the provider runs, someone independent decides, and each can check the other.
Everything the business would need to replace them: admin access, domains, software licences, cloud and email accounts, backups, documentation and passwords held in a manager you control. Outside help can hold delegated access. It shouldn't hold the only keys. If a provider leaves or fails, you should be able to hand everything to the next one without asking permission.
It's the same test of what you keep when an engagement ends that applies to every outside partner, from your IT provider to whoever builds your website.
Ask about decisions, not just credentials. A good candidate asks more about your business than they talk about technology, can tell you what they'd recommend against, and says plainly who does the implementation. Ask whether they earn commissions or referral fees from vendors they recommend, and get that answer in writing.
The same conflict of interest shows up in automation work. The vetting questions for a business automation consultant go deeper on how to tell an adviser from a reseller.
Start with what's missing. Choose managed IT if day-to-day operations are slipping, an IT consultant for a defined decision or project, and a fractional CTO only when technology decisions are frequent, connected and costly, with nobody senior owning them. Whichever you choose, keep the accounts in your name and keep strategy independent of what you buy.
We work on the decision and build side of digital infrastructure: websites, apps, search and AI. I'm the practitioner on every SyncDS engagement, and when a decision turns into AI and modernization work, the build happens under the same roof.
It depends on how many days a month they work, how long the engagement runs and what they're accountable for. Compare it with the full cost of a senior technology hire, including salary, benefits and recruiting, and with the cost of decisions nobody is making. A firm price before scoping is a guess.
For a defined problem, a scoped project price is usually clearer, because you know the deliverable and the total before work starts. Hourly billing suits open-ended troubleshooting. Either way, get the scope, the deliverables and what counts as done in writing before anyone starts.
Usually not a full-time one. Most small and mid-sized businesses outside tech need reliable operations and good decisions at a few key moments. A full-time CTO makes sense when technology is the product, or when you employ a development team that needs senior technical leadership every day.
They overlap. A virtual CIO, or vCIO, usually focuses on internal systems, infrastructure and IT operations, and the title is often bundled with a managed IT contract. A fractional CTO usually focuses on the technology that shapes your products, services and customer experience. Check the scope, not the title.
IT services is the broad term for any technology help, including one-off repairs, projects and consulting. Managed services means a provider takes ongoing responsibility for running part of your technology under an agreement, usually for a recurring fee, with response times and coverage defined in advance.
It can, and it's convenient. The trade-off is independence: the firm advising on what to buy may also sell and manage it. If one firm does both, get a second opinion on major purchases and keep admin accounts and licences in the business's name.
Long enough to set direction and see the first decisions through, then review. Agree on goals and a review point at the start rather than an open-ended arrangement, and plan the handover from day one, whether it goes to an in-house hire, a consultant or your own leadership.
A list of the systems and subscriptions you pay for, who has admin access to each, the decisions you keep putting off, any vendor quotes you're weighing and what's costing staff the most time. You don't need a strategy. Building one is the consultant's job.
Yes. Assessment, planning, vendor reviews and most decisions work well remotely. Hands-on device and network work needs someone on site, which is one reason it sits with managed IT. We're based in Winnipeg and work with clients across Canada and any English-speaking country.