Onboarding that runs itself.

Every new hire gets a first week that fits their role, team, and location. No lists to upload. No spreadsheet of start dates. Nobody has to remember.

Why onboarding breaks

New starters get a good first day and then silence. The week-one check, the 30-day handbook nudge, the 90-day conversation, and the six-month review all depend on someone in HR remembering each person's start date. So they happen late, unevenly, or not at all, and nobody can say who missed out.

The trouble is the number of pieces. A typical onboarding involves HR, IT, a hiring manager, a buddy, and facilities, often working across different tools, inboxes, and calendars. Messages need to go out in the right order. Access needs to be ready before day one.

Then the exceptions show up. A start date changes. IT never saw the access request. A manager is traveling that week. Each one needs someone in HR to notice, figure out what's broken, and step in.

“We have to chase IT for laptop setup, managers for intros, HR for paperwork. It’s a mess.”

The manager is where it slips

HR can explain the company. Only the manager can explain the work: what success looks like in this role, how decisions get made, which projects matter most. That is the part of onboarding that decides whether a new hire settles in, and most programs leave it to memory.

Managers don't miss onboarding steps because they don't care. They miss them because onboarding competes with the work they are measured on, and nobody has told them which moments are theirs. So HR becomes the reminder system. Managers feel pestered, and HR feels responsible for work it can't own.

We've written about both halves of that: why onboarding is a manager's job and how to improve manager participation.

Most of what makes onboarding feel broken is the small things that slipped: the laptop that didn't arrive, the second week when nobody reached out. Remembering is the part you can hand over.

How Pyn runs it on the HRIS you already have

Pyn connects to your HRIS, so it already knows the moment someone starts. There is no list to upload and no one to remind. You set onboarding up once, and every step runs off each person's own start date.

Connect Greenhouse or Ashby and the journey can start the moment an offer is signed, long before day one.

What a new hire gets, and when

Here is a first six months to start from, with a page from our library for each step. Change the days, the words, and the sender to fit your company.

Before day one
The new hire hears what their first day will look like: Your first day is approaching fast. Their manager gets what to do before the new hire arrives and picks a buddy.
Day one
A welcome in Slack or email, sent in a real colleague's name. For example: Welcome from CEO.
Week one
What to expect and do in your first week, then one question at the end of it: how was your first week?
Day 30, 60, and 90
The manager and the new hire review the plan together: How to create a 30/60/90 day plan for your new hire.
Month six
A check-in the manager doesn't have to write from scratch: six questions to ask your new hire after six months.

Sent by a person, where people already work

Messages arrive as a Slack DM, in Microsoft Teams, or by email. They come from a real person in HR, from the new hire's manager, or from an alias such as "the People Team", not as a system notification. Sure, you could send onboarding from noreply@. Or from your CEO.

“If an employee responds to an automated message, the conversation continues with the team member we set as the sender, making Pyn invisible to employees (which was a huge selling point).”

A G2 reviewer

Different for every role, the same setup for you

Content varies by role, department, and location. An engineer in Sydney and a marketer in New York get different onboarding from the same automation.

New starters are added to the calendar invites you already have, which keeps cohorts and orientation classes easy to manage.

Followed up until it's done

Put a button on a message and Pyn reminds, escalates to the manager, and stops the moment the person acts. You see who has read what and who hasn't acted, so you can stop sending chasing emails.

On the stack you have

No rip-and-replace. Pyn reads your HRIS and acts where people already work. It works with BambooHR, HiBob, Rippling, Workday, Greenhouse, and Ashby, in Slack, Microsoft Teams, or email. See every integration.

The manager and the buddy get their part too

Most onboarding tools talk to the new hire. In Pyn, one step can reach the new starter, their manager, and their buddy, each with their own part.

The split is simple. HR brings structure, timing, and consistency across the company. Managers bring context, expectations, and day-to-day guidance. Pyn sends managers the nudge, the context, and the words at the moment they need them. The words are already written:

A buddy for every new hire, without the spreadsheet

The manager picks a buddy inside Slack. Pyn warns them if that person was picked recently, so the load spreads fairly, and tells the buddy what they've been chosen for. No spreadsheet required.

There is more on running one in Onboarding Buddy and in how to build an onboarding buddy program.

What Pyn doesn't do

Pyn doesn't do the welcome itself. A chatbot can't replace a warm welcome from a real manager, or what a buddy tells you about how the company really works. Pyn makes sure both of them show up.

Vibe-code the part nobody sells

Every company's onboarding has a part no vendor sells. The first week is a ritual, and rituals change shape as the company grows.

Your People team can now build that part itself. Open Claude, describe the thing, and have a working version before lunch. The question stops being whether you can build it. Now it's whether you should. Our rule: vibe-code the rituals, buy the systems of record.

The whole argument is in Vibe coding for HR: a field guide. For a straight answer on one tool, take the ten questions in Should you vibe-code that HR tool?

You build it. We hold the plumbing.

The hard part comes after the demo works: where the tool runs, who can log in, and who sees what. Tools you host on Pyn inherit org chart permissions, managed HR integrations, admin controls, and an audit trail. They use the same employee data, roles, workflows, and messaging that run your onboarding, from your HRIS to Slack, Microsoft Teams, and email.

Your code stays yours. Open a hosted app in Claude or Codex, make a change, and publish the update when you're ready. Hosting for vibe-coded HR tools is in early access.

Don't build payroll, contracts, or anything a real decision hangs off. Buy those.

Ask Claude who starts next week

People teams already ask AI assistants for help. Usually that means pasting an export into a chat.

With Pyn, an admin gives Claude, ChatGPT, or Cursor a permission-scoped way into your workspace. The assistant then answers "who starts next week?" from live data, or works through an onboarding checklist, as the person who asked.

Every call runs with that person's own permissions. Your AI assistant only sees what you could already see, and nobody shares a master key.

Give the agent a job description

An agent needs what a new team member needs: a clear scope and a playbook. What it can access. What it must not do. When to hand over to a human. For an onboarding agent, the role can be two sentences:

“You are an Onboarding Assistant. Your job is to help new hires feel supported, not to answer legal questions.”

From there it is a short step to a headless process: an HR process an AI agent runs end to end through Pyn, with no screen, under the permissions of the person who asked. Enrolling a new starter from Claude, for example. The platform page has the rest.

AI can flag that a manager hasn't checked in. It can't tell you whether that manager needs a reminder, a conversation, or something else. That call stays with you. If you're evaluating AI tools, start with 12 questions to ask AI vendors.

Measure the moments, not the annual survey

Most companies run an annual engagement survey, often paired with an onboarding survey. Each captures one moment in time. Onboarding unfolds over months, so measure it step by step.

Coverage
Are you showing up when it counts? Coverage is the share of important moments that are actively supported. For onboarding: did every new hire get every step, in every team and location?
Follow-through
Did the people around the new hire do their part? Was a buddy picked? Did the manager do the prep? Pyn shows who was asked to do what, and who hasn't yet.
Sentiment
Ask at the moment, not at year end. Do new hires feel confident, connected, and ready to contribute? One question at the end of week one is enough to start.

Coverage tells you whether support was delivered. Sentiment tells you how it landed. Together they show where to act. The method is set out in Key success metrics for employee enablement and experience.

Then count the hours you get back

In one year Carta sent more than 3,000 pre-boarding and onboarding messages to new hires. At about five minutes a message by hand, that gave one program manager 271 hours back. Read the Carta case study.

“Pyn saved us 700 hrs in manual tasks”

Mary Newville, Director of People Experience at Arctic Wolf

To run your own numbers, use the Pyn ROI Calculator.

Start with the onboarding you already run

Keep the onboarding program you have. These four steps take the remembering out of it.

  1. Connect your HRIS.It stays the system of record, and new hires never need a Pyn account.
  2. Bring what you already send.Put your existing welcome content on the right day, as Koala did, or start from the onboarding pages in our library.
  3. Check the first few by hand.Preview each message as the new hire, their manager, and their buddy. Keep a person on the first few starters until you're happy with it.
  4. Add the next moment.Once onboarding runs itself, the same setup covers promotions, new managers, leave returns, and anniversaries. See every solution.

Comparing tools? Read the buyer's guide to modern onboarding platforms, or see Pyn next to other onboarding tools.

Book a demo. Bring your HRIS and your current onboarding program. We rebuild it on Pyn during the call.

FAQ

Do new hires need a Pyn account?
No. They get every message in Slack, Microsoft Teams, or email, from a colleague they know. There is nothing to log into.
Which HR systems does Pyn work with?
Pyn reads the HRIS you already have, including BambooHR, HiBob, Rippling, and Workday, and delivers in Slack, Microsoft Teams, or email. The integrations page has the full list.
Can onboarding start before day one?
Yes. With Greenhouse or Ashby connected, the journey can start the moment an offer is signed, long before day one.
What happens when a start date moves?
Pyn re-reads your HRIS every hour, or instantly where the system sends webhooks, and reschedules every step off the new date.
We already have an onboarding tool. Do we have to replace it?
No. Pyn works alongside existing systems. Start with the moments after onboarding, such as promotions and anniversaries, while you plan the move.
How long does it take to set up?
Most teams recreate their core workflows in Pyn within two weeks. We provide migration templates and hands-on support.

Your HR stack, with superpowers.

Pick the tools you need. Launch in a day. Cancel anytime.