Indian wellness FMCG group · two-product engagement · client name held until next launch

Smart connected product engagements

Two parallel product programmes for a leading Indian wellness FMCG group. Programme #1: an affordable category-killer connected product, designed to undercut on price while matching feature parity — currently in market. Programme #2: a smart plug-in product, currently in active development. Same client, same engineering team across both — full-stack delivery from concept to manufacturing readiness.

Industrial design
Hardware engineering
Embedded systems
Mobile + cloud

The problem

The client is a leading Indian wellness FMCG group operating in a category increasingly defined by smart-connected products at premium price points. Two product opportunities surfaced in parallel — one to disrupt the category on affordability while keeping the smart-product feature surface intact, the second to bring a smart plug-in product into a previously unconnected adjacency. Both required rapid, full-stack engineering by a single integrated team rather than three separate vendors.

Our approach

Programme #1 — the affordable category-killer — was built around a tightly-cost-engineered BoM, simplified industrial design, and a minimal-but-honest feature set. Manufacturing readiness was prioritised over feature exploration. Programme #2 — the smart plug-in product — is in active engineering: industrial design, embedded firmware, mobile companion app, cloud telemetry, and a smarter feature stack matched to the higher price point of the adjacency.

Outcome

Programme #1 is in market. Programme #2 is engineered to manufacturing readiness; client name will be added publicly here at the next product launch milestone.

Related pillar

This engagement sits inside our Product Development pillar.

From raw concept to market-ready hardware. We build IoT devices and prototypes that work.

Read the Product Development pillar in detail

Disclosure

What this page does and doesn't say.

Public case-study copy describes the engagement at category level — what kind of problem we solved, what kind of platform we built, what kind of outcome it produced. It deliberately doesn't share deployment metrics, vendor partnerships, internal codenames, or specific architecture beyond what's required to evaluate fit.

On a signed NDA, in a first or second meeting, we'll share the depth — reference contacts, specific outcomes, and the architecture in detail. The first conversation is 30 minutes; reference setup happens after that.

Bring us a problem in the same shape.

Or a problem in a shape we haven't built yet. Both are interesting. The first conversation is 30 minutes, founder-led.

Book consultation See all work