Customer onboarding · Sales
Your new customer should not have to chase you after signing.
Your salesperson wins the order, but the delivery team receives little more than a name and phone number. The buyer has already explained their requirements and now has to explain them again. Work stalls before it properly starts.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

In one paragraph
Customer onboarding is the planned sequence between a customer signing and reaching an agreed first result with your business. GullySales designs the sales handover, welcome messages, setup checklist, and staff responsibilities so your team knows what to do next and your customer knows who is responsible for getting them started.
In a B2B relationship, the person who approved the purchase may not be the person supplying documents or using the service. Customer onboarding makes those responsibilities clear and carries the sales promise into delivery.
The same need exists when a family takes possession of a flat or a resident moves into a PG. The starting point changes, but every customer needs a named contact and an agreed point at which setup is complete.
Who it is for
This is written for you if these sound familiar.
- B2B service firms where signed orders wait for a handover from sales
- Subscription businesses whose new customers stop responding during setup
- Builders handing buyers from sales to possession or customer care
- Banks, wealth managers, and hospitals collecting documents before service starts
- PG and hostel operators managing move-in paperwork and room handovers
- Owner-led firms where each new customer still depends on the founder
Not for
It is not the right fit if.
- Single-transaction purchases with no meaningful setup or handover period
- Established customers who need ongoing adoption or renewal support rather than onboarding
- A team expecting GullySales to replace its day-to-day delivery staff
The problem
Does this sound like your business?
Common situations this work addresses.
“The customer signed and then nobody called”
Sales has moved to the next enquiry, but delivery has not accepted the handover. The customer does not know whether work has started.
“We keep asking for the same documents”
Sales, accounts, and operations make separate requests because nobody can see what has arrived. Your customer spends time repeating a task they thought was finished.
“What sales promised is missing from the handover”
A delivery date or special requirement stays in a WhatsApp conversation. The receiving team discovers it only when the customer asks why it has not been honoured.
“We cannot tell who is stuck”
A welcome message has been sent, so the customer appears to be onboarded. But nobody checks whether the first booking happened or the agreed setup was completed.
Choose the right scope
Start with the work your business needs.
B2B sales-to-delivery handover
For orders that stall after acceptance, start with the handover note and receiving-team checklist. The buyer's requirements reach delivery before the welcome call.
Document-heavy service starts
For financial services or hospital registration, start with the approved document list and receipt tracker. The focus is missing information and clear responsibility, subject to your compliance review.
Possession and move-in handovers
For builders or PG operators, organise the customer's handover appointment, required paperwork, and outstanding-item record. Physical readiness and completion decisions remain with your responsible team.
First-use onboarding
For subscription or service customers who sign but never begin, define the first useful action and the check-in when it is missed. Ongoing usage support follows under a separate adoption scope.
What we do
The work we can include.
Each deliverable and the purpose it serves. Your written scope confirms what is included, who is responsible, and what it costs.
Sales handover note
A record of why the customer bought, agreed commitments, key contacts, and unresolved questions. You check it against the proposal or order before the receiving team accepts it.
Document and access checklist
A single list of required documents, forms, access permissions, or site details, with reasons and receipt status. Your team checks what is missing without asking the customer to resend everything.
Welcome message and kickoff agenda
Ready-to-use wording for WhatsApp or email, plus an agenda where a kickoff call is needed. You review whether it identifies the contact person and explains the next action clearly.
First-success definition
A written milestone such as the first booking made, first report used, or keys handed over. It states what counts as completion and what evidence the onboarding owner records.
Onboarding tracker and check-in plan
A shared sheet or tasks in your existing CRM showing ownership, pending actions, and milestone status. Check-ins follow the customer's progress rather than a generic message schedule.
Staff checklist and walkthrough
A practical checklist and training session for the people handling new customers. Staff test it against a real handover so unclear instructions are found before wider use.
Completion handover note
A short record for the person taking over ongoing service, including completed setup and open issues. Your team checks that the customer knows who handles the next stage.
How the result is measured
- Time from signing to first contact
- Time from signing to the agreed first-success milestone
- Customers stalled or withdrawn before completion, with recorded reasons
- Repeated document requests and overdue checklist actions
- Completed onboarding milestones, separate from messages sent
- Completed orders or service starts where these follow signing, separate from qualified opportunities still in sales
Recorded as a baseline before work starts, so every later report has an honest comparison.
Marketing and sales together
Sales receives a record of what happened after the order.
The onboarding tracker carries the accepted handover, milestone status, and unresolved promises back to the person responsible for sales. They can distinguish a signed order awaiting setup from a completed service start. Where customers repeatedly arrive with the wrong expectation, that record gives the sales lead a specific proposal or promise to correct.
Decisions to make before the work starts
Access to real handovers
The work depends on recent records and access to the people handling them. Missing history limits the baseline and must be recorded as a gap.
Operational and compliance ownership
Your team remains responsible for delivery readiness, document approval, and customer decisions. Process design cannot resolve an unavailable room or an unfulfilled sales commitment.
Sequence complexity and separate work
Different products, locations, or approval paths affect the scope. New software, custom integrations, and ongoing onboarding operations are not included unless expressly agreed in writing.
This or a nearby service
Which piece of work fits your situation.
These services sit close to each other. The line between them, in plain words.
- Digital customer journey design
- Choose digital customer journey design when the need is the app notifications, WhatsApp messages, emails and SMS sent between human conversations. Choose customer onboarding when the gap is the handover from sale to start: who does what, what the customer provides, and what counts as a first result.
- Customer adoption programmes
- Choose customer adoption programmes when customers have started but stop using the product or service and you need prompts and an activity view. Choose customer onboarding when the problem sits before that point: the start itself is confused, slow to begin or handed over poorly.
- Customer success automation
- Choose customer success automation when the check-ins and renewal reminders are known and only need rules in your CRM. Choose customer onboarding when the milestones, the staff responsibilities and the definition of a successful start have not yet been written down.
A sample of the output
An onboarding tracker shows each milestone, its proof, and who is responsible.
This extract is for a software firm signing a new business customer. Each row is a milestone from signature to first result. Read across to see the evidence that closes it and who acts on each side.
| Milestone | Evidence it is done | Customer owner | Staff owner |
|---|---|---|---|
| Sales handover | Handover note read and questions answered | Not applicable | Account executive |
| Documents and access | Every listed document and login received | Office administrator | Onboarding lead |
| Kickoff meeting | Agenda covered and next steps recorded | Project sponsor | Onboarding lead |
| Setup complete | Customer confirms the setup matches the agreed brief | Department head | Delivery specialist |
| First result reached | Customer states the agreed first result is visible | Project sponsor | Account executive |
| Completion handover | Note sent and ongoing contact named | Project sponsor | Onboarding lead |
Before we start
What we need from you.
The work depends on these. Each says why it is needed and what happens when it is missing.
- Access to real handover notes
- Recent sales handovers show where information is lost between the seller and the team that starts the work. Three or four real examples are enough. Without them, the sequence is built on assumption and misses the actual failure points.
- A definition of the first result
- Someone must say what the customer should have achieved for the start to count as done. A plain sentence is enough, such as the first report sent. Without it, the tracker has no finish line and handover never closes.
- Named staff for each milestone
- Each milestone needs a person on your side who is responsible, including cover for absence. Names matter more than titles. Where a milestone has no owner, the tracker is built but nobody is accountable for moving it.
- A list of what customers must provide
- Documents, access, approvals and contacts a customer must supply differ by business. Provide the current list, even if it is informal. Without it, the checklist is incomplete and the work stalls waiting for items nobody asked for.
- One live customer to trial with
- The sequence is tested on a real customer who is about to start. Your team chooses the customer and tells them it is being tried. Without a live case, the sequence remains untested and ships as a draft.
How it works
How the customer onboarding work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Recent-customer review
You share recent onboarding records and messages. GullySales traces the path from signing to first result, identifies delays, and records the available baseline before changes begin.
- 2
Milestone and ownership approval
Your sales and delivery leads agree where onboarding starts and ends. Each action gets a responsible person, including the decision about who accepts a completed sales handover.
- 3
Sequence and wording approval
We draft the handover note, requests, and customer messages. Your team confirms that each commitment is deliverable before the sequence is used.
- 4
Tool setup and staff handoff
The approved sequence goes into your existing WhatsApp workflow, shared sheet, or CRM tasks. Staff walk through a sample customer and confirm where they record completion or a delay.
- 5
Live-customer trial
Your team runs the sequence with new customers while GullySales reviews skipped steps and confusing requests. You approve revisions before the checklist becomes the working standard.
- 6
Baseline comparison and service handover
We compare progress with the recorded starting point and adjust the sequence. The ongoing service owner receives the completion record, with unresolved matters kept visible.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 7, after the sale. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
How long should onboarding last?
Does sales have to stop handling the customer?
Do we need a new CRM?
Can this cover regulated documents and consents?
What happens after the customer is onboarded?
How do we agree the scope and fee?
By industry
Customer onboarding, written for your industry.
Related services
Often bought with this, or instead of it.
Learn the method
The teaching pages behind this work. Read them to judge the work, or to do the parts you want to do yourself.
Read before you buy
- A customer onboarding checklist for a service business, with an owner for every lineA working checklist for the first stretch after a service customer says yes: reply, documents, kick-off, access and a first result, each with an owner
- Mould trial and sample approval: how to get a moulded part signed offWhat a moulder should agree with the buyer before a trial run, who signs the approval, and how to keep signed samples and settings on file.
- Turning a trial order into a regular accountA trial order becomes a regular account when you call on arrival, fix the next order date on that call and put regular terms in writing.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.