Client Onboarding for a Small Team: Who Owns Each Step, and What Runs in Slack
A client signs on a Tuesday. By Friday you are still waiting for the countersigned contract, two of the five documents, the system access, and nobody has issued the first invoice. You are the person chasing all of it, and you are about to write a job description for an onboarding coordinator whose first month would be the same chasing. This guide is for the owner or operations generalist of a 5 to 100 person service firm who wants client onboarding to stop depending on memory. It gives every step in the first 30 days an owner, a trigger and a verdict, shows which part can run in one Slack thread, and ends with a rule for when the hire is worth it.
The short answer: three verdicts for every step
Sort each onboarding step into one of three buckets and the hiring question gets much smaller.
- A scheduled check can see it. The signal exists in a system: a file in the client's Drive folder, a CRM task, an invoice record. A morning list can report it without anyone remembering to look.
- An approved draft can chase it. The step is waiting on the client. A reminder gets written for you and goes out only after you press Approve.
- A person must do it. The kickoff conversation, the scope discussion, access to the client's systems, and every exception.
Most published checklists stop at the list. The rest of this guide adds the trigger and verdict columns they leave out.
Why client onboarding turns into chasing
The checklist is rarely the problem. Jet Admin's client onboarding checklist says most onboarding problems come from missed handoffs: sales promised something delivery never heard about, or a document sat in someone's inbox for a week. It also says "Chasing is the most time-consuming part of onboarding." OnboardMap, a vendor that sells onboarding software, makes the same claim about the person you would hire: the majority of what a client onboarding specialist does in their first month is chasing, reminding and copying data between tools.
Treat the vendor numbers as vendor views. Practitioner posts show the pattern too, though they come from tool builders. The founder of a document-collection tool wrote on Hacker News that accountants and HR people spend hours chasing clients for documents over email. A competing builder replied in the same thread that automated reminders were the biggest value driver for their early users. These are author reports from people selling a fix, not proof of how common the problem is.
When a client signs, the firm's attention moves to the next deal. Every step that waits on the client has no owner who gets a signal when it stalls. A contract that was countersigned but never filed, a first invoice nobody created, a document request that went unanswered: each is invisible until someone asks. Chasing is what the owner does to make invisible things visible.
The ownership table for the first 30 days
Jet Admin's checklist splits the first 30 days into five phases with day ranges: before kickoff (days 0 to 3), information and document collection (days 1 to 7), kickoff (days 5 to 10), setup and first delivery (days 10 to 30), and a review at day 30. Its template gives each step an owner role and a due date. That is more than Zoom's seven-practice checklist, which covers welcome messages, contracts, a single client record, invoicing terms and a kickoff call but does not assign people or say how a late step is noticed.
A role and a due date still leave a gap. A checklist names who owns a step but not what tells you the step is late, so every step needs a trigger and a verdict: a scheduled check can see it, an approved draft can chase it, or a person must do it. Without the trigger, the owner of the step is the person who happens to remember it.
Here is the table, using Jet Admin's phases as the skeleton. The owners are for a 12-person firm with an owner, an account lead and a delivery lead; swap in your own roles. The verdicts are my recommendation, based on what the Kipwise agent can read and do (see the next section).
| Step | Days | Owner | Trigger that says it is late | Verdict |
|---|---|---|---|---|
| Countersigned contract stored with the client | 0 to 3 | Owner | No signed file in the client's Drive folder | Scheduled check |
| Sales-to-delivery handoff (goals, promises, risks) | 0 to 3 | Owner writes, delivery lead reads | Delivery lead cannot restate the promises | Person |
| Client created in CRM and billing | 0 to 3 | Account lead | No deal or task in the CRM, no contact in the invoicing tool | Scheduled check |
| Welcome email with next steps | 0 to 3 | Account lead | No sent message to the client in Gmail | Approved draft |
| First invoice or deposit | 0 to 3 | Owner | No invoice record, or unpaid after the due date | Scheduled check, then approved draft |
| Questionnaire and document request | 1 to 7 | Account lead | Request not sent by day 1 | Approved draft |
| Missing documents | 1 to 7 | Account lead | Items still absent from the Drive folder at day 3 | Scheduled check, then approved draft |
| Access to the client's systems | 1 to 7 | Delivery lead | Delivery cannot log in | Person |
| Kickoff scheduled and held | 5 to 10 | Owner and delivery lead | No date by day 5 | Person |
| Scope, success metrics, communication plan | 5 to 10 | Owner | Not written down after the call | Person |
| Setup and first deliverable | 10 to 30 | Delivery lead | Plan has no milestone dates | Person |
| 30-day review | 30 | Account lead | No review on the calendar by day 25 | Scheduled check, person holds it |
In this table seven of twelve steps involve the machine in some way, and none of those is fully hands-off: each needs a person to read the list or press Approve. At a small firm, client onboarding automation removes the remembering, not the responsibility.
What runs in Slack, step by step
The setup is one internal thread per new client. After the deal closes, the owner mentions the Kipwise agent once in that thread and asks it to list the onboarding steps for this client against the firm's checklist. Replies in the same thread continue the conversation without another mention. Per Kipwise's product documentation, the agent works with your own connected accounts and permissions, so a Drive folder or mailbox you cannot open cannot be read through it.
The morning check. Ask the agent to run a scheduled task each weekday morning in that thread. Creating a scheduled task needs your approval once. The task uses your connected tools. It reads the CRM deal and its tasks (HubSpot or Pipedrive), lists what is in the client's Google Drive folder, and looks up the client's invoices in QuickBooks or Xero. It then posts a single list in the thread, grouped by owner, of what is still missing. Each connection is separate: Drive, Gmail, the CRM and the invoicing tool each need a one-time connection, and connecting one does not grant the others.
Run the chase as a read-only morning list and keep every write behind a card, because the step that goes wrong in onboarding is the wrong reminder to the wrong client, not the missing one. Write the scheduled task so it reads and reports only. Writes (an email, a CRM note, a closed task) happen in the live thread, when you ask for them, behind an Approve or Deny card that only you can press. The card expires after 30 minutes, and denying it or letting it expire means the action does not run. This is a recommendation about how to word the task, not a claim about what a scheduled run is technically unable to do.
The reminder. When the list shows a missing document on day 3, reply in the thread and ask for a reminder to the client. The agent searches your Gmail, writes the draft, and shows the recipient, subject and message on an Approve card. Nothing is sent until you press Approve. Jet Admin's checklist suggests chasing missing items after three days, which is a reasonable default for the trigger, though that figure is the vendor's guidance rather than a measured result.
The record. When a document arrives, ask the agent to log a note and close the matching CRM task, again behind a card. In HubSpot and Pipedrive the agent can add a note or a task when you explicitly ask.
The invoice. The check can tell you that no first invoice exists. Creating one is a write that the agent only does when you explicitly ask, and in QuickBooks an invoice is posted live rather than as a draft, so decide whether you want it done by a person in the invoicing tool instead.
What stays with a person. The kickoff call, the scope conversation, access hand-over for the client's systems, and any exception. Jet Admin's checklist warns against collecting credentials by email and recommends a secure portal or password manager sharing, and that advice applies here too: do not paste a client's logins into a Slack thread. The agent also does not invite people to a calendar event unless you ask, and it says plainly when it has not read a file rather than guessing.
An illustrative example, made up for this article: a four-person bookkeeping team signs a new client on Monday. The Wednesday morning list in the thread reads: contract signed and in the Drive folder; client created in the CRM; first invoice not yet created; two of five documents received (bank statements and payroll report absent). Owner reply: "Draft a reminder to the client for the two missing documents." The agent shows the draft on a card, the owner presses Approve, and the email goes out. The remaining work, the kickoff call and the system access, is still a person's job.
Client onboarding in a shared Slack channel
If you also want clients in Slack, Slack's Slack Connect guide says a channel with another organization needs each organization on a paid Slack plan, only the organization that owns the channel can invite organizations, and a DM with an outside person works on any Slack plan. Keep the chase list in the internal thread and use the shared channel for what the client should see.
When an onboarding coordinator is worth hiring
OnboardMap's guide says a dedicated hire starts to make sense somewhere around 8 to 15 new clients a month, when onboarding volume and complexity outgrow what the senior team can absorb. That is a vendor's view, and a vendor of software, but it is the only explicit volume number in the sources I opened.
Volume, not pain, is the hiring trigger: the only published threshold, a vendor's 8 to 15 new clients a month, means a firm onboarding two clients a month has a process problem, not a headcount problem. OnboardMap says most of a specialist's first month goes to chasing, reminding and copying data between tools, so a coordinator hired at that volume would mostly do the same chasing.
OnboardMap gives these cost figures, which I am quoting as the vendor's numbers:
- Full-time specialist: $45,000 to $70,000 in salary plus 25 to 40 percent in taxes and benefits. Applying their percentages to their own range gives roughly $56,250 to $98,000 a year (my arithmetic). They say it lands over $60,000 fully loaded.
- Part-time or contract coordinator: $20 to $35 an hour. At 10 hours a week, about 43 hours a month, that is roughly $870 to $1,520 a month (my arithmetic).
- Onboarding software: a few hundred dollars a month.
For the Kipwise agent, the price is $10 per user per month, or $108 per user per year, with a minimum of three users. Three users is $30 a month or $324 a year. Each user's $10 includes $5 of personal AI credit that resets monthly, and there is $2 per user of shared team credit behind it. A $2, 7-day trial needs only the install; saving a card without being charged, or being on a paid Slack plan, unlocks a $10, 14-day trial. Heavy use can run past the included credit, so watch the usage in the first month before you rely on the monthly figure.
Here is a copyable rule. Hire a coordinator only when all three are true:
- You onboard at least 8 new clients a month, consistently, or the clients are complex enough that each needs several people and unusual documents.
- After a 30-day pilot of the three-verdict table, the steps marked "person" still take more than about 10 hours a week across the firm. This threshold is my recommendation, chosen as a round figure that a part-time contract coordinator could absorb; adjust it for your pay rates.
- You have a written process for the new hire to run, not one to invent.
If only the first is true, buy the system and add a contract coordinator for the person steps. If none is true, do the pilot and hold off on the job post.
Handle failure and edge cases
- The check reads the wrong folder. Client folder names drift. Put the Drive folder link in the first message of the thread, and have the owner confirm it once.
- The client replies by phone or text. The list will keep showing the item as missing. The person who took the call closes the loop in the thread, and the owner asks the agent to log it.
- A connection is missing or expired. The agent offers the link to connect, and only the person whose account it is can complete it. If a check stops posting, ask the agent what happened on previous runs; it can list your scheduled jobs and the outcome of earlier runs, including failures.
- An approval card expires. After 30 minutes the action simply does not run. Ask again.
- An exception. A client who is upset, a document request that does not fit the template, a scope disagreement: all person steps, by design.
Verify it works
Run the table on the next three new clients before you change anything else. Track four numbers for each:
- Days from signature to the last required document. Jet Admin's phase ranges give days 1 to 7 for collection as a reference point.
- Number of manual chases you sent without the list prompting you.
- Whether the first invoice was issued by day 3.
- Whether the kickoff was scheduled by day 5.
If the number of manual chases falls and the days to last document do not rise, the list is doing its job. If the list is posted but nothing moves, visibility was not the problem. The person steps are, and that is the evidence for or against a hire.
What to do next
Today, open your last three new clients and mark each step with one of the three verdicts, using the table above. For the next client, install the Kipwise agent (trial details are on the pricing page), connect Drive and your CRM, and ask it for the onboarding list in one thread. Write the morning check as a read-only task. After three clients, apply the hire rule with your own numbers. For related jobs, see how to stop client requests disappearing into Slack, send weekly client updates, chase overdue invoices and hire a virtual assistant. The kick-off call template covers the one step that stays with you.
References
- Client Onboarding Specialist: What They Do and When to Hire One: role description, cost comparison, 8 to 15 clients a month signal, coordination versus judgment (vendor source, 2026-07-27)
- Client Onboarding Checklist: Steps and Free Template (2026): five phases with day ranges, owner and due-date template, chasing is the most time-consuming part (vendor source, 2026-09-30)
- Client onboarding checklist: 7 best practices for 2026: seven practices, no step ownership or reminder logic
- Slack Connect guide: Work with external organizations: paid plan requirement, who can invite, DM invitations
- Show HN: FolioDoc - I built a tool to stop chasing clients for documents: builder report of document chasing (author report, 2026-02-17)
- Hacker News reply on chasing clients for documents: competing builder report on reminders (author report, 2026-03-03)
- How to Stop Client Requests from Disappearing into Slack Without Hiring a Coordinator: related Kipwise guide
- How to Send Weekly Client Updates from Slack Without Hiring an Account Coordinator: related Kipwise guide
- How to Chase Overdue Invoices from Slack Without Hiring a Bookkeeping VA: related Kipwise guide
- How to Hire a Virtual Assistant for a Slack-Based Team: related Kipwise hiring guide
- Kick-off call template: template for the kickoff step
- Kipwise pricing: agent price and trial
