Notes for owners · Channel and customer growth
How to create a customer onboarding process
A customer onboarding process is the written handover from sales to delivery and the first thirty days that gets a new customer to their first real result.
The GullySales team · Updated 15 Sept 2026 · 7 min read
On this page
A customer onboarding process is the written sequence of what happens between the order being signed and the customer getting their first real result. It matters because cancellations, disputes and unpaid invoices are usually set in motion in the first thirty days, not in month eight. Four things make one work: a proper handover from sales to delivery, a written set of expectations, a first value moment reached quickly, and one named owner who calls when they said they would.
Onboarding starts when the order is signed, not when work starts
There is usually a gap between the signature and the first day of work. Purchase order formalities, an advance payment, a site visit to schedule, documents to collect. In most small companies that gap is silent, and silence right after a customer has committed money is the worst moment for it.
The customer has just made a decision they may have to defend internally. A call on day one, from a named person, saying what happens next and when, is the cheapest retention work available.
The handover from sales to delivery is the whole problem
Most onboarding failures are handover failures. The salesperson agreed to a Sunday shift, a particular reporting format, a discount on the second site, or a specific person's involvement. None of it reached the team doing the work.
Fix it with a single handover note, filled by the salesperson before delivery begins. It should cover:
- Who the customer is and who signed
- What exactly was sold, including quantities and durations
- Every commitment made verbally
- The price and payment terms agreed
- The customer's reason for buying, in their own words
- Who the day-to-day contact will be
- Any risk the salesperson noticed
Ten minutes to write. It saves weeks.
Then a joint first call, with both the salesperson and the delivery owner on it, where the delivery owner is introduced as the person the customer will now deal with.
A first thirty days that works
For example, a facility management company in Bengaluru taking on a 220-flat apartment complex has a predictable first month, and writing it down turns it from improvisation into a routine.
| When | What happens | Who |
|---|---|---|
| Day 0 | Handover note filled, delivery owner assigned | Salesperson |
| Day 1 | Welcome call: confirms scope, dates, contacts, what the customer must supply | Delivery owner |
| Day 2 to 3 | Written onboarding summary sent: scope, staff deployed, timings, escalation numbers, invoice dates | Delivery owner |
| Day 4 | Site walk with the customer's contact, gaps and exceptions recorded and signed | Supervisor |
| Day 5 to 7 | Work begins, daily check-in for the first week | Supervisor |
| Day 14 | First review call: what is working, what is not, one fix committed with a date | Delivery owner |
| Day 30 | First month review with the decision maker, first report shared, onboarding formally closed | Delivery owner and salesperson |
| Day 45 | Ask for a review or a reference, only if the month went well | Salesperson |
Change the row contents for your business. Keep the shape: a call on day one, something in writing by day three, a review at two weeks, a review with the decision maker at thirty days, and a formal close.
What to put in writing on day one
Not a contract, which nobody rereads. A one-page summary in plain words: what you will do, what you will not do, who the customer should call and on which number, what you need from them and by when, when invoices come and on what terms, and how to escalate if they are unhappy.
Include the exclusions. A customer who reads on day two that deep cleaning of the basement is not in the scope will not be angry about it in month three. The instinct is to leave the awkward parts vague to keep the mood pleasant. Vagueness is what turns into a dispute over an illustrative ₹40,000 invoice later.
The first value moment
Every purchase has a moment when the customer first feels they bought the right thing. For a service contract it might be the first clean handover report. For a CRM it is the first week where the whole team logged calls. For machinery it is the first accepted production batch.
Name that moment for your business and design the first thirty days to reach it as early as possible. Everything else in onboarding is arrangement. This is the part that decides renewal.
Who owns it in a small company
One person, by name, with the customer's number in their phone. In a six-person business that is usually the delivery lead, with the owner stepping in only for the day 30 review. What does not work is "the team will look after it". Then the customer has no one to call, and phones the owner instead, starting the relationship on a complaint.
What to measure, and what to do next
Days from signature to first call. Days from signature to the first value moment. Handover notes completed as a share of new orders. Issues raised in the first thirty days. Customers still with you at ninety days and at one year. And the plain question at the day 30 review: on a scale of one to ten, how likely are you to recommend us, and why that number.
Take your three most recent customers and write down what actually happened in their first thirty days, day by day, from memory and from WhatsApp. The differences between the three will show you what is improvised. Then write the sequence you want, in one page, and use it on the next order.
If you would like help doing that, and a view on where your handover is leaking, tell us what you need.
