Red flags when hiring a product studio

Most founders hiring a studio for the first time are evaluating the wrong things: portfolio polish, client logos, the confidence of the pitch. Those signals are easy to optimize for and tell you almost nothing about what the actual engagement will feel like. The real warning signs show up earlier and quieter, usually before a contract is even on the table.

The first is a studio that can't tell you who did the actual client work in their portfolio. A polished case study with no clear answer to "who on your team built this, specifically" usually means the people who impressed you in the pitch aren't the people who'll be doing the work.

The second is vague scope presented as flexibility. "We'll figure out the details as we go" sounds collaborative and often means nobody has actually thought through what "done" looks like, which is how projects drift for months without anyone being able to say whether they're on track.

The third is a studio that talks exclusively in deliverables and never in outcomes. A studio focused on shipping screens will ship screens. A studio focused on your actual problem will sometimes tell you the screen you asked for is the wrong one to build first, and that willingness to disagree is a better signal than any amount of agreeableness in a pitch.

A studio focused on your actual problem will sometimes tell you the screen you asked for is the wrong one to build first.

The fourth, and the one we think matters most: ask what happens after launch. A studio with no answer, or an answer that amounts to "we hand it off," is telling you the engagement ends the moment their incentive to care does. We'd treat that as the clearest red flag of all, because a product's hardest problems usually show up after it ships, not before.