Fixed quote after a free call

IoT CRM automation that knows which devices each customer runs

Connected-device companies sell in a way most CRMs do not expect: a trial kit ships, devices get activated weeks later, and the real buying signal is a fleet coming online. We connect your website forms, order system and device platform to one pipeline in HubSpot or the CRM you use, flag accounts whose devices go live, automate follow-ups and keep each customer record linked to the devices they run. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why IoT companies lose track of pilots

An IoT sale often starts with a pilot: a handful of sensors shipped to one site. Whether the customer activates them, how many report data and whether the pilot site expands are the signals that matter, and they live in the device platform, not the CRM.

Sales and support then work from different lists. Sales does not know a pilot went quiet; support does not know an account is mid-negotiation when its gateway fails. Customer success finds out about expansions or churn last.

What we build

What our IoT CRM automation includes

One pipeline for every enquiry

Website forms, trial requests, distributor leads and trade show lists flow into one CRM pipeline, matched by company domain.

Device activation signals

Devices claimed, first data received and active device counts written to the account from your IoT platform.

Pilot health alerts

Sales and success alerted when a pilot goes live, stalls or expands, with device counts attached.

Stages for hardware deals

Enquiry, trial shipped, pilot live, proposal, rollout and renewal, matched to how you sell.

Follow-ups with stop rules

Setup help after a trial ships and check-ins during the pilot, stopping when devices are live or the customer replies.

Fleet and revenue report

A weekly email with pilots live, active devices by account and pipeline by stage.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry or order

    A form, trial request or order creates or updates the account in the CRM.

  2. 02 Automated

    Devices linked

    Device activations and active counts are linked to the account each day.

  3. 03 Automated

    Signals flagged

    Pilots that go live, stall or expand trigger alerts to the account owner.

  4. 04 Ops team review

    Account owner acts

    The account owner checks in, helps with setup or prepares the rollout proposal.

  5. 05 Engineer or ops lead decides

    Pricing and contract

    Fleet pricing, service levels and contract terms are decided by the founder or sales lead.

How it behaves

How the IoT sales pipeline behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • Setup help after a trial kit ships
  • A timely check-in when the pilot goes live or stalls
  • A rollout proposal based on how their devices are used

What the team sees

  • Accounts with linked devices and activation status
  • Alerts for pilots that go live, stall or expand
  • A weekly fleet and pipeline report

What the automation does

  • Matches enquiries, orders and devices to accounts
  • Writes activation and active counts daily
  • Sends follow-ups with stop rules

Edge cases and fallbacks

Device activated under an unknown account
Flagged for a person to match; nothing is guessed.
Pilot devices go offline together
Passed to the offline monitoring workflow and the account owner.
Distributor and end customer both enquire
Linked under one account with the distributor noted.
CRM or platform API unavailable
Updates are queued and retried, and the team is alerted.

Architecture

An IoT sales and fleet pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Forms and orders Trials, enquiries IoT platform Activations n8n Match and update CRM Accounts, devices Pilot alerts Live, stalled, grow Account owner Follows up
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Trial requests, orders and enquiries arrive with device activation data from the IoT platform.
  2. 2 n8n matches them to the account and updates the CRM with active device counts.
  3. 3 Pilots that go live, stall or expand alert the account owner with context.
  4. 4 The account owner follows up; pricing and contracts stay with the sales lead.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

IoT CRM: trials, activations & fleet accounts project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, order flow, how devices map to accounts and what the sales stages are.

  2. 02

    Design

    2 to 3 days

    Account and device matching, signals, follow-ups and report contents.

  3. 03

    Build

    1 to 2 weeks

    Form and order capture, device activation sync, alerts, follow-ups and report.

  4. 04

    Shadow run

    About 1 week

    Alerts go to a test channel and are checked against real accounts.

  5. 05

    Launch

    1 to 2 days

    Switch on and walk sales and success through the pipeline.

  6. 06

    Support

    Ongoing

    New signals, stages and products.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HubSpot CRM API or your CRM Your IoT platform API (AWS IoT Core, ThingsBoard, Particle) Your order or e-commerce system Slack or Microsoft Teams Your email provider

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Sources, device matching, signals and stages.

    $200 – $400

  • Build

    Capture, activation sync, alerts and follow-ups.

    $500 – $1,300

  • Integrations

    CRM, IoT platform, orders and chat.

    $150 – $400

  • Testing and shadow run

    Alerts checked against real accounts.

    $100 – $250

  • Launch and training

    Switch-over and team walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM, IoT platform and n8n subscriptions are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM: Your CRM vendor's own plan.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: commercial email rules

Trial follow-ups must include a postal address and honor opt-outs within 10 business days under CAN-SPAM, which has no exception for business-to-business email.

Source: www.ftc.gov

UK: electronic marketing

PECR regulation 22 restricts unsolicited marketing email to individuals; consent and opt-out flags travel with each contact.

Source: www.legislation.gov.uk

EU and UK: processors under contract

Your CRM and automation host process customer data on your behalf, so GDPR Article 28 processor contracts are needed.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

IoT CRM: trials, activations & fleet accounts questions, answered.

Linking each account to the devices it runs. Activation dates, active device counts and pilot status tell sales and success far more than email opens.

Usually, through the platform API or an event webhook: AWS IoT Core rule actions can post to an HTTPS endpoint, Particle webhooks fire on device events and ThingsBoard has a REST API for devices. We confirm the route for yours.

Yes. Support sees the same account with its devices and open deals, and the AI support agent can read the CRM record before opening a ticket.

Yes. Accounts can carry a distributor field, and distributor leads can follow their own stages and reports.

HubSpot suits most small hardware companies and has a documented API. If you already use another CRM, we automate that one.

Trials shipped, pilots live, time from shipment to first data, pilots that expand and active devices per account.

Free 20-minute call

Want this for your iot & connected device?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call