The Grant You Missed Was Already on Your List

Last week I spent an hour with someone who helped build one of the best known software products in this sector. At one point I told him the story I've told a lot of people. At the end of 2024, when Lee first showed me a working prototype of what became BeMo, I looked at it and asked him what button I was supposed to push. I'm not an engineer. I wanted to be told the next move.

He said that years earlier, before he launched the product he's known for, he'd run his own version of Project TTP. He went out and asked nonprofits what they actually wanted, which is the same thing I've been doing for the last year and a half. The request he heard more than any other was almost word for word mine. Can you make one that just tells us what to do.

That was a long time ago. The sector answered him with bigger databases.

It still does, and nowhere more than around money. Ask a nonprofit leader what would help most with grants and most of them say a version of the same thing. Find me more of them. It's the answer the whole sector is built around. There are databases with hundreds of thousands of funder profiles, and the promise attached to every one of them is a longer list.

Then ask what actually went wrong this year.

In a year and a half of Project TTP calls, I've never once heard someone describe a grant they missed because they never found it. They describe a date that arrived while something louder was happening. The gala was that week. The audit opened. A board member needed something by Thursday. The deadline didn't sneak up on anyone. It was on the list the whole time.

Which brings us to August, the month that stops being theoretical. Letters of inquiry come due in September, full applications in October and November, and the reporting deadlines for whatever you won last year land somewhere in the middle of all of it. If you're the person at your organization who holds that calendar, you already know roughly what the next four months look like. You probably also know which pieces of it aren't going to happen.

What a miss actually looks like

A development director I spoke with keeps her pipeline in a color-coded spreadsheet. She walked me through it, and when she got to a block of yellow rows I asked what that meant.

"That means I wrote it but didn't send it."

I've thought about that answer more than almost anything else anyone has told me. Yellow isn't a category of failure anybody plans for. It's work that got done and didn't count. The research happened, the narrative got drafted, the case was made, and then something got in the way between the draft and the deadline, and none of it produced a dollar.

Someone else, running development at a small program, put the stakes plainly: "There's no going back if you miss a grant deadline." That's what separates this from most work that slips. You can apologize for a late report. A postponed meeting gets rescheduled. A grant deadline is a door that closes, and the next one is twelve months out.

Then there's who carries it. An executive director of a conservation nonprofit told me what actually weighed on him, and it wasn't that good funders were out there undiscovered. It was knowing that opportunities were slipping because nothing in his organization was sequencing them, and that he'd be the one explaining it to his board. His word for that was embarrassing.

A funder you never found costs you nothing this year. A funder you found, meant to write, and watched go by costs you the whole year.

The sector answered a different question

Almost every tool built for grants treats this as a discovery problem, because discovery is the part that's easy to sell. A bigger database is a number you can put on a website. Sequencing isn't.

A founder who also runs a grant strategy practice said the thing that reorganized how I think about this. She was describing what her clients actually need from her, and it wasn't a list of prospects:

"This is not a directory. This is literally a timeline for you over the next nine months."

Grant work isn't a search problem. It's a sequencing problem. Don't miss, don't overlap, don't get surprised. Which application has to start in three weeks so it can be finished in six. Which report is due to a current funder while you're asking a new one for money. Which two deadlines land the same week as your event, and which of the two you're going to choose, on purpose, in August, instead of by accident in October.

None of that is answered by a longer list. A list of two hundred matches isn't two hundred opportunities. It's two hundred unopened projects, each one carrying research, a fit judgment, a relationship, and a set of dates you now have to hold in your head alongside everything else you were already holding.

I should be fair to the other side of this, because for some organizations the list really is the problem. Some are new and don't have funder relationships yet. Some watched their funder base age out. And some have been quietly excluded by the structure of the market itself: minimum numbers served, funders who give only inside one county, domestic-only mandates that disqualify an international program before anyone reads a word of it. I've heard that described clearly at least once, by a leader who'd stopped applying altogether and built earned revenue instead. Not out of frustration. Out of arithmetic. I suspect it's more common than the sector admits. If that's your organization, a better list is a real answer and you should go get one.

The rest of this is for everyone else, which in my experience is most people.

The part nobody counts

There's a quieter cost underneath all of this, and it's the one I think actually explains why the calendar keeps winning.

Even organizations with a real pipeline rebuild their understanding of it every cycle. What did we tell this funder last time. Why did we decide to pass in March. Who on the board actually knows the program officer. What was the number we asked for, and what was the reason we picked that number. The pipeline persists as a list of names. The reasoning behind it doesn't.

So the season doesn't start when the deadline appears. It starts weeks earlier, with someone reassembling from memory and old files what the organization already decided once. By the time the picture is rebuilt, the runway is shorter than it looked in August, and the yellow rows start appearing.

None of this is chaos, and none of it is incompetence. It's capable people running a sequencing operation with no system holding the sequence, absorbing the gap with vigilance and personal memory, and eating the occasional closed door as the cost of doing business.

Before you buy another database

If your fall calendar is already worrying you, I'd try one thing before you add any tool to it.

Take an hour and write down every deadline you already know about between now and December. Next to each one, write what it needs and when the work has to start for that date to be met.

Then add one more column. Next to each funder, write the reasoning you'd otherwise have to rebuild in October. Why this one. What you told them last time and how they responded. What you asked for, and why you picked that number. Who at your organization actually knows someone there.

That column takes about twenty minutes and it's the only part of the exercise that survives you. The dates are public. You can always get them back from a website. The reasoning isn't. It lives in one person's head, and every fall it gets rebuilt from scratch, because it was never written down anywhere anyone else could reach.

Then look at what you have. It isn't a list of funders. It's the shape of your fall.

My guess is that you will find what I keep hearing. The problem was never that the list was too short. It was that the list was never a plan, and nothing was holding the plan except one person.

There are organizations running their real fall calendars in BeMo right now. Real deadlines, real money, no pilot scenario.

The work keeps happening. It just doesn't always build.

The people he talked to all those years ago weren't asking for a shortcut, and neither is anyone in our Project TTP calls now. They were asking for something that knows what they're in the middle of. It's what I asked Lee the first time he showed me a prototype, before I understood anything about what we were going to build. It's a reasonable thing to want, and the answer was never going to be a longer list.