Industrial design studios are becoming strategic partners for brands developing new products

–

Why do brands now bring an industrial design studio in before the engineering brief exists, rather than after? Because the earliest choices — product architecture, target cost, supplier assumptions, what the product has to do better than the alternatives — are the ones a programme keeps paying for later. A studio that frames the problem, writes testable requirements and records trade-offs is doing procurement and engineering work as much as drawing work.

In plain terms: a strategic industrial design partner is a studio hired to make, document and defend product decisions, not only to produce visuals.

The short version. Three things are worth asking for before you sign: a decision log from a closed programme, phase-by-phase deliverables with the decision each phase closes, and evidence of design-for-manufacturing work carried out with real suppliers rather than described in a capability deck.

A note on vocabulary, because it has become slippery. Industrial design is the discipline that shapes a manufactured product's form, use and production logic together. Product design is often used more broadly, covering the whole path from requirement to released specification. Concept design is the early exploratory phase where options are generated and compared before anything is committed. Hiring a studio strategically means paying for the reasoning as much as for the drawings that result from it.

The brief changed because the product did

Many categories that were once largely mechanical now arrive with a control board, firmware, a connectivity story, a companion app, recyclability expectations and a certification path across several markets. Espresso machines show how far the discipline has travelled: coffee machine design was once mostly a question of stainless steel, proportion and a memorable silhouette. A comparable programme today tends to involve thermal management, water circuit tolerances, descaling access, interface logic, acoustic behaviour, and a bill of materials that has to survive a purchasing review without losing the qualities the price point promised.

Then there is the fragmentation of the supply chain. Few brands manufacture everything under one roof. Tooling may sit with one supplier, electronics with another, assembly somewhere else, packaging with a fourth party. Each optimises for its own constraints, which is rational behaviour. The difficulty is that nobody owns the seams — and in many programmes the seams are where the schedule breaks.

Misalignment rarely appears as a budget line. In practice it tends to surface as a tooling modification weeks before pilot production. As a retest, because a wall thickness moved after a certification submission. As a product that functions correctly but feels cheaper than intended, because a soft-touch finish was removed in a cost-down meeting nobody documented. Late changes are slow in themselves, and teams often find they propagate: a dimension that moves can invalidate a fixture, a gasket, or a test report already filed. This is precisely the failure mode that studios structured around early integration say they exist to prevent — a claim you can test by asking how, and with which artefacts.

What is a strategic industrial design partner?

The word strategic gets used loosely. Here it has a narrow, usable meaning: strategy is deciding what to optimise and what to sacrifice, early enough that the decision is still cheap to make.

A useful way to distinguish a supplier from a partner is to look at what lands in your inbox. Outputs alone — sketches, renders, a CAD file, a moodboard — describe a service relationship. A partnering relationship adds the reasoning that produced them: requirements split into negotiable and non-negotiable, comparable concepts with their cost and manufacturing implications stated alongside them, a record of the alternatives considered and rejected, and prototype evidence that answers a specific question rather than simply photographing well.

That last artefact deserves a name. Call it a decision log: a plain document listing each significant choice, the alternatives, the constraint that drove the outcome, who approved it and when. Entries are unglamorous and short. Rear housing wall raised to 2.4 mm to pass the corner drop test; adds 6 g and one second of cycle time; approved by engineering and product on 14 March; alternative rib pattern rejected because the mould would have needed a side action. It reads like paperwork. Months later, when a supplier proposes shaving that wall back to save a few cents per unit, the log tells you in thirty seconds whether the dimension was arbitrary or load-bearing. Traceability is what allows a decision to be revisited without being re-litigated from scratch.

Studios organised around this logic tend to describe their work as a sequence of named gates rather than a creative arc, and the phrasing matters: named phases produce named deliverables, and named deliverables can be reviewed before they turn into steel. It is worth looking at how that structure gets published. On its website, the Italian studio PQ Design sets out its method as product strategy, product architecture, product design, user experience, design validation, alignment and design for manufacturing, and states that integrating design, engineering and manufacturing from the earliest phases is what keeps late-stage errors from hitting cost, timing and quality. Read against the decision-log argument above, two of those names do real work: an alignment phase is a scheduled moment where procurement and manufacturing have to speak before geometry hardens, and a validation phase is where prototype evidence is meant to exist in writing rather than in someone's memory. The studio, founded by Piero Quintiliani, has operated since 2009 and works from Milan, Pisa and Shenzhen, and in a 2025 interview it declared more than 150 clients worldwide. Those are stated figures rather than audited ones; the transferable part is the phased structure and the insistence on early integration, which you can ask any candidate studio to demonstrate on a past programme.

The six responsibilities brands increasingly delegate

Taken together, these read less like a service menu and more like a set of standing responsibilities that somebody in the programme has to hold.

1. Problem framing

Who uses the product, in what context of use, and what has to be true for it to succeed commercially. Concept design that skips this step often produces attractive proposals that cannot be defended in a steering committee, because nobody agreed in advance on the criteria for choosing between them. Framing is also where measurable objectives get written down: landed cost, assembly time, weight, cycle life, and the two or three usability outcomes that genuinely matter.

2. Concept architecture

Before surfaces, the skeleton: how the product splits into modules, where the interfaces sit, which components could be shared with a future family. Architecture choices tend to be the hardest to revisit later. A single-model architecture unable to host a second variant can turn out to cost far more than the original design fee once the roadmap moves.

3. Cross-functional alignment

Brand, engineering, procurement and manufacturing each hold a partial view of the same constraint set. Somebody has to hold the whole picture and force the conversations that internal calendars tend to postpone. In lean teams that role frequently lands with the external studio, for the unglamorous reason that it is often the only party present in every meeting.

4. Prototyping strategy

Fidelity is a budget, not a virtue. The discipline lies in sequencing: take the highest-risk question first, at the lowest fidelity that produces a trustworthy answer. A crude foam block can settle an ergonomic argument that a photorealistic render will only prolong. Equally, no amount of visual polish will tell you whether a hinge survives its intended number of cycles.

5. Industrialisation readiness

Design for manufacturing and assembly, tolerance logic, draft angles, materials and finishes chosen against real supplier capability, and a documentation package a factory can build from. This is usually where studios with production exposure separate themselves from studios with beautiful portfolios. A typical moment: the moulder comes back and says the parting line has to move because the undercut requires a slide, which adds tooling cost and a week of lead time. A studio without industrial reflexes accepts the change and discovers later that the parting line now crosses a visible surface. A studio with them proposes a different split, or negotiates the cosmetic consequence explicitly, and writes the outcome down.

6. Launch resilience

Packaging that protects the product through the logistics chain you actually use. Assembly instructions a line operator can follow without interpretation. Serviceability, spare parts availability, and the quiet work of preventing returns — handling, inspection and refurbishment costs that do not always sit in the original margin model, and that are worth putting on the table while the design can still influence them.

Where the partnering model pays for itself

No engagement model produces outcomes on its own, and a studio promising a fixed percentage of savings is selling something other than method. The mechanisms by which a strategic engagement can create value, though, are concrete enough to name and to check.

• Fewer iteration loops. Manufacturability and usability problems caught before tool cutting are corrected in CAD. After tool cutting, they are corrected in steel — and in the schedule.
• Margin protection. Cost can often be designed out through part consolidation, simpler assembly and smarter material choices without degrading what the customer perceives. Cost removed in a purchasing meeting with design absent from the room has a habit of showing up on the shelf.
• Shorter time-to-market. Not by working faster, but by running design, engineering and supplier dialogue in parallel against a shared constraint set, instead of sequentially with a surprise at each handoff.
• Portfolio coherence. A consistent physical design language and interaction logic across a range is a brand asset, and defining it once is generally cheaper than retrofitting it across five models.
• Cleaner handovers. Documentation written for someone who was not in the room reduces dependency on individual memory when the team changes.

How to evaluate a studio as a partner, not a vendor

Portfolios are a weak filter, because the visible part of a project is the part that survived. The criteria below are more revealing, and each can be tested in a single conversation.

• Depth of discovery. In the first call, do they ask about your business model, distribution channel, target landed cost, expected volumes, service strategy and regulatory context — or mainly about references and style?
• Decision governance. Ask to see a redacted decision log or trade-off summary from a closed programme. If nothing of the kind exists, decisions on your project will live in email threads.
• Engineering integration. How do they work with an internal engineering team they do not control, and with a supplier's engineers who have every incentive to simplify their own work?
• Prototype literacy. Can they describe a test they designed, what it was meant to falsify, and what changed as a result? Building models is a craft; planning experiments is a competence.
• Production handoff quality. Ask what the release package contains: drawings, tolerance rationale, finish specifications, colour standards, assembly sequence, acceptance criteria. Vagueness here becomes expensive later.
• Sector realism. A toy designer working to child-safety requirements and a team designing industrial equipment for continuous duty operate under different failure modes. Relevant constraint experience usually beats general brilliance. In regulated fields, ask whether the team works under an applicable quality management system — for medical devices, for example, whether anyone in the chain is certified to ISO 13485 — and ask for the evidence rather than assuming it.

Red flags tend to be the mirror image: a proposal that prices only visual deliverables; reluctance to speak with your suppliers; a schedule without validation milestones; material choices framed as sustainability with no discussion of lifecycle, disassembly or repairability; and an unwillingness to state plainly what they would not take on.

Structuring the engagement

Two models cover most situations. An embedded team — the studio operating as an extension of your organisation, involved continuously — suits programmes where requirements are still moving and decisions arrive weekly. Milestone-based engagement suits well-bounded scopes with a stable brief and gives finance a cleaner picture. Royalty arrangements also exist, with the studio developing the product and the intellectual property while the brand carries manufacturing and distribution; that structure can align incentives around commercial success, but it changes who controls the roadmap, so it deserves careful reading before signature.

Whatever the model, three things are worth agreeing in writing before kickoff. Who decides what, and by when. What the brief contains: constraints, target cost, volumes, applicable regulations, brand principles, and an explicit list of items not open for negotiation. And how intellectual property, documentation and design source files transfer, so that version two is not hostage to version one.

The recurring mistakes

Design treated as a late-stage skin remains the most common and among the most costly: by the time the object exists, many of the choices that determine its cost, its assembly time and its user experience have already been made by people optimising for something else. Close behind sits heavy investment in visual exploration with light investment in requirements — a project can accumulate dozens of concept boards and still lack an agreed definition of success.

Then there is the supplier conversation postponed until drawings are frozen, which converts negotiable design intent into a fixed constraint. And the absence of any plan for the next generation: an architecture locked so tightly around one configuration that the follow-up product effectively starts from zero. Coming back to the phased method discussed earlier, this is exactly why naming an alignment gate is more than vocabulary — it creates a scheduled obligation to hold that conversation while it is still free.

Three questions buyers keep asking

What are the typical stages of product development?

Most structured programmes move through some version of the same sequence: opportunity framing and requirements, concept generation, concept selection, detailed design and engineering, validation and testing, industrialisation and pilot production, then launch and post-launch iteration. Names differ between organisations; what matters is that each stage ends with a decision someone owns.

How much does working with an industrial design studio cost?

Fees vary widely with scope, sector and the amount of engineering included, so any single figure would mislead. A more useful approach is to ask for pricing broken down by phase, with deliverables and decision points listed per phase — that way you can see what you are buying, and stop after a gate if the business case changes.

Where should a brand look for a partner?

Design award databases, sector directories, industry publications and referrals from suppliers or contract manufacturers all surface credible candidates, and directory entries make basic facts — founding year, locations, declared specialisms — reasonably easy to check. The filter that matters afterwards is the same in every case: production experience in a comparable constraint environment, and a documented way of making decisions.

What this means for teams building products now

For a lean organisation, the right industrial design partner works as a capability multiplier — not because it replaces internal expertise, but because it holds the parts of the programme that would otherwise fall between departments each optimising separately. The engagements that go well tend to start the same way: with a risk map rather than a moodboard, and with an agreed framework for how decisions will be made, recorded and revisited.

One practical test for your next selection call. Ask the studio to describe a project where they got something wrong, and what the decision record showed afterwards. The answer will tell you more about how they will handle your programme than any portfolio.