Ongoing technology partnership
You do the good work. I'll handle the technology.
I'm a senior developer building a practice for mission-driven organizations — nonprofits, schools, civic teams, and anyone else making their community better. Not project to project. About half a day to a few days a week, ongoing, as part of your team.
Most mission-driven organizations don't need a vendor. They need someone who stays.
You've probably been through this. An agency builds you a beautiful site, hands over a login, and disappears. Two years later nobody knows how to update the events page, the donation form broke in March, and the person who understood the CRM left in 2023.
The work isn't hard. It's just that nobody's holding it.
That's the job I do.
How much of me you need.
Every engagement is different, but they tend to land in one of three shapes. We'll figure out yours on a call.
A day a week
Steady maintenance, small improvements, and someone to call when something breaks. For teams whose systems mostly work but have nobody keeping them working.
Two days a week
Active building alongside the upkeep. Migrations, redesigns, integrations, automations — moving forward without falling behind on the day-to-day.
Half the week
Embedded. I'm effectively your technology department: planning, building, vendor decisions, budget conversations, the whole picture.
Engagements are meant to run six months or longer, because that's when this actually starts to pay off. Some weeks are quiet and some weeks something big ships — I plan for that rather than billing you surprises for it.
Some engagements are smaller than that — about half a day a week, twenty hours a month. That's enough to keep things running, fix what breaks, and move something forward every month. It's not enough to rebuild your site by spring. If your systems mostly work and you need someone holding them, this is often the right size to start at.
The work itself.
Over a long engagement, most of this comes up eventually.
- Websites
- Rebuilds, redesigns, migrations off platforms that stopped serving you.
- Accessibility
- WCAG remediation, audits, and building it in from the start so you're not remediating again in three years.
- Workflows & automation
- The spreadsheet everyone re-types into. The form that emails someone who forwards it to someone else.
- Data & CRM
- Cleanup, migrations, integrations, and reporting your board can actually read.
- Practical AI
- Where it genuinely saves staff time, with clear boundaries and a written policy. Not because it's on a slide.
- Senior judgment
- Vendor evaluations, RFP review, "should we buy this or build it," and telling you when the answer is neither.
How I work.
Fit call
A real conversation, not a sales call. What's breaking, what's coming, whether I'm the right person. Sometimes the answer is no, and I'll tell you who might be better.
Roadmap
A short paid discovery: I look at what you've actually got, then hand you a prioritized plan with honest costs. It's yours either way, even if we never work together again.
Steady work
We settle into a rhythm — regular hours, a shared list, a standing check-in. You always know what I'm working on and what's next.
Staying
No handoff cliff. The point of this arrangement is that there's never a moment where everything I know walks out the door.
Who this is for.
I built this practice around nonprofits, schools, and local government — I know how those budgets, boards, and procurement rules actually work. But I'm open to any organization making its community better.
Nonprofits
Donor journeys, CRM reality, and getting staff time back. →
02Local government
Accessible, resident-ready services that hold up to scrutiny. →
03Education
Schools, districts, colleges, and the systems families actually use. →
04Fractional technology lead
Senior guidance for organizations too small to hire it. →
Let's be honest about fit.
This works well if:
- You need someone consistently, not once.
- You have real systems people depend on and nobody dedicated to them.
- You'd rather have one senior person than a rotating agency team.
- Your budget is limited but real and recurring.
This isn't a fit if:
- You want a sealed handoff — build it, close the door, never speak again.
- You're collecting bids and choosing on price alone.
- You need a team of five starting Monday.
- What you're building isn't in the public interest.
If you're in the second column, I'm glad to point you toward someone who's a better match. That costs me nothing and saves us both a month.
Why this work
One person, a long career, pointed somewhere useful.
I've worked across nearly every stack there is. At some point it stopped being interesting to apply that range to whatever paid the most, and started being interesting to apply it where it's genuinely scarce — organizations doing necessary work on thin staff and tight budgets.
So I'm building this to stay small: a handful of organizations, years at a time. Rates are simple, and they get better the longer we work together. I'd rather have five clients for five years than fifty for five months.
Read more about me →Let's find out if this is a fit.
A half-hour call, no pitch. Tell me what's breaking and what's coming, and I'll tell you honestly whether I'm the right person for it.