Skip to content
← All articles

Notes for owners · Channel and customer growth

Customer adoption: making sure they use what they bought

How to spot customers who bought but do not use the product, and how to set check-ins at usage milestones for software, equipment and services before the silence turns into a lapse.

The GullySales team · Updated 17 Oct 2026 · 6 min read

Editorial illustration for Customer adoption programmes
On this page
  1. Logins lie, and so do delivery notes
  2. A milestone card, written before delivery
  3. How long to wait
  4. Four kinds of silence, and the question that tells them apart
  5. A case: billing software for traders in Ratlam
  6. What to leave out
  7. Write the card for the next ten deliveries

A customer who bought and never really started may not renew, may not recommend you, and may not tell you why. The sale is on your books, so the account looks healthy. Adoption work is the habit of asking, soon after delivery, whether the thing is being used for the job it was bought for. You choose two or three milestones that show real use, you note the date you expect each, and you ring the customer who misses one.

Logins lie, and so do delivery notes

Many firms measure the wrong thing. They know the product was delivered, the invoice was paid and the training session happened. None of those proves use. A shopkeeper can pay for billing software and open it every morning only to print one invoice, while stock stays in a notebook.

So pick evidence a customer cannot produce by accident. Ask what you could see or hear that proves the product now sits inside the daily work. If a buyer could have bought, paid and still not reached the milestone, it measures adoption. If not, it only measures the sale.

A milestone card, written before delivery

Fill one card per product, and attach it to the delivery note so the person who delivers knows what comes next.

Product: billing and stock software for wholesale traders
First use     : first real purchase entry posted (not a test bill)
Habit         : a second person other than the owner posts entries
Value         : owner reads the stock report before reordering
Expected by   : date set at delivery, per milestone
Who rings     : the person who did the setup
If missed     : one call, one question, one specific next step

Three milestones is the ceiling. For a machine the words change: first job run by the customer's own operator, then run without anyone beside the operator, then a job that used to be outsourced. For a service such as a training programme: the customer acts on the first deliverable, asks for the next, and can say what changed.

How long to wait

Set the expected-by date on the day of delivery, while the buyer is still enthusiastic and you can judge what is realistic for that business. A small trader may reach first use in days. A factory installing a machine may need a month, because the operator must be freed from other work. Write the date down, say it to the buyer, and let it be a shared expectation rather than a trap. When it passes, you ring. You do not wait for the customer to call, because a customer who has not started may never call.

Four kinds of silence, and the question that tells them apart

When a milestone date passes, do not send a general reminder. Ring and ask something that separates the causes.

  • The person trained may have left. Ask, "Who is using it day to day now?" If the answer is a pause, brief the new person as if they were a new customer.
  • Sometimes nobody knows how to do the next step. Try, "Which part do you do outside it?" The answer names the exact gap.
  • The product may not fit how they work. Ask what they would have to change about their day to use it. Sometimes a small setup change fixes it. Sometimes the sale was wrong, and you should say so.
  • Or they are only busy. Offer ten minutes at their desk or machine at a time that costs them little.

If none of these applies and the customer simply does not want to engage, note it on the account and watch the next order. Stop after two or three tries.

A case: billing software for traders in Ratlam

Here is an invented case. A reseller sells billing and stock software to wholesale grocery and hardware traders around Ratlam. It tracked adoption by logins, and the numbers looked good. Yet several traders asked for refunds at renewal and two moved to a competitor.

A visit showed why. Each trader's accountant logged in daily, printed that day's bills and left. Purchases and stock were still in a ledger, because entering them looked tedious and the one training day had covered only sales. The logins were real, and the adoption was not.

The reseller's first reaction was a free second training day for everyone. Few came, because a trader cannot easily close the shop for a day. It adopted the milestone card above and one rule. If the first purchase entry was missing by the expected date, the person who did the setup rang. The caller offered a half-hour at the shop on one task only: entering that week's inward goods. The next call confirmed a second person had done it at most shops, but two traders never got past the first entry and left at renewal anyway.

One more habit helps: keep a short list of the customers who missed a milestone and what turned out to be the cause. After ten or fifteen entries you will see whether the gap sits in your training, your product or your choice of customer, and that tells you what to change before the next delivery.

What to leave out

An onboarding email series gets treated as adoption work and is often left unread, so do not rely on it. Do not blame the customer in your notes, because the next person reading them inherits the attitude. And do not promise that use will raise the customer's sales or savings. Say what the product does and let the customer measure the rest. If the product touches health, safety, finance or another regulated use, keep to the maker's documents and tell the customer to check with their own adviser.

Write the card for the next ten deliveries

Decide the first-use milestone for what you sell, put it on the delivery note, and ask about it on the call after delivery. If you want a hand choosing milestones and deciding who owns them, tell us what you need; repeat buying is covered under sales.

Questions

Questions owners ask.

How do I know a customer is not using what they bought?
Ask the thing itself. For software, look at log-ins or the records they have created. For equipment, ask the operator what it ran last week. For a service, check whether the person you trained has acted on it. Silence is often the first sign.
Is low usage always my fault?
Not always. Sometimes the buyer's priorities changed or the person who wanted it left. But low usage is still your problem, since that customer may not renew or recommend you. Find out which cause it is before deciding what to do.
Who should run adoption check-ins in a small firm?
Whoever delivered the first setup, because the customer already knows them. If sales and delivery are separate, the salesperson can open the conversation and hand over, but a named person must be responsible for each customer's first use.

From the blog

More notes for owners.

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.