Marketing & Growth

How to build lifecycle email flows as Small Customer Success Teams

Marketing & GrowthFor Small Customer Success Teams3 apps11 steps~22 min to set up

Your 3-person team manages 250 B2B accounts and lifecycle email is theoretically owned by marketing — except marketing built flows for trials and signups, not for the post-sale journey you actually own. So when a customer hits 60 days without logging in, nobody sends anything. When a renewal is 90 days out, you write a personal email from scratch. When a customer upgrades, the 'congrats' lands three weeks late because you spotted it manually in HubSpot. You've cobbled together sequences in Gmail, a Mailchimp list you half-maintain, and a Notion doc of 'triggers to watch for.' None of it talks to your usage data, your support history, or your renewal dates. You need a CS-ops person to fix it and you don't have one.

Build this on Starch → See the apps used

Marketing & GrowthFor Small Customer Success Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

An automated lifecycle email system that fires milestone-based messages — onboarding nudges, low-usage alerts, renewal lead-ups — based on live HubSpot deal data and usage signals, without manual list management

A health-score dashboard that surfaces which of your 250 accounts are at risk, which are primed for expansion, and which haven't been contacted in 30+ days — so you know which email to write next and why

A weekly digest that tells you what changed across your book of business this week and suggests the three follow-up actions that matter most, sent to your inbox every Monday before your team standup

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Sales Agent CRM Email Agent Growth Analyst

Data sources & config

Starch connects directly to HubSpot on a scheduled sync — contacts, companies, deals, and owners refresh automatically. Gmail is also on a scheduled sync — message history and labels feed into email draft context and thread summaries. Intercom is connected from Starch's integration catalog; the agent queries it live when a health score or email draft needs ticket data. Google Calendar is on a scheduled sync, powering the renewal-meeting gap detection. Mailchimp or ActiveCampaign, if you use them, connect from Starch's integration catalog for live queries against your existing campaign lists.

Prompts to copy

Build me a CS health-score dashboard on top of my HubSpot data. I want to see each account's deal stage, last activity date, open support tickets from Intercom, and a health score I define: red if no activity in 30 days or an open ticket older than 7 days, yellow if renewal is within 90 days and health score is below 7, green otherwise. Show expansion candidates separately — accounts in a 'Growth' stage or with MRR above $2,000 and no upsell conversation in the last 60 days.

Set up a lifecycle email automation for my CS book of business. Trigger a personalized onboarding check-in email to any HubSpot contact whose deal moved to 'Onboarding' in the last 7 days and hasn't received an email from me in 5 days. Pull their company name, deal owner, and any open Intercom tickets to personalize the draft. Queue each draft for my review before sending.

Every Monday at 8am, pull my HubSpot deal updates from the past 7 days, summarize which accounts had meaningful activity changes, flag any renewal dates within 90 days that don't have a scheduled meeting on my Google Calendar, and email me a prioritized action list with suggested subject lines for each follow-up I need to send this week.

Draft a renewal email for [account name]. Pull their HubSpot deal history, last 3 Intercom support tickets, and any Gmail threads from the past 60 days. Write a warm, specific email that references their actual usage context and opens a conversation about the next contract term.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect HubSpot via Starch's scheduled sync. This pulls your contacts, companies, deals, and deal-stage history into Starch on a recurring schedule — it becomes the spine of every lifecycle email and health-score calculation you build.

2 Connect Gmail via Starch's scheduled sync. This gives Starch full thread history per account, so when it drafts a renewal email or onboarding check-in, it's reading what you and your team actually said, not starting from a blank template.

3 Connect Google Calendar via Starch's scheduled sync. Starch uses this to detect gaps — accounts whose renewal date is within 90 days but have no meeting on the calendar — and surfaces them in your weekly digest.

4 Connect Intercom from Starch's integration catalog. When your health-score app or email-drafting automation runs, it queries Intercom live to pull open ticket count, ticket age, and most recent ticket subject for each account.

5 Start the Sales Agent CRM app and tell Starch to build your CS health-score view on top of the connected data. Describe exactly how you define red, yellow, and green, and which accounts qualify as expansion candidates. Starch builds the dashboard — you don't configure fields in a UI.

6 Build your onboarding trigger automation. Tell Starch: 'Watch for HubSpot deals that move to Onboarding stage. Seven days after the stage change, if no email has been sent from Gmail to the primary contact, draft a personalized check-in using their company name, deal owner, and any open Intercom tickets. Queue the draft for my review.' Starch wires the logic and surfaces a draft-review queue in your app.

7 Build your renewal lead-up sequence. Tell Starch to draft a sequence of three emails — first touch at 90 days out, a follow-up at 60 days if no reply, and a hard-stop flag at 30 days — pulling HubSpot renewal date, last Gmail contact, and open tickets into each draft. All drafts go to a review queue before sending.

8 Set up the Monday morning digest using the Growth Analyst app. Tell Starch: 'Every Monday at 8am, pull the past 7 days of HubSpot deal activity, identify accounts with no email contact in the past 30 days, list renewals within 90 days with no calendar meeting, and email me the top 5 follow-up actions with suggested subject lines.' This replaces the hour you currently spend manually scanning HubSpot on Monday mornings.

9 Use the Email Agent app to handle the reactive side — incoming customer emails that ask onboarding questions you've answered ten times before. Tell Starch to recognize the question pattern, pull the answer from your Notion knowledge base via Starch's integration catalog, and draft a reply for one-click sending.

10 Set a 30-day review cadence. Ask Starch: 'Show me which lifecycle emails had no reply, which accounts moved to red health score this month, and which expansion candidates still have no upsell conversation started.' Use this to tune your trigger logic — Starch lets you update the automation definition the same way you built it, in plain language.

11 Optionally, publish your health-score app configuration to Starch's shared marketplace so your team can fork it. If you've tuned the health-score formula to your specific business, it's worth saving as a reusable template.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q2 2026 renewal push — 18 accounts up for renewal in 60 days

Sample numbers from a real run

Meridian Logistics ($3,400/mo MRR)	40,800
Corten Labs ($1,800/mo MRR)	21,600
Fieldwork HR ($2,200/mo MRR)	26,400
Stackwell ($900/mo MRR)	10,800
12 additional accounts < $1,000/mo	72,000

Coming into April, your team has 18 renewals landing before June 30 — $171,600 in ARR on the table. Manually, this means scanning HubSpot for renewal dates, checking Gmail for the last time anyone emailed each account, and writing 18 individual emails over the next two weeks. With Starch, the Monday digest on April 7 surfaces all 18 accounts, flags that Meridian Logistics ($3,400/mo) has no scheduled meeting and their last support ticket — pulled live from Intercom — was a billing dispute closed 11 days ago. Starch drafts a renewal email that references the billing resolution by name and asks to schedule a call. Corten Labs, by contrast, has green health, high product engagement signals in PostHog (queried live from the integration catalog), and no upsell conversation on record — Starch flags them as an expansion candidate and drafts an upgrade conversation opener instead of a standard renewal. You spend 40 minutes reviewing and sending 18 personalized emails rather than writing them from scratch. Fieldwork HR's renewal email gets no reply within 7 days; the 60-day follow-up automation fires automatically and queues a second draft citing their onboarding completion and a new feature they haven't tried. By the time the June 30 deadline arrives, all 18 accounts have had at least two CS-initiated touchpoints that referenced real account context — and the whole thing ran on two hours of your team's attention, not twenty.

Measurement

How you'll know it's working

Renewal rate (%) across the 250-account book, tracked monthly and segmented by deal size and health score tier

Email response rate on lifecycle sequences, broken out by trigger type (onboarding, low-usage, renewal lead-up) so you know which messages actually land

Mean days since last CS-initiated contact per account — your canary metric for churn risk before it shows up in usage data

Expansion pipeline created from CS-identified upsell conversations as a percentage of total book MRR

Time-to-first-contact for new Onboarding-stage deals — the gap between a deal moving stages and a human email going out

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Gainsight or ChurnZero

Purpose-built CS platforms with deep health-score logic and playbook automation, but they start at six figures annually, require a CS-ops person to configure, and take 3-6 months to go live — not viable for a 3-person team at this account volume.

HubSpot Sequences

Native to HubSpot and solid for sales sequences, but has no awareness of support ticket history, usage data, or health scores — you'd be triggering off deal stage alone, which misses most of the context that makes a lifecycle email actually land.

Mailchimp + manual HubSpot export

Cheap and familiar, but the lifecycle logic is entirely manual — someone on your team has to pull the list, check the data, and set up the segment every time, which means it either doesn't happen or it happens wrong when you're slammed.

Customer Support Agent (Starch — coming soon)

Starch's Customer Support Agent — coming soon — will handle inbound onboarding questions automatically; today you can approximate this with the Email Agent app and a Notion knowledge base, but the dedicated support automation isn't live yet.

On Starch RECOMMENDED

One platform — sales agent crm, email agent, growth analyst all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually send emails, or does everything go to a review queue?

Your call. You can configure any automation to queue drafts for your review before sending — which is what most CS teams want for renewal and expansion emails where the context matters. For lower-stakes automations like a day-5 onboarding nudge with a templated message, you can tell Starch to send automatically. The decision is part of how you describe the automation when you build it.

We use Intercom for customer communication, not Gmail. Will lifecycle emails go out from the wrong place?

Starch uses Gmail (or Outlook) for the emails it drafts and sends on your behalf — those come from your actual work email address, not a marketing tool. Intercom data (tickets, conversation history) is pulled from Starch's integration catalog and used as context when drafting, but Starch isn't sending messages through Intercom. If you want to trigger Intercom messages as part of an automation, that's a custom flow you'd describe to Starch — Intercom is reachable from the integration catalog.

How does the health score work — can we define our own formula?

Yes, and that's the point. You tell Starch what red, yellow, and green mean for your book of business — days since last contact, open ticket age, renewal proximity, usage signals from PostHog, whatever combination matters to you. Starch builds the scoring logic based on your description. If you want to change the formula in month two, you tell it what to change, same way you built it.

What if we're not using HubSpot — our deal data lives partly in a spreadsheet?

Starch connects to Google Sheets from its integration catalog and queries it live. You can describe a lifecycle email automation that pulls from a Sheet if that's where your accounts live. It's less structured than HubSpot data — there's no schema discovery — but if your Sheet is consistent, Starch can work with it. You'd describe the column names and what each one means when building the app.

Is this going to replace what little we've already built in HubSpot Sequences?

Starch isn't a HubSpot replacement and doesn't try to be. HubSpot Sequences can keep running. What Starch adds is the layer HubSpot doesn't have: health scores that combine CRM data with support tickets and usage signals, drafts that reference real account context, and a weekly digest that surfaces the accounts your sequences missed. Think of it as the CS-ops logic layer on top of the tools you already use.

Is Starch SOC 2 certified? We're in enterprise B2B and our customers ask about this.

Not yet — Starch is not SOC 2 Type II certified. If your procurement process or customer contracts require it, that's worth knowing upfront. It's on the roadmap, but we won't tell you it exists when it doesn't.