The two weeks after signature set the tone for the whole engagement. An onboarding checklist for a service business: documents, access, expectations, billing and start.
Key takeaways
- Onboarding is a process with a fixed list, not a series of emails somebody remembers.
- The customer record is opened before work starts, not after the first invoice.
- Most onboarding delays are waiting on material from the customer - so ask for everything once.
- A short kickoff call saves two weeks of email, even on a small deal.
- What you agree during onboarding about channel and response time prevents most later friction.
The customer signed, and now the part that sets the whole engagement begins: who collects the details, who opens them in your systems, when work actually starts, and what they expect to happen in week one. In service businesses most misunderstandings are born in these two weeks, not in the work itself.
What happens without a process
The customer signed on Sunday. On Tuesday somebody asks for billing details, on Thursday it turns out a logo is missing, the following week you discover they expected an immediate start. None of these is a serious failure alone, but together they read as disorganisation - at precisely the moment the customer is paying most attention.
The fix is not a system but a fixed list that starts on signature day and ends at a defined go-live point.
The checklist: signature to go-live
- Open a customer record with legal name, company or business number, contact and phone.
- Send one request for all required material, as a numbered list.
- Collect billing details - payment method, who approves invoices, and the invoice email.
- Book the kickoff as a 30-minute meeting with a date, not "we will coordinate".
- Agree expectations - what happens first, what the response time is, on which channel.
- Open access to tools or systems, and record who granted what.
- Define the go-live point - the sentence that says onboarding is finished.
Step two saves the most time. Businesses that request material in a drip wait two weeks; the same business with one numbered list has most of it within two days, because the customer has a single clear task instead of seven interruptions.
Exactly what to ask for, once
| What | Why it is needed | When |
|---|---|---|
| Full legal entity details | A valid invoice and a customer record | Day 1 |
| Operational contact | Who you deal with day to day | Day 1 |
| Invoice approver and invoice email | Prevents an invoice getting stuck | Day 1 |
| Payment method / mandate | For the first charge | Before work starts |
| Access and materials | To actually begin | Before work starts |
| Purchase order requirement | Some larger customers require one | Day 1 |
The last row looks marginal until a first invoice is rejected over it. In larger organisations an invoice without an internal PO number simply does not enter the payables system, and the business discovers this at month end - after the work is done.
What the kickoff call settles
- What happens first and on what date.
- The communication channel - one, not four.
- A stated response time in business days.
- Who decides on the customer side.
- What an update looks like - frequency and format.
- What is required from the customer throughout, not only at the start.
The single-channel point is the most useful. A customer writing on WhatsApp, by email and by phone creates a state where nobody is sure what was agreed, and it always ends in the same sentence - "I told you that". The logic of moving requests into one defined channel is in internal forms instead of WhatsApp chaos.
Where onboarding actually stalls
Almost always in waiting: material that did not arrive, access not granted, or an internal approval on the customer side. So it is worth defining what happens during a wait - who chases, when, and how many times. One reminder after three business days and another after a week is a routine nobody resents.
What does not work is waiting quietly. The customer usually does not remember the ball is with them, and silence reads to them as progress. A short document showing what is pending on their side solves it without friction.
Why do suppliers get asked for a withholding tax certificate?
Many business customers will ask you for a withholding tax certificate and a proof-of-bookkeeping certificate before the first payment, and this is a routine business-to-business request in Israel. The operational logic is simple: these are documents the paying side files, and their absence delays payment even when the work is complete.
For onboarding, the conclusion is that these documents belong on the day-1 list rather than at the moment the first invoice goes out. They are issued by the Israel Tax Authority and have a validity period, so it is worth knowing when yours expires. This is an operational description only; for questions about liability and rates the Tax Authority or your accountant is the source.
What the customer receives, and when
The part of onboarding that is almost always forgotten is the customer's side: what they get in their hands and when. Three documents are enough in practice - an engagement confirmation or deal summary, the list of material required from them, and a short summary of the kickoff call with the agreed dates.
That third summary is the best investment in the whole process. Five lines sent after the call - what happens first, when, who owns what on each side - turn memory into written agreement, and every future discussion about "what was agreed" starts there instead of from impressions.
The go-live point: the sentence that ends onboarding
Onboarding with no defined end runs forever, and the owner keeps providing "early days" service months later. So one sentence has to declare it finished: "the system is live and the customer has access", "the project started and the weekly meeting is in the calendar".
What happens at that moment: the customer moves to routine, the record is marked active, and billing starts as agreed. If there is a training stage it is part of onboarding rather than after it - and its logic is in training your team on a new system.
Sources
Frequently asked questions
How long should onboarding take?
In small service businesses, between three days and two weeks depending on how much material is needed. What matters is not the duration but that the customer knows it in advance, because a customer who does not know when work starts begins asking after two days.
Is a kickoff call needed on a small deal?
A 20-minute call, yes, even on a small deal. It saves an email chain and produces agreement on what happens first - which is exactly what breaks in small deals that start without one.
Who should own onboarding?
One person, even if others perform parts of it. Onboarding split between two people with no owner produces exactly the state where both assume the other sent the request for materials.
What do you do when a customer does not send material?
Chase twice in writing, then state plainly what changes: the start date moves. What you should not do is start anyway without it, because that creates rework and teaches that the list was never really required.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.