New client onboarding: the handover and the four dates
New client onboarding for a small services business: the six things that move from the deal record, the five questions a kickoff call is for, and four dates.
Salva Sanchiz · Founder
/ 12 min read / Art. #28
Client onboarding is the stretch between a signature and the first thing the client can actually look at. For a small services business it starts on the day the agreement is signed and it ends on the day you hand over something the client can use, read, or react to. Everything in between counts as onboarding, including the ten days nobody worked because you were waiting on a logo file.
That closing date is the part almost nobody writes down. Search for a client onboarding checklist and you get task lists to run inside a portal, a form tool, or a project tracker. Very few of them say how you know a client is onboarded. Without a date on it, "onboarded" is an opinion, and two people in the same company will hold different opinions about the same client.
A client onboarding process for a small team has three parts. Six things move from the deal record to the client record. Five questions get asked on the kickoff call, and only five, because everything else was already answered while you were selling. Four dates get filled in, and the fourth one is what ends onboarding.
None of this needs software you do not already have. It works in any CRM, and it works in a spreadsheet with a few extra columns. What matters is that the six things arrive, the five questions get asked once, and the four dates exist as dates rather than as a feeling.
The two weeks nobody owns
The pattern is easy to recognise once it has a shape. A post in r/agencynewbies in January 2026 put it in one line: "Every time we sign a new contract, the momentum dies." An agency owner in r/marketingagency at the start of February described the cause as "chasing them for logos, ad account permissions, their Google Analytics login," and said the chase was costing real money, not just patience.
A post in r/smallbusiness in November 2025 listed the same pain point for service businesses: a new client signs, then two weeks go on getting them ready, collecting initial information, setting up access and explaining the process, and projects are delayed before real work begins.
And then there is the one that names the real cause. From r/smallbusiness in March 2026: "Client onboarding that used to take 3 days is now taking over a week because nobody is sure whose job each step is." Nothing broke. The company grew, one person stopped being both the seller and the deliverer, and nobody wrote down the transfer between the two.
Teamwork.com wrote in May 2026 that they had seen agencies lose accounts inside the first 90 days because the sales to delivery handoff felt disorganised to the client. That is a vendor blog making a vendor's point, so treat it as one. It matches what operators describe, which is the part worth keeping.
The sales to delivery handoff gets named in almost every onboarding guide. What matters for a small team is what actually crosses the line, so start there.
Part one: the handover, six things that cross the line
The person who sold the work learned all six of these while selling it. None of them survive a copy of the company name into a new record.
| # | What moves | Why it goes missing |
|---|---|---|
| 1 | What they bought, and for how much | The proposal PDF exists, the one-line version the delivery side can act on does not |
| 2 | What they said no to | Nobody writes down an absence |
| 3 | Who decides, and who you talk to daily | Usually two different people, stored as one |
| 4 | The start date they were promised | The soft version got said on a call and never typed anywhere |
| 5 | Where they came from | Re-guessed later instead of carried across |
| 6 | What they are worried about | It sounded like an objection at the time, so it got answered and discarded |
Items 1, 3, and 5 are the mechanical ones. Write the scope in the words the person doing the work can read in ten seconds, not the proposal. Store the decision maker and the day-to-day contact as two separate people, because the one who signs is rarely the one who answers on Tuesday morning. Carry the source across from the deal, because a referred client gets a different first week than one who arrived from a search.
The other three are the ones that cost you something.
What they said no to. During the sales conversation, things came up and got cut. The extra territory, the second language, the reporting nobody wanted to pay for. Six weeks later the client asks where it is, in good faith, because they remember discussing it and not the part where it was removed. This is the single most common source of a week-three argument, and it is the item most often lost, because a list of things that are not happening feels like a strange thing to write down. Write it down anyway.
The start date they were promised. Whatever was actually said on the last call, including the soft version of it. "We could probably have you live by the end of the month" is a promise. The client remembers the soft version, always, and the delivery side has never heard it.
What they are worried about. The objection they raised before signing, in their own words. It is the thing that will resurface in week six if the first two weeks do not answer it. If the worry was "the last agency went quiet on us," then your first two weeks are about being visible, whatever else is on the plan.
Six fields. Two of them are long text, one is a date, two are relations to people, one is a select. Any CRM has all five types, and a spreadsheet has five columns.
Part two: the kickoff call, five questions and one rule
Do not re-ask what the deal record already answered
This is the rule that decides whether the call is worth holding. The client already told you their budget, their scope, their decision process, and their worry, because that is what a sales conversation is. Asking again on the kickoff call tells them the two halves of your company do not talk to each other, and it spends first-week credibility that took a whole sales cycle to earn.
Part one exists so that part two can be short. If the handover happened, the call is five questions long, and the five kickoff call questions below are the ones the deal record cannot answer for you.
| # | Kickoff call question | What the answer writes down |
|---|---|---|
| 1 | Who else needs to be in the loop on this? | The other people at the client, linked to the company record |
| 2 | What does done look like in ninety days? | The success line, in their words |
| 3 | What do you already have that we need? | The inputs list, each item with a person and a date |
| 4 | How do you want to hear from us, and how often? | The channel and the cadence |
| 5 | What went wrong the last time you did this? | The risk note |
Question 3 is where onboarding actually stalls, so it gets the most attention on the call. Take the list item by item, and put a name from the client's side and a date against each one. "Send us your brand files" produces nothing. "Marta sends the logo pack by Thursday" produces a logo pack, or produces a specific person to ask on Friday. The logins, the ad account permissions, the analytics access: all of it belongs on this list with an owner, on the call, while the client is still in the room.
Question 2 is worth protecting from your own instincts. The answer is not a restatement of the scope, and you should not tidy it. Keep the client's wording, even when it is vague, because the vague version is what they will measure you against in ninety days. A success line of "I want to stop being the person who chases this" is more useful than anything you would write in its place.
Question 5 works because every client who has bought this kind of work before has a story. The story tells you what to over-communicate. It is also the question most likely to change how you run the first month, which is a good return on one sentence.
Question 4 ends a negotiation before it starts. Agree the channel and the frequency once, on the call, and the rest of the relationship stops being a running argument about email. The same logic sits behind a written first response time standard: the agreement is cheap, the ambiguity is expensive.
One more idea worth borrowing. A reply in an r/Entrepreneur thread in June 2026 recommended starting every project with a one-page kickoff listing the PO and AP contacts alongside the decision makers. Billing contacts are not glamorous and they are the reason an invoice sits unpaid for six weeks.
Part three: the four dates that make "onboarded" checkable
Everything above is a list of things to do. This is the part that tells you whether they worked, and it is the part missing from every onboarding checklist we could find.
Four date fields on the client record. Onboarding is finished when the fourth one has a value, and not before.
| # | Date | What it means |
|---|---|---|
| 1 | Signed | The day the agreement was closed |
| 2 | Kickoff held | Not booked. Held. |
| 3 | Inputs complete | The day the last item from question 3 arrived |
| 4 | First value delivered | The first thing the client can look at, use, or react to |
Kickoff held is a held date, not a booked one, because a booked kickoff that moves twice is exactly the situation this is meant to expose. Inputs complete is the date that slips, and it usually slips on the client's side, which is precisely why it needs a date rather than a feeling. First value delivered is not the project end and not the invoice. It is the first thing the client can react to, and for most services businesses it arrives long before the work is finished.
Onboarding time, one subtraction
Onboarding time = First value delivered minus Signed.
One subtraction, in days. It is the only onboarding metric a small team needs, and it is comparable across every client you have ever signed. Run it on your last ten clients this afternoon and you will have a number that no competitor blog can give you, because it is about your company and not about an industry average.
The second reading, and it is the more useful one
Take the gap between Kickoff held and Inputs complete. That gap is a measure of your chasing, not of the client's goodwill.
When it is the biggest slice of the total, the fix is on your side: question 3 was asked loosely, the inputs list had no names against it, or nobody owned the follow-up. When the gap between Signed and Kickoff held is the biggest slice, the fix is in your calendar. When most of the time sits after Inputs complete, onboarding is fine and the problem is capacity.
Three different diagnoses from four dates, and none of them require a report to be built.
The board, if you want to see it
Four dates tell you what happened. A board tells you where things are right now. The stages that match this model are Signed, Kickoff booked, Kickoff held, Inputs chased, Inputs complete, First value delivered.
The useful thing about a Kanban board here is time in stage. A client sitting in Inputs chased for eleven days is the "nobody is sure whose job each step is" problem, visible without anyone asking for a status update. It is the same read as a dormant client audit, applied to a finite interval instead of an open-ended one.
What a CRM does here, and what it does not
Syncek is not an onboarding tool. There is no client-facing portal, no intake form the client fills in, no automated welcome email, no document requests, and no file collection. Tasks are on the roadmap and will stay lightweight and attached to the record. If your business collects a large volume of documents from every client, a dedicated onboarding product solves a real problem, and this is not that.
What we hold is the record. The six handover items are fields on the client record: two long text, one date, two relations to people, one single select. The four dates are four date fields. Onboarding stage is a single select driving a Kanban board, and Syncek tracks time in stage, so the board answers "where does this stall" without anyone building a report. Choosing the fields well matters more than the tool does, which is the whole argument of our guide to CRM field design for small teams.
There is a 15-day free trial on the Pro tier, and you can export to CSV or JSON at any time, including after you cancel.
If you have a spreadsheet instead, add six columns for the handover, one column per date, and a status column. The subtraction is a formula. You lose the board and the linked people. You keep everything that matters.
Get the guide
We've prepared a guide to keep on hand while you build or audit your CRM. 14 pages, A4.
Download the client handover card (PDF)
Frequently asked questions
What is client onboarding for a small business?
Client onboarding is everything between the signature and the first thing the client can look at, use, or react to. For a small services business it starts on the day the agreement is signed and ends on the day of first value delivered. It covers the transfer from the person who sold the work to the person doing it, the kickoff call, and the collection of logins, files, and access from the client.
How long should client onboarding take?
There is no honest industry number, and any blog quoting one is guessing about your trade. Measure your own instead: first value delivered minus signed, in days, across your last ten clients. That gives you a baseline you can compare against yourself each quarter. An operator in r/smallbusiness in March 2026 described onboarding drifting from three days to over a week as the team grew, which is the shape of the problem this measurement catches.
What should be in a client onboarding checklist?
Three parts, in order. Six things that move from the deal record to the client record: what they bought, what they said no to, who decides and who you talk to daily, the start date they were promised, where they came from, and what worries them. Five questions asked once on the kickoff call. Four dates on the record: signed, kickoff held, inputs complete, first value delivered.
What questions should I ask on a kickoff call?
Five, and none that the sales conversation already answered. Who else needs to be in the loop on this? What does done look like in ninety days? What do you already have that we need? How do you want to hear from us, and how often? What went wrong the last time you did this? Each answer writes to a specific field, and question three is where onboarding usually stalls.
Why should I not re-ask questions the client already answered?
Because the client answered them while being sold to, and asking again tells them the two halves of your company do not talk to each other. It spends first-week credibility that took a whole sales cycle to earn, and it is the most common complaint operators make about their own kickoff calls. A handover from the deal record to the client record is what keeps the call to five questions.
When is a client fully onboarded?
When first value delivered has a date on it. Not when the kickoff call happened, not when the contract was countersigned, and not when the client stopped emailing. Picking a single dated event as the end of onboarding turns a matter of opinion into something two people in the same company can check in three seconds. It also makes the interval measurable, which is what lets you compare one client against another.
Do I need onboarding software to do this?
No. Onboarding portals and intake tools solve a genuine problem for companies collecting a lot of documents from every client, and if that is you, they are worth looking at. The model above is six fields, five questions, and four dates, and it runs in any CRM or in a spreadsheet with extra columns. Buy the software later, once you know from your own dates where the time actually goes.
Can I run client onboarding in a spreadsheet?
Yes. Add six columns for the handover items, four date columns, and a status column, then write the subtraction as a formula. What you lose is the board with time in stage, and the ability to store the decision maker and the day-to-day contact as real linked people rather than as typed names. What you keep is the whole model, which is the part that changes how the first two weeks go.