Skip to content
IntellobotsTechnologies

Product engineering

Outsourced product development, with one lead who owns it

Hardware, firmware, cloud and apps from one team in India, instead of four vendors pointing at each other.

DATASHEET
IB-SVC-PRD
  • An idea or a written spec
  • Target cost and volumes
  • Launch window
  • Systems it must talk to
  • Discovery and architecture sprint
  • Hardware, firmware, cloud and apps
  • A dedicated cross-functional pod
  • QA automation and release engineering
  • Post-launch support
Interfaces
  • Embedded C
  • C++
  • Go
  • Java
  • Node.js
  • Python
  • React
  • GCP
  • AWS
Applies to
Connected devices · Retail hardware · Industrial products
Engagement
Fixed-scope MVP · Dedicated pod · Product partnership

In plain words

You have an idea for a product. We design, build and test the whole thing (electronics, the program inside it, the app and the cloud) as one team.

Who it's for
Founders and companies launching a new connected product who don't want to manage four separate vendors.
How to start
A 30-minute call, then a fixed-price plan for your first working version.
Ask a person about this
Words on this page, explained
Firmware:
The small program that runs inside a device, like the brain of a shelf label or sensor.
Cloud:
Software that runs on servers in a data centre, reached over the internet, so you don't run servers yourself.
MVP:
Minimum viable product: the first version with just enough to put in front of real users.
Proof of concept (PoC):
Proof of concept: a small, fixed-scope trial that shows whether an idea works before you invest more.

We take products from a requirements doc to production and keep them healthy after launch. One engineering lead owns delivery across electronics, firmware, backend, web and mobile, so integration problems surface in week two, not month six. Engagements start with a short discovery and architecture sprint, then move into fortnightly releases with demos you can put in front of customers.

Smart homes & buildings · automation

One tap for the whole house.

Lights, fans, AC and the water pump on one app. Switch a room from anywhere, put the house to sleep with one tap, and see what it costs in power right now.

Home · 2 bedrooms · live

0.23 kW now
Living roomLIGHT ONKitchenLIGHT ONBedroom 1LIGHT OFFAC OFFBedroom 2LIGHT ONENTRYWATER TANK62%PUMP AUTO

Using now

0.23 kW

Left like this all night: 1.8 units

  • Living room
  • Kitchen
  • Bedroom 1
  • Bedroom 2

What you’re seeing: a small home from above. Tap a room to switch its light, use the switches for fans and AC, or pick a scene. The meter moves with every switch, and the tank turns its own pump on before it runs dry. We built Homebot, a home automation system like this, back in 2014.

For engineers

Retrofit relay and dimmer modules behind existing switchboards, talking to a home hub over a low-power mesh; the hub keeps scenes and schedules working offline, and syncs to the cloud app when connected. Energy is metered per circuit; the tank uses a level sensor with hysteresis to drive the pump contactor.

Lights on in Living room, Kitchen, Bedroom 2. Using 0.23 kilowatts. Water tank 62 percent.

  1. 01

    Your roadmap needs skills you don't have in-house

    Firmware, cloud, apps and QA rarely sit in one team. We bring all four under one lead who owns the result.

  2. 02

    Prototypes that never become products

    A demo board on a desk is not a product. We design for manufacturing, certification, field updates and support from the first sprint.

  3. 03

    Vendors who hand over code nobody can run

    Every engagement ends with documentation, CI pipelines and a handover your team can actually take over.

How we work

From first workshop to running in production.

  1. STEP 01

    Discovery sprint (1–2 weeks)

    Workshops, constraints, risks and a costed architecture. You keep the document whether or not we build it.

  2. STEP 02

    Architecture and proof

    We de-risk the hardest part first: the radio, the model, the integration or the scale test.

  3. STEP 03

    Build in two-week increments

    Working software every sprint, demoed to your team, tracked in your tools.

  4. STEP 04

    Certify and industrialise

    Test plans, compliance support, manufacturing files, provisioning and OTA update paths.

  5. STEP 05

    Launch and run

    Hypercare after go-live, then a support plan sized to your product, or a clean handover.

What you get

Deliverables, not slideware.

Architecture decision records
Why each choice was made, so future teams don't relitigate it
Source code and CI/CD
In your repositories from day one, with automated builds and tests
Hardware files
Schematics, layouts, BOM and manufacturing outputs, when hardware is in scope
Test evidence
Unit, integration, soak and field test reports
Runbooks
Deployment, monitoring and incident procedures for whoever operates it

Technology

No stack limits. Right tool for the problem.

Embedded

CC++embedded RustRTOS and embedded Linux on ARM Cortex-M/A and RISC-V

Backend

Go.NET / C#JavaNode.jsPython

Desktop and legacy

C++ / MFCWPFWinFormsQtmodernising long-lived Windows applications

Web and mobile

ReactNext.jsAngularFlutterReact NativePWAs

Data

PostgreSQLSQL ServerBigQuerySparkKafkaRedis

Cloud

Google Cloud and AWS in depthAzure for client estatesDockerKubernetesTerraform

Need something not listed? We hire for it or bring in a specialist. The problem picks the stack.

One accountable team

Hardware, firmware, cloud and apps without vendor finger-pointing

Predictable delivery

Fixed-scope discovery, then sprint-based delivery with visible progress

Code you own

Repositories, pipelines and documentation stay with you

Do you work fixed price or time and materials?

Discovery is fixed price. Delivery can be fixed scope per milestone, a dedicated pod, or time and materials, whichever suits the risk.

Can you join an existing team?

Yes. We often embed engineers into a client's squads and follow their rituals and tooling.

Who owns the IP?

You do. Code, designs and documentation are assigned to you on payment.

What if we need a skill you don't have on the bench?

We hire or bring in a specialist consultant. Technology choice is driven by your problem, not by our bench.

Engagement models

Fixed-scope MVP

defined scope, timeline and price

Dedicated pod

a squad that works as your team

Product partnership

roadmap to support, outcome-based

Where this sits in the stack

Six blocks on one die. One team across all of them.

We work across .NET, C, C++, MFC, Go, Java, Python, Node.js, React and Spark, on GCP, AWS and Azure, plus embedded C on RTOS and embedded Linux. Pick a block to see where it fits.

Hover, tap or tab through the blocks. Lit copper shows which blocks work together.

Block · Apps

Screens for staff, customers and administrators.

  • React
  • Node.js
  • .NET
  • Java
  • C++ / MFC
  • Web consoles and dashboards
  • Mobile and handheld apps for floor staff
  • Desktop tools, including C++/MFC and .NET upkeep
  • Approval and admin workflows

Where it shows up

Scope your Outsourced product development project

Tell us the problem, the constraints and the deadline. A senior engineer replies within one business day.

Add company, budget and phone (optional)
Know someone who should see this? Share it