ExecRoster

Fractional CTO for Nonprofits: What They Do, When to Hire

November 20, 20266 min read

A fractional CTO for nonprofits is a senior technology leader who works part time to make the organization's systems dependable: the donor CRM, online giving, program data, security, and vendor contracts. Hire one when technology decisions are being made by whoever is least busy, and a failed migration or a breach would put funding at risk.

How nonprofit technology differs from a company's

A nonprofit rarely builds software. It assembles it. The core is a constituent database (the donor CRM), surrounded by online donation forms, an email tool, an event or peer-to-peer fundraising platform, a volunteer system, and a fund accounting package. Program teams add a case management or client tracking system, and the data team (often one person) tries to produce outcome reports for funders from all of it.

Several conditions make this harder than it looks:

  • Technology is funded as overhead. Many grants restrict spending to programs, so systems get bought with whatever unrestricted money is left.
  • Nobody owns it. The role falls to an operations manager, a development associate who is good with spreadsheets, or a volunteer who built a database years ago and has since moved away.
  • The data is sensitive. Client records can involve health, immigration status, housing, or minors. Donor records include giving history and payment details.
  • The calendar is unforgiving. Many organizations count on the year-end appeal, and systems cannot change or fail in that window.
  • The board has opinions. A board member who works in tech may push for a tool their company uses, which may not fit an organization with two operations staff.

A fractional CTO in this setting acts more as an architect and buyer than as an engineering manager. The general seat is described in the fractional CTO guide, and the nonprofit version leans heavily on vendor selection, data, and risk.

What a fractional CTO takes on

ResponsibilityWhat it looks like in practice
Systems map and roadmapA one-page diagram of every system, what data lives where, who owns it, what it costs, and when each contract renews. Then a two to three year plan the board can approve.
CRM selection or rescueWrites requirements with development staff, runs the RFP and demos, checks references, negotiates the contract, and oversees the implementation partner
Data migrationPlans deduplication, household and soft credit rules, gift history mapping, and a reconciliation of migrated gift totals against the accounting system
IntegrationConnects giving forms, CRM, email, and fund accounting so gifts are not keyed twice and restricted funds are coded correctly
Security baselineMulti-factor authentication, offboarding for staff and volunteers, device management, backups, phishing training, an incident response plan, answers for the cyber insurance questionnaire
Vendor managementManages the outsourced IT provider, reviews licenses for nonprofit discounts, cancels unused subscriptions
Funder and board reportingWrites the technology section of capacity-building grant proposals and reports to the board or its finance and audit committee

Problems that are particular to nonprofits

The database only one person understands

Custom fields were added by five development directors over fifteen years. Nobody knows which "major donor" flag is the real one. Reports take a day to build and the totals do not match finance. The CTO documents the data model, retires what is unused, and writes data entry standards so the next migration is not a rescue.

Program outcomes trapped in spreadsheets

Funders ask for outcome data: clients served, services delivered, results at six months. If each site tracks this in its own spreadsheet, every grant report is a manual assembly job. A CTO defines the common data set, picks a case management tool sized to the organization, and sets up reporting that program staff can run themselves.

A CRM project that is running long

The implementation partner is billing for change orders, staff have stopped attending training, and go-live has moved twice. Nonprofits in this position usually lack someone on their side of the table who can read a statement of work. The CTO resets scope, sets acceptance criteria, and schedules go-live away from the year-end appeal and the gala.

Volunteers and former staff who still have access

Shared logins and accounts for people who left years ago are common. An access review is unglamorous and is frequently the highest-value work in the first month.

Privacy and data protection obligations depend on your jurisdiction and the populations you serve. This article is educational and is not legal advice.

Signs your organization is ready for one

  • You are about to choose or replace a donor CRM or case management system, and the decision will cost more than any previous technology purchase.
  • Development and finance report different revenue numbers and spend days each month reconciling.
  • A funder, auditor, or insurer has asked security questions nobody could answer.
  • Your managed IT provider handles laptops and email, and no one is thinking about data or strategy.
  • A capacity-building grant is available for technology and you need a credible plan to apply.
  • The person who "knows the systems" has given notice.
  • The board has asked for a technology plan and the executive director does not know where to start.

A very small organization with a handful of staff and one off-the-shelf donor tool is usually better served by a few hours with a nonprofit technology consultant. A full-time CTO makes sense mainly for large organizations or those whose program is itself a digital product.

Shape of the engagement, and how to pay for it

A typical arc has three stages. The first is an assessment lasting four to eight weeks: interviews with development, programs, finance, and operations, a systems inventory, an access review, and a short written roadmap with costs. Many executive directors take that document to the board and to funders. The first 90 days guide shows how to structure this period.

The second stage is a project, usually a system selection and implementation, where the CTO might work a day or two a week for several months. The third is light ongoing oversight: a few hours a month for vendor reviews, the annual security check, and board reporting.

On funding, three approaches come up often. Write the role into a capacity-building or technology grant. Include a share of it in program grant budgets where the system directly supports that program. Or ask a board member or major donor to underwrite the assessment as a one-time gift, since a bounded, named project is easier to fund than general overhead.

When you write the scope, be specific about decisions. State that the CTO recommends and the executive director approves purchases above a set amount, with board approval above a higher threshold. The guide to scoping a fractional engagement has a template you can adapt. One more point belongs in the scope: staff training and documentation. A nonprofit's systems fail most often at handoff, when a trained person leaves and the knowledge leaves with them. Make written procedures and a named internal system owner a required deliverable, so the organization can run what was built after the engagement steps down.

For experienced executives

Get found and hired for fractional work.

  • A profile companies can find
  • A calendar they can book
  • Paid to your bank, you keep 90%
Join the Roster Hiring? Browse the roster →

Frequently asked questions

What does a fractional CTO do for a nonprofit organization?+

They own technology strategy part time: mapping current systems, selecting or fixing the donor CRM and case management tools, planning data migrations, connecting giving forms to accounting, setting a security baseline, managing the IT vendor, and reporting to the board. The role is mostly architecture, purchasing, and risk management.

When does a nonprofit need a fractional CTO instead of an IT provider?+

A managed IT provider keeps laptops, email, and networks running. A fractional CTO is needed when someone must own data, system selection, and strategy, for example before a CRM replacement, when development and finance numbers disagree, or when a funder or insurer asks security questions nobody can answer.

How can a nonprofit pay for a fractional CTO with restricted funding?+

Common approaches are writing the role into a capacity-building or technology grant, allocating part of the cost to program grants where a system directly supports that program, or asking a board member or major donor to underwrite a defined assessment. A bounded project is easier to fund than general overhead.

Should a small nonprofit hire a fractional CTO or a technology consultant?+

A very small organization with one off-the-shelf donor tool usually needs only a few hours from a nonprofit technology consultant. A fractional CTO fits when there are several connected systems, sensitive client data, a major purchase ahead, or a board asking for a multi-year technology plan.

Put your experience to work.

Get on the roster, get found by companies that need exactly your background, and get paid on your terms.

Qualified, paid engagements · Your rate, your calendar · Cancel anytime

We use cookies to understand how the site is used and to measure our marketing. See our cookie policy.