Set up lifecycle email for new signups

The most important decision in lifecycle email is which action counts as a new signup getting value, because every email in the sequence exists to move people toward it. That action is different for every product. It might be importing a first file, inviting a teammate, connecting a data source, or publishing a first page.

Kite finds it in your own data. With Supabase connected, it reads how your tables are organized and writes its own queries. For example, it might notice that people who create a workspace within their first day are far more likely to still be active a month later. With PostHog connected, it reads retention and lifecycle numbers to see how many new signups come back in the weeks after they join.

Kite then checks the answer against revenue. It matches signups to their Stripe customer records, usually by email address, and compares what paying customers did in their first week with what everyone else did. Kite proposes the activation step it found and shows you the numbers behind it. Once you agree, it saves the definition to your team's knowledge base, so the emails, the reports, and later work all use the same meaning of "activated."

Kite plans the whole sequence before it writes a single email, because the plan decides more about the result than any subject line. For each email, the map records when it sends, what the reader has and hasn't done by then, and the one thing that email is for.

A typical map for a free trial might look like this:

• A welcome right after signup that points to the activation step.
• A follow-up a day later, for people who haven't taken that step, that shows the result they'd get if they did.
• An email a few days later covering the feature your best customers rely on most.
• A note before the trial ends that reminds the reader what they've already set up and what they'd lose.
• A short, plain-text check-in from a named person on your team asking what's in the way.

Kite checks the map for emails that overlap. If two emails could swap places without anyone noticing, they're the same email, and Kite cuts one or gives it a different job. It shows you the map beside the drafts, so you can judge the timing and the copy together.

Kite decides which email a signup gets from what that person has done in your product, which is what marketers call behavioral marketing. A fixed schedule sends the same five emails to everyone. A behavior-based sequence sends the nudge about connecting a data source only to the people who haven't connected one.

Kite uses two ways to make that happen, depending on the email.

The first is an event. When your product records an action, such as a signup or a first project created, it can send that event to your email tool, and the event starts the matching email or sequence for that person. Kite defines the events and the data each one should carry, such as the person's plan or the use they picked at signup, so a single email can speak to the reader's own situation.

The second is an audience built from behavior at the time of sending. For nudges that should reach only the people who stalled, Kite queries your product data or builds a PostHog cohort, such as everyone who signed up in the last week and hasn't created a workspace. Those people get the nudge, and everyone who already took the step is left out. Kite can run that check on a schedule, for example every weekday morning, so each stalled signup hears from you at about the same point in their first week.

Kite writes each email so it still reads well if the person has done what the last email asked. Signups don't always act in the order a map expects, and an email that assumes they haven't started can feel off to someone who just did.

Kite writes every email around the reader's situation when it arrives and the single action that moves them forward. Your product is the subject of each email. The email says what the product does for the reader, or what it already did for them, and asks for the one step that lets it do more.

Every email gets a subject line, preview text, and a body in your brand voice. Kite picks the format to fit the job. A welcome or feature email can carry your design. The check-in works best as plain text signed by a real person on your team, because that's the email people reply to. Kite fills each email with the details your data carries, such as the reader's first name, company, or plan, and sets a fallback so a missing name reads "Hi there" instead of leaving a gap.

If you want a sense of what strong first emails look like before you start, see Welcome email examples that turned new signups into active customers Coming soon .

Kite builds the sequence where your email already runs, so your team can see it and edit it in a dashboard they know. What it builds depends on the tool.

In Resend, Kite builds the whole setup. It creates the contact properties the emails use, defines the signup event, creates each email as a template and publishes it, and builds the automation that sends the templates with a wait between each one. It also checks that your sending domain is verified, and if it isn't, Kite adds the domain and gives you the DNS records to place.

In PostHog, Kite writes the email templates and builds the workflow that sends them, starting on a signup event or on a scheduled batch for an audience like a stalled cohort. For a batch, it tells you exactly how many people the audience matches before you approve.

In Mailchimp, Kite adds and tags new signups, logs the events Mailchimp uses to sort contacts and start automations, and starts a Customer Journey or an automation email for a specific contact when that contact reaches the right moment. If Kite hosts your website, signups from the form you choose land in your Mailchimp audience with the tags you pick.

In Brevo, Kite writes and rewrites the email templates your Brevo automations send, such as the welcome message, so every email that automation sends from then on carries the new copy.

If you don't use an email tool yet, Kite can send from your team's Kite email address. Replies to that address reach Kite, which reads them and tells your team what people said.

Some new signups deserve more than an automated sequence, and Kite can find them as they arrive. You can give Kite a web address that your product, or a tool like PostHog, calls whenever someone signs up. Each signup then starts a fresh piece of work for Kite.

Kite researches the person's company and role, compares them with your ideal customer profile, and drafts a short note from someone on your team for the signups that fit well. Say a product lead at a 200-person company that looks like your best customers signs up on a Tuesday. Kite tells your team who they are, why they matter, and what the note says, and it sends the note once you approve. The automated sequence keeps running for everyone else.

Kite tests every sequence on a test contact before any real signup goes through it. It sends the signup event for an address you choose, such as your own, and then reads the run step by step. You receive the emails exactly as a new signup would, with the details filled in, so you can read them in a real inbox.

If a step fails, Kite reads the error, fixes the template or the step, and runs the test again. Turning on a sequence sends email to real people, so Kite shows you the plan and every email first. Approve them with the button in the conversation or with a reply, and Kite turns the sequence on.

Kite judges lifecycle email by whether signups take the activation step and go on to pay, because those are the outcomes the emails exist for. Opens are unreliable in many inboxes, so Kite treats clicks on each email's call to action as the early signal and activation as the result that counts.

Once the sequence is live, Kite reads the delivery, open, click, bounce, and unsubscribe figures for each email from your email tool. It then compares the people who received each email with your activation step in Supabase or PostHog and with their subscriptions in Stripe. That shows which email moved people forward and which one they ignored. For example, Kite might find that the day-one nudge lifts activation, while the feature email two days later gets clicks but changes nothing about who activates.

When one email clearly lags, Kite rewrites it and updates the template, so later signups get the better version. It records which subject lines and angles worked in your team's knowledge base, so your next email program starts from those results. If you'd like a regular check, ask Kite to review the sequence every month, and it will report what changed.