copywriting

Hi {{first_name}}, Your [TRIAL_LENGTH]-day trial of [PRODUCT] is live and runs until {{trial_end_date}}. The quickest way to find out whether it fits is to put a project you're actually working on this week into it. Add the tasks, give each one an owner and a due date, and open [VIEW NAME] to see your own work laid out. **[Create your first project]** Coming from [Trello / Asana / spreadsheets]? [NEED: confirm supported imports] You can bring your tasks over here: [import link]. If you get stuck, reply to this email. It comes to me. [NAME] [Role], [PRODUCT] --- ## Email 2: Invite a teammate (Day 2) **Subject:** A project is easier to judge with a second person in it **Preview:** Assign one task and see what happens. Hi {{first_name}}, Most of what makes a project tool useful only shows up once someone else is in it: tasks with another person's name on them, comments, a due date that somebody else can see move. Invite one teammate and assign them a task from your first project. [NEED: what the invitee sees and gets notified of; one sentence.] **[Invite a teammate]** Your teammate can [NEED: confirm whether invitees need a card or account setup, and whether they count toward the trial]. [NAME] *Branch: if they've already invited someone, swap in a version that says "You've got [X] on your team. Here's what to try next" and links to Email 3's feature.* --- ## Email 3: One feature (Day 4) **Subject:** [Outcome the feature delivers, in the customer's words] **Preview:** Three steps, about [X] minutes. Hi {{first_name}}, [NEED: the single feature that best separates you from named competitors, and the problem it solves in customer language. Example shape: "If you've ever spent Monday morning chasing people for status updates, this is the feature to try."] Here's how to set it up: 1. [Step with a verb and an outcome] 2. [Step] 3. [Step] **[Open [FEATURE] in [PRODUCT]]** [NEED: optional proof line. A real customer quote or number, with permission and a name. Leave it out if you don't have one.] [NAME] --- ## Email 4: Check-in (Day 7) **Subject:** What would make this a keeper for you? **Preview:** One question, and a 15-minute call if you want one. Hi {{first_name}}, You're [X] days into your trial. I'd like to know one thing: what would [PRODUCT] need to do for you to keep using it after {{trial_end_date}}? Hit reply with a sentence or two. I read every answer, and if the answer is something we can't do, I'll tell you. If it's easier to talk it through, here's my calendar for a 15-minute call: [booking link]. [NEED: confirm someone can actually staff these calls.] [NAME] *Note: the "I'll tell you" line is intentional. It gives the sequence one honest limit, and replies from people we can't serve are cheap to handle.* --- ## Email 5: Trial ending (2 days before end) **Subject:** Your trial ends {{trial_end_day}} **Preview:** Here's what happens to your projects. Hi {{first_name}}, Your trial ends on {{trial_end_date}}. Here's what happens next: - **If you choose a plan:** everything stays as it is, including your [X] projects and [Y] tasks. {{dynamic usage count}} - **If you don't:** [NEED: exact behavior. Does the account downgrade, lock, or get deleted? How long is data kept?] Plans start at $[PRICE] per [user/month]. [NEED: billing terms, and any real guarantee, e.g. refund window. Only include it if it's written policy.] **[Choose a plan]** Need more time or want to talk pricing for your team? Reply and tell me what you need. [NEED: confirm you extend trials.] [NAME] --- ## Annotations - **Email 1 asks for a real project.** Sample data teaches nothing about fit, and a real project is what users come back to. - **Email 2 is the activation push.** Most project tools only prove their value when a second person is involved. Confirm that's true for your product. - **Email 4 is a reply-bait question.** It surfaces objections you can fix, and replies also help deliverability. - **Email 5 spells out the consequences.** Clear "what happens to my data" copy reduces anxiety more than urgency tactics do. I left out countdown and scarcity language on purpose. ## Subject line alternatives - **Email 1:** "Start with one project" / "{{first_name}}, your trial is ready" - **Email 2:** "Who else should be in this?" / "Assign your first task to someone" - **Email 4:** "Stuck on anything?" / "Quick question about your trial" - **Email 5:** "Last two days" / "Your projects after {{trial_end_date}}" ## What I need to finish this 1. **Trial details:** length, card required or not, and what happens at expiry. 2. **Audience:** who signs up (agency leads, software teams, ops?) and what they're escaping (spreadsheets, a competitor?). 3. **Differentiator:** the one thing you do that Asana, Monday, ClickUp, or Trello don't, so Email 3 passes the swap test. 4. **Activation event:** which action best predicts conversion (invites, tasks created, an integration)? Use it to reorder Emails 1 to 3. 5. **Proof:** any customer quote, number, or case study you're allowed to use. 6. **Voice:** a sample email or page you like, and who the sender should be. 7. **Behavioral triggers:** can your ESP skip or branch emails based on in-app actions? If so, I'll write the branch versions.