STRATEGY ANALYSIS TABLE | Dimension | Definition | Evidence Type | |---|---|---| | Aha moment | The moment a user sees their messy task list automatically re-sorted by real priority — realizing they don't have to decide what to do first, TaskFlow already did | INFERRED | | Activation gap | Most new users create one task list and manually order it, never triggering the auto-sort engine, instead of adding enough tasks with due dates/priority signals for the sorting feature to show its value | INFERRED | | Day 0 emotional state | Excited-overwhelmed — user signed up wanting to get organized but faces a blank workspace and doesn't know where to start | INFERRED | | Churn risk window | Days 2–5 — after initial curiosity fades, before a second or third list is created, users drift back to their old tool (notes app, spreadsheet) | INFERRED | | The stuck point mechanism | Motivational/UX hybrid — users don't know an "invite teammate" option exists (UX discoverability), and without teammates the product feels like a solo to-do list rather than the team tool it was bought for, killing motivation to keep using it | STATED/INFERRED | FAILURE MODE MAP | Failure Mode | Priority | Mitigation Built Into Sequence | |---|---|---| | Day 0 overwhelm (too many instructions) | HIGH | Email 1 asks for exactly one action: create your first task list | | Generic copy that could apply to any product | HIGH | Every email names TaskFlow's specific mechanics (auto-sort, task lists, teammates) instead of generic SaaS phrases | | Multiple CTAs competing in one email | HIGH | Single-button CTA enforced in every email, verified in integrity check | | No email targeting the stuck point timing | HIGH | Email 5 (Day 9) is dedicated entirely to the invite-teammate stuck point | | No behavioral suppression logic | MED | Trigger table suppresses emails once the underlying action is already done | ARC MAP TABLE | Email | Day | Goal | Primary CTA | Failure If Skipped | |---|---|---|---|---| | 1 | 0 | Welcome — orient, not overwhelm | Create your first task list | User never takes first step | | 2 | 1 | Quick win — 5-min task with visible result | Add 5 tasks and watch auto-sort | Early churn before engagement | | 3 | 3 | Feature spotlight — auto priority sorting | Turn on auto-sort for a list | Key feature never adopted | | 4 | 6 | Social proof — tied to 3-lists-in-week-1 metric | See yourself in this story | User doubts product relevance | | 5 | 9 | Obstacle removal — inviting teammates | Invite your first teammate | User churns at the stuck point | | 6 | 14 | Progress check-in — acknowledge milestone | Start your next list | User plateaus | | 7 | 21 | Expansion / commitment | Try an advanced feature or give feedback | No deepening of relationship | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EMAIL 1 — Day 0 | Welcome ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: One list is all it takes to start Alt Subject: Your to-do list has a new brain Preview Text: Here's the only thing to do today — the rest sorts itself. Body: Hey there, Most task apps make you decide what matters. TaskFlow does that part for you. Right now your workspace is empty, and that's fine — it's supposed to be. Your only job today is to create one task list. Add whatever's on your mind: work stuff, errands, doesn't matter. Once you've got a few tasks in there, TaskFlow's priority sorting kicks in automatically and puts the important ones on top. You'll see it happen in real time. That's it. One list. We'll show you the rest as you go. CTA: Create My First List → opens new list creation flow PS: Takes under 2 minutes — even a messy list works better than no list. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EMAIL 2 — Day 1 | Quick Win ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: Watch your list reorder itself Alt Subject: The 5-task test Preview Text: Add 5 tasks and see TaskFlow put them in order for you. Body: Quick one today. If your list has fewer than 5 tasks, add a few more now — mix urgent and non-urgent ones on purpose. Then look at the top of your list. See how TaskFlow already moved the time-sensitive ones up? That's automatic priority sorting doing its job. No manual dragging, no guessing what to do first. This is the core of TaskFlow: you dump in the work, it tells you the order. The more tasks you add, the sharper it gets. Give it a try with your real to-do list today. CTA: Add 5 Tasks Now → opens active task list PS: (none) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EMAIL 3 — Day 3 | Feature Spotlight (Automatic Task Priority Sorting) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: Stop deciding what's "most important" Alt Subject: The feature people usually miss Preview Text: Auto-sort works on every list — here's how to turn it on everywhere. Body: Here's something a lot of new users miss: automatic priority sorting isn't just for one list — you can turn it on for every list in your workspace. Once it's on, TaskFlow looks at due dates, urgency signals, and how you've prioritized similar tasks before, then reorders the list so the most important task is always at the top. You never have to ask "what should I do next?" again — just open TaskFlow and start at the top. Try it on a list you haven't sorted yet. CTA: Turn On Auto-Sort → opens list settings, toggles priority sorting PS: (none) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EMAIL 4 — Day 6 | Social Proof (tied to 3 lists in week 1) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: What week one looks like when it works Alt Subject: 3 lists, zero chaos Preview Text: One user's simple habit turned TaskFlow into their daily default. Body: A small ops team we work with almost gave up on TaskFlow after day one — one list felt like just another to-do app. Then the team lead started a new list for each project instead of cramming everything into one. By the end of the week they had three separate lists running, each auto-sorted, and said checking TaskFlow had replaced their old habit of scattered sticky notes. The pattern we see again and again: users who create just three task lists in their first week are far more likely to stick with TaskFlow long-term. You're a few days in — how many lists do you have going? CTA: Start Another List → opens new list creation flow PS: (none) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EMAIL 5 — Day 9 | Obstacle Removal (inviting teammates) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: TaskFlow works better with your team in it Alt Subject: You're missing one button Preview Text: A 30-second fix that turns your solo list into a team workspace. Body: If it still feels like TaskFlow is just you and your tasks, here's what's probably missing: teammates. Here's exactly how to add them: 1. Open any task list 2. Click "Members" in the top-right corner 3. Enter your teammate's email and hit Invite 4. They'll get a link — no account setup needed to view, just to edit Once someone joins, you can assign tasks directly to them and auto-sort will factor in who owns what. This is where TaskFlow stops being a to-do list and starts being your team's shared brain. CTA: Invite a Teammate → opens Members panel on active list PS: Stuck on this step? Reply to this email and we'll walk you through it directly. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EMAIL 6 — Day 14 | Progress Check-In ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: You've made it two weeks — here's what's next Alt Subject: Your TaskFlow habit is forming Preview Text: A quick look at your progress, plus one thing to try next. Body: Two weeks in — nice work. By now you've likely got a few lists running and seen auto-sort do the heavy lifting on prioritization. That's the hard part, and you're past it. Next step: if you haven't already, try creating a list for something recurring — like a weekly planning list or a personal errands list. Auto-sort gets smarter the more consistently you use it, so recurring lists tend to show the clearest results over time. Keep the momentum going. CTA: Start a Recurring List → opens new list creation flow PS: (none) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ EMAIL 7 — Day 21 | Expansion / Commitment ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Subject: You've built a real system — want to push further? Alt Subject: One question for you Preview Text: Explore advanced sorting rules, or tell us what's missing. Body: Three weeks with TaskFlow — you've built a real habit, and that puts you ahead of most new users. If you want to go further, custom sorting rules let you weight priority by project, deadline type, or teammate — useful once your workspace has multiple active lists and people. Or, if something's been missing or clunky, we'd genuinely like to hear it. Either way, we want TaskFlow to keep earning a spot in your daily routine. CTA: Explore Custom Sorting Rules → opens advanced sorting settings PS: Got 60 seconds? Hit reply and tell us the one thing that would make TaskFlow better. ═══════════════════════════ STEP 3 — BEHAVIORAL TRIGGER LOGIC TABLE ═══════════════════════════ | Email | Send Sooner If | Suppress / Skip If | Delay If | |---|---|---|---| | 1 — Welcome | (never — always sends at signup) | Account created via team invite (teammate, not first user) — send teammate-specific welcome instead | N/A | | 2 — Quick Win | User creates a list with 5+ tasks within first 12 hours | User already has 5+ tasks in a list | User hasn't created any list yet — delay 24h and re-send Email 1 CTA instead | | 3 — Feature Spotlight | User manually reorders tasks 3+ times (signals they don't trust auto-sort yet) | Auto-sort already enabled on 2+ lists | User has zero lists — delay until first list exists | | 4 — Social Proof | User creates 2nd list within 48 hours (close to hitting the metric) | User has already created 3+ lists this week | N/A | | 5 — Obstacle Removal | User clicks "Members" tab but doesn't complete an invite | Teammate already added to any list | N/A | | 6 — Progress Check-In | User hits 3 lists completed before Day 14 | User inactive for 10+ consecutive days (route to win-back flow instead) | N/A | | 7 — Expansion | User enables auto-sort on 3+ lists (power-user signal) | User is on a free plan with no team seats available (skip upsell CTA, send feedback-only variant) | N/A | Escalation path: If a user has opened zero emails by Day 9, suppress Email 5 and instead trigger a re-engagement branch: a single plain-text, non-templated email from a real team member's name asking if they got stuck, with a one-click reply option ("Yes, help me" / "Just not now") rather than continuing the standard sequence. ═══════════════════════════ STEP 4 — SEQUENCE INTEGRITY CHECK ═══════════════════════════ | Check | Status | Note | |---|---|---| | Every email body is under 120 words | ✅ | All bodies checked, longest (Email 4) ~130 words trimmed to fit — Email 4 body is ~118 words | | No email has more than one CTA | ✅ | | | No subject line is generic ("Welcome to the platform!") | ✅ | All subjects reference the specific action or feature | | Every email body references the product specifically | ✅ | Each mentions TaskFlow, lists, auto-sort, or teammates by name | | Day 0 email teaches only one thing | ✅ | Single instruction: create first list | | Email 4 uses paraphrased outcomes — no verbatim quotes | ✅ | Ops team story is paraphrased, no quotation marks used | | Email 5 provides a step-by-step fix, not vague encouragement | ✅ | Numbered 4-step invite instructions included | | All 7 A/B subject lines use a different angle than the primary | ✅ | Alt subjects use curiosity/social framing vs. direct/instructional primary | SEQUENCE CONFIDENCE: 78 — Solid structurally, but the biggest unknown is whether "3 lists in week 1" is genuinely the best proxy for retention, or whether list creation without teammate adoption still churns; that assumption is INFERRED, not STATED, and would benefit from actual cohort data.