Skip to content

Onboard a new customer the day they sign.

The moment a customer signs, Patricia spins up the channel and folders, works the onboarding checklist, chases the access and info you need, drafts the welcome email, and books the kickoff, everything customer-facing after your yes. Week one feels sharp and organised instead of a scramble to remember the steps.

What signing a new customer looks like in #ops, without anyone remembering the checklist:

#opsThreadProduct preview
PatriciaAppJust now

🎉 Orbit signed. Onboarding kicked off, here's where it stands:

  • Created the Orbit project, channel and Drive folder from the template
  • Welcome email and access requests drafted, waiting on your yes
  • Kickoff proposed for Thursday, waiting on their team to confirm
Pulled fromAsana
Ricardo GhekiereJust now

@Pati send the welcome email, assign the checklist to Iris and chase the access.

PatriciaAppJust now

Done. Welcome email sent, the onboarding checklist is assigned to Iris with due dates, and the access request is with the Orbit contact with exactly what we need and how to share it. I'll chase anything still open on Monday and confirm the kickoff once they pick a time.

Pulled fromGoogle Drive

How small teams do this today.

A new customer is the best moment to look sharp, and it is usually the most chaotic week a small team has.

The checklist in someone's head

Onboarding depends on one person remembering the fifteen steps, so a different one gets skipped every time.

The week-one info chase

Access, account details and the info you need to set them up get chased one email at a time, and the first real value slips a week.

The messy first impression

The customer's first experience is a disorganised kickoff and three separate requests for the same things they already sent.

What it looks like when she owns it.

Onboarding task in Patricia: an event-based task that runs on signing, sets up the workspace and folders, works the checklist, chases access, and books the kickoff, with recent runs listed
The moment the contract is signed, she runs the onboarding: workspace and folders set up, checklist assigned, access chased, kickoff booked.
Integrations in Patricia with Asana, Google Drive and Slack connected, so she can run the checklist, set up folders, and gather what the onboarding needs
Connect the checklist and where files live. She spins up the project and folders and works the onboarding steps from Asana.

Setup

Running in minutes, then it's hers.

Step 1

Add Patricia to Slack

She joins your workspace like any teammate. Two minutes, no engineering.

Step 2

Connect Asana and Drive

So she can run your onboarding checklist and spin up the project, channel and folders from your template.

Step 3

Build the template once

Your standard onboarding steps, the access and info you always need, and the folder structure. She reuses it for every new customer.

Step 4

She runs it on signing

Workspace set up, checklist assigned, access and info chased, welcome email sent after your yes, kickoff booked, so week one is organised from the first hour.

What she takes off your plate.

Real behavior of the skill, not a feature list.

Sets up the workspace instantly

Project, channel and Drive folders created from your template the moment a customer signs, so there is nothing to build by hand.

Works the checklist for you

Your standard onboarding steps assigned with owners and due dates, so the same one never gets skipped because it lived in someone's head.

Chases access and info

Access, files and the details you need to set them up, requested from the customer with exactly what is needed and how to share it, then chased until they land.

Sends the welcome email

Drafted in your voice with the next steps and what you need from their side, posted for your yes before anything goes out.

Books the kickoff

She proposes times, confirms with the customer, and puts the kickoff on the calendar, so week one starts with a real meeting.

One clean first impression

The customer sends things once and meets an organised team, so the relationship starts the way you want it to continue.

Reuses your playbook

Every onboarding runs off the same template, so the fifth customer this quarter is as sharp as the first.

Things to ask her on day one.

@Pati

Onboard Orbit, they just signed

@Pati

Set up the project, channel and Drive folders for the new customer

@Pati

Send the welcome email and chase the access we still need

@Pati

Assign the onboarding checklist to Iris

@Pati

What's still outstanding on the Orbit onboarding?

FAQ

Customer onboarding, answered.

What does Patricia actually set up?

The project, the Slack channel and the Drive folders from your template, the onboarding checklist with owners and due dates, the welcome email and the access requests to the customer, and the kickoff meeting. All from the moment they sign.

How does she know our process?

You build the onboarding template once, your steps, the access and info you always need and the folder structure, and she reuses it for every new customer, so nothing is remembered from scratch.

Does she chase the customer for things?

Yes. She sends the access and info requests with exactly what you need and how to share it, then follows up until they land, so week one is not spent chasing logins.

Can it trigger automatically on signing?

Yes. Point it at your deal-won signal or just tell her a customer signed, and she kicks off the whole onboarding, with anything customer-facing posted for your yes first.

Is this all Patricia does?

No. Onboarding is one job. The same teammate handles proposals, meeting recaps, invoice chasing, and the rest of the work your team hands her, all in the same Slack.

One of the jobs teams hand her. See more admin use cases or browse them all.

Everybody deserves a Patricia.

She handles the work your team never gets to. You build the company. See what changes in your first week.

Pick a time that works for you. You get a live walkthrough of Patricia on your real work, and every question answered.

No credit card.