How Much Does Hardware Product Development Cost in India?

The figures below are invented teaching numbers. They are not BrahmWorks fees, not Indian market rates, and not a budget. Replace every line with a written scope before you compare anyone.

A quote is a scope with a price, not a price for the word hardware. An enclosure around a bought module and a product that needs custom electronics, firmware, a radio claim and a tool are different sets of invoices, even if the photographs look alike.

A design team in India still buys boards, modules, tools and often lab time on a wider market. A lower day rate does not make the programme cheaper if the brief is open and the days multiply. Freight, duty and tax sit on many invoices. Ask whether a figure excludes them. This is not tax advice.

One number also mixes costs you can stop with costs already frozen. Engineering can pause at a gate. A cut tool is sunk. A submission of the wrong design is a repeat. Split the quote by bucket, each with a definition of done and a list of what is outside the fee.

This bucket is judgement: industrial design, mechanical design, electronics, firmware, manufacturability reviews, test definition, and the time to turn a supplier’s question into a decision. Sell it as a phase with a deliverable, or as time from a named team. It is not the parts and it is not the mould.

What moves the fee is how many questions are open, and which disciplines must touch them. A closed brief with one mechanical interface is smaller than an idea that still has no requirement. Firmware is a common miss: a stack, a bootloader and a factory test log are scope, not a weekend after the boards arrive. A fixed phase stays fixed only while the brief does. If your own people will write firmware or stand on the pilot, write that time down. A missing invoice is not a zero cost.

Prototype parts are the boards, machined or printed pieces, modules, cables and cells you buy in order to learn. They are pass-through when a vendor invoices them, even if a studio places the order. A fast process is often dear per piece and a poor teacher of production. That is fine for a fit or firmware question, and wrong for a moulding question.

Count the spins. “Prototypes included”, with no number of turns, is an argument waiting. Say what each build may answer, and who can approve another. A board that cannot be programmed inside the enclosure wastes the assembly around it. If the studio recharges the vendor, show the bill and any mark-up on their own line. A blend turns the next spin into a fee dispute.

A lab test is what a laboratory charges to run an agreed method on samples you submit. A pre-compliance check on a named risk is not a certificate. Formal testing is the evidence a market wants for a claim you chose to make. Both are lab invoices unless the contract says the studio pays and recharges them.

The second submission is often the dear one. A new enclosure, supply, radio or relevant firmware can void the result. One assumed pass, with no resubmit rule, is how the bucket doubles without a change to the fee. Ask for sample count, configuration, exclusions and the repeat price. If the claim and the market are unnamed, you cannot price the line. A round “certification” figure either underfunds the real submission or buys the wrong tests.

Tooling is the mould, die, jig or fixture that makes later units cheaper or more repeatable than the prototype route. It is capital: an owner, a location, and a quantity at which it is rational. It is not an engineering fee, even when one firm designs the part and introduces the toolmaker.

A quote that hides a tool looks large beside a fee-only quote. A quote that omits a tool you need before sale looks small. Ask which tools are included, whether they are soft or production tools, what they cannot change later, and who owns them if you move. Amortise only against a stated count of saleable units. A production tool bought to make 50 trial units freezes a design you have not finished learning from.

A pilot is a small build on the process you claim you will use, so defects and confusion show up while the batch is still small. The invoice is parts, assembly, and often fixtures and travel. It is not the fee for writing the instructions, and it is not a production unit cost.

Some units will be scrap, rework or retained samples. Treating all of them as saleable understates the pilot. Dividing the whole programme by the pilot quantity overstates the later unit cost. Keep three numbers apart: the fee to prepare the pilot, the invoice to build it, and the variable cost once the process is stable. The third is not knowable from the first two. If the pilot uses another material, hand assembly or no fixture, say so. You may have learned something. You have not learned the production cost.

Compliance is the cost of being allowed to sell a stated claim in a stated market. The lab invoice is one piece. The rest can include a technical file, markings, a manual, factory information, a registration or representative, and the time to keep those true when the design changes. Which pieces apply is a question for someone accountable for that market, not a number to copy from an article.

“Included”, with no market and no claim, usually means not included. A late finding sends you back to engineering, which is why the path is chosen before the tool. The rule for which part changes must be retested continues after the first certificate. Leave it out and year one looks cheaper than the business you will run.

Imagine one narrow product: a small mains-free industrial indicator, one market, one claim set, two prototype spins, a soft tool, a pilot of 50, and a formal submission that passes first time. Every rupee below is invented. None of it is a BrahmWorks price or a rate to take to a vendor.

The lines sum to 37,15,000. Engineering is 18,00,000 / 37,15,000, about 48 percent. Another formal submission, at the same invented 6,00,000, takes the sum to 43,15,000. That repeat is larger than the parts line of 2,40,000. “About 37 lakh” hides it.

Dividing 37,15,000 by 50 gives INR 74,300 per pilot unit. That is not a production cost. It loads the fee, the tool and the labs onto a learning batch. The build line alone is 3,25,000 / 50 = INR 6,500, and even that figure is an invented pilot invoice, inefficiency included. Do not put INR 74,300 on a price list, and do not quote INR 6,500 as a unit price.

A band, if you need one, belongs on a single bucket after a scope exists, and it is a guess. Averaging these lines into one India range does not make them one measurement.

Ask for three columns.

The fee is time and judgement: phase, deliverables, disciplines and how many turns. A brief change reopens it under a rule you agreed. Pass-through is the vendor invoice for parts, labs, freight or the pilot. Say who pays, and what mark-up applies. Hidden mark-up cannot be compared. Capital is the tool or fixture: owner, location, and soft or production. Fee and capital may come from one company and must still be separate lines. If you do not own the tool, you have rented a process.

If a board or a lab is quoted in another currency, show the rate and who carries a move. Write the exclusions: duties, golden samples, your travel, a second market. Compare fee with fee on the same deliverable, then the pass-through rule, then capital. A lower all-in number that omits the tool and the lab is not a cheaper programme.

The same rendering can sit on different totals. Count disciplines, prototype loops inside the fee, and markets. A second market is another evidence set. Say whether firmware is in the fee, in your team, or missing, and whether the risky function is a module or a custom circuit. Say whether a designer attends the pilot. If a quotation cannot say which of these it assumed, do not accept it.

Put contingency on the lines that can repeat, not as a flat percentage of the blend. In the invented split, another parts spin is on the order of INR 2,40,000, and a failed formal submission is INR 6,00,000 again. Ten percent of 37,15,000 is about INR 3,71,500, which covers neither and pretends the risk is spread evenly.

Send this, or the same facts in your own words. A quotation without them prices a guess.

• User, environment, mandatory function, markets and claims fit on one page, including what is out.
• The quote names a phase and a quantity. It is not a price “to mass production”, and a prototype quantity is not a unit cost.
• Buckets you want priced, and buckets you will buy yourself, are listed.
• Existing CAD, schematics, firmware and logs are listed, with what may be reused.
• Done is a deliverable list. Spins inside the fee are a number.
• Tooling is excluded, or listed with an owner, soft or production, and what it cannot change later.
• Lab work is excluded, or split into pre-compliance and formal, with a market and a resubmit rule.
• Pass-through, mark-up, currency and who carries a rate move are visible.
• Exclusions name freight, duties, tax treatment, a second market, samples and your travel.
• In-house time is listed. You will compare fee, pass-through and capital, not only a blended total.

Not as a rule. Day rates differ by seniority. Boards, tools and laboratories do not become cheap because the designers are in India. A low rate on an open brief can cost more than a higher rate on a closed phase. Compare scope and the three columns.

Only if you mean to buy it, and only as its own line with an owner. A hidden mould cannot be compared with a fee that has none. Omitting a tool you must buy before sale makes the programme look cheaper than it is. Match the tool to the quantity you are funding.

A fixed price fits a closed brief, a closed deliverable list and a stated number of turns. It does not fit the whole journey to mass production, which has gates where evidence may stop the work. Fix the next phase. Contingency belongs on the buckets that can repeat.

The checklist, the revision of any design you already have, and a note of what is out of scope. If claims and markets are unknown, buy a phase that defines them. Do not buy a total that pretends compliance is inside.

Bring the brief, the markets and claims, and the phase you want priced. BrahmWorks can separate the fee from parts, tools and lab invoices, and say which of those you cannot price yet.

Review the next stage with BrahmWorks