People & HR

How to run an interview loop as Solo Media and Creator Founders

People & HRFor Solo Media and Creator Founders4 apps11 steps~22 min to set up

You're a solo creator — newsletter, podcast, or YouTube — and occasionally you need to bring on a contractor, a part-time editor, a VA, or a podcast guest researcher. Running even a lightweight interview loop is chaos when you have no HR stack. You're copying candidate info from your Gmail into a Notion page, scheduling intro calls with three back-and-forth emails, taking notes in a Google Doc nobody will find again, and losing track of whether you sent the follow-up. The whole thing takes 4–6 hours of admin per hire that you simply don't have. There's no ATS. There's no recruiter. There's just your inbox, your calendar, and your memory.

Build this on Starch → See the apps used

People & HRFor Solo Media and Creator Founders4 apps11 steps~22 min to set up

Outcome

What you'll set up

A lightweight interview pipeline that captures candidate info from Gmail, books screening calls automatically, and tracks each candidate's status in one place — without a full ATS

AI-generated meeting notes from every interview call, with action items extracted and assigned, so you never lose a hiring decision in a forgotten Google Doc again

A task-based follow-up system that reminds you to send offer letters, rejection emails, or second-round invites so no candidate goes dark because you got busy editing an episode

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 Scheduling Meeting Notes Task Manager

Data sources & config

Starch syncs your Gmail data on a schedule to power the Email Agent's inbox triage and candidate detection. Google Calendar is connected as a scheduled-sync provider so the Scheduling app reads your real availability in real time and Meeting Notes can auto-trigger after interview calls end. Task Manager pulls candidate status from the pipeline to generate follow-up reminders. No external ATS or HR software required.

Prompts to copy

Watch my Gmail for emails with subject lines or body text that mention 'application,' 'portfolio,' 'hire,' or 'collab pitch.' When one arrives, extract the sender's name, what role they're pitching, and any links they included. Add them to a candidate list and draft a reply asking for a 20-minute intro call using my Calendly booking link.

Create three meeting types: '20-min Contractor Intro,' '45-min Working Session,' and 'Async Check-in.' Block 10 minutes of buffer after every interview. Share the booking link in my email signature and in my standard candidate outreach template.

After every call tagged 'interview' or 'contractor intro' in my calendar, generate a summary with: who we talked to, what role they'd fill, their relevant experience, any red flags I mentioned, and a hire/no-hire recommendation placeholder I can fill in.

When I mark a candidate as 'move forward,' create a P1 task: send offer email within 48 hours. When I mark a candidate as 'no,' create a P2 task: send a polite rejection within 5 days. Alert me if either task goes overdue.

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

Walkthrough

Step-by-step

1 Connect Gmail as a scheduled-sync provider in Starch. The Email Agent starts watching your inbox for inbound applications, cold pitches from freelancers, and any email that looks like a hiring inquiry — you describe the filter in plain language.

2 Tell the Email Agent what a candidate email looks like for your business: 'flag any email from someone pitching to be an editor, video producer, researcher, or VA, and extract their name, role pitch, and any portfolio links.'

3 Set up the Scheduling app with your three interview meeting types. Set your weekly availability (for example, Tuesday and Thursday afternoons only), add buffer time, and copy your booking link into a saved Gmail draft you can paste into any outreach reply.

4 Tell the Email Agent to draft a reply to each flagged candidate that includes your booking link and a one-line summary of what you're hiring for — you review and send with one click, cutting the scheduling back-and-forth entirely.

5 Enable Meeting Notes to auto-trigger on any calendar event with 'interview,' 'intro call,' or 'contractor' in the title. From this point forward, every interview is automatically transcribed and summarized.

6 After each interview, open the Meeting Notes summary and fill in the hire/no-hire field — one word. The note is archived in a searchable history so you can compare candidates weeks later without trying to remember who was who.

7 Tell the Task Manager: 'When I mark a candidate as move-forward in my notes, create a P1 task to send an offer or contract email within 48 hours. When I mark a candidate as no, create a P2 task to send a rejection within 5 days.'

8 At the start of each week, check your Task Manager candidate follow-up list. Any overdue task surfaces automatically — you'll know if you accidentally ghosted someone before they post about it.

9 For any candidate who books via your scheduling link, tell the Email Agent to auto-send a confirmation email with a short prep note ('We'll talk for 20 minutes about your editing background and what you'd charge per episode') so the call starts faster.

10 After you make a hire, tell Starch: 'Archive all tasks and notes for this candidate pipeline and create a P2 task to set up an onboarding Notion page within one week.' The Knowledge Management app can hold your onboarding doc so the next hire doesn't require you to explain everything from scratch again.

11 At the end of any hiring cycle, ask Starch to summarize: 'How many candidates came through Gmail in the last 60 days, how many booked a call, and how many did I move forward?' You now have a rough funnel number for future reference — useful if you're hiring for the same role again.

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

April 2026 Part-Time Video Editor Search

Sample numbers from a real run

Inbound applications via Gmail (3-week window)	14
Candidates who booked a 20-min intro via Scheduling link	7
Interviews where Meeting Notes auto-triggered	7
Follow-up tasks created in Task Manager	7
Offers sent within 48-hour P1 deadline	1
Estimated admin hours saved vs. manual process	9

In mid-April you put out a two-sentence post on LinkedIn and X that you were looking for a part-time video editor. Over the next three weeks, 14 people emailed you — some with portfolios, some with just a line of text. Previously, all 14 would have sat in your inbox until you had a free afternoon that never came. With the Email Agent watching Gmail on a schedule, each inbound was flagged, the sender's name and pitch were extracted, and a draft reply with your Scheduling link was waiting for you to approve. Seven people booked the 20-minute intro slot. Meeting Notes triggered on each call, transcribed the conversation, and spit out a four-sentence summary with the candidate's rate, relevant credits, and any concerns you mentioned aloud. You compared all seven summaries in 15 minutes — something that would have required hunting through seven different Google Docs before. You marked two candidates 'move forward' and five 'no.' Task Manager created two P1 tasks (send offer within 48 hours) and five P2 tasks (send rejection within 5 days). You hired one editor, sent all five rejections before the deadline, and spent roughly 3 hours total on admin instead of the 12 you'd burned on your last freelance hire.

Measurement

How you'll know it's working

Application-to-call rate: how many inbound emails convert to a booked interview (tells you if your outreach reply and scheduling link are working)

Time-to-follow-up: average days between interview and offer or rejection sent (your candidates notice this — it affects whether good ones wait for you)

Admin hours per hire: total time spent on email, scheduling, and notes per hired contractor (target: under 4 hours for a simple freelance hire)

Overdue follow-up tasks: number of candidate tasks that blew past their due date (should be zero — ghosting candidates is a reputational risk for a public-facing creator brand)

Candidate pipeline volume: how many applications arrive per hiring cycle, so you can plan search windows around your content schedule

Comparison

What this replaces

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

Notion + Google Calendar + Gmail manually

Free and flexible, but you're the integration layer — copying data between tools, remembering to follow up, and losing notes in unfiled docs is exactly the problem Starch solves.

Greenhouse or Lever (ATS)

Built for teams running dozens of requisitions simultaneously — overkill and expensive for a 1-person media business that hires a contractor once or twice a year.

Calendly alone

Solves the scheduling back-and-forth but does nothing for inbox triage, note-taking, or follow-up tracking — you still need four other tools to run the full loop.

Google Forms + Airtable

Works if every candidate fills out your form, but most freelancers just email you directly — you'd still be manually transferring half your applications.

On Starch RECOMMENDED

One platform — email agent, scheduling, meeting notes 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 only hire a contractor once or twice a year. Is this worth setting up?

Yes, because the setup is a one-time description — you tell Starch what a candidate email looks like, what meeting types you need, and what follow-up tasks to create, and it stays configured. The next time you hire, the whole pipeline is already running. The first hire might take 2 hours to configure; every hire after that is just reviewing what Starch surfaces.

Will this work if candidates email me from LinkedIn DMs or Instagram, not Gmail?

The Email Agent runs on Gmail (or Outlook), so it catches candidates who email you directly. For DMs on LinkedIn or Instagram, those come through your browser — Starch can automate checking LinkedIn messages through browser automation with no API needed, but you'd describe that as a separate automation. For Instagram DMs, the same browser-based approach applies.

Does Starch store my candidates' personal data, and is it SOC 2 certified?

Starch is not SOC 2 Type II certified yet — that's an honest limit worth knowing if you're handling sensitive information. For most creator-business hiring (freelance editors, VAs, researchers), you're not processing medical or financial data, so this is unlikely to be a blocker. But if it matters to you, that's the current status.

Can Meeting Notes join a Riverside or Zoom interview call automatically?

Meeting Notes transcribes calls that appear in your Google Calendar. If your interview is a Zoom or Google Meet link attached to a calendar event — which it will be if the candidate booked through your Scheduling app — Meeting Notes will trigger on it. Riverside is a recording platform; if you export the transcript from Riverside, you can ask Starch to summarize it, but it doesn't join Riverside sessions natively.

What if I want to build a slightly different version — like tracking guest pitches for my podcast instead of contractor hires?

That's exactly what Starch is built for. Just describe it differently: 'Watch my Gmail for podcast guest pitches. Extract the sender's name, their suggested topic, and their audience size if they mention it. Draft a reply with my guest booking link and add them to a guest tracker.' The underlying apps are the same; the natural-language prompt is what makes it your pipeline instead of a generic one.