IoT companies · CRM
Keep one record per site, from first call through pilot to rollout.
A CRM for an IoT company holds the owner, the site, the loss, the survey, the pilot and the rollout in one place, along with the installer who introduced the lead. GullySales sets up the fields and stages and trains the team to keep them current.
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.
Last updated 18 Oct 2026.
For IoT companies
Where it usually goes wrong, and what we would do.
“The account is a site, not only a company”
A transport firm with three depots is three surveys and maybe three pilots. A record kept only at company level loses which depot is at which stage, and who at that depot answered the last call.
“Device and contract details belong in the record”
When a sensor goes offline, support needs the model, the mounting date, the battery change history and the pilot terms. If those live in separate sheets, the person on the phone cannot answer on the spot.
“Pilot outcomes are the data worth keeping”
A pilot that ended with no rollout holds the reason: price, power access, a manager who left. Without a field for that reason, the same stall repeats across accounts and nobody sees the pattern.
What we do
What we deliver for IoT companies.
Every deliverable, what it covers for you, and the result it is there to produce. Nothing here is an extra.
Stage design
Stages for enquiry, qualifying call, survey, pilot, rollout and support, each with a clear exit rule.
Result: Every lead sits in one stage and the team agrees what moves it on.
Site and device fields
Fields for the site address, setting, number of assets, devices installed and mounting date.
Result: A support caller sees the installed devices on one screen.
Source and introducer tracking
Fields recording where the lead came from and which installer or dealer introduced it.
Result: Each lead carries its source from the first entry.
Pilot result log
A required reason field when a pilot closes without rollout.
Result: Stalled pilots show their reasons in a list the team can read.
Team training notes
A short guide for the sales and support staff on what to record at each call.
Result: New staff know which fields to fill and when.
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.
Who it is for
This is written for these IoT companies.
- Fleet and vehicle tracking providers
- Cold chain and temperature monitoring specialists
- Smart energy and electricity metering firms
- Water, borewell and tank level monitoring providers
- Industrial machine monitoring and condition sensing firms
- Agriculture sensing and irrigation control providers
- Smart building and access automation integrators
- Asset and container tracking firms
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 sales process
We record how a deal actually moves from enquiry to close in your business today.
- 2
Configure stages and fields
The CRM's pipeline and fields are built to match that process exactly, not a generic template.
- 3
Set up automations
Reminders, assignment rules and follow-up triggers are configured so routine steps happen without manual effort.
- 4
Test with real deals
We run the configuration against actual current deals to catch gaps before the whole team relies on it.
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?
Can the CRM connect to the device platform?
Who should have access to client data?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What if we are not happy with the work?
More for IoT companies
Everything else we would do for you.
Closest to this: leads and follow-up
Also for IoT companies
Or start from the overview: sales and marketing for IoT companies.
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.