fix(email): shorten the day-7 founder note to one question

Merged
KI
13h ago
+9-13

What & why

The day-7 founder note (activation drip, sent to people who signed up but never started a workspace) ran about 90 words, asked five questions and promised a fix "this week". Cold-email reply data (Lavender) favors 25 to 50 words and one easy question.

New copy, 40 words:

Hey {name},

I'm Kiet, one of the founders of Paradev. Looks like you signed up last week but haven't started a workspace yet.

Did something break? Even one word helps: download, setup, trust, or busy.

Kiet

The preview text now shows the first sentence instead of "quick question from a Paradev founder".

After merge: Resend sends the published template activation-02-founder-note, so it must be re-published for this to reach users. The subject also lives there; proposed: "Paradev setup".

How I tested it

  • Rendered the component to plain text with @react-email/components render and checked the output above.
  • bun run typecheck and bun test in packages/email pass; biome check clean.

Checklist

  • PR title follows conventional commits (type(scope): subject)
  • bun run lint and bun run typecheck pass (CI fails on lint warnings too)
  • "Allow edits from maintainers" is checked on fork PRs
  • I have signed the CLA (the bot asks on your first PR)

Summary by cubic

Shortens the day-7 founder note sent to users who signed up but never started a workspace, cutting it from about 90 words with five questions to 40 words with one easy question, per cold-email reply data. The preview text now shows the first sentence.

After merge, the email needs to be re-published in Resend to reach users. Propose updating the subject there to "Paradev setup".

Summary by CodeRabbit

  • Content Updates
    • Updated the activation email to say the recipient signed up last week but hasn’t started a workspace. The greeting and founder’s note now use more conversational wording.
    • Replaced the longer explanation with a brief question about whether something went wrong, offering download, setup, trust, and being busy as possible reasons to reply.