Skip to content
GullySales

Sensor manufacturers · Follow up systems

Ask every engineer how the bench test went, and write down what they said.

A follow-up system for a sensor manufacturer is a set of fixed next steps after a sample, a quote or an exhibition meeting, each with an owner. GullySales builds the scripts, reminders and records so that a silent sample does not stay silent.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Sensors product collection

What follow up systems means

A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.

Last updated 14 Nov 2026.

For sensor manufacturers

Where it usually goes wrong, and what we would do.

  • “A sample goes out and the line goes quiet”

    The engineer is testing and has no reason to write. If nobody asks how the test went, the supplier who does ask gets the answer, and the design-in.

  • “A technical question opens the door better than a status check”

    An engineer replies to a question about the output signal or the mounting. They do not reply to 'any update?'. Follow-up scripts built on a real technical question get an answer.

  • “A quote to a purchase team needs its own thread”

    Once the engineer approves a sensor, a quote reaches a different person. That buyer needs price breaks, lead time and a named contact, and may take no action unless reminded of the approval.

  • “Exhibition cards need sorting before they go cold”

    A stack of visiting cards holds engineers, buyers and passers-by. Sorting by what each visitor looked at gives the follow-up a reason to exist.

What we do

What we deliver for sensor manufacturers.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Sample follow-up script

    A short call and message script built on technical questions, with a place to record the engineer's reply.

    Result: Each sample has a recorded conversation about the test.

  2. Owner and reminder for every sample

    A named person and a reminder date against each open sample in your CRM.

    Result: No open sample is without an owner.

  3. Quote follow-up path

    A route for moving from sample approval to a quote to the purchase team, with the price break note attached.

    Result: A purchase manager receives the quote with the approval context.

  4. Exhibition follow-up sort

    A sheet that groups visitors by interest and sets the reason for contact beside each name.

    Result: Visiting cards turn into a sorted contact list.

  5. Lost-reason log

    A short list of reasons recorded when a sample or quote does not convert.

    Result: You can read why enquiries were lost, in the buyer's words.

How the result is measured

  • Follow-up completion rate
  • Average number of follow-ups before close
  • Enquiries closed after repeat follow-up

Recorded as a baseline before work starts, so every later report has an honest comparison.

What to capture or send

The moments after a sample dispatch when a message or call keeps the trial alive.

Dispatch confirmation
Send the courier detail and the serial of the unit. The engineer knows what to look for and when it should arrive.
Arrival check
Ask whether the unit came undamaged and whether a wiring diagram is needed. Some trials stall on a connection question.
Bench result
Ask what the engineer saw against their reference. Record the reading, since it is the basis of any quotation.
Quote sent
Note the lead time and validity on the record and set the next call for before the validity ends.
Order not placed
Record the reason in the buyer's words, such as price, approval or a competitor part, and who to ask again.

Who it is for

This is written for these sensor manufacturers.

  • Temperature sensor and thermocouple makers
  • Pressure sensor and transducer makers
  • Proximity, inductive and photoelectric sensor makers
  • Level and flow sensor makers
  • Gas and air quality sensor makers
  • Load cell and force sensor makers
  • Humidity and environmental sensor makers
  • Automotive and EV sensor makers
  • Custom and OEM sensor makers

Before you decide

When this may not be the right fit.

  • Nobody owns the sample list, so reminders would fire with no person to act on them.
  • Your samples go out without a unit serial or a recorded application, leaving nothing specific to ask about.
  • You want automatic messages to engineers with no human reply behind them, which they will ignore.

Before you decide

Agree the work. Know how to judge it.

Follow-up systems for sensor manufacturers: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Trace recent enquiries from arrival to the last recorded action. Include a won enquiry, an unsuitable one, and one that went quiet, with personal details removed for the initial discussion.

Make the scope clear

Agree who accepts each enquiry, what makes it qualified, and how ownership changes. Include a rule for missed replies and a clear reason for closing an enquiry.

Check the work in use

Pick an enquiry at random and ask the team to find its owner, latest conversation, and next action. Check that the record agrees with what actually happened.

Know when to change course

If no one has capacity to respond, assign that responsibility before buying more leads. Automation can support the owner, but it cannot replace an unresolved handover.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from sensor manufacturers. Anything missing is noted in the written scope, with who will supply it.

The log of samples sent for a year
We need dates, recipients, part numbers and any outcome you recall. A dispatch register is fine. With it we can see where silence fell. Without it, we begin the log now, and the first reading looks only at the samples sent after that point.
Recordings or notes of recent customer calls
If your salespeople note what an engineer said on a call, or if calls are recorded with consent, share a handful. They show how replies really sound and which questions got an answer. When there are none, we write scripts from your application engineer's description and adjust after the first live calls.
The exhibition cards and visitor lists
Cards and badge scans from the last two shows tell us how many contacts were collected and what was done with them. They need not be sorted. If the lists have been lost, we plan the sorting method for the next show instead.
A rule on who may call a customer
Decide which accounts belong to the field salesperson, which to the inside team and which to a distributor. Without a rule, an engineer is chased by three people or by none. We write the rule on one page and attach it to the reminder.
A salesperson to try the scripts first
One willing person should use the new messages on live samples before the whole team does. Their changes to the wording are worth more than ours. If no one volunteers, we start with the sales head's own accounts.

How it works

How the follow up systems 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. 1

    Open the sample register and quote file

    We take the records of samples sent, quotations given and exhibition cards collected over the past year and mark, for each, what happened next and who did it. Gaps where nothing was done are counted, not judged. Together with your sales head we choose the stages where silence does the greatest damage, which for a sensor maker are after a sample and after a purchase team's quote.

  2. 2

    Decide what counts as won, lost or parked

    We agree the closing states with you: a sample that led to an order, a sample that failed the customer's test, a project dropped, a buyer who chose an import. Each needs a reason the salesperson can pick in a second. These reasons become the lost-reason log, and your engineers read it for what to fix in the product.

  3. 3

    Write the questions that open a reply

    For each stage we draft the message or call script. After a sample, the question is technical: did it mount, did the output match the controller, what did the bench show. For a quote, the message goes to the purchase contact and speaks of quantity and supply terms. Your application engineer reads each wording before it is used.

  4. 4

    Set an owner and a reminder for each sample

    Every sample gets a named person and a reminder that fires when a follow-up is due, entered in the sheet or the CRM you already use. We test it with a few live samples and watch whether the reminders are seen. Exhibition cards are sorted into those to call, those to email and those to leave, before the show ends.

  5. 5

    Practise the calls with the sales team

    We run the scripts with the salespeople, role-playing an engineer who is busy, one who has not opened the box, and one who has rejected the part. They change the wording until it sounds like them. The team agrees who calls and who writes, so that two people do not chase the same engineer.

  6. 6

    Read what happened to each sample

    We open the register and compare it with the starting count of samples with no next step. For each sample we look at whether it was followed up, what was said and what came back. You and your sales head decide which scripts to change, which stage to tighten and which lost reasons deserve attention in the product.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 2, qualification. The audit comes before it, and sales management keeps it running.

  1. 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.

  2. 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.

  3. 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.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

What should we say when we follow up on a sample?
Ask about the test itself: the application, the readings, any trouble with output or mounting. Offer an application engineer's help, and keep the message specific to the engineer's project so that it reads as a technical question and not a sales chase.
Should follow-up be automatic?
Reminders can be automatic, but the contact should come from a person who understands the sensor. Automated messages suit acknowledgements, not technical conversations.
When is it too early to ask about a sample?
Ask once the unit has arrived and a bench test is plausible, not on the day it ships. Engineers resent a call before they have opened the box, and the arrival check tells you when they have.
Who should make the follow-up call?
Whoever knows the sensor well enough to discuss the reading, the application engineer in most firms. A sales caller can open the door, but the technical question decides whether the trial moves.
How soon after a sample should we ask about it?
Ask when the engineer is likely to have had a chance to mount and test it, and that depends on the customer's own schedule, not on a fixed gap. The best way is to ask at dispatch: tell us when you plan to test it, and note that date as the reminder. If the engineer gives no date, your salesperson asks one technical question and sets the reminder from the answer. We do not fix an interval for you.
Should an automatic email chase every sample?
We advise against it for samples. An engineer who gets a standard chase email learns that nobody has read their application. A reminder that tells your salesperson to call, with the part, the application and the last thing said already on screen, is better. Automatic messages can still serve a limited purpose, such as confirming that a sample has been dispatched with a courier tracking reference, but the follow-up itself should be a person.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.

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.