For twelve or sixteen weeks, someone else was building your funnel for you. Mentor office hours, a partner introducing you to three people who might buy or invest, a demo day stage in front of a room built to pay attention to you specifically, and a batch full of other founders trading intros like currency. Then the program ends, the Slack goes quiet within a couple of weeks, and the structure that was quietly generating your conversations disappears all at once, usually right when the adrenaline of demo day is still wearing off and it feels like momentum should be building rather than stopping.
Demo day traction is mostly interest from people who fund companies, not people who buy from them
A full inbox after demo day feels like validation, and some of it is. Most of it, though, is investors and other founders reacting to a well-rehearsed six-minute story, not buyers reacting to a product they need. It's worth separating these on purpose, because they get answered differently and they mean different things: a term sheet conversation says something about the story and the market size. A reply from someone who runs the kind of business you built this for and wants to actually use it says something about the product. Founders coming out of a batch routinely spend the first post-demo-day month having the first kind of conversation and mistaking the volume of it for evidence the second kind is happening too. It usually isn't, yet.
The warm-intro well is shallow, and most of it is already spent
Mentors and batch-mates gave you something real: a first round of introductions to people who took the meeting because someone they trusted asked them to. That is a genuine, valuable, one-time gift. It is not a channel, because it doesn't renew itself. You cannot ask the same dozen people for a new introduction every month without the relationship curdling into something that feels like being used, and most founders sense that line well before they'd admit it out loud, which is exactly why the pipeline goes quiet a few weeks after the batch ends: the intros ran out and nothing replaced them.
What to actually do the week the batch Slack goes quiet
Stop refreshing the inbox for replies to demo day follow-ups that already went cold. Put the buyer into a sentence of plain description — what they do, how big the company is, which industry, and whatever made this particular month the right one to reach them — then run it through Rocketship for free and see two things back: the real count, and twenty-five actual names to read. A count that comes back tiny means the description was too narrow to support a real company. One that comes back enormous means it wasn't really a description yet, just a category.
Then start writing to strangers, this week, in a small batch you can actually read. This is the part that feels like a step down from a room full of people applauding a pitch, and it's also the actual job now. The batch gave you a running start. It was never going to run the company's customer acquisition for the next three years, and pretending otherwise for one more month just delays the point where the real number of paying customers starts moving.
Investor updates are not a sales channel, no matter how well they read
A lot of the energy that used to go into finding customers during a batch quietly redirects into polishing the monthly investor update instead, because that update has a real audience and a real deadline, and a well-written paragraph about "strong early signal" feels like progress. It isn't a substitute for the thing it's describing. If the honest version of next month's update should report the same flat user count as this month's, no amount of editing fixes that. What fixes it is running an actual acquisition loop in the weeks between updates, so there's something true and better to report next time, rather than a better-written version of the same number.
Building the loop that replaces the batch, in the first ninety days after it ends
The mechanics here are the same ones that would have applied on day one if there'd been no accelerator at all: find the real buyer, write to them, answer quickly when they answer back, and be reachable by phone for the ones who'd rather just call. What's different post-batch is the urgency and the absence of a safety net, which is exactly why it's worth setting up properly rather than improvising it between investor update drafts.
None of the sizing work costs anything: the search, the real count, and the free preview of names all come at no charge, so the first ninety days can open with a genuine read on market size instead of a number carried over from the pitch deck. From there, credits work the same way everywhere in Rocketship: one to add a name, five to turn up a verified phone number or email, landing only when something real actually comes back. Launch runs twenty-five dollars a month and brings one worker to write and read replies plus one line answered at any hour, useful sooner than most founders expect once the message is aimed at a real buyer instead of a demo day audience. When enough real conversations are happening that they need a calendar slot instead of you negotiating every time individually, Frontier's seventy-nine dollars adds a second worker and the scheduler. The top tier, Mission Control, runs a hundred and forty-nine dollars a month and brings the worker count to three, removing the ceiling on apps altogether — useful once there's a second product line or segment running alongside the first.
The batch gave you a story. Customers give you a company.
The high of demo day fades on its own schedule, usually faster than anyone wants to admit, and it's worth letting it fade rather than trying to keep it running through a better-written update. What replaces it isn't a bigger stage or a second round of intros from the same dozen mentors. It's the plain, repeatable work of finding a real buyer and talking to them, starting the week the Slack goes quiet rather than the month after the runway conversation gets uncomfortable.