I work across Product, Manufacturing and the Market to help hardware founders get this right.
Fractional Head of Product & Manufacturing for launch-ready founding teams
The window between testing customer hypothesis and building prototypes is usually measured in months. The cost of not doing this is measured in failure or success.
The engagement I run is designed to open that window before it closes.
Early in my career, I was at a startup developing innovative ideas in fiber laser tech.
But it struggled to build products and had no customers.
Out of frustration, I picked up the phone and called a potential customer.
To my surprise, they were excited about what we were developing and wanted to order two units.
I took that back to the founder, however, they wanted to focus on getting the innovation right before moving forward with the customer.
So, I left.
I decided to start a hardware social enterprise, building an energy-efficient irrigation pump for smallholder farmers in South Asia.
This time I knew I needed to talk to customers. So I did.
And I still got it wrong.
I was talking to users — not customers — farmers who would use the pump, but not the ones who would actually buy it.
By the time I figured out who the real customer was, I’d run out of funding.
That distinction — between who uses your product and who decides to buy it — is one of the sharpest lines in hardware.
Missing it is easy, expensive, and nearly invisible until it’s too late.
“The companies that reach product-market fit are the ones continuously checking assumptions with customers alongside development, not after it.”
Willingness-to-pay and ability-to-pay look identical until you’re in the field.
Both show up as “they won’t buy at that price.” But one means your value proposition isn’t landing — and the other means the price is above what they can justify, even when they want it.
Customer conversations tell you which problem you’re facing. The product and manufacturing work that follows is completely different depending on the answer.
The hardest manufacturing decisions arrive before you have enough data.
Early versions of a product are not always perfect. Customers could be struggling to use it correctly. But you become aware of this after committing to your manufacturing line. Making changes could mean significant expenses and time delays to improve customer experience.
The decision itself is never in doubt. But timing is everything.
Customers don’t always buy for the reason you built it.
In hardware, you usually discover the real motivation after the manufacturing line has been set up. And field conversations surface this not as a single breakthrough, but as a pattern across many conversations that tells you what actually moves someone to buy.
This pattern reorders your roadmap.
Manufacturing constraints follow your customers’ buying cycles.
Most businesses aren’t year-round. Commercial fishing is seasonal. Healthcare deployments follow procurement cycles. Climate-tech solutions also have to follow climatic events.
When you understand when and why customers use your product — that shapes how you forecast demand, how you negotiate with manufacturing partners, and whether those partners commit to you.
Did you notice this also impacts your New Product Introduction (NPI) decisions.
I ask questions like “what is the problem we’re trying to solve?”, “what is the hypothesis for customers caring?”, “what led to these product design choices?” Founder, engineering, sales, ops — anyone close to the work. I’m building toward a clear separation between the problem and the solution that’s already been assumed. And a map of which product decisions are still open versus already committed.
Unit economics, COGS analysis, manufacturing timelines, component options, volume projections, current product roadmap. I’m mapping what’s actually buildable against what’s actually been committed to. The PM work here isn’t just understanding constraints — it’s identifying which product decisions are still reversible and which ones aren’t. In hardware, a feature that’s easy to change in software can lock in tooling costs.
JTBDs per customer type — at least one conversation from each target segment, market, and industry. One technique: share what one customer told you with a different customer. The friction that creates is more revealing than passive listening. The conversations are designed to answer specific product and manufacturing questions: does this validate the roadmap priority? Does it change what we’re building and for whom?
IoT temperature monitors deployed across government vaccine cold chains in India.
Satellite GPS trackers for commercial fishing fleets, built to locate gear in any weather, anywhere at sea.
EV trailer platform technology designed for the commercial trailer industry.
“Mitesh is a fantastic product consultant. His work is defined by his patience and thoroughness. I was impressed by his curiosity and the dedication he showed in learning our business inside and out. He asks the right questions, and it’s clear he is committed to getting the details right. He has my highest recommendation, and I’d be happy to recommend him to any friend or colleague.”
Susan Linwood · CEO, Novos Power
Client, November 2025
“He knows what it means to do discovery in the field. He’s built so much hardware — from lasers to pumps to ocean tech. His entrepreneurship DNA is hard to miss.”
Moiz Kapadia · Fractional Head of Product · Climate/Energy
LinkedIn, February 2026
No pitch — just a conversation about what you’re building and whether I can help.
Get in touch →