IoT applications tailored to the client

Your product with a mobile app. An admin panel for the manufacturer. 12,000 users connected in the first phase.

Manufacturer of boilers, air conditioning, lighting, machines, controllers? Your product physically works, but the customer has no way to manage it from their phone. KG Electronics (25 years on the market) commissioned us an application - the effect from a case study: customers come back calling "the one with WiFi".

12,000 connected devices at KG Electronics
1,000+ app downloads on Google Play
8 weeks / 3 months MVP / Full implementation with integrations

Four signals that your product needs an app

If you recognize at least two of these—it makes sense to discuss a custom IoT application.

01

The competition sells "the Same product with an app"

A customer in a store asks the salesperson about Wi-Fi, not the price. Your product is dropping in the rankings among distributors because it "doesn't support" it. Your competitor's brand is winning, even though your device is technically superior.

02

The hardware already has the data—no one can see it

The controller sends telemetry data, but the data isn't being recorded anywhere. The support team learns about the malfunction from a customer complaint, not from an alert. The manufacturer doesn't know how customers are actually using the device.

03

You're scaling your product for Western markets

Customers in foreign markets expect the application as a standard. Without a software layer, the conversation ends with a leaflet instead of an order.

04

The software company we've been working with hasn't developed software for that hardware

IoT is not an ordinary application. OTA updates, network errors, energy efficiency, fail-safe modes - without experience with hardware, the application only works in laboratory conditions. It's raining outside.

A video from our visit to KG Electronics

Real customer, real faCTOry, real product. Not a portfolio of mockups.

Full post at LinkedIn JSON Crew.

Five implementation phases. 30/30/30/10 timeline.

A clickable prototype in a test environment before we write a single line of production code. Payment in four installments.

1

Week 1

Exploration

A map of your device's protocols (ModBus, MQTT, manufacturer-specific protocol), a list of integrations (ERP, service providers, distributors), and decisions regarding what the MVP includes. Deposit: 30%.

2

Weeks 2–3

UX/UI Design

Clickable mobile app prototype + admin panel. Screen flow by user type: end user / service / manufacturer. Screens on real devices.

3

End of Week 3

Project approval

You approve the prototype. We won't start building the MVPithout your approval. Upon approval: another 30%.

4

Weeks 4–7

Building an MVP

iOS and Andswarmd app, backend with telemetry, admin panel, and OTA updates ready for deployment. Weekly iterations on a real device. After the MVP release: another 30%.

5

Week 8

Release + availability in stores

Publication on Google Play and App Store. Onboarding of first customers. Code transfer and deployment to your environment. After implementation: last 10%.

What exactly changes after implementation

Your product becomes "the one with WiFi"

The customer in the store consciously chooses your controller because he sees that he has the application. The distributor asks about the price "with the application included in the package". The manufacturer's brand returns to the first screen, not leaflets.

The service sees a failure before the customer calls

Alerts from the device are sent to the service panel. Planned replacement, not reactive. Fewer trips to the customer, fewer complaints, shorter failure repair time.

Telemetry turns into product decisions

You see how customers actually use the device - what functions, at what times, with what errors. The second generation of the product is based on data, not on the guesswork of R&D.

OTA updates and repairs without replacement

A driver bug? Remote update for the entire fleet. A new feature? Push it to the app without returning the device. Faster iteration, lower support costs.

When to use a ready-made IoT platform, and when to go custom

Two paths, two different manufacturer profiles.

Choose a ready-made platform

  • Standard use (smart bulb, socket, simple sensor) - Tuya, Ayla, Particle are enough
  • The brand doesn't matter—the customer sees the Tuya logo, not yours
  • Fewer than 1,000 devices in total; no plans to expand into Western markets
  • Without integration with your ERP / Customer Relationship Management / service

Choose Custom IoT

  • A Polish device with its own protocol (gas controller, air conditioning, dedicated machine)
  • The brand name appears on the app's first screen—the customer sees your logo, not someone else's
  • Over 5,000 devices, a 2–3-year development plan, integrations with Polish ERP systems and services
  • Telemetry feeds into ERP, customer complaints, and production planning—not just the dashboard

Tuya will suffice for most simple uses. Custom IoT is made for manufacturers for whom a brand on the first screen of the application and integration with the Polish ERP/service are a condition for entering the market.

Before you schedule an interview

What happens after implementation, and who we are.

After implementation

Maintenance packages

  • Launch Care 1,19PLN 0/month WP/stack maintenance, backups, monitoring, 1 hour of dev/mc work
  • Growth Circle 2,39PLN 0/month Launch Care + 2×2 hours of consulting per month + Slack + weekly workshops
  • Partner Lab from 4,19PLN 0/month Growth Circle + reserved dev work block + higher SLAs

Optional packages. We will discuss the details during a meeting after implementation.

30 seconds on JSON Crew

Who We Are

2024year of establishment
3founders
4Live case studies

A software company specializing in digital transformation for B2B sales. Product configurators, dashboards, and sales process automation. Three key case studies (Akpil, Forest, and the internal JSON Hub platform) and portfolio implementations (KG Electronics, Metal Roofing, a heat recovery center, and modular homes).

Meet the team · 15-minute diagnosis

Frequently Asked Questions

How much does an IoT application with a backend cost?

Custom pricing following the initial discovery phase. Typeically, an IoT MVP ranges from 80,000 to 300,00PLN 0 for the first version (backend + iOS/Andswarmd mobile app + admin panel). Fixed price once the scope is defined; 30/30/30/10 payment schedule.

What communication protocols do you support?

Modbus, MQTT, OPCUA, and proprietary manufacturer protocols. The decision regarding the communication stack is made during the initial discovery phase—we base our approach on what your device is already transmitting and what you expect in terms of scalability.

Do you publish the app on Google Play / App Store?

Yes. The Smart Control app from KG Electronics — Now available on Google Play. Setting up a developer account, screenshots, store description, and passing Apple and Google verification — all included. Typeically 1–2 weeks from the date the MVP is completed.

What about IoT backend hosting?

Backend hosting is your responsibility (AWS, Azure, GCP, or your own infrastructure). We recommend a scalable architecture—KG Electronics operates reliably with 12,000 connected devices. Hosting costs are not included in our project scope—we’ll work with you to determine the details before launch.

Can you scale from 1,000 to 100,000 devices without rewriting?

Yes, provided the architecture is designed for scalability from the outset. Architectural decisions (queues, batch processing, partitioning, edge computing) are made in the initial phase. KG Electronics — 12,000 devices with no performance issues over 18 months of production.

What about maintenance after implementation?

The Launch Care and Growth Circle maintenance packages are available as optional add-ons. Plus, developer support is available on demand. We’ll discuss the details during a post-implementation meeting.

Quick inquiry · no obligation

Want to chat? Leave a short description

Describe your device and how you'd like to modify it. We'll get back to you within one business day.