Which technologies do you consult on?

All of the major location, identification and IoT technologies: RTLS (UWB, BLE, Wi-Fi), RFID (passive, active and RAIN UHF), industrial IoT and sensors, GPS and GNSS, AGV and AMR robot fleets, and hybrid stacks that combine them. We recommend the right mix for each zone and use case, not a single technology.

Are you really vendor-neutral?

Yes. We do not sell hardware or a software platform of our own, and we take no resale commissions, so our technology and vendor recommendations serve your outcome rather than a product we need to move.

Do you work outside the UK?

We are UK-based and work across Europe and internationally, delivering in English, German and French. Engagements can be remote or on-site depending on the work.

What does a consulting engagement include?

Typically discovery and requirements, vendor-neutral technology selection, vendor evaluation and RFP support, ROI and business case, solution architecture, and an implementation roadmap. We scope each engagement to where you are.

Can you help after the decision is made?

Yes. We work across the full lifecycle - we can also deploy, integrate, and operate the system, so you can keep one independent team from business case through to live operation.

How do we get started?

Usually with a short call or a fixed-fee discovery to scope the problem, followed by a proposal with clear deliverables, timeline and fees. There is no obligation and no platform pitch.

Do you take fees or commissions from carriers or vendors?

No, ever. Our fees come from clients only. See /about/independence for the full policy and public commitments.

Do you run LoRaWAN deployments end-to-end, or just advise?

Both, depending on engagement. We run end-to-end (scoping, vendor management, deployment, integration handover) for clients without internal IoT capability. We advise alongside internal teams for clients building capability.

Can you work with our existing LoRaWAN partner?

Yes, often. We work alongside your existing integrator, carrier or platform partner as the independent advisory layer. Vendor-neutral by design.

How long is a typical LoRaWAN engagement?

Scoping engagement: 4–8 weeks. Pilot: 8–12 weeks. Production deployment: 12–24 weeks depending on scale. Many clients engage us across multiple stages.

Do you cover NB-IoT / LTE-M as alternatives?

Yes — see /insights/lorawan-explained for the LoRaWAN vs cellular IoT comparison. We help clients choose between LoRaWAN, NB-IoT, LTE-M and hybrid stacks during stage 1.

SERVICE · AVIS LORAWAN

Le conseil LoRaWAN — indépendant, neutre envers les fournisseurs.

We advise enterprises on LoRaWAN — feasibility, network choice (public vs private vs hybrid), device selection, integration, deployment and managed-services partner selection.

Independent, no commissions or kickbacks, our fees come from clients only. If you're scoping a LoRaWAN deployment and want a vendor-neutral second opinion, this is what we do.

Réservez un appel de 30 minutes pour le périmètre

Ce que nous faisons lors d’un engagement LoRaWAN

Three stages, mapping to /method. Stage 1 — Scope, architect, cost: use-case validation, predictive RF coverage modelling, public vs private vs hybrid network choice, gateway and device sizing, integration architecture, 5-year TCO.

Stage 2 — Pilot: vendor-neutral pilot design, success criteria, validation against accuracy / battery-life / coverage targets in production environments.

Stage 3 — Production rollout: full deployment plan, vendor management, integration with enterprise systems, handover to managed-services partner.

We work with public carriers (Orange, Bouygues, KPN, Senet, Everynet), private network platforms (Actility ThingPark, The Things Industries, ChirpStack) and devices across the LoRaWAN ecosystem.

Cas d’usage que nous couvrons

Outdoor asset and returnable-container tracking: containers, livestock, plant equipment, vehicles. Hybrid LoRaWAN + GNSS designs (Semtech LR1110 / LR2021) for multi-year battery life.

Agriculture and farm sensing: soil moisture, livestock health, equipment location across hectare-scale fields.

Smart-city infrastructure: parking, waste, environmental, lighting. Remote equipment monitoring: utility / oil-and-gas / energy network sensors.

Industrial telemetry: factory ambient and process sensors, tank levels, run-hours. Building and facility management: occupancy, temperature, air-quality, restroom and meeting-room utilisation.

Public, privé ou hybride

We don't have a default answer — it depends on use case, geography, security posture and economics. Public LoRaWAN for assets that move across regions where carrier coverage exists.

Private LoRaWAN for sensitive in-site applications (defence, regulated industries, large factories). Hybrid for distributed enterprises with both. See /comparisons/public-vs-private-lorawan for the deeper treatment. We model both economics and architecture in stage 1.

Sélection des dispositifs et silicium

Semtech dominates LoRa silicon. Their LR1110 (with GNSS sniffing) and LR2021 (with GNSS + Wi-Fi sniffing) chips enable hybrid LPWAN-positioning at multi-year battery life — a game-changer for outdoor asset tracking.

We help clients evaluate devices across the LoRaWAN ecosystem (Adeunis, Abeeway, Browan, Dragino, Elsys, Kerlink, Multitech, Tektelic, Yabby) for fit to specific use cases.

Architecture d’intégration

LoRaWAN deployments connect to enterprise systems via the network server — REST, MQTT, AWS IoT, Azure IoT, Google Cloud IoT integrations are mature.

We design integration patterns into WMS, ERP, IWMS, BMS, asset-management and ITSM systems. See /integrations for our enterprise patterns and /comparisons/public-vs-private-lorawan for network architecture detail.

Pourquoi nous engager plutôt que le facteur ou le fournisseur ?

Carriers and vendors will tell you their option is the right one. We don't have that bias — our fees come from clients only and we have no economic stake in the network choice or device selection.

We've advised enterprises on deployments ranging from 50-device pilots to 50,000-device rollouts; we know where the costs and pitfalls are. See /about/independence for our independence policy.

FAQ

Questions fréquemment posées

Acceptez-vous des frais ou des commissions auprès des transporteurs ou des fournisseurs ?

Non, jamais. Nos honoraires proviennent uniquement des clients. Voir /about/independence pour la politique complète et les engagements publics.

Est-ce que vous exécutez les déploiements LoRaWAN de bout en bout ou vous donnez-vous juste des conseils ?

Les deux, selon l’engagement. Nous gérons un processus de bout en bout (cadrage, gestion des fournisseurs, déploiement, transfert d’intégration) pour des clients sans capacité interne IoT.

Nous conseillons aux côtés des équipes internes pour développer leurs capacités des clients.

Pouvez-vous collaborer avec notre partenaire LoRaWAN actuel ?

Oui, souvent. Nous travaillons aux côtés de votre intégrateur, opérateur ou partenaire de plateforme existant en tant que couche de conseil indépendante. Neutre envers les fournisseurs par conception.

Combien de temps dure typiquement un engagement LoRaWAN ?

Définition de l’engagement : 4 à 8 semaines. Pilote : 8 à 12 semaines. Déploiement en production : 12 à 24 semaines selon l’échelle. De nombreux clients nous font appel à plusieurs étapes.

Couvrez-vous NB-IoT / LTE-M comme alternatives ?

Oui — voir /insights/lorawan-explained pour la comparaison entre LoRaWAN et cellulaire IoT. Nous aidons les clients à choisir entre les stacks LoRaWAN, NB-IoT, LTE-M et hybrides lors de la première phase.

Dernière mise à jour : 26 mai 2026