The question US founders really ask isn't "is India cheaper?" It's "will I lose control of my product?" That fear is reasonable. Cheap engineering that you can't steer, can't audit and can't take back costs more than expensive engineering that works. This post covers the cost case, and then the four things that decide whether outsourcing works: ownership, communication, compliance and manufacturing.
Why the cost case is real
Engineering labour is the biggest line in a hardware MVP budget. Components cost roughly the same everywhere. Fabrication and small-batch assembly prices are competitive across Asia. The difference sits almost entirely in engineering hours — industrial design, electronics, firmware, app and backend.
A seed-stage US team paying local rates for four disciplines burns through runway in the prototype phase alone. The same scope, built by a senior India-based team, typically costs a fraction of that. That gap can fund a second board revision, a proper field trial, or three more months of runway before Series A.
| Budget line |
What changes when the studio is in India |
| Engineering hours (ID, PCB, firmware, app) |
Significantly lower — the main saving |
| Components and BOM |
Roughly the same — global distributor pricing |
| PCB fabrication and prototype assembly |
Competitive with other Asian sources |
| Certification lab fees (FCC) |
Same — paid to the lab, wherever it is |
| Tooling |
Depends on where you mould, not where you design |
Two cautions. First, the saving disappears if the work needs redoing. A cheap team that ships a board you have to redesign costs more than a senior team that gets it right. Second, the saving only matters if you redirect it to things that de-risk the product — field units, validation, a second spin.
Who owns the IP
US founders need two things in writing.
Assignment of everything created for your product. Schematics, PCB layout, CAD, firmware source, app and backend source, test fixtures. The contract should assign these to your company on payment. Indian contract law supports this kind of assignment, and well-drafted agreements specify governing law and dispute resolution that both sides accept.
Continuous handover. Don't wait for a final bundle. Source should land in repositories your company owns at every milestone. Accounts — cloud, app stores, domains — should sit in your company's name from day one. If the relationship ends at milestone three, you leave with milestone three.
We wrote a separate guide to the exact handover list. The short version: native source plus outputs plus rebuild instructions, for every discipline, plus a signed IP assignment.
Time zones: the overlap is better than it looks
India Standard Time sits 9.5 to 10.5 hours ahead of US Eastern, and 12.5 to 13.5 hours ahead of US Pacific, depending on daylight saving.
That sounds hard. In practice, it creates a useful rhythm:
- US morning = India evening. A daily overlap window for calls, reviews and decisions.
- US night = India working day. You send feedback at the end of your day. You wake up to the changes.
- Hardware isn't real-time work. Board fabrication takes days. Enclosure prints take hours. Most of the build doesn't need simultaneous presence.
The rule that makes it work: written decisions. Every review ends with a short written log of what was decided, by whom, and what happens next. Time-zone pain comes from ambiguity, not from distance.
FCC: design for it, don't discover it
Any electronic product sold in the US needs to meet FCC rules. Products with radios — Wi-Fi, BLE, cellular, LoRa — are intentional radiators and need equipment certification through an accredited certification body. Products without radios still emit unintentional radiation and need to meet Part 15 limits, usually through a supplier's declaration of conformity.
Design choices that make FCC easier:
- Use pre-certified radio modules for the first product. Integrating a module with an existing grant avoids most of the cost and risk of certifying a custom radio design. The final product still needs testing for unintentional emissions.
- Follow the module's integration guidance exactly — antenna type, placement, ground clearance. Deviating can void the module's grant.
- Run pre-compliance scans during development. A scan in EVT costs a fraction of a failed formal test in DVT.
- Plan labelling and documentation early — FCC ID references, user manual statements and test reports.
Your studio should design to these constraints from the schematic stage. The formal test happens at a US-recognised lab, and the lab fees don't change based on where the design team sits.
Manufacturing is a separate decision
Where your product gets designed and where it gets built are two different choices. A good studio designs for whichever manufacturer fits your volume, cost and market — in India, elsewhere in Asia, or closer to home. Import duties and tariffs depend on where finished goods are manufactured and shipped from, not on where the design work happened.
What matters is the manufacturing package: drawings, BOM with alternates, assembly instructions, test procedures and fixtures. With that package, you can get competing quotes from any qualified factory.