IoT dashboard development for your fleet and your customers
Off-the-shelf IoT dashboards show readings; your customers want to see their sites, their devices, their alerts and their history under your brand. We build fleet, site and customer dashboards on top of your IoT platform or time-series store, with sign-in and roles for staff, customers and technicians, alert history, device health and data export. Because devices, data volumes and features vary, we scope the price after a free call, often starting with one customer view.
The problem
Why vendor consoles are not customer dashboards
Many IoT companies run their business on the platform vendor's console: fine for engineers, confusing for customers. Customers ask for reports by email, support screenshots charts and every new customer request becomes a custom export.
Rules are adding pressure: in the EU, connected products placed on the market from 12 September 2026 must be designed so users can access their data by default where relevant and technically feasible, and customers increasingly expect self-service export.
What we build
What our IoT dashboard development includes
Fleet view
Every device and gateway with status, last-seen time, battery and firmware, filterable by customer and site.
Customer and site views
Each customer sees only their sites, devices, readings and alerts, under your brand.
Alert and incident history
Alerts, acknowledgements and outcomes from your workflows, with timelines per site.
Roles and sign-in
Roles for your staff, customer admins, customer users and technicians, with single sign-on where needed.
Data export and API
CSV export and an API so users can access the data their devices produce.
Reports
Scheduled summaries by customer or site, such as weekly energy, uptime or excursion reports.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Data synced
Readings, device status and alerts sync from the platform or time-series store.
-
02
Automated
Views updated
Fleet, site and customer views refresh, scoped by role.
-
03
Automated
Reports sent
Scheduled reports go to each customer's chosen contacts.
-
04
Ops team review
Support uses it
Support and technicians work from the fleet view and incident history.
-
05
Engineer or ops lead decides
Access and data sharing
Who gets access to which customer data and any third-party sharing is decided by your ops lead and the customer.
How it behaves
How the IoT dashboard behaves
What the customer sees
- Their sites, devices and alerts under your brand
- History and scheduled reports
- Self-service data export
What your team sees
- A fleet view across every customer
- Incident timelines per site
- Fewer manual report requests
What the system does
- Syncs status, readings and alerts
- Scopes every view by role and customer
- Logs access and exports
Edge cases and fallbacks
- Data source delayed
- Views show the last good data with a timestamp.
- Customer user leaves their company
- Access is removed by the customer admin or your team.
- Very large export requested
- Prepared in the background and emailed as a download link.
- Platform API outage
- Dashboards fall back to stored history and show a status banner.
Architecture
An IoT dashboard for fleets and customers at a glance.
- Input
- Logic and services
- Output
- People
How it flows
- 1 Device status, readings and history come from your IoT platform and time-series store.
- 2 The dashboard API serves them with roles that decide who sees which customer and site.
- 3 Staff, customers and technicians use fleet, site and customer views, and users can export their data.
- 4 Your ops lead controls access and any sharing of customer data with third parties.
Project planner
How the project runs, phase by phase.
IoT dashboards for fleets & customers project plan
Typical time to launch: about 11 weeks, then support
-
01
Discovery
1 to 2 weeks
Users and roles, data sources, volumes and the views customers ask for.
-
02
Architecture and design
1 to 2 weeks
Data access, roles, wireframes and branding.
-
03
Build
4 to 6 weeks
API, sign-in, fleet, site and customer views, export and reports.
-
04
Pilot
About 2 weeks
One or two customers using it, with data accuracy checks.
-
05
Rollout
About 1 week
Invite remaining customers and hand over run books.
-
06
Support
Ongoing
New views, device types and reports.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Privacy and consent
Rules we design for, with the sources.
EU: data access by design
Connected products placed on the EU market from 12 September 2026 must be designed so users can access their data by default where relevant and technically feasible; export and API access support that.
Source: www.matheson.comEU: user data rights
The EU Data Act, applying from 12 September 2025, lets users access the data their connected products generate and share it with third parties such as repair providers.
Source: digital-strategy.ec.europa.euAccessibility
We build to WCAG 2.2 AA so customer users with assistive technology can read dashboards and reports.
Source: www.w3.orgFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 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 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 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 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
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
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
IoT dashboards for fleets & customers questions, answered.
Device and gateway status, last-seen time, battery, firmware and recent alerts for staff; sites, readings, alert history and reports for customers. We design each view around what that user acts on.
Vendor consoles are built for engineers. A custom dashboard gives customers a branded, scoped view, combines data from your workflows and supports export and reports. Where Grafana panels fit, we embed them rather than rebuild.
Yes. We can add IoT views to an existing Laravel or Python app, or build a separate dashboard that shares sign-in.
Through CSV export and an API scoped to their account, which also supports EU Data Act access expectations.
Yes, when history lives in a time-series database and the dashboard reads aggregates. We size it for your device count and reporting intervals.
Customer sign-ins, report requests that no longer reach support, time support spends finding device history and dashboard load times.
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.
More for iot & connected devices
All servicesIoT CRM: trials, activations & fleet accounts
Link trial signups, device activations and fleet size to one CRM, flag accounts whose devices go live, automate follow-ups and keep every customer record tied to the devices they actually run.
From $1,000 · About 4 weeks Details
Sensor alerts to tickets & on-call SMS
Turn threshold breaches from your IoT platform or MQTT broker into one ticket per real problem, text the on-call technician from your rota, escalate if nobody acknowledges and log every step.
Scoped after a free call · About 6 to 9 weeks including a pilot Details
Offline device & gateway monitoring
Compare every device and gateway with its expected reporting interval, catch silent devices before customers do, separate gateway outages from single devices and open a ticket or customer notice with history.
From $1,000 · About 4 weeks Details