The short version
- Choose for hardware depth, not slide decks. Ask who will design the board and write the firmware, and to see their own measurement data.
- Insist on ownership: source code, schematics, layout and build instructions delivered to you, with open tools wherever possible.
- Run a paid, small first phase. A scoped feasibility or prototype stage reveals more about a team than any proposal.
- Be wary of fixed price with vague scope and of any vendor who cannot name the risks in your project.
Questions to ask every vendor
| Topic | Ask | A good answer sounds like |
|---|---|---|
| Team | Who exactly will work on this, and are they employees? | Named engineers, in-house, with relevant experience |
| Process | How do you manage requirements and change? | Written spec, review gates, change log |
| Evidence | Can I see a similar product or reference? | Specific devices, with limits stated honestly |
| Ownership | What do I receive at the end? | All source, design files, BOM, test procedures |
| Testing | How will you prove it works? | Test plan, measured results, failure injection |
| Risk | What could go wrong with my project? | Concrete risks: supply, certification, power, antenna |
Red flags
- Promises a fixed date and price before understanding requirements.
- Cannot explain trade-offs between two parts, or recommends the same platform for every problem.
- Software-only team that subcontracts the hardware to unnamed parties.
- No plan for testing, certification or manufacturing handoff.
- Proprietary lock-in: closed tools, undelivered source, or a licence needed to rebuild firmware.
- Reluctance to sign an NDA or to define IP ownership in writing.
Contract terms to agree
- IP ownership of all deliverables on payment.
- Milestones tied to demonstrable results, not dates alone.
- Acceptance criteria written as tests.
- Source escrow or delivery at each milestone.
- Warranty period for defects and a support option afterwards.
- Confidentiality and non-solicitation terms both ways.
Run a small first phase
A paid feasibility study or proof of concept, of a few weeks, tests communication, engineering quality and honesty about risk at low cost. It also produces a better estimate for the full project. Our pricing page shows how we structure engagements, and about us describes the team. You can compare us against that checklist.
Sources and further reading
- Startup India — Government programme information for hardware startups.
- IPC — Industry standards for acceptance and quality.
- MeitY — Electronics policy and schemes.
Last reviewed: October 2026. Regulations and product availability change; confirm current rules with the issuing authority before you commit to a design.