Research & development
Research and development, not just delivery.
IIRAD explores ideas that do not fit a standard product brief: experimental engineering, AI and ML applications, IoT, embedded systems and hardware-software prototypes.
R&D areas
Where curiosity meets engineering discipline.
Research is useful when it answers a question. We scope experiments with a decision in mind, not an open-ended budget.
Experimental technology
Projects that do not fit an existing product category, explored through small, testable prototypes.
AI/ML research
Applied machine learning experiments, model evaluation and custom AI prototypes for specific business questions.
IoT & embedded systems
Sensor integration, device logic, firmware, connectivity and local data pipelines for connected products.
Hardware & software prototyping
Rapid prototypes that combine physical components, software interfaces and field testing.
Custom engineering
One-off engineering solutions where the problem is real but no suitable product exists.
Evaluation & feasibility
Technical due diligence, feasibility studies and evidence to support a build, buy or stop decision.
Featured project
Bombilaar: an experiment in affordable mobility.
Bombilaar is an experimental ultra-low-cost electric vehicle prototype. The project explored repurposed battery packs, low-cost motor design and the practical constraints of building for Indian daily commuting.
It is a research prototype, not a commercial vehicle. We publish it because it shows how we work: constrained resources, real testing and a willingness to learn in public.
- Prototype, not a production vehicle
- No current commercial availability
- Engineering details shared where appropriate and agreed
- Research projects may change, pause or conclude without a commercial outcome
How an R&D engagement works
A question, a test, a decision.
-
Define the question
What are we trying to learn, and what evidence would change the decision?
-
Build the smallest test
A prototype, experiment or feasibility study scoped to answer the question without overbuilding.
-
Measure and document
Capture results, limitations, cost and the risks that remain after the experiment.
-
Decide
Iterate, productise or stop. A research result is not a reason to keep spending by default.
IoT & embedded
Connected systems, built from the device up.
We work across the practical layers of a connected product: the sensor or device, the firmware, the local interface and the data pipeline behind it.
- Sensor integration and data collection
- Firmware and device logic
- Local dashboards and connectivity
- Prototype hardware iteration and enclosure planning
- Cloud or on-premise data pipelines
- Field testing support
Who this is for
Businesses with a technical question that cannot be answered by buying off-the-shelf software, and teams that need a credible prototype before committing to a larger engineering budget.
We are careful about regulated, safety-critical or certification-dependent work. If a project needs specialist certification or domain expertise we do not have, we will say so.
FAQ
Research and development questions.
Do you take on early-stage ideas?
Yes, if there is a clear technical question and a realistic scope. We are more useful when the idea can be tested with a small prototype than when it is only a broad concept with no defined problem.
Can a prototype become a commercial product?
Yes, when the prototype justifies the next investment. We separate exploratory work from product engineering so that a research result is not mistaken for a finished, supportable product.
Can you sign a non-disclosure agreement?
Yes, where needed. We prefer to agree confidentiality and intellectual property terms before detailed technical discussions begin.
Is Bombilaar for sale?
No. Bombilaar is an experimental research prototype, not a commercial vehicle. We describe it because it demonstrates how we approach constrained engineering problems, not as a product offer.
Do you work on electric vehicle projects?
Bombilaar is our own experimental project. We consider related engineering work case by case, based on scope, safety and whether we can contribute something credible.
Next step
Have a technical question worth testing?
Describe the idea, the constraint and what you are trying to learn. We will tell you whether a small experiment is worthwhile.