A portfolio is evidence, not an album

Reviewing an engineering firm's portfolio is one of the most efficient ways to decide whether the vendor in front of you actually fits your project. The problem is that most founders look at a portfolio the way they would look at a photo album: they are impressed by beautiful renderings, recognizable products, and client logos, and they never ask the questions behind the picture.

A good portfolio is not a collection of renders. It is evidence that the firm can take an idea all the way to hardware that works and gets manufactured. Here is what to look for, what to ask, and what should make you cautious.

What to look for

  • Technological proximity, not industry proximity. Projects that resemble yours technically matter more than projects from your industry. A mechanism-driven mechanical product is closer to your device than a software product from your exact market.
  • Depth of involvement. Did the firm carry the project from requirements through production, or execute a single phase and hand off the rest?
  • Real hardware. Photographs of physical prototypes, production runs, drawings, and test setups — not only computer renderings.
  • Variety of manufacturing methods. Projects spanning injection molding, machining, sheet metal, and electronics indicate genuine engineering breadth rather than one repeated trick.
  • The whole story. What was the problem, what was tried, what failed, what got fixed. A firm that talks about the difficulties usually knows how to solve them.
  • Evidence of production reality. Photos of first article parts, fixtures, or assembly steps signal that the firm has been through manufacturing, not just design.

The questions to ask about each project shown

After looking at the pictures, the real work starts. For each project that interests you:

  • What exactly did you do here? Full design, an improvement to an existing product, or only production drawings from someone else's concept?
  • Who was the project engineer, and are they still with the firm? Knowledge lives in people, not in folders.
  • How long did it take versus the original estimate? The gap, and how they explain it, tells you how they estimate.
  • How many prototype iterations were needed before a version that worked?
  • Did the product reach production, and is it selling? A project that stopped after prototyping is not necessarily a failure, but the answer teaches you a great deal.
  • What would you do differently? The quality of this answer separates engineers who reflect from engineers who repeat.

A broader interview list is in how to choose a product design firm.

Warning signs in a portfolio

Weak vendors show consistent patterns.

A portfolio made entirely of spectacular renderings with not a single photograph of physical hardware usually indicates visual capability rather than engineering capability. Displaying a large company's logo without being able to explain what was actually done for them is padding. A portfolio consisting only of work from many years ago, with nothing current, raises a fair question about who is still there.

Another sign is a blanket refusal to say anything about any project. NDAs genuinely restrict disclosure, but an experienced firm can describe an engineering challenge and its solution without revealing identifying details. If even that is impossible, ask at minimum for a reference who can confirm the engagement.

A final and less-discussed warning sign is a portfolio consisting exclusively of projects in one narrow field. That is excellent if you are in that field, and risky if your product requires disciplines the firm has never touched. The related question of how much domain experience you actually need is covered in whether your engineering firm needs experience in your industry. The full catalog of vendor warning signs is in red flags when hiring an engineering firm.

How portfolio review fits the overall decision

Portfolio review does not stand alone. It is one criterion alongside availability, team composition, pricing model, and personal chemistry. Cross it with the size question — see a large firm versus a boutique engineering studio — and with the technical depth assessment described in technical due diligence.

Pay attention to how the firm treats ownership of deliverables, a subject detailed in who owns the IP in product development. An impressive portfolio is worth little if the files at the end are not yours. In the same spirit, ask what a completed project's release package looked like — the contents of a proper package are described in the manufacturing data package. A firm that can show you a real one has finished real products.

What we recommend doing in practice

Pick two or three projects from each vendor's portfolio and go through them in depth in conversation, instead of skimming dozens. Fifteen minutes on a single project reveals more than any presentation.

Ask to see the drawing, the intermediate version that was rejected, and the part that was 3D printed before it was molded, and ask what was learned at each step. Ask who made the hard call when two disciplines disagreed. Ask what the firm would price the same project at today, and why the number changed.

Then compare the answers rather than the images. Vendors who have actually shipped products enjoy these conversations, because the war stories are the interesting part of the work. Vendors who have not will steer you back to the renders.

Ask us the same questions

You are welcome to put every question in this article to Projects House and go through our projects in the same depth. More on selecting a development partner is in our product engineering companies guide. Reach us through the contact form and we will show you projects close to your product and explain exactly what we did in each one.