CTO vs IT company
Fractional CTO vs MSP or Dev Shop: Who Fixes It, Who Builds It, Who Decides
Your IT company keeps the laptops alive. Your dev shop ships the feature you asked for. Neither is paid to tell you the feature was a bad idea or that the laptops were never the problem. That gap has a job title, and sometimes it needs filling.
November 5, 2026 · 8 min read
- PassLaptops, email and patchingIT provider
- PassWebsite and booking codedev shop
- FailTechnology budget for next yearnobody
- FailWhich vendor to replacenobody
- WarnBackup restore testedassumed
The short answer
A managed IT provider keeps computers, networks and accounts running. A dev shop builds the software you specify. A fractional CTO decides what the company should buy, build or leave alone and holds both to account. They are different jobs, so many companies need one or two of them, and few need all three.
On this page
- What a managed IT provider is actually paid to keep running
- What a dev shop is paid to want
- The work that falls between them, and stays there
- Eleven chores and whose name goes beside each
- Why whoever writes the code should not grade it
- Which combinations make sense, and which waste money
- Three questions to put to the vendors you already pay
What a managed IT provider is actually paid to keep running
A managed service provider, or MSP, is the company on the sticker on your laptop. It answers the help desk, sets up new hires, manages email accounts, patches machines, watches the network and usually runs some form of backup. A good one is worth more than its invoice, because you only think about it on the day it fails you. We have no quarrel with the species.
Look at how it gets paid, though. Most charge by the seat or the device, for keeping things working. So the MSP's worldview is the running system. It will tell you a server is out of warranty. It will not tell you that the custom app on that server should have been retired three years ago, or that the field service platform you bought last spring overlaps with half of what you already pay for. Nobody asked, and that question is not on the contract.
What a dev shop is paid to want
A dev shop writes software to order. That is what DataCram's custom software service does, so read this section as a confession. You bring a request, the shop estimates it, builds it and sends the invoice. The good ones push back on bad ideas. They still get paid to build, and no shop in history has examined a business problem and concluded, with regret, that the answer was a spreadsheet.
Build shops also tend to treat your specification as the truth. If the document is wrong, you get a correct version of the wrong thing, on time. Who wrote the specification? In a small company, often the owner, on a Sunday, from memory. That is no way to spend money on web app development. It is also one of the first things Casey Kinnison takes over as DataCram's fractional CTO. Casey builds custom software applications and manages relational databases, so the specification comes from someone who knows what a specification tends to leave out.
The work that falls between them, and stays there
Each vendor can be good at its job while the company still has no one doing these things. Read this list and ask who holds each one today. If the honest answer is "I guess I do," that tells you something.
- The total. What the company spends on technology across every vendor, card and department.
- The retirement decision. Which system to stop paying for, a question no vendor will raise about itself.
- The restore test. The MSP says the backups run. Does the custom app's database come back with them? Each party assumes the other checked.
- Ownership. Who controls the code repository, the domain, the cloud account and the admin logins, in writing.
- The data path. Which system holds the truth when the CRM and the field service platform disagree, and whether an integration should settle it.
- The AI rules. What staff may paste into which tool. Neither vendor was asked to write this down.
- The hard meeting. Who answers when an investor, buyer or auditor asks how any of this works.
Eleven chores and whose name goes beside each
| Managed IT provider | Dev shop | Fractional CTO | |
|---|---|---|---|
| Reset a password, replace a laptop | Does it | No | No |
| Patch desktops and servers | Does it | Patches its own code | Checks that someone does |
| Build a feature | No | Does it | Writes the specification, reviews the result |
| Decide whether to build at all | No | Rarely against its interest | Owns it |
| Review code quality | No | Reviews its own | Reviews independently |
| Connect two systems | Sometimes | Does it | Decides which system holds the truth |
| Run backups | Often | Sometimes | Sets the owner and the schedule |
| Prove a backup restores | If contracted | If contracted | Requires it and records the result |
| Negotiate vendor renewals | Its own only | Its own only | Across all vendors |
| Own the technology budget | No | No | Proposes it; the owner approves |
| Answer an investor or auditor | Partly | Partly | Leads it |
The last column does not touch a keyboard very often, which is exactly why some owners do not see the need. Some companies truly do not have one. If everything you run is rented and your hosting and maintenance is handled, you may be fine with an MSP and a yearly look. The page on what the role does each month can help you decide.
Why whoever writes the code should not grade it
The principle is old and unglamorous. Accountants do not audit their own books, and home inspectors should not sell the repairs. Code is no different, and the stakes are not abstract. Verizon's 2026 Data Breach Investigations Report found that 31% of breaches start with software vulnerabilities, now ahead of stolen passwords as the top way in. When the people who wrote the software are also the only ones reviewing it, a blind spot has no way of getting noticed.
No one should be the only judge of their own code, and that includes us.
Which combinations make sense, and which waste money
An MSP alone
Fine for a company with rented software, no custom code and a flat technology bill. Say a 12-person insurance agency (made up). Add a site audit once in a while and spend the savings elsewhere.
An MSP and a dev shop
Works if someone on your staff can write specifications and read invoices. If that someone is you, on Sundays, the arrangement has an unpaid part-time CTO already.
An MSP and a part-time lead
A common fit when everything is bought and not built. The part-time CTO handles renewals, integrations and the plan while the MSP handles the machines.
All three
Makes sense when custom software matters to revenue. Say a contractor whose custom quote tool or portal drives sales (made up). The part-time CTO keeps the other two honest.
A dev shop acting as your CTO
The most common bad version. The shop's advice may be sound, but no one checks it. At a minimum, get an independent review before a large build.
A strong in-house leader and vendors
Then you need none of this from us. Hire more hands if you need them, and keep your leader happy.
Three questions to put to the vendors you already pay
You can run a rough version of this audit yourself this week, at no cost beyond a little awkwardness. The answers will not prove anyone is bad. They will show you whether the gaps above exist at your company. Run a free website health check alongside them if your site is part of the picture, and look at twelve questions for any web company if you are about to sign with a new one.
Casey Kinnison worked as a trader, and these questions come from that habit. Size the exposure: how much of the company sits with one vendor? Set the exit: how do you leave with your code and data? Mark it to the actual number: what did the last restore really produce? A shop holding the only copy of your code is a single point of failure, however friendly the account manager.
- 1
Ask to see the last backup restored
Not the log saying it ran. Ask for the date of the last real restore, what came back and who did it. Ask both the MSP and the developer.
- 2
Ask who owns the code and the accounts
Request admin access to the repository, the domain and the cloud account in the company's name. Watch how the request is received.
- 3
Ask what they would stop selling you
Every vendor knows of something you pay for and barely use. A good one will say so. Note who answers and who changes the subject.
Send us the answers if you want a second reading, and a person at DataCram will reply. The same logic applies to your marketing bills: the page on a fractional CMO versus an agency makes the same argument about who grades whom on that side. If the cost is the sticking point, the published ranges and hours math will help you budget.
Questions owners ask about a fractional CTO
Some sell a virtual CIO add-on, and a good one can help with planning and renewals. The limit is the conflict: it is hard for a provider to recommend replacing itself or to grade its own work. If you go this route, ask for the same five documents you would demand from anyone, and have someone else check the backup test.
Usually yes. A fractional lead does not reset passwords, image laptops or answer the help desk at 8 a.m. on Monday. What the lead does is review the IT company's contract and performance, and sometimes recommend changes. Keep a provider that does its job. The lead's arrival should make its work easier, not replace it.
Not on arrival, and never without your decision. The first step is reading the work and comparing invoices with what shipped. Plenty of developers do better with clear specifications and someone to ask questions of. If the audit finds real problems, Casey Kinnison brings you the evidence and the options, and you decide what happens.
They are not substitutes, so the comparison misleads. A dev shop charges to build, and a fractional lead charges to decide and oversee. Ten hours of good oversight may prevent a project that should not exist, or it may simply confirm the project is sound. DataCram publishes prices for hands-on work, and the fractional seat starts at $5,500 for 15 hours a month.
Then one firm holds both the plan and the build. For anything critical, we would suggest an outside review. Splitting the two roles between firms is also a sensible choice.
Keep reading
- The job, itemizedWhat a Fractional CTO Does: One Month in the Seat and the Paper It Leaves BehindWhat a fractional CTO does in a real month, what the role owns, five documents a buyer should demand, a made-up sample, and what a good one refuses.
- Technology audit checklistFractional CTO First 90 Days: A Technology Audit Checklist and RoadmapWhat a fractional CTO should do in the first 90 days: inventory, access, a backup restore test, the NIST functions, first vendor decisions and AI rules.
- CTO as a service pricingFractional CTO Cost: What the Published Rates Say and What They Leave OutFractional CTO rates: one vendor's published range, the hours math, the bills that arrive later and our own price, from $5,500 for 15 hours a month.
- Do I need a CTOFractional CTO vs Full-Time CTO: The Math, the Exceptions and the HandoffFractional CTO vs full time: federal pay data and the benefits math, when a full-time hire clearly wins, and how to hire a first engineering lead.
- CTO for startup foundersFractional CTO for Non-Technical Founders: How to Check Work You Cannot ReadHow non-technical founders can check developers' work, who should own the code and accounts, what tech debt means, and what investors will ask you.
- Everything in Fractional CTOSee the section
Find out who at your company is doing the job nobody hired
Tell us who your IT provider and developers are and what falls through the cracks. A person at DataCram replies with where the gaps look to be, and whether a part-time lead would close them.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.