People & HR

How to run an employee engagement survey as CPG Founders

People & HRFor CPG Founders3 apps12 steps~24 min to set up

You run a 6-person CPG team and your only 'employee engagement survey' is a gut feeling during Monday standups. You've never sent a formal survey because the tools that do it well — Lattice, Culture Amp, 15Five — are priced for 200-person companies and require an HR admin to set up. So instead you find out someone is burned out or thinking about leaving two weeks after it would have been easy to fix. Your co-packer coordinator just quietly rage-quit during peak seasonal production. Your team is small enough that one disengaged person on a six-person crew tanks output. You need a lightweight, repeatable pulse survey process you'll actually run — not another SaaS subscription that sits unused.

Build this on Starch → See the apps used

People & HRFor CPG Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A recurring employee engagement survey sent via email on your schedule, with responses automatically collected and summarized so you see themes without reading every reply

A simple knowledge base where survey results, action items, and follow-throughs live in one place so your team sees you actually acted on their feedback

An inbox workflow that flags urgent responses (burnout signals, co-packer frustrations, workload complaints) for same-day follow-up so nothing gets buried

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 Knowledge Management Task Manager

Data sources & config

Email Agent connects to Gmail (Starch syncs your Gmail data on a schedule — read and send) to distribute survey emails and triage incoming replies. Knowledge Management connects to Notion (Starch syncs your Notion data on a schedule) so survey summaries and action-item trackers live in your existing workspace. Task Manager runs standalone to track follow-through commitments. No additional integrations required — survey responses come back to Gmail, which Starch already reads.

Prompts to copy

Draft a 5-question monthly pulse survey email for my 6-person CPG team. Questions should cover workload, co-packer coordination stress, clarity on priorities, and whether they feel heard. Keep it under 2 minutes to complete. Send to [team list] on the first Monday of each month and follow up with anyone who hasn't responded by Wednesday.

Summarize the responses I've pasted below from this month's engagement survey. Identify the top 2-3 themes, flag any responses that signal high burnout or flight risk, and draft a 3-sentence 'what we heard, what we're doing' reply I can send back to the team.

Create a Knowledge Management page called 'Team Pulse — Q2 2026' that stores this month's survey summary, the action items we committed to, and tracks whether each one got done. Alert me if any action item is still open 30 days later.

Add a task: review June engagement survey results and send team response by June 6. Priority P1.

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

Walkthrough

Step-by-step

1 Open Email Agent in Starch and describe your survey: tell it how many people are on your team, what topics matter most for a CPG operator (production stress, co-packer friction, seasonal workload spikes, priority clarity), and how often you want to run it.

2 Starch drafts a 5-question pulse survey email optimized for under 2 minutes of response time — short enough that your ops coordinator will actually fill it out between pick-pack shifts.

3 Set the send schedule (first Monday of each month is standard; weekly during peak season like Q4 or new product launches) and give Email Agent your team list.

4 Email Agent sends the survey and automatically follows up with non-responders on Wednesday — you don't have to track who replied and who didn't.

5 As responses arrive in Gmail, Email Agent triages them: it flags any reply containing language that signals frustration, overwhelm, or intent to leave, and surfaces those in your daily digest first.

6 Paste collected responses into Starch and prompt it to summarize themes — you get a paragraph on what your team is feeling, ranked by frequency and severity, not a raw dump of six different answers.

7 Open Knowledge Management and create a page for this survey cycle. Starch structures it automatically: summary at the top, verbatim quotes in a collapsible section, action items in a checklist with owners and due dates.

8 Draft your 'what we heard, what we're doing' reply using Email Agent — one prompt gets you a plain-English team update you can send within 24 hours of the survey closing, which is the single biggest driver of whether people trust the process.

9 Add each action item as a P1 or P2 task in Task Manager with a due date, so your commitment to the team is tracked the same way you track production milestones.

10 Thirty days later, Knowledge Management flags any action items still marked open — you review, update status, and the next month's survey summary links back to the previous one so you can show trend lines.

11 Before a seasonal peak (summer grilling, Q4 holiday, new retail launch), run an unscheduled pulse to catch friction early — just prompt Email Agent to send a 2-question check-in rather than the full monthly version.

12 At the end of each quarter, prompt Starch to pull the last three Knowledge Management pulse pages and write a one-page 'team health summary' you can reference in board updates or share with investors asking about retention.

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

May 2026 Pulse Survey — 6-Person CPG Team, Peak Pre-Summer

Sample numbers from a real run

Survey send	6
Responses received within 48 hours	5
Responses flagging high workload stress	3
Responses mentioning co-packer communication gaps	2
Action items committed to in team reply	4
Action items completed within 30 days	4

It's the first Monday of May and you're six weeks out from your biggest retail reset — 800 new shelf placements at a regional grocery chain. You prompt Email Agent to send the monthly pulse. Five of six team members respond within 48 hours (Email Agent followed up with the one holdout automatically). Starch summarizes the responses: the dominant theme is co-packer communication — two people on your ops side feel like they're chasing your co-man for production confirmations and not getting straight answers. One response from your demand planner reads 'I feel like I'm making up numbers without confirmed run dates' — Email Agent flags that one as high-friction and puts it at the top of your digest. You prompt Starch to draft a team reply: 'We heard workload and co-packer visibility are the two big stressors right now. Here's what we're doing: (1) weekly written confirmation protocol from co-packer starting this week, (2) production run dates locked into the shared Knowledge Management page by Wednesday of each week, (3) demand planner gets a standing 30-min sync with ops lead every Tuesday.' You send it within 24 hours of survey close. Task Manager has four P1 tasks created from those commitments, each with a due date and an owner. By the June survey, three of the four action items are done and one is in progress — when you run the next pulse, your team sees that their feedback actually changed something. Nobody quit during the pre-summer push.

Measurement

How you'll know it's working

Survey response rate (target: 80%+ within 48 hours for a 6-person team)

Time from survey close to team reply sent (target: under 24 hours)

Action item completion rate within 30 days of commitment (target: 100% for P1 items)

Repeat theme rate — how many issues flagged last month appear again this month (leading indicator of unresolved friction)

Voluntary turnover rate across seasonal peaks (quarterly; your baseline is probably 1-2 people per year on a team this size)

Comparison

What this replaces

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

Lattice or Culture Amp

Purpose-built engagement platforms with benchmarking and manager dashboards, but $8–12 per employee per month with annual contracts and setup overhead that assumes you have an HR team — not worth it at 6 people.

Google Forms + Sheets

Free and most CPG founders already use it, but you manually send it, manually chase non-responders, manually summarize results, and the action items live in a spreadsheet nobody checks — the follow-through falls apart immediately.

SurveyMonkey

Easier survey builder than Google Forms and has response tracking, but it's still a one-way data dump with no AI summarization, no inbox triage for urgent replies, and no connection to your task or knowledge management workflow.

Slack polls or informal check-ins

Zero setup cost and your team is already in Slack, but async Slack polls produce no documentation, no trend data, and no accountability loop — you have no record of what you heard or what you committed to.

On Starch RECOMMENDED

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

We're a team of 6. Is this overkill?

It's actually built for this size. At 6 people, one disengaged employee is 17% of your output, and you probably can't afford the turnover cost of a key ops hire during a production run. The whole setup takes under an hour and the recurring work is maybe 20 minutes per survey cycle. The ROI isn't in analytics — it's in catching the problem two weeks earlier than you would have otherwise.

Do survey responses get stored somewhere I can't control?

Responses come back to your Gmail, which Starch syncs on a schedule. You control what gets summarized and what gets saved to Knowledge Management. Starch is not SOC 2 Type II certified, so if you're handling sensitive HR matters that require formal compliance documentation, keep the raw response data in your own Google Drive folder and only store the anonymized summary in Starch.

Can Starch send the survey itself, or do I have to use a form tool?

Email Agent sends the survey as a plain email. Team members reply directly to that email — no separate form link, no new login. That's intentional: reply rates for plain emails are higher than form links, especially for a small team where you already communicate via email. If you want to use Google Forms or Typeform for structured response fields, Starch can automate the follow-up and summary workflow from responses you paste in, and can automate browser-based form submission for sending survey links through those tools — no API needed.

What if my team is skeptical that the survey actually does anything?

The 'what we heard, what we're doing' reply sent within 24 hours is the only thing that builds trust in the process. Starch drafts that reply for you in one prompt. The Knowledge Management page where action items live with owners and due dates gives your team a place to check whether you followed through — which most founders never have. After two cycles where they see action items get done, response rates go up on their own.

Can I customize the questions for CPG-specific stressors like co-packer friction or seasonal workload?

Yes — just tell Starch what to ask. A prompt like 'write a 5-question pulse survey for a CPG ops team that covers co-packer communication stress, seasonal workload clarity, whether people have what they need to hit the summer reset deadline, and overall sense of being heard' produces a tailored draft in under a minute. You're not locked into a generic HR template.

Will this work if we use Slack instead of email as our primary team channel?

Starch connects to Slack (available for custom apps in the integration catalog). You can build a custom automation that posts a survey prompt to a Slack channel and collects thread replies — describe what you want and Starch builds it. That said, email tends to get higher engagement for short surveys because it sits in the inbox rather than getting buried in Slack message volume.