# The Founder Email to New Signups > How to write the founder email new SaaS signups actually reply to, with timing, a plain-text template, what to ask, how to handle replies and how to keep it honest as you scale. Source: https://comppound.com/blog/the-founder-email-to-new-signups (published 2026-08-29) Most new SaaS signups receive a stack of automated emails in their first week: a welcome message, a getting-started guide, a feature tour and an invitation to a webinar. Each one is designed, branded and carefully timed. Yet one email often does more than all of them for replies and goodwill: a short, plain-text founder email to new signups, sent from a real person and asking a single real question. It works because it feels like a human reaching out, which is exactly what it should be. It also gives you something automated sequences rarely do: direct answers from new users about what they want, what they are comparing you to and where they are stuck. For an early-stage company still figuring out positioning and onboarding, that stream of answers can be more valuable than any metric on a dashboard. This guide covers why the email works, when to send it, what to write, what to avoid, how to handle replies and how to keep it honest as you grow. ## Why the founder email works ### It stands out A new user's inbox is full of designed marketing email, much of it from tools they signed up for in the same week. A plain message from a named person, with no logo, no header image and no buttons, looks different. It reads like something a colleague would send, so people open it and read it. ### It invites a reply Automated onboarding emails are built to drive clicks. The founder email is built to start a conversation. A good one asks one simple question that the user can answer in a sentence. When they reply, you have a direct line to a new user at the moment they are forming their opinion of the product. ### It signals care Early customers want to know there are real people behind the product, especially when they are betting on a newer company. A note from the founder, followed by a real reply when they respond, tells them that their success matters to someone who can actually change things. ### It generates research Replies tell you why people signed up, what they were using before and what confuses them, in their own words. That is the kind of insight teams usually pay for through interviews and surveys. Here it arrives in your inbox as a side effect of good onboarding. ## When to send it Timing matters more than it seems. Send it too early, and it arrives alongside the email verification message and the automated welcome, where it gets lost or looks like part of the same machine. Send it too late, and the user may already have decided whether to continue, often without telling you why. A common approach is to send it a few hours after signup, or the next morning in the user's time zone, so it arrives at a reasonable time and stands apart from the first automated messages. Some teams prefer to wait until the user has logged in at least once. That way, the question can refer to what they have already seen, and the email does not go to people who signed up and never came back. Either approach works. What matters is choosing deliberately and keeping the email separate from the automated sequence in the user's mind. ## What to write Keep it short, plain text and from a real person's email address. No logo, no images, no buttons and no signature block full of social links. The email should look like something the founder typed, because ideally it is close to that. ### Template > Subject: Quick question > > Hi [First name], > > I'm [Your name], founder of [Product]. Thanks for signing up. > > I like to ask everyone who joins one question: what made you sign up today? Knowing what you're trying to get done helps me point you to the right part of the product, and honestly helps us decide what to build next. > > Just hit reply. I read every answer. > > [Your name] The question "what made you sign up today?" is open enough that anyone can answer it and specific enough that the answers are useful. It also gives the user a reason to reply that benefits them, since you can point them to the right part of the product. ### Variations You can change the question to suit what you most need to learn. A goal-focused version asks about the user's immediate aim: > What's the one thing you'd want [Product] to help with in your first week? A comparison-focused version helps with positioning: > Were you using anything else for this before? I'm curious what you were comparing us to. A help-focused version suits products with a tricky setup step: > If you get stuck setting up [key step], reply here and I'll help directly. Pick one question per email. Several questions in one message reduce replies, because answering becomes a chore. If you want to learn different things from different users, rotate the question over time rather than stacking them. ## What not to do ### Do not fake it If the founder never reads the replies, the email becomes a broken promise, and users notice when their honest answer disappears into silence. If the founder cannot keep up, have the email come from a named team member who genuinely responds. A real customer success lead who replies is far better than a founder's name on an unmonitored inbox. ### Do not pitch This is not the place for upgrade offers, webinar invitations or feature lists. Adding a pitch turns a personal note into marketing, and users will treat it that way. Keep the email about them and their goal. ### Do not use fake personal touches Lines like "I noticed you're from [Company] and love what you're doing," generated from enrichment data, look automated immediately. They undermine the sense that a real person wrote the email, which is the whole reason it works. If you cannot personalize genuinely, do not personalize at all. ### Do not send it to everyone forever As signup volume grows, sending the founder email to every new user may become impossible to handle honestly. At that point, consider sending it only to signups that match your ideal customer profile, or rotating responsibility across the team. ## Handling replies The value of the founder email lives in the replies, so plan how you will handle them before you start sending. Reply quickly, ideally the same day. A fast response proves the promise in the email was real and catches the user while they are still engaged. Answer the actual question or comment before pointing to resources. If a user describes a goal, connect it directly to the feature or template that serves it, with a link and a one-line explanation. Avoid sending a generic link to your help center, which feels like being handed off. For high-fit accounts with complex needs, offer a short call when it would genuinely help them get set up. Do not push a call on everyone. Many users prefer to work things out themselves with a nudge in the right direction. Log what you learn. Keep a simple spreadsheet with the reason each person signed up, any alternatives they mentioned and any problems they hit. Patterns appear quickly. Within a few weeks, you may notice that a large share of users mention the same competitor, or that many arrive looking for a use case your homepage barely mentions. Those patterns are useful for positioning, onboarding and content. ## An example reply A user might write back: > We need to report on which marketing channels bring paying customers. Right now it's a mess of spreadsheets. A good founder response would be: > Thanks, that's exactly what we built this for. The fastest path is connecting Stripe and Google Analytics, then opening the "Revenue by channel" report. Here's a 3-minute guide: [link]. If the numbers look off once it's connected, reply and I'll take a look with you. This answer is short and specific, and it moves the user toward value. It acknowledges their problem, gives them the exact next step, links to one resource and offers further help without demanding a call. ## Turning replies into changes The spreadsheet is only useful if someone reads it with a decision in mind. Once a month, set aside an hour to review the replies with whoever owns onboarding and marketing. Look for the reasons people signed up that your homepage does not mention, the alternatives that come up repeatedly and the setup steps where people ask for help. Each of those points to a concrete change: a new use-case page, a comparison page, a clearer empty state or a better help article. Close the loop with the users who raised an issue when you fix it. A short note saying "you mentioned this was confusing, and we've changed it" costs a minute and tends to be remembered for a long time. It also shows the rest of your early users that replying to the founder email leads somewhere. ## Measuring the impact Track the reply rate first, since replies are what the email is designed to produce. Then compare activation between users who reply and users who do not, while keeping in mind that motivated users are more likely to reply in the first place. That comparison will overstate the email's effect, so treat it as a signal rather than proof. Most of the value is in the themes that emerge from the replies, which shape everything from onboarding to messaging. Do not judge the email by click-through rate. It is designed for replies, not clicks, and adding links to raise click-through would undermine its purpose. ## Scaling it honestly As signups grow, the founder may not be able to answer every reply personally. There are honest ways to scale. Route replies to a shared inbox handled by the founder and a teammate, so someone always responds quickly. Send the email from a customer success lead instead, using their real name and real address. Or limit the email to high-fit signups, where personal attention is most likely to make a difference. What matters is that the person named in the email, or someone clearly on their team, actually responds. Users forgive a reply from a colleague. They do not forgive silence. ## The takeaway The founder email is simple, cheap and surprisingly effective. Keep it short and plain, ask one real question, send it at a sensible time and read every reply. Answer quickly, point people toward value and log what you learn. It improves onboarding for the people who respond, and it gives your whole team a steady stream of customer insight in the customers' own words. ## Keep reading - [Cold Email Deliverability Setup for a New Domain](/blog/cold-email-deliverability-setup-for-a-new-domain) ## Frequently asked questions ### Should SaaS founders email every new signup? Many early-stage founders do, as long as they can read and respond to replies. As volume grows, it can be limited to high-fit signups or sent by a named team member. ### What should a founder email to new users say? A short thank-you and one simple question, such as what made them sign up, in plain text from a real person. ### When should the founder email be sent? Often a few hours after signup or the next morning, so it does not get lost among verification emails. ## About Comppound Comppound runs SEO and AI search for B2B SaaS companies: a person sets the plan and reviews samples and every high-risk page, and AI speeds up production. - [See SEO Growth](https://comppound.com/services/seo-growth): Buyers compare before they book a demo. Are your pages there when they do? - [Book a call](https://comppound.com/contact): Most of this works better when buyers can find you first