Why Pay for a Phase That Produces Only Documents

The most common objection to a definition phase is that it produces no hardware. That is exactly the point. Its job is to convert an idea into a specification precise enough that an engineering team can quote the real work with confidence, and precise enough that you can decide not to build it.

The economics are simple. A change made in definition costs an hour of somebody's time. The same change during detailed design costs a few thousand dollars. After tooling is cut it costs $10,000 to $40,000 and six weeks. Skipping definition does not remove the decisions; it defers them to the point where they are most expensive.

What the Phase Actually Produces

A definition phase is a research and decision project. Typical output:

  • A written requirements document with measurable targets: dimensions, weight, run time, force, accuracy, temperature range, target landed cost, target retail price, and the standards the product must meet.
  • A technical concept. Two or three architecture options with block diagrams, a recommendation, and the reasoning behind it.
  • Preliminary industrial design. Sketches or a rough CAD volume study, enough to see size, proportion, and user interaction.
  • A costed BOM estimate at your target volume, with the big-ticket components identified and priced from real distributor data rather than guessed.
  • A regulatory map. Which approvals apply, roughly what they cost, and how long they take, so you know early whether the answer to does your product need regulatory approval changes the whole business case.
  • Competitive and patent landscape. What already exists, what it costs, and whether an obvious design path is blocked.
  • A development plan and budget for the phases that follow, broken into gates with deliverables.
  • A risk register. The five to ten things most likely to break the project, each with a mitigation and a cost.

What Drives the Price

Definition phases vary in cost by a factor of twenty, and the variation is not arbitrary. Six factors explain most of it.

Number of engineering disciplines. A purely mechanical product needs one specialist. A connected device needs mechanical, electronics, firmware, app, and cloud thinking, and each discipline adds days of architecture work and coordination.

How much is unknown. If the physics is established and you are packaging known parts, definition is fast. If the core question is whether a sensing method works at all, you are running a feasibility investigation, not a definition, and the pricing in feasibility studies applies instead.

Regulatory weight. A consumer accessory maps to a short standards review. A Class II medical device or a product with a lithium battery and a radio requires real regulatory strategy work, and that alone can double the phase.

Market research depth. A desk survey of competitors is a couple of days. Structured user interviews, a distributor pricing study, and a demand test are weeks.

Cost target severity. Hitting a $19 retail price requires the team to price and re-architect repeatedly. A $2,000 industrial instrument gives far more headroom and takes less iteration.

Client readiness. Clients who arrive with a clear use case, a target customer, and a price point cut the phase substantially. Clients still deciding what the product is pay for that deliberation.

Realistic Price Ranges

Working from typical US and offshore-blended engineering rates, which run $85 to $200 per hour depending on the firm and the discipline, as covered in product development consultant rates:

  • Simple mechanical product, no electronics. $3,000 to $8,000, typically two to three weeks. A housewares item, an accessory, a fixture.
  • Mechanical product with basic electronics. $8,000 to $18,000, three to five weeks. A battery-powered device with a motor and a few controls.
  • Connected product with an app. $18,000 to $40,000, five to eight weeks. Adds wireless architecture, cloud, app scope, security, and provisioning decisions.
  • Regulated device. $30,000 to $75,000 and up. Adds regulatory pathway strategy, preliminary risk analysis, and a quality system plan.
  • Industrial machine or system. $25,000 to $80,000, driven by throughput requirements, safety standards, and integration with existing plant equipment.

As a sanity check, a definition phase usually lands between 5 and 12 percent of the full development budget. If someone quotes you a definition phase that is 40 percent of what you expect to spend overall, either the phase is padded or the development estimate is fantasy. The broader picture is in what it costs to develop a new product.

How to Spot a Serious Proposal

A definition phase is easy to sell and easy to pad, so read the proposal like a contract, not a brochure.

  • Named deliverables with formats. "Requirements document, 15 to 25 pages, PDF and editable source" is a deliverable. "Concept exploration" is not.
  • A fixed price and a fixed duration. A definition phase has a bounded scope; if a firm will only bill it hourly and open-ended, the scope is not defined.
  • Cost estimates with sources. The BOM estimate should cite distributor pricing and quoted tooling, not round numbers.
  • An explicit stop option. A good firm tells you the phase may conclude that the product should not be built, and treats that as a successful outcome.
  • Portable output. You should be able to take the package to any other firm and get a comparable quote. If the deliverable only makes sense to the firm that wrote it, you are locked in. That portability is what makes comparing engineering quotes possible at all.
  • Clear IP terms. The requirements, concepts, and analysis should be yours on payment, with no ambiguity.

Who Writes It, and Can You Do It Yourself

You can write a first draft of the requirements yourself, and you should. Founders know the use case and the customer better than any consultant will after two weeks. What most founders cannot do alone is set achievable engineering targets or price a BOM. The practical split is covered in who writes the product requirements spec, and the format to aim for is in how to write a PRD.

Hiring one firm for definition and a different one for development is entirely legitimate, and buying a single phase is a normal way to test a firm before committing to a year of work. The considerations are in hiring a firm for one phase.

Get a Scoped Definition Proposal

Projects House runs fixed-price definition phases with named deliverables and a fixed end date, sized to the product rather than to a template. Describe your idea, your target price, and your volume through our contact form and we will come back with a scope, a number, and a date.