People & HR

How to onboard a new hire as Chief of Staff and Founder's Office

People & HRFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

When a new hire starts at a 150-person growth-stage company, the chief of staff is the one who actually makes onboarding happen — not HR, not the hiring manager. That means chasing down Notion page access, making sure payroll got set up in Paylocity, confirming the new hire is in the right Slack channels, verifying their first two weeks of 1:1s are on the calendar, and wrangling five different people to submit their 'intro decks' by day one. None of this lives in one place. You're toggling between Notion, Slack, Google Calendar, Gmail, and whatever the office manager uses for equipment orders — and every new hire adds another round of the same 20 manual tasks.

Build this on Starch → See the apps used

People & HRFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

Outcome

What you'll set up

A single onboarding tracker app — built in natural language — that pulls from Notion (docs), Google Calendar (kickoff scheduling), Gmail (confirmation threads), and Paylocity (payroll enrollment status) so you can see every new hire's status in one place without asking anyone.

An automated Slack briefing that fires on the new hire's start date, listing their open onboarding tasks, assigned buddies, and first-week calendar events — so the hiring manager and team lead get a single message instead of five separate nudges from you.

A reusable onboarding checklist template that you describe once and Starch generates for every subsequent hire — role, team, start date as variables, no rebuilding from scratch each time.

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

Knowledge Management Scheduling Task Manager

Data sources & config

Starch syncs your Notion data on a schedule (pages, databases, users) and your Google Calendar data on a schedule (events, 12 months back, 3 months ahead). Gmail is connected as a scheduled-sync provider for confirmation threads and overdue alerts. Paylocity syncs employee and payroll enrollment data on a schedule. Slack is connected so automations can post channel messages. Any vendor portals for equipment ordering or background check status that don't have a direct API connection are automated through your browser — no API needed.

Prompts to copy

Build me an onboarding tracker app for new hires. It should pull each hire's name, role, start date, and team from a Notion database I'll connect. Show me a checklist of standard onboarding tasks (IT setup, payroll enrollment, first 1:1 scheduled, Slack channels joined, buddy assigned) with a status field I can update. Alert me by Gmail when any task is more than 2 days overdue.

Every Monday morning, check my onboarding tracker for any new hire who started in the last 14 days and still has open checklist items. Send a Slack message to the relevant hiring manager listing what's incomplete and who owns each item.

Using my Google Calendar connection, find the first open 30-minute slot in my calendar and the new hire's manager's calendar within their first three days, and create a 'Day 1 kickoff' event with both of us invited. Add a Notion page link to the event description.

Build me a knowledge base onboarding path for the 'Chief of Staff / Ops' function. It should pull relevant Notion pages tagged 'onboarding' and sequence them into a 5-day reading list. Surface any pages that haven't been updated in more than 6 months so I can flag them as stale before the new hire sees them.

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

Walkthrough

Step-by-step

1 Connect Notion, Google Calendar, Gmail, Paylocity, and Slack — all as scheduled-sync providers in Starch. This takes about 10 minutes; Starch syncs the data on its own schedule from that point forward.

2 Open Starch and describe your onboarding tracker in plain language: what fields you need per hire, what the standard task checklist looks like, and who owns each task category. Starch builds the app; you don't configure a single field manually.

3 Import your current open hires from Notion. Starch reads your hiring database and pre-populates the tracker with each person's name, role, start date, and team — no CSV export required.

4 For each hire, walk through the checklist inside the tracker and mark what's already done (IT ticket submitted, offer letter signed, etc.) so you're starting from an accurate baseline.

5 Set up the Monday morning Slack automation: describe the logic once ('check for any hire in their first 14 days with open tasks and message the hiring manager'), and Starch schedules it. Test it by running it manually on your current cohort.

6 Use the Knowledge Management app to build the onboarding reading path. Point it at your Notion workspace, tell it which pages are onboarding-relevant, and ask it to flag anything stale. This replaces the 'here are 40 Notion links' doc that no one reads.

7 Use the Scheduling app to create a 'New Hire Day 1 Kickoff' meeting type with a fixed 30-minute duration, buffer time, and a Notion template link auto-added to the description. Share the booking link with hiring managers so they can schedule their own kickoffs without coming to you.

8 For any vendor or tool that doesn't have a direct connection — background check portals, equipment order forms, office access systems — set up a browser automation in Starch to check status and report back. Describe what page to visit and what to look for; Starch handles the navigation.

9 Wire a Gmail alert: any onboarding task that passes its due date without a status update triggers a summary email to you with the hire's name, the overdue task, and the assigned owner. You forward it or not — but you're not manually tracking due dates anymore.

10 After 30 days, run a completion report from the tracker: what percentage of tasks were finished on time, which tasks are chronically late across hires, and which managers are the slowest to complete their steps. Use this data to refine the checklist rather than re-learning the same bottlenecks each quarter.

11 Publish your finalized onboarding tracker as a private app inside your Starch workspace so any ops team member can open a new hire record without asking you how the system works.

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

Jordan Chen starts as Head of Revenue Operations — May 5, 2026

Sample numbers from a real run

Notion pages flagged as stale before Jordan's start date	7
Onboarding tasks in tracker at kickoff	22
Tasks auto-assigned to hiring manager (VP Sales) via Slack	6
Tasks auto-assigned to IT via Gmail alert	4
Days until tracker showed 100% task completion	9
Minutes CoS spent manually chasing status updates	0

Jordan's offer was signed April 25. The CoS opened the Starch onboarding tracker, typed 'add new hire: Jordan Chen, Head of Revenue Operations, starting May 5, reports to VP Sales,' and the app populated a 22-task checklist from the saved template — IT setup, Paylocity enrollment, Slack channel invites, Google Calendar access, day-1 kickoff, buddy assignment, first 1:1 series, and 7 others. Starch pulled Jordan's start date into the Google Calendar automation and found the first mutual 30-minute window in the CoS's and VP Sales's calendars on May 5 at 9:30am — event created, Notion onboarding page linked in the description. The Knowledge Management app scanned all Notion pages tagged 'rev ops onboarding' and surfaced 7 that hadn't been updated since Q3 2025. The CoS spent 45 minutes refreshing those 7 pages — not hunting for which ones were stale. On May 5, the Monday Slack automation fired and sent the VP Sales a message listing 6 open tasks in their column. By May 14, all 22 tasks were complete. The CoS's involvement after initial setup: one 15-minute check-in on day 3 and forwarding one overdue-task Gmail alert to IT.

Measurement

How you'll know it's working

Time-to-productivity for new hires (days from start date to first independent deliverable)

Onboarding task completion rate by day 14 (% of checklist items closed on time)

CoS hours spent per new hire on logistics and coordination (target: under 1 hour total after setup)

Stale documentation rate at time of hire (% of onboarding Notion pages flagged as outdated)

Hiring manager task completion lag (average days between task assignment and completion, by manager)

Comparison

What this replaces

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

Notion + manual checklists

Notion is where the docs live and it should stay there — but a Notion checklist requires someone to manually open it, update it, and remember to check it; there's no automated status pull, no Slack nudges, and no cross-system visibility into whether payroll enrollment actually happened.

BambooHR or Rippling onboarding modules

Purpose-built HR onboarding tools handle the HRIS side well but can't pull in Google Calendar for kickoff scheduling, read Notion for doc readiness, or post custom Slack messages to hiring managers — so the CoS is still manually bridging the people-ops and exec-coordination halves of onboarding.

Monday.com or Asana project template

Project management tools give you a structured checklist but they're disconnected from your actual data sources — you manually update them rather than Starch pulling Paylocity status or Gmail confirmation threads automatically.

Spreadsheet + calendar reminders

Works for a company with 5 hires a year; at 150 people and 2-3 new hires per month, the spreadsheet is always a week out of date and the calendar reminders are noise because they don't tell you what's actually incomplete.

On Starch RECOMMENDED

One platform — knowledge management, scheduling, 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

Does Starch actually read our Notion workspace, or do we have to export everything?

Starch syncs your Notion pages and databases directly on a schedule — no export needed. Once you connect Notion, the agent can read page content, database properties, and user assignments. You describe what you want to pull and how to display it; Starch handles the rest.

We use Paylocity for HR. Can Starch see whether a new hire's payroll enrollment is actually complete?

Yes. Starch syncs Paylocity employee and payroll run data on a schedule, so you can build a tracker field that reflects enrollment status without logging into Paylocity and checking manually. If your specific enrollment status field isn't surfaced in the sync, Starch can also automate the Paylocity web UI through browser automation — no API needed.

We also use Rippling and BambooHR depending on the team. Can Starch connect to those?

Both Rippling and BambooHR are reachable from Starch's integration catalog of 3,000+ apps; the agent queries them live when your onboarding app needs the data. If a specific data field you need isn't available via their APIs, Starch can automate the web interface directly through browser automation.

What if I want to customize the onboarding checklist for different roles — engineering vs. sales vs. ops?

That's exactly what the natural-language authoring is for. Tell Starch: 'If the new hire's role is in engineering, add these 5 extra tasks: GitHub access, AWS credentials request, dev environment setup, on-call schedule review, and architecture doc reading.' Starch applies the logic to every new hire record from that point forward. You're not building conditional logic in a spreadsheet; you're describing the rule.

Is Starch SOC 2 Type II certified? We have a security review process for any new tool touching HR data.

Not yet — Starch is not currently SOC 2 Type II certified. If your security review requires it, that's a real constraint worth knowing upfront. It's on the roadmap, but we'd rather you hear it here than in a security review meeting.

Will the Slack automation spam the hiring manager every time it runs?

Only if there are open tasks in their column. The automation checks for incomplete items before posting — if everything is done, no message goes out. You can also configure it to post only if tasks are overdue by more than a day, so it's a signal, not noise.

We have an equipment ordering portal that has no API. Can Starch check order status for us?

Yes. Starch can automate any website you can log into through browser automation — no API needed. Describe what page to navigate to and what status field to read, and Starch handles it. This is the same mechanism it uses for any web-based vendor portal where a formal integration doesn't exist.