Founder Guide 3 min read

How to Evaluate a Product Development Studio: 7 Questions Every Founder Should Ask

Most founders evaluate studios on portfolio and price. That's not enough. Here are the 7 questions that actually predict whether an engagement will go well — based on interviews with 200+ founders.

Choosing a product development studio is one of the highest-stakes vendor decisions an early-stage founder makes. Get it right and you have a team that ships, learns fast, and de-risks your fundraise. Get it wrong and you’re six months and $150k in with nothing usable.

1. Who specifically will work on my project — and can I meet them before signing?

Studios win work with their senior partners and present case studies from their best teams. The people who actually build your product are often different. This is the bait-and-switch that experienced founders warn about most consistently.

Ask for the specific names, titles, and seniority of the team assigned to your engagement. Then ask to meet them — even a 30-minute Zoom — before contracts are signed. Any studio worth working with will say yes immediately.

Red flag: “Our team assignment process happens after contract signing.” This is how founders end up with three junior engineers when they expected two seniors.

2. Can you share 3 clients from the last 18 months I can call?

Testimonials on a website are useless. What you want are warm reference calls with founders who built something similar to what you’re building, in the last 18 months, at a comparable budget. When you get on those calls, ask: “What went wrong? How did they handle it? Would you rehire them if you could start over?”

What good looks like: Three references provided within 48 hours, all from the last 18 months, all willing to share the hard parts.

3. What does your discovery process look like — and is it included in the quote?

The best studios invest real time in discovery before writing a line of code. This means defining user flows, identifying technical risks, and producing a scoped spec. Founders who skip this step consistently report scope creep and timeline blowouts.

Ask for: A sample discovery deliverable from a past client. If they can’t show you one, they probably don’t do real discovery.

4. How do you handle scope changes mid-engagement?

Every MVP changes mid-build. The question is whether the studio has a mature process for handling that. Studios with good processes have a formal change order workflow with written approval, clear pricing logic, and no surprises.

Green flag: “Here’s our change order template. We document every scope change in writing and get sign-off before we build.”

5. What happens to the code if we part ways?

Ensure your contract specifies that all code, design assets, and credentials are your property from day one — and that the studio is obligated to hand over clean, documented repositories upon engagement end.

6. How do you communicate progress — and how often will we meet?

The studios that founders consistently rate highest have one thing in common: predictable, low-friction communication. Weekly demos with the actual product, async Slack updates, and a single point of contact who has technical authority.

7. What does post-launch support look like?

Ask specifically: what’s the support SLA after launch? Who’s the point of contact? Is it included, or billed separately? A reasonable expectation: 30–60 days of post-launch support included at no additional cost.

The bottom line

A good studio will welcome these questions — and will have clear, consistent answers. A studio that hedges, deflects, or can’t produce references is telling you something important before you sign anything.

If you want our shortlist of studios that scored well across all these dimensions, see the 2025 product development company rankings.

Alex Morgan
Senior Research Analyst
8+ years evaluating software studios for startup founders. Developed the EarlyStage.guru scoring methodology.
Stay updated on our rankings
Add EarlyStage.Guru as a preferred source on Google — see our updates first.