Picking a development partner is a bet on how the next six to twelve months of your product will go. Portfolio screenshots tell you almost nothing about how a team actually works day to day — and that's the part that determines whether your project ships on time, on budget, and in a state your own engineers can maintain afterward.

Look Past the Portfolio

Every agency's case studies are, by definition, their best work presented in the best light. Ask instead how they scope discovery, whether they show you code during the engagement or only at the end, and how they've historically handled scope changes when a client's priorities shifted mid-project. The answers to those questions predict your experience far better than a polished before/after slide.

Ask for a Reference From a Year Ago

Ask for a reference from a client whose project shipped over a year ago — not last month. Software that's still running cleanly a year later, without a costly rewrite, says more about a team's engineering discipline than a launch-week demo ever will. A team that's proud of month-old work is easy to find; a team whose year-old work still holds up is the one you want.

Evaluate Their Estimating Track Record

Every team gives estimates. Fewer teams have a track record of hitting them. Ask directly: over your last ten projects, how close did the final delivery date land to the original estimate, and what caused the biggest miss? A team that can answer this honestly, including the miss, is more trustworthy than one that claims a perfect record.

Watch How They Handle "No"

The best signal often comes from watching how a potential partner responds when you propose something that's a bad idea — an unrealistic timeline, a shortcut that will cause problems later, or a feature that doesn't serve your actual users. A team that pushes back with a clear rationale, rather than agreeing to keep the deal, is one that will protect your product later when it matters more.

The Real Checklist

• Can they show you working code mid-engagement, not just at delivery?
• Do they have a reference from a project that shipped over a year ago?
• Can they explain a time an estimate was wrong, and why?
• Do they push back on bad ideas, or just say yes?
• Is their communication cadence something your team can actually sustain?

None of this shows up in a portfolio. All of it shows up in the first month of working together — which is exactly why it's worth asking about before you sign anything.