Why a message from the founder works
Most onboarding emails come from "the team" at a no-reply address. A note from the founder or CEO, signed with their name and sent from an account that takes replies, says something the product can't: the person who runs the company noticed you.
Users read it as a direct line. When beehiiv's CEO, Tyler Denk, connected with a new user on LinkedIn, the user wrote that the message was "generic and probably used for everyone else. But that doesn't bother me. The key here is that he used his personal account to do this. Now, I feel I have a direct way to communicate with him" (Nick Madrid on LinkedIn). Denk replied under the post that he has done this from the beginning.
The best-timed messages fix something. In June 2025 a user hit a billing glitch while upgrading to Cursor Pro, worked around it and moved on. Within 24 hours Cursor's CEO, Michael Truell, emailed him: "I saw that you tried to sign up for Cursor Pro but didn't end up upgrading. Did you run into an issue or did you have a question? Here to help." The user replied that he was "a happy customer now", and a year later wrote a LinkedIn post about the email (Roman Erlacher).
Three things happen at once. The user gets unblocked or welcomed by the most senior person possible; the company learns why people sign up and where they get stuck, straight from the replies; and some of those users tell the story in public, which is free distribution no ad can buy.
The moments to write
A founder can't write to everyone about everything. Pick the moments that decide whether a trial becomes a customer:
- Right after signup. A welcome that asks one question: why did you sign up, or what are you trying to do? beehiiv does it on LinkedIn. At DoltHub, every new signup gets an email from a real person with the CEO, Tim Sehn, copied, and work email addresses get a follow-up from him directly (DoltHub, May 2025).
- Right after something fails. A failed payment, an abandoned upgrade, an error, an import that didn't finish. Cursor's email is the model: it names what happened and asks one question.
- At a milestone or a stall. The first real use ("you just sent your first newsletter"), or a week of silence after signup. Ask what got in the way.
- To your own network, before signup. Ramp's VP of Product, Geoff Charles, offered his LinkedIn network a deal: sign up through his link and he would personally onboard you, you'd get $500, and he would run an AMA with your product team.
- After someone says no. A lost deal or a cancellation is the moment most companies go quiet. lemon.io's CEO, Aleksandr Volodarsky, emails leads who didn't buy, under the subject "lemon.io: what went wrong?", and asks them why (Aleksandr Volodarsky on X, December 2024). The answers tell you what to fix, and sometimes reopen the deal. Pair it with a cancellation flow for customers who leave.
Each of these is a message the user didn't expect from someone they assumed was too busy to send it. That surprise is the whole effect, so don't spend it on newsletters, feature announcements or upsells.
How to write it
Short. Netlify emailed every new user from its head of customer success, offering help. At 150+ words, 1% replied; cut to 37 words, 4%; cut to 14 words, 8%, eight times the conversations from the same signups (Greg Kogan, 2017). A founder's note should read like a text from a person, not a newsletter.
Plain. No logo, no buttons, no HTML template, no tracking-pixel tricks in the subject line. Truell's email is four lines and a signature.
One question. "Did you run into an issue or did you have a question?" or "What made you sign up?" A question gets replies; a list of resources gets archived.
From a real account that answers. The founder's own name and address, or their personal LinkedIn profile, not a company page. Replies go to a person who reads them.
At most one ask, and make it small. Denk asks new users to subscribe to his newsletter about building beehiiv, which turns every welcome into a reader. Asking for a call, a review or a referral in the first message reads as a sales email.
Specific when you can be. "I saw that you tried to sign up for Cursor Pro" works because it's about the user's problem. Mention what they did only when it helps them; a note that recites their every click feels like surveillance.
Automate the trigger, keep the reply human
Under the Cursor post, several commenters guessed the CEO's email was automated: a system flagged the failed upgrade and sent a template in his name. The user didn't mind, because it arrived at the right moment and someone was there when he replied. The beehiiv user said the same about Denk's generic LinkedIn note.
That's the line that matters. Automating when the message goes out is fine, and at thousands of signups a week it's the only way. Pretending a person is there when nobody reads the replies is what burns trust. One commenter on the Cursor post said a similar email he got went unanswered when he replied.
How teams scale it:
- Trigger from product events. Signup, failed payment, abandoned upgrade, first key action, seven days inactive. Send from the founder's real mailbox, in plain text.
- Route replies to people. The founder reads a sample every week; support or success answers the rest, signing with their own name.
- Segment. DoltHub sends a follow-up from the CEO only to work email addresses, where a conversation is worth most. Keep LinkedIn connections for the users who match your best customers: LinkedIn limits how many invitations an account can send each week.
- Measure replies and conversion, not opens: reply rate, trial-to-paid for users who got the message against those who didn't, and what the replies say.
DoltHub reports about 1–2% of signups reply, which it calls "much better engagement than even the best automated onboarding flow could achieve." Every reply is a user telling you, unprompted, why they came and what's in the way.
Where it fails
- Replies that go nowhere. A founder's email that nobody answers is worse than no email. Before you send one, decide who reads the replies and how fast.
- The founder stops. It starts as a habit and fades as the company grows. Put it in the product's event triggers, not on the founder's to-do list.
- Fake intimacy. "I personally noticed you" sent to everyone, or a fake "Sent from my iPhone", gets screenshotted for the wrong reasons. Generic is fine; pretending isn't.
- A sales pitch in disguise. A founder note that books a demo on the second line is an outbound email with a famous name on it.
- Too creepy. Naming the exact feature someone hovered over, or messaging within seconds of a signup, feels like being watched. Write about the thing that went wrong or the goal they told you.
