Fractional CIO, Interim CTO, or a Consulting Firm: How a Credit Union Should Choose
These three are not price tiers of the same service. They differ on who holds decision authority, and choosing on day rate is what produces a stalled engagement. A practical guide for credit unions and community banks facing a technology leadership gap.
A credit union loses its CIO. The search will take four to six months on a good day. Someone has to hold the function in the meantime, and within a week the CEO is looking at three kinds of proposal: an interim CIO, a fractional CTO, and a consulting firm offering a technology assessment.
They read like three price points for the same thing. They are not. They differ on who holds decision authority, and picking on day rate rather than on authority is the most common way these engagements stall.
The distinction that actually matters
| Interim CIO / CTO | Fractional CIO / CTO | Consulting firm | |
|---|---|---|---|
| Decision authority | Holds it. Approves spend, signs off on vendors, reports to the board | Stays internal. Advises; someone on staff decides | None. Delivers a defined scope |
| Time commitment | Close to full-time | One to three days a week, ongoing | Fixed project window |
| Ends with | A permanent hire, or conversion | An ongoing cadence, or a permanent hire | A deliverable |
| Best when | The seat is empty | The seat is filled but the judgment is thin | The question is bounded |
| Fails when | Used for advice nobody acts on | Used to cover an empty seat | Used to make a decision only an owner can make |
Most institutions that call asking for an interim CTO actually need an interim CIO. The distinction is not pedantic. In a credit union the role that owns vendor relationships, the core contract, the examination response, and the board reporting line is almost always titled CIO, and titling the engagement CTO tends to signal to internal staff that this person is here to do architecture rather than to run the function.
Vocabulary varies more than the work does. Some providers market the same engagement as a virtual CIO, a vCIO, or a strategic technology advisor. Ask what they will hold authority over, not what they call it.
Which situation maps to which model
Your CIO resigned and leaves in three weeks. This is interim, and close to full-time. Somebody has to be in the vendor calls, the board meeting, and the exam prep. A fractional engagement here produces a well-informed advisor watching a function drift, because the decisions still queue behind someone who no longer works there.
Your CIO is in place and capable, but a core conversion is coming. This is fractional, or a firm. The seat is filled. What is missing is someone who has been through a conversion and can say which vendor answers are evasive. Do not displace a working CIO with an interim; you will lose them.
The board mandated a digital or AI program and nobody senior owns it. Usually fractional, escalating to interim if it turns out the mandate is really a leadership gap wearing a project costume. Worth being honest with yourself about which one it is before you write the scope.
You need a current-state assessment to take to the board. A firm, and probably not us. Bounded scope, clear deliverable, competitive market. If what you need is a document, buy a document.
Examination findings need remediation. Depends entirely on whether you have someone to own the remediation. Findings do not get closed by advice.
What it costs, and why the full-time interim market is thin
The pricing conversation usually starts in the wrong place, with an hourly rate compared against the departed CIO's salary. That comparison is not useful, for a reason worth understanding before you budget.
A permanent CIO gets a salary, benefits, and a reasonable expectation of employment continuing. An interim on a six-month contract with no equity and no severance is unemployed in month seven unless something else materialises. The rate carries that risk, and it carries the cost of the person turning down other work to be available. An engagement priced against permanent salary will attract people who could not get the permanent job.
The practical consequence, which is worth knowing before you set requirements:
- Asking for 40 hours a week narrows the candidate pool sharply. Senior people with regulated-finance depth are usually already engaged. Filling a full-time interim seat means persuading someone to leave a stable arrangement, which takes longer and costs more.
- Capping at 25 to 30 hours widens it considerably and shortens time to start, often from months to weeks. For many institutions this is the better trade, because the difference between 25 and 40 hours of senior attention is smaller than the difference between starting next month and starting next quarter.
- On-site requirements narrow it again. A hard requirement for weekly on-site presence in a market without deep talent supply can cost you the candidate you wanted. Being specific about which moments genuinely need someone in the room, rather than defaulting to a weekly cadence, is usually worth more than it costs.
If the budget genuinely cannot support senior interim coverage at full-time hours, the honest move is to reduce the hours rather than the seniority. A capable person two days a week beats an available person five.
The questions your board and your examiner will ask
Both will ask about this engagement, and it is easier to have answers ready.
Who has authority, in writing? An interim needs a documented scope covering spend approval limits, vendor signature authority, and reporting line. Examiners look for clarity on who is accountable for technology risk. "The consultant handles it" is not an answer that survives a review.
How is third-party risk being managed for this arrangement? The irony is not lost on anyone that the person managing your vendor risk is themselves a vendor. NCUA's 2026 supervisory priorities tell examiners to assess third-party risk-management practices where lending, servicing, or collection functions are outsourced. Document this engagement the way you would document any critical vendor.
What happens to institutional knowledge when they leave? This is the question boards ask last and should ask first. An interim who writes nothing down leaves you where you started, minus the fee.
Structure the exit before the start
The single most useful clause in an interim agreement concerns how it ends.
Agree up front on what gets handed over: a written current-state assessment, a vendor and contract inventory with renewal dates, a documented risk register, and a roadmap with sequencing and cost. Agree on when the permanent search begins, and whether the interim participates in it. Many do, and having the person who has been running the function help define the role and sit on the panel is worth more than the awkwardness of them being replaced by their own recommendation.
Agree also on what happens if the fit is wrong. A thirty-day mutual exit in the first sixty days costs nothing to include and saves a great deal when it is needed.
An engagement without an ending plan quietly becomes a dependency, which is the failure mode nobody notices until the third renewal.
Where we fit, and where we do not
We take interim and fractional CIO and CTO engagements where the work is genuinely technical: core conversions, payments and real-time rails, data and analytics programs, AI governance with engineering underneath it. We are not a CUSO and not a managed IT provider.
If what you need is policy documentation, examination preparation, and a governance cadence without hands-on engineering ownership, a vCIO or a CUSO will do it better and cheaper than we will, and we will tell you so on the first call. That is not modesty. Mismatched engagements end badly for both sides, and the market for credit union technology leadership is small enough that reputations travel.
If you are facing a leadership gap, see technology leadership for credit unions and for community banks, or book a call. The first 90 days of an interim engagement covers what the work looks like once it starts.