Four ways to work with me, in the order most people take them.
Most people start with the first one or two. Each stands on its own, and you can stop at whichever rung suits you.
The Tech Check
Eight questions about how your systems work day to day. You get my read at the end, and a recommendation for which of the three below you need, if any.
Take the Tech CheckTakes
About three minutes
You get
A written read, and a recommendation for what to do next
Technology Review
Two or three weeks, fixed fee. I look at what you have, talk to the people who use it, and write you a document: what to keep, what to replace, what it will cost, and in what order.
The Review is a piece of work in its own right. Plenty of clients take it away and act on it without me. That's a fine outcome, and I'd rather you did that than bought something you didn't need.
Talk about a ReviewShape
2–3 weeks, fixed fee, me and your team
You get
A written roadmap, a system recommendation, and a cost model your board can read
Build & Integrate
The thing you decided on, built. Databases, portals, migrations, integrations between systems that were never meant to speak, websites that run off your own data rather than a content editor's patience.
I hand over documentation and train your team. If you can't run it without me, I've built it wrong.
See what that looks likeShape
Scoped project, typically six weeks to six months
Then
Most builds carry on into the ongoing arrangement below, because the questions don't stop at launch
Ongoing Technology Partner
You don't need a full-time technology director. You need one every few weeks, and you need them to already know your systems when something breaks or a vendor calls.
I hold the roadmap, sit in the vendor conversations, review the contracts, and do the small pieces of work that would otherwise become projects. Monthly, cancel when you like.
Talk about a partnershipA month looks like
A standing call, a maintained roadmap, vendor and contract review, and a set amount of hands-on work
Suits
Organizations with real systems and no one senior who owns them
On the AI question
Your board has asked. Someone has sent you a demo. Here's where I stand: almost every AI project that fails in an organization like yours fails for the same reason a data warehouse project would have failed in 2015: the underlying records are inconsistent, duplicated and spread across systems that disagree with each other.
So I treat AI as a lens on the data problem rather than a service line of its own. Fix what the model would be reading, and the useful applications become obvious and small. Skip that, and you get a pilot that impresses the board in March and is quietly switched off by September.
I'm happy to be the person who tells your board that in the room.
Why I'm faster than I should be
When you need a custom data layer, a portal, or forms that no off-the-shelf product does properly, I don't start from zero. I own the platform underneath — Simply360 — which means the parts of a build that are usually months of plumbing are configuration instead.
That isn't a pitch for it. If Salesforce, Airtable or something you already pay for is the right answer, I'll say so and help you get it working. But it's why a project that would take another consultant two quarters sometimes takes me six weeks.
For agencies & software firms
Build on what I've built.
If you already serve nonprofits as an agency, a consultancy or a software firm, you hit the same wall I did: every client needs a slightly different data model, and building that from scratch each time destroys your margin.
Two ways I help. I work alongside your team on the builds and integrations you'd rather not staff for. Or you deliver on Simply360 directly, under your own brand, and stop rebuilding the same foundation for every client.
It's the corner of the sector with the least help on offer, and the one I most enjoy working in. If this is you, say so when you get in touch.
Talk about a partnershipNot sure which rung?
That's what the Tech Check is for. It will point you to the right one.