People & HR

How to run an interview loop as CPG Founders

People & HRFor CPG Founders5 apps11 steps~22 min to set up

When you're a CPG founder with a team of four, running an interview loop means you're the recruiter, the scheduler, the note-taker, and the hiring decision-maker all at once. You're trading 'when are you free?' emails with candidates while trying to get a purchase order out to your co-packer. Interview feedback lives in a Slack thread that someone forgot to update. The person who did the second interview is at a trade show. You hire on gut feel because nobody wrote down what they actually heard. Then the new hire starts and there's no onboarding doc — just you, answering the same questions for three weeks.

Build this on Starch → See the apps used

People & HRFor CPG Founders5 apps11 steps~22 min to set up

Outcome

What you'll set up

A structured interview process with a public booking page, real-time transcription, and extracted action items — so every candidate gets a consistent experience even when you're running on two hours of sleep and a trade show floor

A searchable archive of every interview — what was said, what was decided, who gave what feedback — so your next hire doesn't start from zero

Automated follow-up emails and onboarding task lists that run without you manually triggering anything, so candidates don't ghost and new hires don't flounder

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

Scheduling Meeting Notes Knowledge Management Email Agent Task Manager

Data sources & config

Scheduling connects directly to Google Calendar (scheduled-sync provider) so availability is always live. Meeting Notes captures and transcribes calls. Knowledge Management stores candidate notes and onboarding docs; Starch connects to Notion through its integration catalog for any team docs already living there — the agent queries it live. Email Agent connects to Gmail (scheduled-sync provider) so Starch syncs your inbox and drafts candidate follow-ups automatically. Task Manager tracks onboarding milestones with due dates and overdue alerts.

Prompts to copy

Build me a scheduling page for hiring interviews with three meeting types: 30-minute recruiter screen, 45-minute hiring manager interview, and 60-minute culture fit. Add 15 minutes of buffer between all meetings and block Fridays after 3pm.

After each interview, extract the candidate's name, role they're applying for, key strengths mentioned, any concerns raised, and a recommended next step. Save each one to the candidate folder in Knowledge Management.

When a candidate books a 30-minute screen, automatically send them a confirmation email with our brand story in two sentences and a list of three things to come prepared to discuss.

Create an onboarding task list for a new ops hire at a CPG brand: FSMA traceability training by day 3, co-packer contact list review by day 5, first inventory reconciliation by day 10. Assign to me with due dates.

Search my interview notes for every candidate who mentioned experience with FBA replenishment or food manufacturing compliance.

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

Walkthrough

Step-by-step

1 Set up your Scheduling page with three meeting types (recruiter screen, hiring manager interview, culture fit), pull your Google Calendar availability in real time, and share the link in your job post or outreach email — no more back-and-forth on timing with candidates who are also juggling day jobs.

2 Before the first screen, use Knowledge Management to write a one-page job brief: what the role actually does week-to-week (think: owns the monthly distributor deduction dispute process, manages co-packer production schedule, runs weekly FBA replenishment), what good looks like, and three must-have vs nice-to-have criteria.

3 When a candidate books, Email Agent automatically sends a confirmation with context about your brand and what to prepare — so candidates show up knowing you make food, not software.

4 Run each interview with Meeting Notes capturing the transcript in real time. You stop writing and start actually listening to whether this person knows the difference between a UPC and an SSCC.

5 After each call ends, Meeting Notes generates a summary with key decisions and action items extracted automatically. You get: what impressed you, what concerned you, what to probe in the next round — in a sentence each.

6 Tell Starch: 'Save this interview summary to the candidate folder in Knowledge Management under [candidate name] / [role].' Now it's searchable. When your ops manager asks what you thought of the second candidate, you pull it up in ten seconds instead of hunting through Slack.

7 Email Agent drafts the follow-up to the candidate — either a next-round invite or a polite pass — and you review and send with one click. It also sets a reminder if the candidate hasn't responded in 48 hours.

8 After each round, pull up the Knowledge Management search and ask: 'Which candidates mentioned co-packer coordination or FSMA lot traceability?' You're cross-referencing four interviews without reading four transcripts.

9 When you make a hire, Task Manager generates the onboarding task list from your saved template: FSMA training, co-packer intro calls, first inventory audit, distributor portal access — each with an owner and a due date in the first 30 days.

10 At day 30, search Meeting Notes for any onboarding check-in calls and pull the action items that were extracted. Compare against the Task Manager list to see what's done, what's late, and what fell through the cracks before it becomes a problem.

11 Publish your hiring brief and interview scorecard to Knowledge Management so the next time you hire — whether in six months or two years — your process starts from a documented baseline, not from memory.

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 Ops Coordinator Hire — 6 candidates, 3 rounds, 4 weeks

Sample numbers from a real run

Recruiter screens completed	6
Hiring manager interviews	3
Culture fit interviews	2
Scheduling emails eliminated (estimated)	22
Interview summaries auto-extracted	11
Days from first outreach to offer letter	28

You posted for an ops coordinator in early April because your FBA replenishment spreadsheet had become a part-time job and someone needed to own it. Six candidates booked screens directly through the Scheduling page — no emails about Zoom links, no rescheduling chaos. Meeting Notes captured all six screens and three hiring manager interviews. When your co-founder asked 'which of the final two actually knows food distribution?' you searched Knowledge Management for 'distributor deductions' and surfaced the exact moment in the transcript where candidate #4 described filing a shortage dispute with UNFI. That was the tiebreaker. The new hire started May 12. Their onboarding task list — FSMA traceability overview by day 3, first weekly FBA replenishment run by day 7, co-packer call intro by day 10 — was in Task Manager before their first day. You didn't have to build it from scratch because you built the template during the hire before.

Measurement

How you'll know it's working

Time-to-offer from first screen (target: under 3 weeks for ops roles where being short-staffed has a direct cost)

Candidate drop-off rate between rounds (are slow follow-ups losing good candidates to bigger brands?)

Onboarding task completion rate at day 30 (did they actually learn your FSMA traceability process or are they still guessing?)

Interviews where written feedback was captured vs. total interviews conducted (your historical ratio is probably not flattering)

Weeks before a new ops hire is running the replenishment cycle independently

Comparison

What this replaces

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

Calendly (standalone)

Handles booking fine but does nothing with what happens in the meeting — you're back to Slack threads for feedback and Google Docs for notes the moment the call ends.

Greenhouse or Lever

Purpose-built ATS with structured scorecards and pipeline tracking, but priced for companies hiring 20+ roles a year and requiring setup time you don't have — overkill if you're making four hires annually.

Google Docs + Notion combo

Free and flexible, but feedback lives in one place, notes in another, tasks in a third, and nothing talks to anything — you're the integration layer.

Otter.ai for transcription

Good transcripts, but they stay in Otter — they don't feed your wiki, don't generate follow-up emails, and don't connect to your scheduling or task tracking.

On Starch RECOMMENDED

One platform — scheduling, meeting notes, 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

We only hire two or three people a year. Is it worth setting this up?

Each hire at a four-person CPG company has an outsized impact — one bad ops hire can set back your co-packer relationship or your FBA performance for a quarter. The setup takes a few hours. The payoff is that your third hire starts from a documented process instead of your memory of how the first two went.

Does Starch integrate with job boards like Indeed or LinkedIn so I can track applicants?

Starch doesn't replace a full ATS for applicant tracking at the top of the funnel. Where it fits is from the first screen onward: scheduling, capturing what was said, storing structured feedback, drafting follow-ups, and building the onboarding checklist. You can automate outreach to candidates through LinkedIn using Starch's LinkedIn Automation app, which runs through your browser — no separate API needed.

Can my co-founder or ops lead see the interview notes too, or is this just for me?

Knowledge Management is a team wiki, so anyone you give access to can search and read candidate notes. When your ops lead does the second-round interview, they can read what you captured in round one before they go in — instead of asking you to brief them the morning of.

What if a candidate uses a different video platform than the one I set up?

Meeting Notes works with whatever call platform you're using — the transcription captures the conversation. If you're running interviews over Zoom, Google Meet, or a plain phone call, you can still get a transcript and extracted action items.

Is Starch SOC 2 certified? We'd be storing candidate data.

Starch is not SOC 2 Type II certified today. If your company has data handling policies that require SOC 2 for any tool that touches candidate information, that's worth knowing upfront. For most early-stage CPG founders, the practical question is whether the data is more secure here than in a shared Google Drive folder or a Slack DM — and for most teams it is.

Can I build a structured scorecard so everyone rates candidates on the same criteria?

Yes. Tell Starch: 'After each interview, ask me to score the candidate on four criteria: food ops experience (1–5), distributor/retail channel knowledge (1–5), comfort with ambiguity (1–5), and communication clarity (1–5). Save the scores and a one-sentence rationale for each to their candidate folder.' Starch builds that as a repeatable post-interview flow, and the scores live in Knowledge Management alongside the transcript summary.