Skip to content
GullySales
Tell us what you need

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.

Tell us what you needor call +91 80958 58589

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

Realistic editorial illustration of software development companies at work in India

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 IoT companies

Sales and marketing for IoT companies, the overview.

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.

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

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

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

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

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

Read the full CRM implementation and customisation page

Fields worth keeping

Keep one record per site, not one per contact.

Site type and city
Filled in by the caller at first contact. It lets you plan survey trips by city and see which kinds of site convert.
Loss named by the owner
Typed in the owner's words by the sales person. It decides the device sheet and is the first line of the pilot proposal.
Number of assets
Added after the survey by the engineer. It separates a single-unit pilot from a fleet rollout when you forecast work.
Approver and blocker
Added by the sales person after the survey, naming who signs and who may object. It shows where a stalled pilot is stuck.
Recurring fee agreed
Filled in when the pilot is signed, so support and finance see the same fee the owner was quoted.

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

Not for

It is not the right fit if.

  • You have fewer than a handful of live prospects, where a shared sheet is easier to keep honest than a CRM nobody opens.
  • Nobody owns data entry after a survey, so the record would show a first call and nothing that followed.
  • Your device platform already holds each client's sites and you have not decided which system is the master, which would leave two records that disagree.

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

    Map the sales process

    We sit with the people who sell and write down how a deal moves from enquiry to payment, including where it stalls.

  2. 2

    Agree stages, fields and owners

    Each stage gets a name your team already uses and a proof that the deal has left it. We agree which fields are required at which stage, and who may change what.

  3. 3

    Build on a copy

    Pipeline, fields and views are built on a trial copy where the CRM offers one, or in a separate pipeline where the plan allows. Live work stays untouched.

  4. 4

    Connect channels, then switch on automations

    Channels are connected first. Each automation is then switched on separately, so a misfiring rule is easy to find.

  5. 5

    Test with real deals

    The people who will use the CRM run open deals through it. Gaps are fixed before the whole team switches over.

  6. 6

    Switch over and trim

    Once real use shows which fields stay empty and which stages nobody uses, those are cut and the handover record is updated.

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.

  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

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

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

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.

Tell us what you need
Which CRM should we use?
Use one the team will open every day, whether a common Indian tool or a spreadsheet to begin with. GullySales designs the fields and stages first, then fits them to the tool. A well-kept sheet beats a costly system nobody updates.
Can the CRM connect to the device platform?
Sometimes, through the platform's own export or integration. Check what your platform offers. GullySales can plan which fields would be shared, and any integration work is a separate technical task with your platform team.
Who should have access to client data?
Give each person the records they work on and no more. Personal contact details of client staff are held only for the purpose of the relationship. Check your own data obligations with your adviser.
Should installations from the device platform be copied into the CRM?
Copy only what sales needs: the site, the number of units and the support contact. The platform stays the master for device data. A second full copy goes out of date and the two systems start to disagree about who the client is.
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.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

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.

Tell us what you need