Sensor manufacturers · CRM
Keep one record from first sample to repeat volume order, with a name against each step.
A CRM for a sensor manufacturer is a shared record of every OEM, distributor and enquiry, built around the sample stage. GullySales sets up the stages, fields and habits so that no sample is sent without a next step noted.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Also for sensor manufacturers
- Lead generation for sensor manufacturers
- Follow-up systems for sensor manufacturers
- SEO for sensor manufacturers
- Social media marketing for sensor manufacturers
- Content marketing for sensor manufacturers
- Buyer personas for sensor manufacturers
- WhatsApp marketing for sensor manufacturers
- Digital marketing for sensor manufacturers
Sales and marketing for sensor manufacturers, the overview.
Last updated 14 Nov 2026.
For sensor manufacturers
Where it usually goes wrong, and what we would do.
“The sample is a stage in its own right”
A sensor sale moves through enquiry, sample sent, bench test, trial order and volume order. A general sales pipeline hides the sample stage, which is where the choice is made and where the longest wait happens.
“One OEM has several people”
At a pump maker, an engineer tests, a purchase manager buys and a quality head approves documents. A record kept per person loses the account. A record kept per company, with each person's role, shows who has been told what.
“Distributors and OEMs are linked”
A small OEM may buy through a stockist. If the stockist's record and the OEM's record are separate, you cannot see that the distributor's counter is where your application notes should be.
“Custom enquiries need their own fields”
A non-standard sensor request carries range, environment, volume and project stage. If those details sit in an email chain, the costing is rebuilt from memory every time.
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.
Pipeline stages built for samples
Stages running from enquiry to repeat order, with a required next step at the sample and test stages.
Result: Every open sample appears with a next step and an owner.
Sample register
A record of each unit sent: recipient, application, quantity, date and the test outcome once known.
Result: You can list the samples that have no test result yet.
Account records for OEMs and distributors
Company records holding each contact's role and links between a distributor and the OEMs it serves.
Result: A glance at an OEM shows its people and its stockist.
Custom enquiry fields
Fields for range, environment, volume and stage, matched to your requirement sheet.
Result: A custom enquiry is quoted from written details.
Source field and review view
A source on each enquiry and a saved view of enquiries, samples and orders by source.
Result: You can see which source led to which orders.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
The fields that tie a sample unit to a project and then to an order.
- Sample sent, with unit serial
- Filled by dispatch. Lets you trace a returned unit to its batch and show the buyer which one they tested.
- Application and end product
- Filled by the engineer on the first call. Lets sales group buyers by use and write notes aimed at each.
- Trial result and date
- Filled when you call back after the bench test. It shows which samples converted and which stalled.
- Quoted lead time and price validity
- Filled by sales. Stops two people giving a purchase manager different dates.
- Distributor or direct
- Filled at entry. Shows which stockist brought which OEM, so referrals are recognised.
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.
- Your engineers hand-write sample details in a notebook that nobody else reads, so a system would start with no habit of entry.
- You have too few enquiries to need a system yet, and a shared spreadsheet would hold them cleanly.
- You want the system to replace the application engineer's judgement, which it cannot do.
Before you decide
Agree the work. Know how to judge it.
CRM for sensor manufacturers: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
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 current contact sheets and email lists
- We need every place where OEM, distributor and enquiry names are kept now, including the sales engineer's own file. They can be in poor order. We merge and clean them with you, and what is not cleaned is left in an archive rather than loaded as noise.
- A list of who sends samples and how
- Please tell us who packs, who dispatches and who records a sample, and where that record sits today. The register must match your real practice. If the stores issue slip is the only record, we build the register around it so a sample line is created when the slip is made.
- A decision on who may see customer drawings
- Customers send drawings and requirement sheets that are confidential. You decide whether the CRM stores them, links to a protected folder, or holds only a reference number. Without a rule, files end up in places that anyone can open, so we default to a reference.
- A named owner for the CRM
- One person must be able to add a user, change a field and close an old stage. This is a sales coordinator in a typical firm. If nobody holds it, changes stop being made, people create their own columns, and the setup drifts back to separate sheets.
- Your custom sensor request format
- Whatever form a custom requirement arrives in today, whether a customer's specification sheet or an email, we need examples. They show which fields the CRM must hold. Where none exist, the custom fields are kept short and extended after the first few real requests.
How it works
How the CRM 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
Map the road from enquiry to order
We sit with the sales engineer and draw the actual journey of a sensor sale on one sheet: enquiry, datasheet sent, sample sent, bench test at the customer, quotation, trial order, regular order. You mark where distributors enter and where custom requests branch off. This sheet decides the stages in the CRM, and nothing is built that does not appear on it.
- 2
Set stages, fields and the sample register
We configure the pipeline with a stage for the sample and a rule that no sample is shown as sent without a next step and an owner. Fields hold the part number, application, project stage, expected volume and source. The custom enquiry form gets its own fields for range, tolerance and quantity. You review each field and cut those nobody will fill.
- 3
Decide where the trial runs first
We agree whether to try the setup on a copy before real records go in, and with which sales engineer. The test copy holds a small set of real OEMs and distributors, including one with several contacts. You decide which existing data is loaded and which stays behind in the old sheets, so that the CRM does not start full of dead names.
- 4
Connect forms and check the rules
The website sample form, the enquiry mailbox and the distributor referral link are connected, and we test each with a dummy entry. We check that a new enquiry gets a source, that a sample creates a register line, that duplicates are flagged and that an OEM and its distributor are linked. Faults are fixed before any salesperson sees the system.
- 5
Run the sales team through real cases
We sit with the salespeople and enter three or four live cases, including a custom enquiry, as they would on a normal day. They tell us what is awkward, and we change the labels, order of fields and views. Your sales head signs off the setup only after the people who must use it have used it.
- 6
Hand over and read it against the old way
On the day you switch, the old sheets are closed to new entries and one person is named as owner of the CRM. After a fair period of use, we read the register against the enquiry and sample counts recorded before, looking for samples with no next step, orders with no source and enquiries that were never answered.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
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
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
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.
Which CRM should we use?
Do we need to load all our old contacts?
Should customer drawings be stored in the CRM?
How do we record a custom sensor enquiry?
Do the distributors need logins to the CRM?
What happens to the notes our salespeople keep in their own diaries?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for sensor manufacturers
Related work to consider.
Closest to this: leads and follow-up
Also for sensor manufacturers
Or start from the overview: sales and marketing for sensor manufacturers.
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.