The decision that shapes the whole project
Every product is a stack of subsystems: power, control, communication, mechanism, enclosure. Each one faces the same question — buy an existing solution or develop your own. The working rule is short: develop only what creates your competitive advantage, and buy everything else. The sum of those decisions determines your schedule, your budget, and your unit cost more than any single design choice, and yet in most projects they get made by habit.
What off-the-shelf buys you
- Time. What you purchase today took someone else months to develop.
- De-risked function. The part already works in thousands of products; its childhood diseases are behind it.
- Borrowed certification. This is the biggest and least appreciated advantage in the US market. A pre-certified radio module carries its own FCC modular approval, which can remove a large block of intentional-radiator testing from your program. A listed power supply removes a chunk of electrical safety work. Chip-down designs put all of that back on your budget — context in FCC certification for electronics.
- No NRE. No design cycles, no prototype iterations, no dedicated qualification.
What you pay for it
- Higher unit price. The supplier takes margin on every unit, and at volume the gap compounds relentlessly.
- Design constraints. The product shapes itself around the part: the enclosure grows to fit a module, the mechanism compromises around a catalog motor.
- Supplier dependency. A part going end-of-life mid-life-cycle is a genuine crisis. It demands qualified second sources and awareness of gray-market risk — see counterfeit electronic components.
- Zero differentiation. What you can buy, your competitor can buy on the same day.
- Black boxes. Modules with closed firmware limit how deeply you can optimize power, timing, or behavior.
The two multipliers: volume and stage
The rule bends on two variables. Volume is straightforward arithmetic: divide the non-recurring engineering cost of the custom route by the per-unit saving it produces, and you get the crossover quantity. If a custom board saves eight dollars per unit and costs sixty thousand dollars to develop and qualify, you break even in the mid four-figure unit range — below that, buying wins; well above it, developing wins. Run the numbers with your real bill of materials, not a guess, and use a properly structured BOM as the basis. The same logic applies to process selection generally, as in choosing a manufacturing process by volume.
Stage is the other lever. Early on, buy nearly everything to reach the market fast and learn what customers actually value; then replace the expensive modules with custom designs in later revisions once volume justifies it. That progression is exactly the work described in value engineering to cut product cost.
The middle ground: semi-custom
Between the extremes sits a spectrum most founders overlook. Many suppliers will adapt a standard part for a modest fee and no real development risk:
- A catalog motor with a custom shaft, gear ratio, or lead length.
- A standard enclosure with a machined and printed custom front panel.
- A stock module on your own carrier PCB, so the interface and layout are yours.
- Custom cable assemblies and connector pinouts from standard components.
- Vendor firmware configured to your parameters rather than rewritten.
- A private-label version of a standard product with your branding and packaging.
Semi-custom captures much of the design freedom at a fraction of the cost and schedule of a ground-up design. It is the right default for a first production run.
A practical decision checklist
- Does this subsystem carry the differentiation? If yes, develop it. If no, buy it. Which subsystem carries it is settled by the strategy in how to differentiate a product in a crowded market.
- What does the off-the-shelf option cost at your target volume, as an annual number rather than a per-unit one?
- What certification does the standard part carry, and what would you have to test yourself without it?
- Is there a second source that is a drop-in, or at least a documented alternate? Single-sourced critical parts are a schedule risk with a long fuse.
- What is the part's expected lifecycle, and does the supplier publish longevity commitments for industrial-grade lines?
- Does buying force a compromise a customer would notice? Size, weight, noise, and battery life are where module constraints usually surface.
The common mistakes at both extremes
Over-buying produces a product that is a visibly assembled kit — bulky, expensive per unit, and indistinguishable from competitors using the same modules. Over-developing burns a year and most of the budget rebuilding solved problems, typically a power supply or a wireless link, in the name of engineering pride. The most frequent specific error is going chip-down on a radio or building a custom single-board computer when a mature module would have shipped, a temptation examined in using a Raspberry Pi in a commercial product. And when you do build custom electronics, the controller choice deserves its own analysis — see how to choose a microcontroller.
Draw the line deliberately
Projects House maps this decision subsystem by subsystem at the start of a project: what gets bought, what gets adapted, what gets developed, and what the volume crossover looks like for each. If you want that map for your product before development starts, tell us about it through our contact form.