People & HR

How to manage benefits enrollment as DTC Brand Founders

People & HRFor DTC Brand Founders3 apps11 steps~22 min to set up

You're a 10-person DTC brand and your 'benefits enrollment' process is a folder of PDFs, a spreadsheet your ops person built two jobs ago, and a deadline email you almost missed last November. You're not running HR software — you're running Gusto or Rippling for payroll, but the actual enrollment conversations happen over Slack, the confirmation emails pile up in your inbox, and you find out someone missed their dental election when they call you in February. You lose two to three days every open enrollment window chasing confirmations, answering the same five questions about HSA limits, and manually reconciling who elected what. Nobody built this for a 10-person brand that's also in the middle of Q4 peak.

Build this on Starch → See the apps used

People & HRFor DTC Brand Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

An enrollment tracker that pulls from your payroll provider and shows, in one view, who has confirmed elections, who hasn't responded, and what each person's current coverage costs — updated automatically so you stop building this in a Google Sheet every October.

An email workflow that drafts and sends personalized enrollment reminders, answers common plan questions, and flags any employee who still hasn't confirmed with 48 hours left in the window — without you writing each message.

A task list with P1 deadlines tied to your enrollment calendar so the renewal date, carrier submission deadline, and payroll cutoff all live in one place and you get alerts before you're already late.

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

Email Agent Task Manager Knowledge Management

Data sources & config

Connect Notion via Starch's scheduled sync so your existing plan docs, carrier summaries, and HR policies sync automatically and the Knowledge Management app can search across them. Connect Gmail via Starch's scheduled sync so the Email Agent reads your inbox, threads enrollment replies, and drafts responses. Gusto and Rippling are reachable from Starch's integration catalog — the agent queries them live to pull current employee roster and enrollment status when your tracker or reminders need it. Any carrier portal without an API (most of them) is handled through browser automation — no API needed.

Prompts to copy

Draft a benefits open enrollment reminder email to my team. We're on the [carrier] health plan and the deadline is November 15. Include the HSA contribution limit for 2026, a link to the plan comparison doc in our Notion, and a one-sentence summary of what happens if they miss the deadline. Tone: direct, not corporate.

Build me a task list for our 2026 benefits renewal. Include: send enrollment kickoff email by Oct 20, confirm broker has updated plan docs by Oct 25, chase any non-responders by Nov 10, submit elections to carrier by Nov 14, confirm payroll sync by Nov 18. Set P1 on anything with a hard external deadline.

Create a knowledge base page answering the top 5 benefits questions my team asks every year: HSA vs FSA difference, how to add a dependent, what the waiting period is for new hires, how to change elections mid-year, and who to contact if there's a billing error. Pull context from the Notion pages I've already connected.

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

Walkthrough

Step-by-step

1 Connect Notion via Starch's scheduled sync. Your plan comparison docs, carrier PDFs, and any HR wiki pages you've already written will sync into the Knowledge Management app so the agent can search them when employees ask questions.

2 Connect Gmail via Starch's scheduled sync. The Email Agent will triage your inbox, thread all enrollment replies by employee name, and surface the ones still waiting on a decision so you don't lose track inside a 200-message November inbox.

3 Connect your payroll provider — Gusto or Rippling — from Starch's integration catalog. The agent queries it live to pull your current employee list, existing coverage elections, and hire dates so you know exactly who needs to act.

4 Open the Task Manager app and type your enrollment calendar as a prompt. Starch builds a P1–P4 task list with your real deadlines: kickoff email, broker doc review, non-responder chase, carrier submission, and payroll sync confirmation.

5 Use the Knowledge Management app to build your internal FAQ page. Tell Starch to pull context from your connected Notion docs and draft answers to the five questions your team asks every single year — HSA vs FSA, dependent additions, mid-year changes, new hire waiting periods, billing errors.

6 In the Email Agent, prompt Starch to draft your enrollment kickoff email. Include the deadline, a link to the plan comparison page, the 2026 HSA limit, and what happens if someone misses the window. Review it, adjust the tone, and send from your connected Gmail account.

7 Set an automation: every morning during the enrollment window, Starch checks your Gmail for unread enrollment reply threads and drafts responses to the routine questions — plan cost questions, HSA math, dependent coverage — flagging only the ones that need your actual judgment.

8 With 72 hours left in the window, prompt Starch to cross-reference your employee roster from Gusto or Rippling against confirmed replies in your Gmail threads and generate a list of who still hasn't responded. Starch drafts a personalized follow-up for each non-responder.

9 If your carrier portal requires you to log in and manually enter elections, Starch automates it through your browser — no API needed. Describe what you'd normally click through and Starch handles the data entry.

10 After submissions close, use the Knowledge Management app to update your enrollment FAQ with anything new that came up this cycle — new plan changes, updated limits, questions you hadn't seen before — so next year's process starts ahead of where this one did.

11 Task Manager marks the enrollment milestone closed and surfaces the next hard deadline: confirming the payroll sync reflects updated deductions before your first December payroll run.

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

Fall 2026 Open Enrollment — 11-person team, 3-week window

Sample numbers from a real run

Employees requiring action	11
Enrollment reminder emails drafted by Starch	3
Routine inbox questions handled without founder intervention	14
Non-responders flagged and followed up with 72hrs to deadline	4
Hours spent on enrollment vs prior year	6
Hours spent on enrollment prior year (manual)	18

It's October 22nd and you just kicked off open enrollment for your 11-person team. Last year you spent three days writing the same Slack messages over and over, manually checking who replied, and formatting a Google Sheet that immediately went stale. This year: Starch syncs your Notion plan docs and Gmail on a schedule, pulls your current roster from Gusto live, and the Email Agent drafts a personalized kickoff email in 4 minutes — HSA limit included, carrier comparison link pulled from Notion automatically. Over the next two weeks, 14 routine inbox questions about FSA rollover rules and dependent add deadlines get drafted responses without you touching them. On November 12th, Starch cross-references Gusto against your Gmail threads and surfaces four employees who still haven't confirmed. It drafts four individual follow-ups, you approve them in under five minutes, and all four respond before the deadline. Total time on enrollment this cycle: about 6 hours, spread across three weeks, compared to 18 hours last year when you were doing it manually. The carrier portal doesn't have an API, so Starch enters the final elections through your browser directly. December payroll reflects the updated deductions on the first run.

Measurement

How you'll know it's working

Enrollment completion rate by deadline (target: 100% of active employees confirmed before carrier cutoff)

Founder hours spent on benefits admin per enrollment cycle

Time from enrollment window open to all elections submitted

Payroll error rate on first post-enrollment paycheck (deduction mismatches)

Employee questions answered without founder intervention

Comparison

What this replaces

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

Gusto Benefits + manual email

Gusto tracks elections but you're still writing reminder emails yourself, chasing replies in your personal inbox, and rebuilding your FAQ from scratch every October — none of it is connected.

Rippling Benefits module

Rippling's benefits enrollment UI is solid for employees but doesn't help you manage the communication workflow, track non-responders across your inbox, or maintain a searchable internal FAQ — you're still the human glue.

A Google Sheet + Notion doc combo

Works until it doesn't — enrollment tracking in Sheets goes stale the moment someone doesn't update it, and there's no automation to chase people or draft emails when the deadline is 48 hours away.

A PEO (e.g., Justworks, TriNet)

PEOs offload compliance and carrier negotiation but cost meaningfully more at your headcount, reduce plan flexibility, and still leave you managing internal communications and team questions yourself.

On Starch RECOMMENDED

One platform — email agent, task manager, knowledge management 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

I use Gusto for payroll — does Starch actually connect to it?

Yes. Gusto is reachable from Starch's integration catalog — the agent queries it live when your apps need current employee data, roster updates, or existing coverage status. You connect it once and it's available across any app you build.

What if my carrier portal has no API? Can Starch still submit elections?

Yes — Starch automates any website you can log into through your browser, no API needed. If you normally log into your carrier portal and click through a form to enter elections, Starch can do that for you. Describe the process and it handles the navigation.

Does Starch store my employees' personal data?

Starch is not SOC 2 Type II certified today. If your team requires that level of compliance for HR data storage, that's worth knowing upfront. Data queried live from Gusto or Rippling isn't permanently stored in Starch — it's pulled when your app runs. Synced data from Gmail and Notion does live in Starch's database.

Can the Email Agent actually send emails or just draft them?

It drafts and sends. Starch syncs your Gmail on a schedule, and the Email Agent can draft replies for your review or send directly from your connected account depending on how you set it up. For enrollment, most founders review the first few, then let routine follow-ups go out automatically once they trust the drafts.

I already have plan docs in Notion. Do I have to reupload everything?

No. Starch connects directly to Notion and syncs your pages and databases on a schedule. The Knowledge Management app can search across your existing Notion content immediately after you connect it — you don't rebuild anything.

Is this worth it if I only have 8–12 employees?

Probably yes, specifically because you don't have an HR person. At 8–12 people, benefits enrollment is fully owned by the founder or a stretched ops hire. The time cost isn't smaller than at 50 people — it's just less justifiable to spend it, which is why it keeps getting done at the last minute.