Skip to content
← All articles

Notes for owners · Sales management

Product knowledge training for salespeople who sell technical products

How to teach a sales team the reason behind each specification, using one-line spec cards and a short quiz, so they can answer an engineer instead of saying they will check.

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

Editorial illustration for Sales training and development
On this page
  1. What goes wrong when sellers only know the numbers?
  2. What are the three questions an engineer asks?
  3. What goes on a spec card?
  4. A belt and a wrong yes
  5. How do you run the quiz?
  6. What should the card send to engineering?
  7. When is this the wrong investment?
  8. Write one card before Friday

Teach the reason behind each specification, not the specification. For every figure on your datasheet a salesperson should be able to say what it does on the buyer's machine, what goes wrong when it is wrong, and what to ask next. Build one short card per product line, run a twenty-minute quiz on questions engineers have really asked, and let the seller say "I will confirm" for anything outside the card.

What goes wrong when sellers only know the numbers?

A seller who has memorised "350 bar" has no answer when the engineer asks whether that is working or burst pressure. The seller says yes to whichever sounds better. The engineer notices, and the quote loses the room before anyone discusses price.

The numbers are already on the datasheet. What an engineer tests is whether the seller understands them. That is a different kind of training, and mostly it is made of questions.

What are the three questions an engineer asks?

Many technical queries fall into one of three kinds, and teaching them by name gives the seller something to listen for.

The number question. "What is the rating?" It is answered from the datasheet, and it is the only one a new seller can answer.

The condition question. "Does that hold at our temperature, with our fluid, with this much vibration?" The answer depends on facts about the buyer's site, so the seller has to ask before answering.

The consequence question. "What happens if we run it harder than that?" This is the question that separates a seller from a catalogue. Production or service knows the answer, and it often never reaches paper.

What goes on a spec card?

One line per specification buyers ask about, in four columns written in plain words:

Spec            Belt cover grade
Means in use    How well the top rubber stands up to what is dropped on it
Goes wrong if   Cuts and tears on the loading side; belt replaced early
Ask the buyer   How big are the lumps, and how far do they fall onto the belt?

Spec            Number of plies
Means in use    How much tension and shock the belt body can carry
Goes wrong if   Plies separate at the splice
Ask the buyer   How long is the run, and how often does it stop under load?

The last line is the one sellers need most. It turns an answer into a conversation, and a seller who asks about drop height sounds like someone who has seen belts fail.

A belt and a wrong yes

Imagine a conveyor-belt supplier in Ballari. This case is invented to show the pattern. It sells to limestone crushers and cement plants. A plant engineer asked a seller whether a particular belt would suit the transfer point under a crusher. The seller said yes; the number on the datasheet matched. The belt's cover tore in the first weeks, because the lumps were sharp and fell from a height nobody had asked about. The belt was replaced within weeks, a loss of about ₹1.4 lakh in this invented case, and the engineer did not reorder.

The owner traces the cause to how the team learnt products. They were given a catalogue and told to remember the codes. The owner asks the plant-service foreman, who handles the complaints, to write the card for the six belts the company quotes most. A salesperson sat beside the foreman and asked "so what?" after every line. Two of the foreman's best points turned out to be things the foreman told buyers by phone and had never written down.

In the next similar enquiry the seller asked first: how big are the lumps, and how far is the drop? The buyer did not know the drop, so the seller offered to visit. The belt recommended cost about 15 per cent more than the first one. The buyer agreed to a short trial length before ordering the full run, which delayed the sale by some weeks, but the reason had been given and the engineer reordered later.

How do you run the quiz?

Twenty minutes, one product line at a time.

  1. Collect the last ten engineer queries from emails, calls and site notes. Remove names and write each on a slip.
  2. A seller draws a slip and answers aloud with no notes. The others listen and stay quiet.
  3. Compare the answer with the card. Where it differs, ask why. Often the card is the one that is wrong or unclear, so mend it on the spot.
  4. Someone from the shop floor or service tells one story of a part that failed in use and what caused it. A story is often remembered longer than a table.
  5. Each seller practises the sentence they like least: "I do not have the exact figure here. I will confirm with our team and come back to you."

Practise the fifth step more than you think necessary. A seller who has said it aloud five times will say it to a buyer instead of guessing.

What should the card send to engineering?

Some questions need a drawing, a test or a certificate. The seller's job is to recognise them, not to answer them. Add a "send to engineering" line to each card for unusual media, an application with safety consequences, or anything the product was not designed for.

Where the product is regulated, such as electrical, chemical or medical goods, the rules differ by state and body and change. Route those questions to your own adviser or the regulator and never give a ruling over the phone.

When is this the wrong investment?

If your product is simple and sold on price, long product training is wasted. If sellers change every few months, keep the cards short and lean on the foreman for hard queries. If the real problem is that buyers cannot reach your technical people, fix access first, because no card replaces that.

What the buyer sees before the seller arrives is covered in marketing technical products to business buyers. For the first meeting itself, read high-impact questions to ask a buyer.

Write one card before Friday

Choose the product line you quote most. Ask the person who knows it best to fill in four rows, and ask a salesperson to add what a buyer would ask. Then run the slips session once. If you want help building cards and sessions from your own enquiries, sales training and development is the work, part of how you sell, and tell us what you need is where to begin.

Questions

Questions owners ask.

Should salespeople know everything the engineers know?
No. They need enough to hear what the buyer is really asking and to say what they know and what they will confirm. A seller who bluffs loses the engineer's trust faster than one who says 'let me confirm the exact answer'.
Who should write the spec cards?
The person who knows the product best, usually in production or design, with a salesperson beside them asking 'so what?' after every line. The card is for the seller's mouth, so a seller must be able to read it aloud without stumbling.
How often do engineers actually ask these questions?
Often enough that the same five or six come up repeatedly. Collect them from the last quotes, emails and site calls. Your own list will be more useful than any general one.
How do I keep product training from becoming a lecture?
Teach through questions. Give the seller a customer's actual query and ask them to answer it, then compare with the card. People remember the question they got wrong.

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.