IT Department Structure for a Company That Cannot Justify One: A Fractional CIO and a Contract Bench

Last updated: October 30, 2026

By Colin Boothe, CIO at Foretopia

A $50M to $500M company that cannot justify a full IT department runs one or two employees who own the systems day to day, a fractional CIO for decisions, and contract specialists who rotate in by project. KORE1-placed systems administrators bill $54 to $70 an hour, median $57 (KORE1 Contract Rate Index 2026-Q4, n=12, primarily Southern California). Project managers bill $105 to $124, median $116 (n=21).

Ask the CFO of a $150M company who runs IT. The answers I hear most are “Gary,” “the guy we call,” and a pause long enough to check email.

Nice org chart.

It also explains why the ERP upgrade has been slated for next quarter for six quarters running. At this size IT is rarely a department. It’s a handful of seats, and nobody ever sat down and decided which should be a person on your payroll, which should be borrowed by the day, and which should show up for one project and leave when it ships. That decision is most of the job.

So I’m going to draw it three times, once per revenue band, with a label on every box. Permanent, fractional, or contract. That’s the whole system.

Bias first. KORE1 places contract IT staff, so a post telling you to rent some of these seats suits the site you’re reading. My group at Foretopia sells ERP implementation, which pulls me the other way, toward telling you to hire an administrator and call me twice a year. Where a seat should be an employee I’ll say so plainly. If you want the service versions, KORE1 runs fractional CIO services and IT staffing services, and the contract seats get filled through contract staffing.

What Does an IT Department Look Like When the CFO Owns IT?

A mid-market IT department without a CIO is a set of seats, each one either permanent, fractional, or contract. Permanent seats hold the knowledge. The fractional seat makes the decisions. Contract seats do the project work and leave. Draw it that way and the org chart finally has an owner for every box.

Three charts follow. They come from my own years inside ERP and systems work, not from a survey, so treat the headcounts as a sketch and argue with them. The labels are the part I’d defend.

$50M to $100M: one employee, one rented executive, everything else borrowed

One employee. That’s the chart. Everything else is a label that says someone else shows up.

$100M to $250M: a director, an administrator, a desk, and a bench

$250M to $500M: the same chart with the fractional seat on a clock

Here the permanent core gets real, and the rented executive starts to have an end date. Most companies in this band are either hiring a full-time CIO or have just decided not to.

Every contract box above is priced from the KORE1 Contract Rate Index 2026-Q4, at 40 hours a week for 13 weeks. Observed cells are KORE1’s own W2 contract placements that started between 2023 and 2026, with five or more behind each cell and the count shown. The network engineer cell is modeled, which means wages from the BLS May 2025 Occupational Employment and Wages release plus a 24% employer burden. Bill rates include payroll taxes, insurance, and benefits. How each cell was built is in the index methodology.

Two of those rows deserve a squint. The project manager bills about double the systems administrator, $116 against $57, and nobody at the budget meeting expects it. People rent a project manager for a plan, not for hands, and a plan is priced like judgment. Then the ERP consultant range runs from $73 to $123, a $50 gap inside one cell, which is roughly the distance between someone who administers a module and someone who can redesign how it works. Ask which one you’re getting before you sign. Really.

The systems administrator cell rests on 12 placements. Read it as a ballpark, not a quote. Three of the four observed cells are mostly Southern California placements too, so outside that market the metro cells on the 2026 Contract Rate Card will move the numbers.

Now the lazy math. A systems administrator, an ERP consultant, and a project manager, all full time for the same quarter, come to $29,600 plus $47,200 plus $60,400, which is $137,200. Nobody needs all three at once. Hence the bench. It’s arithmetic on index cells, not a quote for your scope.

Want your own chart priced? Send the revenue band, the seats you’d contract, a start date, and how long through the contract rate quote request, and we’ll price the bench against it.

Which Seats Should Be Employees First?

The ones that hold knowledge nobody wrote down.

KORE1 partner Devin Hornick, talking through contract versus full-time on an internal call, laid out the trade. Contractors are quick to get and easy to scale up or down. Then he turned it around. “The benefit of hiring full time is quite the opposite. It’s really not super flexible, but you have stability… legacy knowledge.”

Legacy knowledge. The unglamorous kind. Which printer has a fixed address because a label script points at it. Why the warehouse scanners live on their own network. The reason approvals for one vendor skip a name. None of it is documented. All of it breaks something on a Friday. Every company has twenty.

That is why the first permanent seat is the person who owns the systems day to day, and why it’s the wrong seat to fill with a contractor on a rolling extension. A contractor can know a project very well. Somebody has to know the company.

The contract data points both ways here. Of KORE1’s contract-to-hire placements, 37.5% convert to a permanent job (n=552), so a contract seat can double as a long interview for the permanent one. And a KORE1 contractor can convert to full-time with no fee after 1,040 hours, which is the cleanest way I know to try a systems owner before committing. The details sit on the contract-to-hire staffing page.

One caution. Permanent doesn’t mean good. A permanent seat with no backup is a single point of failure with a benefits package.

What Does the Fractional CIO Decide, and What Does It Not Do?

It decides. That’s the job. The fractional seat sits above the IT director or the systems owner, signs off on vendors under an agreed dollar threshold, sets the order projects happen in, and settles the question this whole post is about, which seat gets filled by whom. Real authority. Narrow, written scope. I wrote the long version in The Rentable CIO, and the plain explainer lives at what a fractional CIO is and when you need one.

• Vendor selection and renewals above whatever threshold the CFO is tired of approving.
• The sequence of projects. ERP upgrade before the warehouse integration, or after, and why.
• Which seats get hired, which get rented, which get cut.
• Saying no. Most wasted technology spend was approved by somebody who could not.

Short list. Big job.

What it doesn’t do matters more. It doesn’t answer tickets. It doesn’t build reports. It doesn’t replace the IT director, who runs the day, and I’d tell the director before anyone else hears about it. A fractional CIO who spends the week on password resets is the most expensive help desk in town.

Why rent instead of hire? Money, mostly. The Bureau of Labor Statistics puts median pay for computer and information systems managers at $175,140 a year before benefits, and projects the occupation to grow 16% from 2025 to 2035, so you are bidding against every other company that worked out it needs one. A rented seat is producing decisions in weeks. If you would rather start with something bounded, an IT strategy consulting engagement is the smaller first step, and it produces the roadmap I describe in building an IT roadmap without a CIO.

Which Specialists Should Rotate In on Contract, and for How Long?

Plan around four months. The median KORE1 contract assignment lasts 116 days across 1,887 ended assignments (KORE1 job-activity report, 2019 to 2026), so I’d size the first purchase order near that and leave room for one extension. The full spread is in the post on how long contract assignments last.

Rotating in doesn’t mean rotating through. Keep the same ERP consultant for the whole project. Swapping mid-stream resets the learning curve. You pay for that. Every time.

Chairs empty. Speed matters. Median offer-to-start across 1,997 KORE1 contract placements is 3 days. Sourcing and vetting take longer than that, so start the search before the last day.

Which Seats Go Permanent First as the Company Grows?

In this order, roughly. It’s a ranking. The numbers stay.

1. The systems owner. Before anything else, and before the fractional CIO if you can only afford one.
2. The first help desk hire. You’ll know when. It’s when the systems owner starts apologizing for slow tickets.
3. An ERP or business systems administrator. My rule of thumb, not a study. Once the same ERP consultant has been extended three times, you have a permanent seat wearing a contractor’s badge.
4. The IT director. Hire the person who runs the day so the systems owner can go back to owning systems. The search is a normal one, and KORE1 handles it through IT director staffing.
5. A named security owner. Not a team. One employee whose name goes next to the word security on the chart.

The CIO seat goes last. For plenty of companies in this band, never. A rented executive is fine as a permanent arrangement. If it ever runs four days a week for two quarters, stop renting and run the search. KORE1’s CIO recruiters do that part, and whoever you’ve been renting is usually the best available help writing the job description.

What Breaks If the ERP or Security Project Has No Owner?

Nothing, for about a quarter. That’s the trap.

A funded ERP project with a contractor and no employee owner works beautifully right up until the contractor’s last day, when the workaround only they understood, the decision nobody recorded, and the half-finished import all walk out the door together. Contractors build to the last person who talked to them, and without one name on your side the last person who talked to them is whoever was loudest on Tuesday. The median assignment is 116 days. Most ERP projects outlast that. The context doesn’t. Not on your side, anyway.

I don’t think the technology is the hard part. Your people are, which is a polite way of saying ownership. The fix is boring. One employee, named, whose number changes if the project slips, and the contractor works for that person. If you are planning a cutover, the ERP cutover plan template puts an owner’s name on every line.

Security is the same shape. Worse consequences. The contractor who set up the access model leaves on day 116. Who turns their accounts off? Ask who signed the last access review. If the answer is a long pause, you’ve found your missing box.

Devin Hornick’s test for any funded initiative is what breaks if the company doesn’t finish it. When the answer is the quarter close or the audit, you have a project that can’t slide into 2027, and it needs an owner on the org chart before it needs a contractor.

Questions CFOs Bring to the Redraw

At what size does a company actually need a full IT department?

Later than most vendors suggest, and the trigger is the number of systems, not revenue. When one employee can no longer hold the whole map in their head, or tickets sit longer than a day, you’re hiring the second permanent seat. Revenue only matters in how many systems it buys.

Can an outsourced IT provider replace the department?

Half of it. An outsourced provider can run the help desk and basic infrastructure well. It can’t decide what the business should buy, and nobody on its side knows why the label printer has a fixed address. Treat it as a contract box on the chart, not a replacement for the chart.

What would the contract bench cost for one quarter?

$137,200 at median bill rates for a systems administrator, an ERP consultant, and a project manager, all full time for 13 weeks. Few companies need all three at once. That figure is arithmetic on KORE1 Contract Rate Index 2026-Q4 cells, not a quote for your scope.

Our IT person just quit. Who is in the chair on Monday?

Three days from offer to start is the median across 1,997 KORE1 contract placements. Sourcing and vetting take longer than that, so the honest answer is someone by next week if you move fast. What a contractor can’t hand you on Monday is the history, which is why the systems owner should be a permanent seat.

Does a fractional CIO make the IT director redundant?

No, and telling the director first matters more than the answer. The director runs the day, and the fractional CIO owns the decisions above it. Most good directors at this size are drowning in work two levels below their ability, so the arrangement tends to hand them back the part of the job they wanted.

Start With the Labels

Pick the chart closest to your revenue band. Then write permanent, fractional, or contract on every box in your own org chart. The boxes you can’t label are your actual problem. They’re also, usually, the ones with “Gary” written on them.

If you want a second opinion on which boxes to rent, hit me up on LinkedIn. For the staffing side, talk to a KORE1 recruiter, and if the missing box is the executive one, this is what bringing in a fractional CIO looks like in practice.

Data as of October 2026. The KORE1 Contract Rate Index refreshes quarterly.