How to prototype an IoT product in India.

Most IoT product ideas in India never make it past a breadboard. Not because the idea is bad — but because the path from idea to prototype is poorly understood, and the mistakes made early are expensive to fix later.

At Manthrix, we have been through this process many times. This guide documents the exact steps we follow when prototyping an IoT product — from the first conversation with a client to a working unit that can be demonstrated, tested, and shown to manufacturers.

This is a practical guide, not a theoretical one. We are going to be specific about tools, vendors, timelines, and costs relevant to working in India.

---

Why IoT prototyping fails in India

Before the steps, it is worth understanding the failure modes — because most of them are avoidable.

Starting with the PCB too early. The single most common and expensive mistake. Founders rush to a PCB before validating that the electronics actually work. PCB spins cost money and take time. A breadboard costs almost nothing and can be ready in a day.

Not specifying the product before touching hardware. What does the device measure or control? What is its power source? Does it need connectivity — WiFi, Bluetooth, 4G, LoRa? What are the physical dimensions? Without answers to these questions, every hardware decision you make may need to be reversed.

Component sourcing surprises. A component that costs ₹50 and ships in two days from a global supplier may cost ₹200 and take three weeks to arrive in India, or may not be available at all. This needs to be known before the design is locked.

Firmware written in isolation from hardware. Hardware and firmware need to be developed together. Firmware written after the hardware is finalised leads to workarounds, instability, and missed requirements.

With those in mind, here is the process that avoids all of them.

---

Step 1 — Define the product specification

Before a single component is selected, write a product specification document. It does not need to be long — two to three pages is enough. It needs to answer:

• What does the device do? State this in one sentence. If you cannot, the product is not well defined yet.
• What does it sense or control? List every input (sensors, buttons, cameras) and every output (actuators, displays, indicators, relays).
• How does it connect? WiFi, Bluetooth, 4G/LTE, LoRa, Zigbee, wired ethernet, or no connectivity at all.
• What is the power source? Mains power, battery, solar, or a combination. If battery — what is the required life between charges or replacements.
• What are the environmental conditions? Indoor or outdoor. Temperature range. Exposure to moisture, dust, vibration.
• What is the target unit cost? This constrains your component choices from day one.
• What certifications will be required? BIS certification is mandatory for most electronic products sold in India. If you plan to export, CE or FCC may apply.

This document becomes your reference for every decision that follows. When a question comes up — "should we use WiFi or Bluetooth?" — the specification answers it.

---

Step 2 — Choose your microcontroller

The microcontroller (MCU) is the brain of your IoT device. Choosing the wrong one early is painful to reverse. Here is how to choose correctly for the Indian market.

For WiFi-connected devices: The ESP32 family (Espressif) is the dominant choice for good reason. It is powerful, has WiFi and Bluetooth built in, is well documented, has an enormous community, and is readily available in India at ₹150–400 depending on the variant. The ESP32-S3 is worth considering for projects that need more processing power or USB connectivity.

For low-power or battery-operated devices: The Nordic nRF52 series is excellent for Bluetooth Low Energy. The STM32L series for ultra-low-power applications. Both are available in India but at higher cost and with longer lead times than the ESP32.

For cellular connectivity: The SIM7600 or SIM800 modules for 4G/2G. The Quectel EC21 for more demanding applications. These add significant cost and complexity.

For beginners starting a proof of concept: Start with a development board — an ESP32 DevKit, a Raspberry Pi, or an Arduino — before committing to a bare MCU. Development boards have built-in USB, power regulation, and programming interfaces that remove unnecessary friction during early prototyping.

---

Step 3 — Build a breadboard proof of concept

Do not skip this step. A breadboard prototype validates that your circuit works before you spend money on a PCB. It takes one to five days depending on complexity. A PCB spin takes one to three weeks and costs ₹3,000–15,000 for small quantities.

At this stage you are proving three things:

• The sensors or inputs produce the data you expect
• The microcontroller can process and act on that data correctly
• The connectivity (WiFi, Bluetooth, etc.) works in your target environment

Your firmware at this stage can be rough — hardcoded values, serial output for debugging, no error handling. You are validating concepts, not writing production code.

Tools you will need: a breadboard, jumper wires, a multimeter, a USB-to-serial programmer if your MCU does not have built-in USB, and a power supply or USB bank for testing. Total cost: ₹500–2,000.

---

Step 4 — Source components in India

Indian component sourcing has improved significantly in recent years but still has gaps. Here is the current landscape:

Reliable Indian suppliers:

• Robu.in — best for ESP32 modules, sensors, and development boards. Fast shipping, good stock.
• Electronicscomp.com — broader catalogue, good for motors, displays, and power components.
• Evelta.com — strong on industrial components and connectors.
• Rhydolabz — good for niche sensors and communication modules.

For components not available locally: AliExpress and LCSC are the most cost-effective international options. Expect 15–30 day delivery and factor in import duties. For components under ₹10,000 total value, duties are typically manageable.

Critical check at this stage: For every component in your design, verify it is available in India at the quantity and cost you need for manufacturing. A component that works perfectly but cannot be sourced reliably will delay your product launch.

---

Step 5 — Design your first PCB

Only move to PCB design once your breadboard prototype is validated. This is where most first-time hardware founders move too fast.

Software: KiCad is free, powerful, and the most accessible starting point for new hardware teams. EasyEDA is simpler and integrates directly with JLCPCB and LCSC for ordering. Altium Designer is industry standard for complex designs but expensive and overkill for a first prototype.

PCB design principles for a first prototype:

• Keep the design simple. Two layers is sufficient for most IoT devices at prototype stage.
• Add test points on every important signal line. You will need them for debugging.
• Leave more space than you think you need between components. Dense layouts are harder to debug and rework.
• Include a programming interface — a pin header for UART or JTAG depending on your MCU.
• Add decoupling capacitors (100nF ceramic) on every power pin of every IC. This is the single most skipped step that causes the most problems.
• Add a power LED. It sounds trivial. It will save you hours of debugging wondering if your board has power.

PCB fabrication in India: PCBPower (pcbpower.com) is the most established Indian PCB manufacturer with reasonable quality and 5–7 day turnaround. Eurocircuits and JLCPCB are international alternatives that often work out cheaper for small quantities with 10–15 day delivery.

Order at least five copies of your first PCB. You will damage some during assembly and debugging. Having spares costs very little extra.

---

Step 6 — Write the firmware

Firmware for a prototype should be structured but not over-engineered. The goal is a working demonstration, not production code.

For ESP32 projects: The Arduino framework in PlatformIO is the fastest path to a working prototype. PlatformIO (platformio.org) is a significantly better development environment than the Arduino IDE — better library management, better build system, VS Code integration.

Structure your firmware from the start around these layers:

• Hardware abstraction — functions that talk directly to sensors and peripherals
• Application logic — what the device decides based on sensor data
• Communication — WiFi/Bluetooth/cellular connection and data transmission
• Configuration — device settings that may need to change without reflashing

This separation means you can swap a sensor, change the connectivity module, or modify the application logic without rewriting everything. It also makes debugging dramatically easier.

For over-the-air (OTA) updates: Build this in from the start, even for a prototype. The ability to update firmware without physical access to the device will save enormous time during testing and is essential for any deployed product.

---

Step 7 — Test systematically

Testing an IoT prototype is different from testing software. You are testing the interaction between hardware, firmware, connectivity, and the physical environment simultaneously.

Test in this order:

• Power on test. Does the board power on without drawing excessive current? Measure current draw immediately after power-on before running any firmware.
• Programming test. Can you flash firmware? If not, check your programming interface connections before anything else.
• Peripheral test. Test each sensor, actuator, and communication module independently before testing the complete system.
• Communication test. Verify WiFi/Bluetooth range and reliability in the environment where the device will actually be used — not just on your desk.
• Power consumption test. If the device is battery-powered, measure sleep current and active current. Calculate expected battery life. This often reveals optimisation requirements that must be addressed before the design is finalised.
• Environmental test. Test at the temperature extremes your specification defines. Components behave differently at 45°C versus 15°C. India's climate means this matters.
• Stress test. Run the device continuously for 48–72 hours. Many issues — memory leaks, WiFi reconnection failures, sensor drift — only manifest over extended operation.

---

Step 8 — Prepare for manufacture

Once your prototype is validated, preparing for manufacture requires a different set of outputs than the prototype itself.

What you need for a manufacturer:

• Gerber files — the PCB design files in the format manufacturers use
• Bill of Materials (BOM) — every component with manufacturer part number, value, footprint, and quantity
• Pick and Place file — component positions for automated assembly
• Assembly drawings — indicating any special assembly requirements
• Test procedure document — how to verify each assembled unit works correctly

Indian contract manufacturers worth knowing: SFO Technologies (Noida, Kochi), Dixon Technologies (Noida), and Kaynes Technology (Mysore) handle mid-to-large volume. For small prototype runs of 10–100 units, local PCB assembly shops in Nehru Place (Delhi) or Lamington Road (Mumbai) are more accessible and faster.

---

Realistic timeline and cost

Here is an honest estimate for a moderately complex IoT product — a WiFi-connected sensor device with a small display and battery power:

These numbers assume you are doing the design work yourself or with a small team. Outsourcing the entire process to a hardware development company in India typically costs ₹3,00,000–10,00,000 for a first prototype, depending on complexity.

The timeline is also optimistic — it assumes no major design errors and no component availability problems. Real projects routinely take 20–30% longer than estimated. Budget for it.

---

IoT product development in India is more accessible than it has ever been — better component availability, better tooling, better manufacturing options. The process above is not the only way to prototype an IoT product. But it is a process that reliably gets from idea to working prototype without the most common and expensive mistakes.

If you are building an IoT product and want to discuss the specifics of your project, get in touch with us. IoT hardware development is one of our three core pillars at Manthrix.