How to Evaluate a Software Development Company's Portfolio and Case Studies

A Case Study Is Marketing Until You Verify It

A case study is, by design, the best version of a story an agency can tell about its own work — curated screenshots, a favorable metric, a client quote that was almost certainly approved by the agency before publication. That doesn't make it worthless, but it does mean you should treat it as a claim to verify, not evidence to accept. The single most useful thing you can do with any case study is ask to speak directly with the client it's about, unprompted by the agency, and see whether the story holds up in an unscripted conversation.

Check Whether the Product Is Actually Live

Before anything else, check whether the products in a portfolio are actually live and being used, not just shipped once and abandoned, and not just a polished prototype that never launched. A link to an app store listing or a live URL you can actually use tells you far more than a screenshot — you can check load times, real functionality, and whether the thing still works months or years after the engagement described in the case study ended, which tells you something about whether the underlying code was actually built to last.

It's worth also checking who on the current team actually worked on the case study you're looking at, rather than assuming the whole company shares equally in it. Agencies grow and change over time, and a flagship case study from three years ago may have been delivered by engineers who've since left. Ask directly whether anyone currently proposed for your project worked on the referenced case study, because a portfolio entry is only as relevant to your decision as the people still there to repeat it.

Match the Tech Stack and Team Size to Your Own Project

A portfolio full of impressive work in a completely different domain, tech stack, or team size than what you need doesn't tell you much about whether that same company can deliver your specific project well. A five-person team that's built several complex marketplace platforms is a strong signal if you're building a marketplace; it's a much weaker signal if you need a small, focused AI integration built by two engineers. Look for portfolio entries that match your project's actual shape — team size, tech stack, and problem type — not just entries that are impressive in the abstract.

It's also worth reading a case study for what it doesn't mention. If a company describes a project's launch in detail but goes quiet on what happened in the months after — no mention of continued iteration, no numbers on retention or usage that persisted past launch day — that silence is often as informative as anything the case study does say. Agencies are generally happy to talk about work that kept paying off; an abrupt ending to the narrative is worth asking about directly.

Look at How Long Engagements Actually Lasted

Check whether the case studies describe one-off projects or ongoing relationships, and ask directly how long the average engagement with a portfolio client has lasted. A company whose clients consistently leave after the first deliverable is telling you something, even if the case study itself reads as a success — either the initial scope was all the client needed, which is fine, or the relationship didn't hold up past the honeymoon period, which is worth knowing before you sign a longer engagement yourself.

A case study answers whether this worked once. The question that actually matters is whether this client would sign again today, and that's the one no case study page will ever answer for you.

It's also worth weighting quantity over any single flagship story. One impressive case study can be a genuine outlier — the right client, the right scope, a bit of luck in how it came together — while a portfolio of several solid, unglamorous projects that all shipped, launched, and are still running tells you more about repeatable process than one standout success does. When you're learning how to evaluate a software development portfolio, consistency across many smaller engagements is usually a stronger signal than a single headline win.

Ask for a Reference You Didn't Find on Their Website

The most reliable part of learning how to evaluate a software development portfolio is getting a reference you can independently verify — ask the agency for a contact at a past client, ideally one whose project is a few years old rather than freshly wrapped, so you're hearing about a relationship that's had time to reveal its real strengths and weaknesses. If an agency is confident in the quality of its work, this request should be easy for them to fulfill, and the conversation you have will tell you far more in fifteen minutes than any case study page could in an hour of reading.

For a closer look at how an engagement actually runs, see our delivery process.