Skip to content
GullySales

Electronic component manufacturers · Follow up systems

Call the engineer after the sample lands, because that is when the design decision forms.

A follow-up system for a component maker is the set of agreed calls and messages that carry a sample or quote through to a design-in and an order. GullySales writes the steps, the owners and the reminders so no sample goes quiet.

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

A distributor shows electronic components to a customer

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 electronic component manufacturers

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

  • “A sample without a call is a gift”

    The engineer receives the part, tests it when time allows and picks whatever worked first. If your team does not ask how the test went, the decision is made without any word from you.

  • “Design cycles are long, so reminders must be too”

    An engineer may not decide for a long time. A system built on a few early chasers gives up before the board is ready. The reminder needs to follow the project date, not a fixed gap.

  • “Quotes to purchase need a different follow-up”

    A purchase manager asks about price, lead time and terms. The follow-up asks about the approval step and the next order date, and goes to a different person.

  • “Distributor leads need a loop back”

    When a counter passes an enquiry, nobody tells the maker whether it closed. A simple request for an outcome after the quote keeps the information flowing.

What we do

What we deliver for electronic component manufacturers.

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

  1. Follow-up map by stage

    The call or message for each stage from sample sent to scheduled order, with an owner for each.

    Result: Every open project has a next step and a name.

  2. Reminder rules tied to project dates

    Reminders set against the engineer's stated build or review date.

    Result: Calls land when a decision is near.

  3. Call scripts and message templates

    Short scripts for the post-sample call, the quote follow-up and the approval check.

    Result: Different team members ask the same useful questions.

  4. Lost and stalled review

    A short list of projects gone quiet, with a reason and a decision to revive or close.

    Result: Dead projects stop hiding in the pipeline.

  5. Distributor outcome request

    A standard note asking the distributor what happened to an enquiry.

    Result: Channel results come back to your records.

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

Time each call to a point in the design cycle.

Sample delivered
Call to confirm the part arrived and ask who will test it. Record the tester's name and the date they plan to start.
Test results pending
Ask what the engineer measured and whether anything failed. Enter the finding, since a failed test is a lead for a different part.
Prototype approved
Ask about the build plan and the expected quantity, and pass the contact to the purchase side with a short introduction.
Quote sent to purchase
A different call to a different person, about lead time, minimum order and second source, recorded under the same project.
Distributor lead returned
Ask the distributor for the outcome of each lead you passed, so your records show whether it became a design-in.

Who it is for

This is written for these electronic component manufacturers.

  • Capacitor and resistor makers
  • Connector, terminal and cable assembly makers
  • Transformer, inductor and magnetics makers
  • Relay, switch and contactor makers
  • Crystal, oscillator and filter makers
  • Sensor and thermistor element makers
  • Fuse, surge protection and circuit protection component makers
  • Semiconductor packaging and assembly units

Before you decide

When this may not be the right fit.

  • Nobody on the team owns the sample follow-up, and a schedule of calls would produce missed dates.
  • Your projects run on cycles you cannot yet describe, and reminders set at random would annoy engineers.
  • The engineer has asked you not to call, and the contact route they named should be used instead.

Before you decide

Agree the work. Know how to judge it.

Follow-up systems for electronic component makers: 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 electronic component manufacturers. Anything missing is noted in the written scope, with who will supply it.

The list of samples sent last season
Part, recipient and date, with any note of what followed. The review of lost samples depends on it. If it is missing, the comparison begins from the first sample under the new routine. A list in a spreadsheet or a stack of dispatch slips is acceptable, and we sort it with your team.
Each engineer's next project date
Where the engineer has told your team the date of an evaluation or build, the date is recorded. Reminders follow these dates. When none are known, the first call must ask for one.
A named owner for every stage
The person responsible for the call at each stage, with a deputy for absences. A stage without an owner fails quietly. If there are too few salespeople, the stages are merged. Where one person covers a whole region, the plan names a deputy for the periods when that person is travelling.
Your quote and sample cover notes
The messages that go with a quote or sample today. We improve them instead of starting again. If there are none, we draft from scratch with your sales engineer. Messages written by different salespeople are all welcome, since we compare their wording to find the tone that fits your customers.
The distributor contact for each lead
The person at the distributor who received each lead you passed on. The outcome request goes to them. If unknown, you ask the distributor to name one.

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

    Read the samples that never became orders

    We list the samples sent in the last season and mark which led to a design-in, which stalled and which were never followed up. Your sales engineer says what was done after each dispatch. The list shows where a call would have mattered. We also mark which engineers were never called after the dispatch, and which were called by someone who has since left, because those samples are the easiest to recover.

  2. 2

    Set the stages and the calls tied to them

    We write the stages of a design-in, from sample received to board validated, and assign each a call or message and an owner. The sales head approves who is responsible at which stage. The stages also record who at the customer is expected to act, so a sample waiting on the quality team is followed up with that team and not with the design engineer.

  3. 3

    Link reminders to the project dates

    Design cycles are long, so reminders follow the engineer's own dates, such as the evaluation review or the prototype build, not a fixed interval. We ask each engineer for the next date during the call and record it. A project with a prototype build coming is followed up near that build, with a question on whether the part has arrived at the right place on the bench.

  4. 4

    Write the scripts and message templates

    We draft the post-sample call, the quote cover note and the purchase follow-up, each in plain words and each asking one question. Your salespeople rewrite lines that sound unnatural. The purchase follow-up asks about approved-vendor status and the forecast the buyer is working to, and avoids repeating a pitch the engineer has already heard.

  5. 5

    Close the loop with distributors

    We write the request that asks a distributor for the outcome of each lead you passed, and agree who sends it. You see which leads came back with an answer and which are still unknown.

  6. 6

    Review stalled projects against the starting list

    After the routine has run, we compare the projects moved, stalled and lost with the sample list from the first step. You decide which stalled projects to close and what each follow-up should change. We also read which reminders were ignored, and remove those from the routine so the remaining ones are taken seriously.

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.

How often should we chase an engineer?
We set the timing from the engineer's own schedule and the part's role, not a fixed rule. A reminder after a design review date works better than a blind call.
What if the engineer stops replying?
Log it, try the purchase or quality contact, and set a later reminder. If nothing comes back, close the project with a reason so the data is honest.
Who should own the follow-up?
Whoever holds the relationship with the engineer, backed by a reminder everyone can see. We name the owner for each stage so nothing depends on memory.
What if the engineer stops replying?
Try the purchase contact or a colleague named on the sample request, and send a brief message offering the test data. Design cycles stall for reasons unrelated to your part, such as a changed brief. Record the silence and the last known stage, then return when the project would move.
How do we follow up without annoying a busy design engineer?
Make each contact useful and tied to something they said. A call after a sample arrives that asks whether it reached the right person and whether they need a test report is welcome. A nudge that just asks for a decision is not. We write each message around one helpful point, such as a datasheet revision or a drawing, and one question. If the engineer asks you to wait until a date, record it and respect it. Silence after that date is the cue to ask once more.
What should happen when the engineer moves to another company?
Record the move, keep the old project open for the colleague who takes over, and ask your contact whether they will be designing parts in the new company. The new role is a fresh lead, tied to the engineer's name. Do not lose the history. We add a field for former employer so the trail is visible. Your sales engineer decides whether to approach the successor at the old company, which begins with the purchase contact.
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.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
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.

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.