Does Your Nonprofit Need a Fractional CTO?
Most nonprofits do not decide to hire technology leadership. The question arrives in a bad week: a migration proposal nobody on staff can evaluate, or a departing employee who turns out to be the only person with the logins.
A fractional CTO is one answer. It is also a phrase attached to four different things right now, which makes the comparison shopping confusing. This guide says what the role is for an organization your size, when you are ready for it, and when you need something else first.
01Why this question comes up now
The role went from unusual to common in about five years. The numbers say why.
- 64%
of nonprofit professionals name a lack of in-house staff or technical expertise as a barrier to adopting technology, and 67 percent say technology deficits are holding growth back. Organizations know what they want to do. Nobody's job is to decide how.
Chronicle of Philanthropy, 2025 technology survey - 67%
of nonprofit employees said they were looking for a new job or expected to be within a year. Whatever technology knowledge lives in a staff member's head is on a shorter clock than the systems it describes, and the person who could write it down is usually the busiest person there.
Candid, 2024 nonprofit employee survey - Under 3%
of budget is what most nonprofits spend on technology, and 69 percent fund it from general operating money rather than a dedicated line. A budget built that way can absorb licences and a helpdesk contract. It was never designed to hold a leadership seat.
NTEN and Heller Consulting, 2024 Nonprofit Digital Investments Report
There is no shortage of vendors willing to sell your organization something. There is usually nobody on your side of the table whose job is to decide what to buy, what to build, and what to switch off, and who will still be around in eighteen months to answer for it. Fractional leadership is the sector's response: one experienced person, a defined share of their attention, accountable to your leadership rather than to a product line.
02What a fractional CTO actually does for a nonprofit
A fractional CTO owns the technology and product agenda. Everything else follows from that.
Owning it means sitting with leadership rather than reporting in from outside. In the budget conversation, in the board's strategy discussion, in the room when a program director describes what next year's service model needs. It means deciding what gets built, bought, connected, or retired, and answering for those decisions afterward, including the wrong ones. When someone asks which system holds supporter identity, or why the mail platform and the CRM disagree, this person can answer the same day instead of commissioning a discovery phase.
Fractional describes the share of attention. A mid-size nonprofit does not have forty hours a week of technology decisions. It has perhaps a day a week of consequential ones, scattered unevenly, plus a standing need for someone to be reachable when a decision arrives unannounced.
A director should expect three things from the arrangement. If one is missing, ask why.
- 01
A CTO or CPO who stays
The same person, month after month, building up context about your programs, your data, your funders, and your staff. Institutional memory is the scarcest thing in a nonprofit stack, and every project-shaped engagement spends it at the end. - 02
Support that keeps the lights on
Leadership with nothing underneath it produces excellent recommendations and a staff member who still cannot print. Someone has to answer when the CRM breaks on a Friday. That layer can be arranged several ways, covered below, and it has to be directed by the person who holds the agenda. - 03
Continuity through turnover
When a staff member leaves, you should lose a colleague, not a system. The systems map, the credentials, the vendor relationships, and the written processes live with the organization, kept current by someone whose job includes it.
03The four things it gets compared with
Almost everyone weighing this is weighing it against something else. The four alternatives are different products with different jobs. None is a bad answer. The expensive mistake is buying one while expecting another.
| Option | What it owns | When it is the right answer | Where it stops |
|---|---|---|---|
| Managed IT provider | Devices, accounts, network, patching, backups, the security baseline, and a helpdesk your staff can call. | You need infrastructure maintained and someone to answer the phone. Every organization needs this layer, whoever provides it. | Strategy is usually an advisor bolted onto an infrastructure contract. That advisor rarely owns the CRM decision or the data model, and the business is measured in seats and devices. |
| CRM or platform implementer | Configuring, migrating, and launching one platform, generally very well. | The platform decision is made and the work in front of you is delivery. A good implementer beats a generalist at this every time. | The engagement ends at go-live. Nobody owns what the platform connects to next year, or whether it was the right purchase in the first place. |
| Advisory-only or a standalone vCIO | Roadmaps, budget planning, vendor selection, governance, a board-ready assessment. | Delivery and support already work and what you are short of is the plan. Also useful as a second opinion before a large commitment. | Nobody to call when the CRM breaks, and no hands on the work. Execution stays with a staff that was already at capacity, which is why the roadmap is often still a document a year later. |
| A full-time CTO | Everything, inside the organization, with the authority and availability of a staff role. | Technology is a core part of program delivery and there is enough consequential work to fill the week. At that point the internal seat is the right answer. | Hard to hold and hard to retain at mid-size, where the role is either under-used or impossibly broad. One internal technologist is also a single point of failure. When they leave, the seat sits empty for months. |
The distinction that matters most is advisor versus owner. An advisor is asked what they think. An owner holds the roadmap, arbitrates between vendors, and lives with the decision when the migration runs long. Plenty of arrangements marketed as strategic are the first thing described in the language of the second. Ask who is answerable when a decision turns out badly.
These combine. Most organizations we work with keep a managed IT provider and hire an implementer when a platform goes in. Somebody on their side directs both, and that person does not change when the project does.
Two of these decisions have their own guides: choosing a nonprofit CRM and planning a nonprofit website redesign. A fractional CTO would own both. You can also make them yourself with a few focused weeks. The continuity promise has its own guide too: the first AI project a nonprofit should build.
04Managed IT and support, and how they change over time
The support layer is a separate decision from the leadership seat. Treating them as one package is how organizations end up locked into an arrangement that stopped fitting two years ago.
Leadership is about what the organization should do with technology. Support is about keeping today working: the laptop, the account, the printer, the platform that is down. They have different economics, different response times, and different right answers at different sizes. Expect the support arrangement to change as you grow. You should not have to re-decide the leadership seat every time it does.
Three arrangements are honest, and we have seen each of them be right.
- 01
Keep your provider, add direction
You already have a managed IT provider and they are competent. Nothing changes except who sets their priorities. The fractional CTO becomes their counterpart on your side, reviewing the contract, weighing tickets against roadmap work, and taking vendor management off whoever on staff inherited it. This is the cheapest transition and the most common starting point. - 02
Support under the same roof
The fractional CTO includes a support desk under their own direction, so the people answering tickets and the person holding the agenda work from the same plan. Nothing falls between two vendors, and a pattern in the tickets reaches the person who can fix the cause. Suits organizations with no provider, or one that is not working out. - 03
Bring support in-house
At some size a shared external desk stops being the right shape and an employee is. The leadership seat does not disappear when that happens. It becomes the person the new hire reports to on technical questions, and the one who recruits for the role.
When bringing support in-house starts to make sense
There is no headcount at which in-house support becomes correct, but the signals are recognizable.
- Your programs run on technology specific to what you do, such as a case management system or a clinical platform, that no general provider will learn well.
- Onboarding, offboarding, and account changes have become a weekly rhythm rather than an occasional errand.
- Ticket volume has outgrown what a shared desk absorbs, and the wait to be unblocked has started to shape how people work.
- Someone needs to be physically present: sites, events, equipment, a building with its own network.
- There is enough technical work that a capable employee would have a real job rather than a queue of interruptions.
What makes that transition possible
Whether that transition is easy or painful depends on what the organization is holding when it happens, more than on the hiring.
- 01
A living systems map
Every system, what it is for, who uses it, what data it holds, what it connects to, and what it costs. Maintained as things change rather than produced once. A new hire handed this is useful in their second week instead of their second quarter. - 02
Credentials and vendor relationships held by you
Accounts in the organization's name, in the organization's password manager, with the organization as the billing and administrative contact on every contract. Small hygiene, outsized effect. It is the difference between changing providers and being hostage to one. - 03
Documented processes
Onboarding and offboarding, the backup routine, how a new supporter record is created, what happens at year end. Written in the organization's own space, in language a capable newcomer can follow.
Ask for this explicitly, before you need it, whoever you hire.
05Signs your organization is ready
Here are the symptoms rather than a maturity model. If several describe your week, the question in the title has answered itself.
- Nobody owns technology. Decisions get made by whoever is nearest the problem, so they get made repeatedly and inconsistently.
- The same supporter exists in three systems with three histories, and you cannot say which is right.
- A migration or a major purchase is in front of you and nobody internally can evaluate the proposals, so the decision rests on the quality of the sales conversation.
- A staff member is leaving and it has just become clear how much only they knew: the logins, the workarounds, why that one integration is set up the way it is.
- The board has asked for a technology strategy, and nobody has the time or the standing to write it.
- Funders are asking how you collect data, what you can demonstrate, and how you protect it, and assembling the answer takes days.
- Three vendors have quoted the same problem and each proposal describes a different one.
06Signs it is not the right fit yet
For some organizations this is the wrong purchase this year, and we would rather say so here than in a proposal.
- 01
You are small and your stack is simple
A handful of staff, a website, a mail tool, a donation platform, and one place supporter records live. There is not enough consequential decision-making to justify a standing seat. Keep it simple on purpose, write down what you have, and revisit when a program or a grant changes the shape of the work. - 02
What you actually need is a helpdesk
If the pain is laptops, accounts, printers, and a person to call, buy that. A competent managed IT provider is the right product and a smaller commitment. A leadership seat on top of an unmet support need does not fix the support need, and you will resent the invoice. - 03
You are mid-implementation
If a platform is half-installed and the project is in trouble, you need an implementer who knows that platform, or a short rescue. A standing leadership arrangement in the middle adds a voice rather than a pair of hands. Finish or stop the project, then decide about the seat.
07How to budget for it
Finance asks this first, and the intuitive answer causes the most trouble: putting it on the technology line.
The technology line is licences, subscriptions, hardware, and hosting. Things you operate. A fractional CTO is leadership and continuity, and it belongs on the professional services line with legal and audit, the retained expertise the organization relies on but does not employ. That is the more accurate description of what you are buying, and it keeps the arrangement from being cut in the same motion as a software renewal.
There is a practical side too. Technology budgets in most nonprofits are funded from general operating money and reviewed as a cost. Professional services is a line where leadership is understood to cost something, and where the review question is whether the organization is getting good counsel.
We publish no figures on this site. A number that has not seen your programs, your stack, or your support arrangement is not a price. We can be specific about the shape. There are three tiers, they differ in how much support sits under the leadership seat, and which one fits is a scoping conversation.
- 01
Partner
The leadership seat on its own. Strategy, roadmap, vendor direction, and the systems map, with your existing support arrangement directed rather than replaced.
Scoped, not priced here - 02
Partner + Support
The same seat with a support desk underneath it, working from the same plan. For organizations without a provider, or whose current one is the problem.
Scoped, not priced here - 03
Embedded
A deeper share of attention where technology is central to the programs. More hours, more hands, and product work alongside the leadership.
Scoped, not priced here
Which tier fits an organization like yours is a question we would rather answer than publish. Ask for a scoped conversation. We will be plain about it, including when the answer is that you are not ready for one.
One thing to raise with funders rather than absorb. The first phase, the systems map, the documentation, getting credentials and contracts into the organization's own hands, is capacity building by any reasonable definition. It leaves the organization permanently more able to run itself, and some funders will pay for that when they will not pay for a subscription.
08Questions to ask before you sign anything
Ask these of us and of anyone else you are considering. A few are uncomfortable enough that hesitation is itself the answer.
- 01Who holds our credentials, and in whose name are the accounts and contracts? The right answer is yours, in your password manager, with your organization as the administrative and billing contact on every vendor agreement.
- 02What documentation do we receive, and how often? Ask for the cadence. A systems map updated monthly is an asset. One produced at the start is a souvenir.
- 03What happens if you leave, or if we end this? Ask what the last thirty days look like and what gets handed over. A firm that has thought about its own exit will describe it without flinching.
- 04Who do we call when the CRM breaks on a Friday afternoon, and how fast have you committed to answer? Be specific about which systems are covered. The gap between infrastructure support and application support is where organizations find out they are uncovered.
- 05Do you resell software, take referral fees, or hold vendor partnerships? Not disqualifying, but you should know whose interest is in the room when a platform gets recommended.
- 06Which budget line do you expect this to sit on, and why? An answer that engages with how your finance team works is a sign they have done this before.
- 07How many clients does the person we would work with hold at once, and what happens when two of us need them in the same week?
- 08Who is the actual person, and will they be the same person in a year? Ask to meet them, not the principal who sells the engagement.
- 09What does the exit package contain? Systems map, credentials, documented processes, vendor contacts, open decisions and their context, named in the contract.
- 10Tell us about an engagement that did not work and what you changed afterward. Everyone has one. Only some will tell you.
09Questions we get asked
- What does a fractional CTO do for a nonprofit?
- Owns the technology and product agenda on a part-time, retained basis. They sit with leadership, decide what gets built, bought, connected, or retired, direct vendors and support providers, and keep the systems map, credentials, and documented processes current so a staff departure is an onboarding task rather than an emergency.
- Is a fractional CTO the same as managed IT?
- No. Managed IT keeps infrastructure working: devices, accounts, network, backups, and a helpdesk. A fractional CTO decides what the organization should do with technology and answers for those decisions. The two combine well. The common arrangement is keeping your provider and having the fractional CTO direct them.
- How is this different from hiring a CRM consultant or implementer?
- An implementer configures and launches one platform, and the engagement ends at go-live. A fractional CTO is the person who decides whether that platform was the right purchase, how it connects to everything else, and what happens when the mail tool changes next year. Most organizations need both at some point, usually the seat first and then an implementer hired and directed by it.
- When is a nonprofit ready for a fractional CTO?
- When consequential technology decisions are being made and nobody owns them. The usual signs: the same supporter in several systems, a migration nobody can evaluate, a departing staff member who held the passwords, a board asking for a strategy nobody can write. It is not the right purchase if you are small with a simple stack, if you mainly need a helpdesk, or if you are mid-implementation on a platform.
- Which budget line does a fractional CTO sit on?
- Professional services, with legal and audit, rather than the technology line. The technology line is for things you operate. This is retained leadership. We publish no figures. There are three tiers, differing in how much support sits under the seat, and which fits is a scoping conversation. The first phase, discovery and documentation, is often fundable as capacity building.
- What happens to our support arrangement as we grow?
- It should change, and the leadership seat should not have to change with it. Organizations often start by keeping their managed IT provider under the fractional CTO's direction, move to a support desk under that direction if the provider is not working out, and hire in-house once programs run on specialized technology or ticket volume outgrows a shared desk. A current systems map and credentials in the organization's own name are what make that last move painless.
Find out whether you need the seat
A scoped conversation covers what you run now, who supports it, what decisions are in front of you, and which tier, if any, matches. If a managed IT provider or an implementer would serve you better this year, we will say so, and you will leave with a clearer picture of your own stack either way.