I log every no I get, with the date and the reason behind it. Ninety days later, I follow up. Budgets change, timing changes, priorities shift, and most people treat a no as the end of the conversation. I treat it as a placeholder, and more often than you'd think, the follow-up is what turns it into a yes.
I help small teams do big things, and one of the quietest ways I do that has nothing to do with a pitch. It's what happens after someone tells me no. More than once, a prospect or a donor has told me no outright: not interested, wrong timing, no budget right now. Months later, that same person reached back out, ready to move forward. I hadn't made a better pitch. I had tracked the no, and I was the one who checked back in once their situation had time to change.
Why a no isn't actually the end of the conversation
Most people hear no and close the file. Nobody wants to seem like they can't take a hint. But a no is rarely a permanent verdict on you or your offer. It's a snapshot of one moment: this budget, this quarter, this week. A budget line that didn't exist in March can appear in July. Someone who wasn't ready in spring might be ready by fall.
Treating every no as final leaves revenue, donations and relationships on the table, because nobody was watching when the answer was ready to change. The follow-up doesn't manufacture a yes. It makes sure someone is there when the timing catches up.
What I actually log
Logging a no has to take less effort than forgetting it. Every time someone tells me no, I capture four things while the conversation is fresh:
- The date. The actual date, not the one I remember. The 90-day follow-up depends on it.
- Who said it. The specific person and organization, not "that prospect from the spring." Names get fuzzy fast.
- What was asked. The offer, package, sponsorship tier or donation ask that got the no. A follow-up only feels relevant if you can name the exact thing they turned down.
- The stated reason. Whatever they told you, in their words if possible. "Not the right time," "budget's committed elsewhere this year," "need to check with the board." The reason tells you what has to change before the no can become a yes.
A simple system, not a new tool
A spreadsheet with five columns does the job: date of the no, contact, what was asked, stated reason, and a follow-up date 90 days out. Sort by that date, and once a week send whatever's due. If you run a CRM, use a tag or status like "revisit" with a date field, so the deal doesn't vanish from your pipeline the moment someone declines.
Capture the no when it happens, not later from memory, and make a calendar reminder, spreadsheet sort or CRM view resurface it 90 days out.
I've had plenty of nos I was sure I'd remember to follow up on, and didn't. Memory only holds the handful of conversations that happened to stick. Every other no quietly disappears.
Why 90 days, and when to change it
Ninety days is a default because a lot of budgets run on a quarterly cycle. If someone says no in January because the Q1 budget is spoken for, April lands at the start of a fresh quarter, when a new line item might open up. Adjust it to how that relationship moves.
For a fast-moving sales conversation, 30 to 45 days is often closer. For a nonprofit donor whose giving runs on an annual budget or grant cycle, six months or a year makes more sense.
How to follow up without sounding like you're nagging
People worry about this part most. A follow-up feels like nagging when it's generic, repitches from scratch, or shows no memory of the original conversation. One that references what was actually said reads completely differently.
My structure: name the original conversation, ask whether anything has shifted, and make it easy to say not yet. Something close to: "Last time we talked, you mentioned the budget for this wasn't available until later in the year. Wanted to check back in and see if anything's changed. If the timing still isn't right, no worries, just let me know and I'll follow up again down the road." It proves you remembered, it asks instead of assuming, and saying no again costs them nothing.
The follow-up isn't a better pitch. It's being there when the timing catches up.
What to do if they say no again
A second no is more information. Log the new reason next to the original. If it repeats ("still the same budget issue"), lengthen the interval instead of following up every 90 days forever. If the reason changed, note that too: the situation is probably moving, just not all the way yet.
And if someone tells you directly they don't want to be followed up with again, that's a final no. Respect it. This system is for not losing opportunities to inattention, not for wearing anyone down.
Key takeaways
Hack 23 of 30
This is hack 23 in my "30 Hacks From Dahlia" series, and it has almost nothing to do with AI. The full series is linked in my bio. If you run a sales pipeline, a sponsorship program or a donor list, open it today and log the last three nos you got, with a date 90 days out.
Frequently Asked Questions
Log it in whatever you already use to track prospects or donors, a spreadsheet, a CRM field, or a simple tag. One row or one tag per no: the date, who said it, what was asked, and the reason given. It takes under a minute and it only has to happen once, right after the conversation, while the details are still fresh.
Ninety days is a reasonable default because a lot of budgets reset on a quarterly cycle, so it gives enough time for a new quarter, a new priority, or a changed circumstance to actually show up. It is not a fixed rule. Shorten it to 30 or 45 days for fast-moving sales conversations, and stretch it to six months or a year for annual budget or grant cycles, like many nonprofit donors run on.
Reference the actual conversation you had, not a generic check-in. Name what they told you back then, ask a genuine question about whether anything has changed, and make it easy for them to say not yet again. Do not repitch from scratch. A short, specific, low-pressure message reads as attentive, not pushy, because it proves you actually remembered the details.
Log the new reason next to the old one and compare them. A repeated reason usually means the timing has not shifted yet, so lengthen the interval before you check back in. A different reason means something did change, which is worth noting for the next attempt. Either way, a second no is information, not a reason to stop tracking, though at some point a person's clear preference to be left alone should be respected.
