People & HR

How to run an interview loop as DTC Brand Founders

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

You're hiring a paid social manager, a Klaviyo specialist, or a warehouse lead and your 'interview process' is three different Google Calendar invite threads, a Notion doc nobody updates, and feedback living in somebody's Slack DMs. You post on LinkedIn, candidates respond to your Gmail, you screenshot resumes into a shared folder, and half your scorecards are a voice note you forgot to transcribe. By the time you decide to hire someone, you've lost two weeks and the best candidate already took another offer. You don't have an HR team — you are the HR team — and every hire you get wrong costs you three to six months of runway.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A structured candidate pipeline that pulls every application into one place, auto-summarizes resumes, and tracks each person's status without you rebuilding a spreadsheet every time you open a new role

Scheduled interview loops with automatic booking links for each stage, confirmation emails sent from your actual Gmail address, and calendar events that populate for you and every interviewer without a single back-and-forth message

Meeting notes captured in real time for every interview, action items assigned to the right people, and a searchable archive so when you're deciding between two finalists you can pull up exactly what was said three weeks ago

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

Data sources & config

Starch connects directly to Google Calendar (scheduled-sync provider) to read your real-time availability and populate booking pages; Gmail is connected as a scheduled-sync provider so the Email Agent reads incoming applications, drafts replies, and sends from your actual address. Calendly is connected as a scheduled-sync provider for scheduling workflows. Notion is connected as a scheduled-sync provider to store and surface your evaluation rubrics and hiring docs. Any ATS you use — Greenhouse, Lever, or a tool like Rippling — can be connected from Starch's integration catalog; the agent queries it live when your pipeline app needs candidate status data.

Prompts to copy

Build me a hiring pipeline for a Klaviyo email manager role. I need three interview stages: a 20-minute intro call, a 45-minute skills call with my marketing lead, and a 30-minute culture fit with me. Create a booking page for each stage, auto-send confirmation emails from my Gmail when a candidate books, and track every candidate's current stage in a table I can filter by role.

After every interview, transcribe the recording, write a one-paragraph summary of the candidate, extract any concerns the interviewer flagged, and add a task to follow up with the candidate within 48 hours if we haven't sent a decision.

Create a shared evaluation rubric for our Klaviyo hire — scoring on: campaign strategy, segmentation experience, reporting fluency, and DTC brand fit. Save it to our knowledge base so every interviewer uses the same scorecard before the debrief call.

Triage my hiring inbox. Label every new application email, draft a reply acknowledging receipt with our expected timeline, and flag anything from candidates who applied more than 5 days ago without a response from us.

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

Walkthrough

Step-by-step

1 Connect Gmail and Google Calendar as scheduled-sync providers inside Starch — this takes about four minutes per connection and is the foundation the entire loop runs on.

2 Open the Scheduling app from the Starch App Store and tell it: 'Create three meeting types for a hiring loop — 20-minute intro, 45-minute skills interview, 30-minute culture fit. Set buffer time of 15 minutes between each. My available interview windows are Tuesday through Thursday, 10am–1pm.' Starch builds the booking pages and syncs them to your live calendar.

3 Tell the Email Agent: 'Any email with the word resume or application in the subject, or attachments that look like a CV, should be labeled Candidate Pipeline, get a draft reply acknowledging we received it and will respond within five business days, and add the sender's name to my candidate tracking table.' The agent handles this automatically as new mail arrives.

4 Share stage-specific booking links with candidates as they move through your process — you can embed these in Gmail drafts the Email Agent writes for you, so you're not copying URLs manually.

5 Before each interview, ask Starch: 'Pull the last emails from [candidate name], summarize their background in three bullets, and surface any concerns from previous interview notes.' You get a one-screen brief instead of digging through threads.

6 Run every interview call with Meeting Notes active — it transcribes in real time, generates a summary of key candidate statements and red flags after the call ends, and extracts action items like 'send the take-home brief' or 'follow up on compensation expectations.'

7 After each interview, tell Starch: 'Create a task: send [candidate name] a status update by [date two business days from today]. Mark it P1.' Task Manager tracks it with a due date and flags it overdue if you miss it.

8 Store your evaluation rubric in Knowledge Management: 'Save our Klaviyo hire scorecard — four criteria, each scored 1–5 — to the hiring section of our knowledge base. Any interviewer should be able to find it by searching their name or the role.' Every interviewer pulls the same doc instead of scoring on vibes.

9 Run a debrief by asking Starch: 'Pull all meeting notes from interviews with [candidate name] and summarize the panel's feedback into pros, cons, and open questions.' You get a structured brief for the debrief call in under a minute.

10 When you make a decision, tell the Email Agent: 'Draft an offer email to [candidate name] at [their email], referencing the Klaviyo email manager role. Include our standard start date flexibility language.' Review, edit the comp details, and send — no starting from a blank compose window.

11 Archive the completed loop: 'Save all notes, scorecards, and decisions for the Klaviyo email manager search to our knowledge base under Completed Hires — Q2 2026.' Next time you open the same role, you have a record of exactly why each finalist did or didn't get the offer.

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 Klaviyo Email Manager Hire — April to May

Sample numbers from a real run

Applications received (LinkedIn + direct email)	34
Intro calls booked via Scheduling app	18
Skills interviews completed	7
Culture fit interviews	3
Offer sent	1
Days from first application to signed offer	22

You post a Klaviyo email manager role on LinkedIn at the start of April. By day three, 34 applications hit your Gmail. The Email Agent labels every one, drafts acknowledgment replies in your voice, and flags the six candidates whose subject lines and attachments suggest real DTC experience. You run 18 intro calls by sharing a 20-minute booking link — no 'when are you free' chains, candidates pick a slot that's already blocked off in your Google Calendar. After each call, Meeting Notes gives you a 4-sentence summary and flags anyone who couldn't speak to segmentation strategy. You narrow to 7 skills interviews, each 45 minutes with your marketing lead. Before every call she asks Starch to surface prior email threads and the candidate's stated experience — she walks in with context, not a blank page. After each interview, action items land in Task Manager: follow-up emails, reference check requests, take-home briefs to send. In the debrief, you pull all seven scorecards from Knowledge Management and ask Starch to rank finalists by average score across the four rubric criteria. You extend an offer on day 22. The whole loop runs without a single spreadsheet or sticky note — and when you open the same role again in Q4, the archived notes tell you exactly what 'DTC brand fit' meant the last time you hired for it.

Measurement

How you'll know it's working

Time-to-hire per role (days from first application to signed offer)

Interview show rate — percentage of booked calls that actually happen

Candidate response lag — how many applicants waited more than 5 business days for any reply

Offer acceptance rate — how often the person you want says yes

Interviewer time per hire — total hours your team spent in calls before a decision

Comparison

What this replaces

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

Greenhouse or Lever (standalone ATS)

Purpose-built for recruiting teams with dedicated recruiters — strong pipeline views, but adds another monthly tool that doesn't connect to your Gmail, Calendar, or the rest of your ops stack without manual setup.

Notion hiring tracker + Calendly + Google Meet (cobbled stack)

Cheap and flexible, but you're still moving data between four tools by hand, nobody is drafting your follow-up emails, and your interview notes live wherever the last person pasted them.

Rippling or Gusto (HR platforms)

Great once someone is hired — payroll, benefits, onboarding — but the pre-hire interview loop is limited and the platforms aren't built around founder-run, small-team workflows where you're the recruiter, hiring manager, and decision-maker simultaneously.

Hiring a fractional recruiter

Takes the coordination off your plate entirely, but typically runs $3,000–$8,000 per search and they work in their own tools, so you end up with no institutional record of why you hired who you hired.

On Starch RECOMMENDED

One platform — scheduling, meeting notes, email agent 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 integrate with my actual ATS if I already use Greenhouse or Lever?

Yes — Greenhouse and Lever are both reachable from Starch's integration catalog, so the agent can query candidate status live when your pipeline app needs it. You don't have to abandon your existing ATS; Starch layers on top of it.

Will candidates see Starch's name anywhere — on the booking page or in confirmation emails?

The Scheduling app uses your Google Calendar availability directly. Booking pages and confirmation emails come from your own calendar and Gmail account. One honest note: Gmail's OAuth consent screen currently shows the underlying connector's name during the connection setup step, but that's a one-time setup flow you see, not something candidates encounter.

What if my interviews happen over Zoom or Google Meet — can Starch still capture notes?

Meeting Notes works with any call tool. You connect it to the meeting and it transcribes in real time. It doesn't require the video platform to have a native integration — it works from the audio and transcript directly.

We're not SOC 2 certified yet — is Starch safe to use with candidate data?

Honest answer: Starch is not SOC 2 Type II certified today. If you're in an industry where candidates' personal data is subject to strict compliance requirements, that's worth knowing upfront. For most DTC brand founders hiring their first ten to twenty employees, this isn't a blocker — but it's a real fact, not a roadmap promise.

Can I use this for hourly warehouse or fulfillment hires, not just marketing roles?

Yes — the workflow is role-agnostic. You describe the role, the stages, and the criteria to Starch in plain language and it builds to that spec. A three-stage loop for a warehouse lead looks structurally the same as one for a paid social manager; you just give it different rubric criteria and different booking window lengths.

What happens to all this data if I close the role or archive it?

Everything lives in Starch's Knowledge Management app — notes, scorecards, decisions, email threads. You tell Starch to archive the completed search to a specific folder and it's searchable from there indefinitely. When you reopen the same role six months later, you can pull exactly who you interviewed and what you decided.