The vendor you didn't need
A room spent the meeting scoping a vendor for a problem that was solved before the meeting ended. What that gap actually costs NFPs.
“We’ll need a vendor for this.”
I was on a call. The problem: a stack of paper surveys, filled out by hand, that needed to become rows in a spreadsheet. Someone had already started scoping it properly — an OCR vendor, a contract, a timeline measured in weeks. The conversation had that particular heaviness these ones always have. Too specialised. Too hard. Not something we can just… do.
By the time the call ended, it existed.
Not a plan for it. Not a shortlist of vendors to call. Working code — reading the scanned surveys, pulling out the fields, writing them to a CSV. Built with Claude, in the background, while everyone else was still debating who to hire.
I don’t say this to make anyone on that call look bad. Reaching for a vendor isn’t an unreasonable instinct — it’s the same rational-but-wrong instinct behind most NFP waiting. NFPs are trained by experience to expect that anything involving “real” technical work needs a specialist, a budget line, a procurement process. Nobody in that room had done the alternative before. So nobody knew the alternative existed yet.
That’s the actual gap. Not a skills gap. A gap in knowing what’s possible now.
“The problem wasn’t that it was hard. The problem was that nobody in the room knew it was already easy.”
This is the part of the job that doesn’t show up in a fundraising case study. It’s not a subject line test or a segmented email. It’s the unglamorous stuff — the paper survey nobody wants to transcribe, the CRM export somebody does by hand every month, the report that takes a day to compile because nothing talks to anything else. None of it raises money directly. All of it steals the time and headspace that would otherwise go into raising money — or delivering the mission — at all.
The framework I’m building — Nimble — started with fundraising tests. But the instinct underneath it is the same one that built that OCR pipeline mid-call: do the easy version and see. Not the vendor-shaped version. Not the six-week-estimate version. The version you can actually attempt this afternoon.
Most of the time, that’s enough to find out the “impossible” thing wasn’t.
K
Want to run your first Nimble experiment?
The Nimble Kickoff is a half-day session that gets your team asking the right question — and running a real test within two weeks.
Book a Kickoff →