First reply on every signup
A friendly two-line welcome with the right onboarding link, sent inside the first minute.
How-to — — by Mahmoud Zalt
A calm playbook for solo founders to handle a press mention going viral: absorb the inbound, keep the site standing, and convert spike traffic into paying customers without burnout.
The first hour after a press mention takes off is loud and lopsided. Referral traffic climbs in a near vertical line, social mentions stack across three or four platforms at once, and a long tail of cold emails lands from people who skimmed the headline and want a demo by tomorrow. Most of the inbound is shallow: short questions, signup confirmations, partnership pitches, and journalists fishing for a second quote. Underneath the noise sits a small slice of real buyers who will decide based on the first thing they see on your homepage. The trap is treating every ping as urgent and answering all of them by hand. The real job is to keep the site standing, post one calm canonical reply, and protect the queue so the buyers in the noise can still find their way to a paid plan.
Panic looks like answering random DMs for six hours and forgetting that the homepage still says beta. Calm looks like a tight written order of operations you run top to bottom. Your job in the first hour is not to reply to everyone, it is to set the front door, point traffic at it, and make sure your queues are watched while you stay on the product. The five steps below are the exact sequence I run when a piece I have shipped gets picked up by an outlet that moves traffic. Each step is small, finishable inside ten minutes, and intentionally boring. The point is to make decisions once, in writing, so the next 48 hours run on autopilot instead of adrenaline.
Yes, and it is the single biggest difference between a viral mention that converts and one that burns the founder out. A pair of AI Employees, one on sales and one on support, can hold the line on first replies, qualify intent, capture useful context, and escalate the small slice that actually needs you on a call. The work during a spike is repetitive on purpose: the same five questions about pricing, the same three about integrations, the same two complaints about a checkout glitch nobody had noticed before the wave. That kind of repetition is exactly what AI is good at, and what burns a solo founder out fastest by hand. You stay on the calls that close and the bugs that block.
A friendly two-line welcome with the right onboarding link, sent inside the first minute.
Plan comparison, trial mechanic, and refund policy answered from your own help docs.
Bugs classified, screenshots requested, severity tagged, and only the urgent ones bounced to you.
Outreach sorted into qualified, low-fit, and journalist follow-ups, each with a draft reply ready.
Repeat questions surfaced as a daily list so you can ship a help-doc update instead of replying 40 times.
The mental shift is from doing every reply yourself to running a small team of AI Employees during the wave. You write the rules of engagement once: tone, escalation triggers, links allowed to share, deals allowed to confirm. Then you watch the queue, sample replies every couple of hours, and step in only when a real buyer or a real bug shows up. The job stops being inbox triage and becomes editorial oversight.
Once the AI front line is doing the heavy lifting, the next decision is what to do with the attention. A viral mention buys you a wide window of cheap eyeballs and a much smaller window of high intent. Most founders waste both because they keep optimizing for response speed when the higher-value job is conversion. The next section is the small set of moves that turn a noisy day into a healthy month of revenue, without funnels or popup tricks. It is mostly about letting the spike land on a page that actually sells.
Viral attention is a renewable asset only if you actually capture it. Most spikes leak quietly because the landing experience was built for trickle traffic and breaks under a thousand simultaneous visitors with five seconds of patience. The conversion job during a spike is unglamorous: make the homepage answer one question in three seconds, put the strongest social proof above the fold, and remove every step that asks the visitor to think before they click. The five moves below are the highest-leverage things I have seen actually move paid signups during a viral wave. They are small, they are boring, and they are what you should be doing while the AI front line handles replies in the background.
Three or four days in, the curve always softens. Referral traffic halves, then halves again, and the inbound queue empties faster than it fills. This is the moment most founders crash, sleep for two days, and forget that the highest-value work for the next quarter actually happens right now. The week after the spike is when you turn a moment into momentum: you debrief honestly, nurture the long tail of captured emails, ship the small fixes the wave surfaced under load, and put a tiny system in place so the next mention does not feel like a fire drill. The five steps below are the cooldown routine I run after every press mention that lands harder than expected.
If first-reply time on support or sales messages crosses two hours, you are losing more buyers than you save. That is where AI Employees stop being optional.
Most managed hosts absorb a viral spike fine. The risk is the database under your signup form. Cache the homepage, rate-limit the signup endpoint, and load-test once before you need it.
Only if you let them. Give the employees your tone, your phrases, and the lines you would never say. Sample replies on day one, edit a few, and the voice tightens fast.
Yes, for 48 hours. Paid traffic during a spike inflates spend and muddies the attribution on the press signal. Restart once the curve flattens so the lift reads cleanly.
Most press-driven spikes peak inside 24 hours, hold elevated traffic for two or three days, and decay to a new baseline that is 20 to 40 percent higher than before the mention.
If a press mention is not the only kind of attention you are planning for this year, the cousin playbook is worth a read. A launch on a public listing site triggers a similar spike shape but with a different audience and a tighter conversion window, and the moves overlap heavily with the ones above. Treat both as variations of the same skill: absorbing inbound, protecting product time, capturing the long tail.
The honest reframe of a viral press mention is this: it is not a marketing event, it is an operations test. The companies that grow out of one were not luckier with the timing, they were calmer with the queue. They had a pinned reply, a clean homepage, a small AI front line absorbing the noise, and a founder who refused to confuse activity with progress. None of that is glamorous and almost none of it shows up in the case studies later. What shows up is the revenue curve six months on, the small base of early customers who stuck because they got a fast first reply, and the help docs that quietly absorbed every question for the next press cycle. Build the calm first. The spike will find you, and the only thing you control is what it lands on.