Fractional CTO vs Agency vs MSP vs Dev Shop

When a growing company realizes it needs technology help, it usually ends up talking to some mix of four kinds of provider: a digital or marketing agency, a managed service provider (MSP), a software development shop, and a fractional CTO. From the outside they can look interchangeable. Everybody says they "handle your technology."

They don't do the same thing, and they aren't paid to do the same thing. Understanding the difference will save you a lot of money and at least one frustrating year.

A quick disclaimer: I'm a fractional CTO, so read this knowing where I sit. But I've also hired, managed and worked alongside every one of these over more than 25 years of building companies. Agencies, MSPs and dev shops are often exactly the right choice. The problems start when they're asked to do a job outside their model, or when nobody is directing them.

What each one actually is

The agency

A digital or marketing agency builds and runs customer-facing things: websites, campaigns, branding, sometimes an ecommerce store or a simple app. The good ones are excellent at design, content and conversion.

How they make money: hours, retainers or projects. Their natural incentive is to keep the work coming and to recommend the things they're good at building.

The MSP

A managed service provider runs your IT: devices, user accounts, email, networks, backups, security tools and the help desk. It's the grown-up version of "the IT guy," usually with a team and standard processes behind it.

How they make money: typically per user, per device or per ticket, on a monthly contract. Their natural incentive is to keep things stable and standardized, and to add seats and services.

The dev shop

A software development shop builds custom software to a specification: an app, a portal, an integration, a back-office system. The good ones have strong engineering and delivery processes.

How they make money: building. Hourly, by sprint or by fixed-price project. Their natural incentive is to build what's asked for, and there's always another feature to build.

The fractional CTO

A fractional CTO is a senior technology executive who works for your company part-time and owns the outcome: architecture, technology decisions, vendors, security and the roadmap. I've written more about the model in Why Fractional CTOs Are Suddenly Everywhere.

How they make money: usually a monthly retainer, sometimes projects or advisory hours. The incentive should be accountability for results: the systems working, the data agreeing and the business running on its technology instead of around it. And a good one will often recommend spending less, not more.

Side by side

Where each goes wrong

None of these failure modes is about bad people. They happen when a provider is asked to fill a gap their business model doesn't cover.

• The agency as de facto CTO. An agency builds your website, then your store, then gets asked to hook it into your CRM and inventory. Integration and data architecture isn't their core skill, and you end up with a beautiful front end sitting on a tangle of plugins. At one client, the member site I inherited was a brittle WordPress install, and the company's data lived in three databases that never agreed.
• The MSP as architect. MSPs are great at keeping a defined environment running. They're rarely set up to redesign how your business uses its systems, and "should we consolidate these three platforms?" isn't a ticket.
• The dev shop without an owner. A dev shop builds what's in the spec. If the spec is wrong, you get exactly the wrong thing, delivered on time. Without someone on your side who can write the spec, challenge estimates and review the work, you're guessing.
• The fractional CTO who only advises. The fractional model fails too, usually when the person produces recommendations and strategy decks but never owns the result. If nobody executes, a plan is just expensive paper.

When each is the right call

Here's how I'd think about it, assuming a $5–35M company.

Hire an agency when you need a strong website, brand or campaign, and your systems behind it are already in reasonable shape. Give them a clear brief and let them do what they're great at.

Hire an MSP when you have employees, devices and accounts to manage and you don't want to build an internal IT team. For most companies at this size, a good MSP is a smart way to handle day-to-day IT, especially once the environment has been designed properly.

Hire a dev shop when you know what you need built, you have a solid spec, and someone on your side can own the result. Dev shops are a great way to add building capacity without hiring a team.

Bring in a fractional CTO when nobody owns the whole picture: your systems disagree, you're not sure what to build or buy, your vendors are pulling in different directions, or a growth plan depends on technology nobody has scoped. If that sounds familiar, the 7 signs you've outgrown your tech stack will help you confirm it, and When Is the Right Time to Hire a CTO? covers timing.

How they work together

The best setups I've seen don't pick one. They combine them, with clear roles.

1. The fractional CTO owns the architecture and the roadmap. They decide which system is the source of truth for each kind of data, what gets built, bought or retired, and in what order.
2. The dev shop builds to specs the CTO writes and reviews. Estimates get challenged by someone who knows what the work should take, and the code gets reviewed before it becomes your problem.
3. The MSP runs the environment the CTO designed. Devices, accounts, networks and help desk, working to standards instead of improvising.
4. The agency owns the customer-facing brand and marketing, plugged into a platform that can actually support what they're building.

In that arrangement, each provider does the job its business model rewards, and someone on your side is accountable for how the pieces fit.

It also works in the other direction. In many engagements I build the core platform and automation myself, because that's often faster and cheaper than directing a team to do it. At that same client, that meant one React and React Native codebase for web, iOS and Android, a central database, and 120+ production n8n workflows. Other work, like day-to-day help desk or campaign creative, is better handed to a specialist. A good fractional CTO should know the difference and be honest about it.

Questions to ask any provider

Whoever you're talking to, these questions cut through the pitch quickly.

• What exactly are you accountable for, and what are you not?
• Who owns the code, the accounts, the domains and the documentation? It should be you.
• What happens when something breaks at 2 a.m.?
• How would another provider take over from you if we parted ways?
• What would you tell me not to buy?

If you're weighing the fractional option on cost, How Much Does a Fractional CTO Cost? covers the engagement models and how to compare them honestly against a full-time hire. And if you're not sure whether the leadership role you need is a CTO or a CIO, CIO vs CTO breaks that down.

The bottom line

Agencies, MSPs and dev shops are good at the jobs they're built for. The mistake is asking any of them to own a job they aren't paid to do: deciding how your whole business should run on its technology. Put an owner in place first, then hire the right specialists around them. You'll get more out of every provider you pay, and you'll stop paying for the same problem twice.