For nonprofits

Nonprofit technology support that doesn't end at launch.

Websites, donor data, CRM, and the dozen small systems your team quietly holds together. This practice is built for nonprofits that need someone ongoing — about half a day to a couple of days a week — so there's always a person who knows how your stack fits together.

SectorNonprofits
EngagementRetainer
Cadence~½–2 days a week
Based inSt. Louis, MO

You probably recognize at least three of these.

  • Your website was built by an agency that's no longer reachable, or by a board member's relative, or in 2019.
  • Donor information lives in the CRM, the email platform, the event ticketing tool, and a spreadsheet — and none of them agree on the total.
  • The donation form is an embed from a vendor nobody at the org chose, and when it breaks in December, that's a revenue problem.
  • Grant reporting means someone spends two days pulling numbers out of four systems by hand.
  • The person who understood how it all connected left, and nothing was written down.
  • A funder has started asking about accessibility, and nobody's sure what the honest answer is.

None of this is unusual and none of it is your fault. It's what happens when systems accumulate over years and nobody's job is to hold the whole picture.

If you're an education nonprofit, school, or out-of-school program, the education page may be a better fit.

The work, specifically.

Website rebuilds and redesigns
Fast, accessible, and updatable by your staff without calling anyone.
CRM cleanup and migration
Deduplication, reconciliation, and getting your systems to agree about who your donors actually are.
Donation and form infrastructure
Payment flows that work in December, on a phone, at 11pm.
Integrations
CRM to email to accounting to events, so the same information doesn't get typed three times.
Reporting
Numbers your board and your funders can read without a translator.
Accessibility
WCAG 2.1 AA remediation and building it in going forward. If you receive HHS funding, Section 504 has its own web accessibility deadlines — May 11, 2027 for recipients with 15 or more employees, May 10, 2028 for smaller ones. Both were extended by a year in May 2026, on a separate track from the DOJ's Title II dates, so it is worth checking which clock you are actually on.
Practical AI
Drafting, summarizing, intake triage. Where it saves staff hours, with a written policy about what it doesn't touch. Donor data included.

Why I don't sell this as a project.

A nonprofit website launch is not the hard part. The hard part is the two years after, when the calendar plugin breaks, the annual report needs a page, someone needs a new landing page for a campaign by Thursday, and staff turnover means the person who knew the login is gone.

So the offer is a retainer — usually about half a day to a couple of days a week — and that time covers whatever the week actually needs. Some weeks it's a redesign. Some weeks it's fixing a form and sitting in on a board call. You get a known cost and a known person instead of a quote for every request.

More about how engagements work →

Or see the fractional lead offer →

I've worked inside underfunded institutions.

I taught for eight years in public schools before I did any of this — ESL, English, History, robotics, coding, and a volleyball season. I know what it's like to be the person doing four jobs with no budget and no time, and to be handed software by someone who never asked how the work actually gets done.

Then I spent a decade across data security, business intelligence, fintech consulting, and running a startup's entire technology stack, where donor-grade data hygiene is table stakes and everything gets audited.

You get both: someone who builds like a bank and talks like a person.

Read more about me →

Questions I get

We can't afford a full-time technical person. Isn't a retainer the same problem?

It's a fraction of the cost, and it scales down. A day a week from someone senior gets you further than a full-time generalist hire, and you don't carry benefits, equipment, or a hiring process.

Who owns what you build?

You do. Code, accounts, domains, documentation — all in your name, all handed over as we go, not at the end.

What if we need to stop?

Thirty days' notice, no penalty. If this ever stops being worth it to you, it should be easy to end. I'd rather you leave clean than stay resentful.

Can you work with our existing vendors?

Yes, and often that's most of the value — being the person who can talk to your CRM vendor in their language and tell you whether what they're proposing is reasonable.

Let's talk about what's actually breaking.

A half-hour call, no pitch. I'll tell you honestly whether I'm the right fit — and if I'm not, who might be.