NU Product development firm

Build what's
next

We take hardware products from a rough idea to a production line. Industrial design, mechanical and electrical engineering, embedded software and manufacturing transfer, done by one team that stays with the product until it ships.

An engineer marking up a drawing at a workbench, tools and parts within reach.
Bench review, week threeFig. 01
Concept to productionOne team, no hand-offs
Four disciplinesID, mechanical, electrical, firmware
Four sectorsMedical, industrial, consumer, aerospace
You own everythingFiles, IP, tooling, vendor relationships

01 What we do

Most firms build what you specify. We help you decide what to build, then build it.

Every capability below lives in the same room. The industrial designer who sketches the enclosure sits next to the engineer who has to mould it, and both of them talk to the person writing the firmware. That is how the details stay coherent from the first foam model to the first production run.

03 How we work

Four phases. Fixed scope in each. A decision at the end of every one.

You always know what the next phase costs and what you will hold at the end of it. If the honest answer after a phase is stop, we say so.

Phase 01

Discover

We learn the job the product has to do, who does it today, and what would make them switch. We look hard for the reasons it might not work.

  • Field research
  • Technical feasibility
  • Requirements draft
  • Risk register
Phase 02

Define

Concepts on paper and in foam, then in working breadboards. We converge on an architecture we can defend on cost, schedule and risk.

  • Concept studies
  • Architecture
  • Cost model
  • Program plan
Phase 03

Develop

Detailed design across every discipline, built and tested in rounds. Each round retires a named risk. Documentation grows with the design, not after it.

  • Detailed design
  • Prototype builds
  • Verification testing
  • Design reviews
Phase 04

Deliver

Vendors selected, tooling kicked off, pilot units built on the real line. We stay through first production and hand over a package someone else can run.

  • DFM and tooling
  • Pilot builds
  • Line support
  • Transfer package

04 Where we work

Sectors where a second attempt is expensive.

An empty operating theatre with equipment arranged around the table.

01

Medical & life science

Diagnostics, durable equipment, wearables and lab instruments, with design controls run from day one.

Robot arms in an automated production cell.

02

Industrial & energy

Sensors, controllers, test equipment and tools that live in dirty, hot, vibrating places for a decade.

A smartwatch on a dark surface.

03

Consumer

Connected products where the margin is thin and the finish has to be right the first time.

A rocket lifting off the pad.

04

Aerospace & mobility

Payloads, ground equipment and vehicle systems where mass, power and qualification drive every choice.

05 What we believe

A few things we have learned the hard way.

01

Say the hard thing early.

The most expensive sentence in product development is "we should have raised that in month two." We would rather have an uncomfortable conversation in week one.

02

Prototype before you argue.

A two-day breadboard settles more debates than a two-week slide deck. We build early, break things on purpose, and let the results make the decision.

03

Design for the person on the line.

A product is not finished when the CAD is pretty. It is finished when an operator can assemble it in the time allowed, and a technician can service it in the field.

04

Your files are your files.

Native CAD, source code, test data, vendor contacts. Everything lives in your repositories from the start, so there is never a hand-over moment.

06 Start a conversation

Tell us what you are building. A paragraph is enough.

hello@nuproductdevelopment.com
Replies within two working days
NDA on request, before you share anything