Internet of Things

IoT product development, from the device to the app people use

Turn device readings into information people can act on. We build the software connecting devices, cloud services and user applications, including onboarding and device management. Firmware stays with your hardware team or a specialist; industrial and city networks have dedicated service scopes.

Cancel any week. Last week refunded if we didn’t blow you away. No hours tracked.

  • 100+ products shipped
  • 10+ years experience
  • No-Bullshit Guarantee

What do we build for IoT products?

Connectivity Choice

BLE, Wi-Fi, LTE-M, NB-IoT, LoRaWAN or a mix. We compare power budget, range, payload size, latency and running costs before a radio is fixed, then test the shortlist on real hardware in the places the device will live.

Device-to-Cloud Backend

MQTT or HTTP ingestion, per-device authentication, message schemas, and the decoders and encoders that turn raw payloads into clean data. We agree the message contract with whoever writes the firmware, so both sides test against the same definition.

Device Management

Provisioning, credentials and their rotation, remote configuration, fleet status and staged update rollouts. Planned in the first scope, because retrofitting them after launch means touching every device in the field.

Data and Apps

Storage, dashboards, alerts, and the web or mobile app your customers or operators actually use. Warehouse and reporting work that joins device data with business data is scoped as Data Engineering.

What can we build with you?

Connected Product with a Companion App

A device that pairs over BLE or Wi-Fi with a mobile app and reports to your cloud, with onboarding, user accounts and updates your support team can run.

Remote Monitoring of Field Assets

Battery-powered sensors on cellular or LoRaWAN that report status, with alerts and a dashboard for the people who act on them. City-wide sensor networks and metering are scoped under Smart City IoT.

Backend for Hardware You Already Sell

Devices that exist but lack a proper cloud side: ingestion, device management and an app built around the hardware as it is, so your hardware roadmap stays separate.

HOW WE DEVELOP SOFTWARE

How we develop Software

Five phases. Fixed prices. No lock-in.

Phase 01

Discovery Phase

Fixed 3.500€

Fixed price at 3.500€

Buy now
  • Requirements Engineering
  • Software Architecture
  • Milestone Plan
  • Technical Flows and Sequence Diagrams
  • Launch Plan and Milestone Plan

Phase 02

First Iteration

Fixed 15–20k€ max

Fixed price between 15–20k€ (MAX)

Book Discovery Phase
  • Building your real MAP (Minimal Awesome Product)
  • Cost-effective approach. Strip requirements to 15–20k max
  • Test directly on the market as cheaply as possible with real customers
  • Discovery Phase cost is deducted as a rebate

Phase 03

Subsequent Iterations

Agile Fixed Price

Fixed price packages / Agile Fixed Price

What is Agile Fixed Pricing?
  • Building and extending product based on real customer/user demand
  • Ideally partially funded by real sales
  • Data-driven development decisions (watch user behavior over user demands)
  • Continuous improvement cycle

Phase 04

Maintenance

Weekly retainer

Fixed weekly retainer 750€ / week, cancel anytime

Get in touch
  • Security patches (nobody likes data breaches or losing money)
  • Fixing bugs (can be a major reason of customer churn)
  • Technical support (most companies have an abysmal customer support)
  • Performance, cost & CI/CD optimization

Phase 05

Further Dev / Hand-Over

No lock-in, ever

Your product, your team. We’ll never lock you in.

  • We’ll never make you dependent on our team
  • Smooth transition to your internal team
  • Knowledge transfer and documentation
  • Continued support as needed
// proof

Proof, not promises

These are selected projects, not our full portfolio. We have shipped 100+ products since 2018.

What clients say

Google

Shipped what would normally take a bigger team a lot longer. Report overhaul, security hardening, infrastructure tightening, they owned it end to end. They kept production stable through pilot prep and investor demos. They communicated clearly and never made us chase a status update. Awesome team!

April Elias
Original
Trustpilot

TOP! Excellent teamwork and communication. Smooth and efficient collaboration. Highly recommended partnership!

Sabrina Heinzle
Original
LinkedIn

If you’re thinking about digitization of your company, tokenization, coding... you name it, I’d strongly recommend to get in touch with Kevin. His knowledge in the field is unparalleled and working with him a sheer pleasure as he is a super nice guy, strategic thinker and proactively hard worker. Thanks for your brilliant work Kev!

Jörg Mayr CEO, alpha strategies
Original

Independently rated 5.0/5 on Google Read the reviews

FAQs

IoT product development in practice

End any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you’re ever committed to is the current week.
It’s in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week.
Because hours are the wrong metric. If we optimize for hours billed, we do not optimize for your outcome. The deal is simpler: every week has a defined result, and we earn the next week by delivering it. You pay for progress against that result, not for a timesheet.
We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party’s systems, we say so, and if we can’t align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves.
The software above the firmware: choosing and testing connectivity, the device-to-cloud backend, payload codecs, device management, and the data, dashboards and apps on top. Two narrower offers sit next to this page. If you run a LoRaWAN network, metering or asset tracking for a city or utility, see Smart City IoT. If the devices are machines and controllers in a plant (MQTT, OPC UA, Modbus), see Industrial IoT.
We start from where the device lives and how it is powered. BLE fits when a phone or gateway is nearby. Wi-Fi fits when power and a site network are available. LTE-M and NB-IoT fit wide-area, low-power devices that can carry an operator contract. LoRaWAN fits small, infrequent payloads over long distances on battery, on your own or a shared network. MQTT is not a radio: it is the messaging protocol on top of the IP link, and it works over Wi-Fi or cellular alike. We test the shortlist on real hardware before anyone orders a production batch.
When latency matters (LoRaWAN delivers in seconds to minutes and downlinks only follow uplinks in narrow windows). When a payload exceeds roughly 50 to 200 bytes per message. When you need many-to-many messaging. When you need high duty-cycle telemetry (EU868 duty-cycle limits cap how often a device may transmit). For those cases: NB-IoT or LTE-M for low-power cellular, Wi-Fi when power is not constrained, Bluetooth Mesh or Zigbee for indoor mesh, MQTT over cellular for higher-bandwidth fleets. If LoRaWAN does fit and the network spans a city or a utility, Smart City IoT covers that work.
The one that fits your data residency, fleet size and tolerance for lock-in. We evaluate managed services from the large clouds (such as AWS IoT Core or Azure IoT Hub), open-source platforms such as ThingsBoard, and self-hosted MQTT brokers, and write down why one wins. Whatever the choice, provisioning, credential rotation, update rollout and fleet telemetry are in the first scope, not a version two problem.
We don’t write firmware. We write the decoders and encoders for your devices, define the message contract with your firmware team, build the infrastructure that ingests the data and handle everything on the application and monitoring side. If you need firmware written, we bring in a hardware specialist and agree the boundary in writing before the work starts.
Yes, that is the work. At IKB, Innsbruck’s municipal utility, we worked inside their Smart City build alongside IKB’s own team on infrastructure, devices and per-device codecs, against datasheets that did not always match the hardware, then handed the platform over completely. Read the IKB case study for what that covered. We write a decoder per vendor, normalize into one schema and monitor for vendors silently changing a payload format in a firmware update. The free LoRaWAN payload codec tester packages the offline fixture workflow we use for that.
Mostly the number of device types and vendors, whether the hardware already exists, the connectivity choice, the fleet size at launch, how deep device management has to go (staged updates, credential rotation, remote configuration), which apps users need, and which existing systems the data must reach. Hardware, connectivity contracts and network fees are quoted separately, so they do not surprise you in month three. We scope a first phase you can test on real devices before you commit to a rollout.
// Get to know us

Get to know us

Long-term relationships over quick wins.