Most business owners evaluating a dev agency spend too much time looking at the wrong things. They scroll through portfolio screenshots, admire the visual design, and decide the agency looks “legit.” Then they sign a contract and discover, six weeks in, that the work on those screenshots was done by a different team, for a client with completely different needs, two years ago.
A portfolio is not evidence of quality. It’s marketing. Your job when evaluating one is to look past the aesthetics and find out what the work actually was, who it was for, and whether any of it is relevant to what you need built.
Here’s how to do that.
Look for Relevant Industry Experience, Not Just Volume
An agency with fifty portfolio items might have less useful experience than one with eight, depending entirely on what those projects were.
What matters is whether the agency has built something similar to what you need, in terms of complexity, industry context, or user type. An agency that has built SaaS tools for healthcare clients has a different kind of knowledge than one that has built e-commerce stores for retail brands. Both might produce beautiful code, but only one understands the constraints and requirements of your situation.
When reviewing a portfolio, ask: “Have they built something structurally similar to what I need?” Not an identical product, that rarely exists. But a product with similar user flows, similar integration requirements, or a similar target audience.
If the portfolio feels thin for your use case, that’s worth raising directly on a discovery call. Ask what projects they’ve done that aren’t publicly listed. Some agencies have confidentiality agreements that prevent them from showing certain work, but they can describe the project type, scope, and outcome without naming the client.
Ask About Results, Not Just Deliverables
The weakest portfolios describe outputs. The strongest describe outcomes.
“We built a booking platform for a home services company” is an output. “We built a booking platform for a home services company, and their inbound inquiry-to-booking conversion rate went from 12% to 34% in the first three months” is an outcome.
Outcomes tell you two things: that the agency measures the right things, and that the client was willing to share the results because they were good enough to be worth sharing. Most agencies don’t ask clients for outcome data because asking means being accountable to it. The ones that do ask are usually confident in what they built.
On a call, ask directly: “Can you tell me about a project where you can point to a specific business result?” If the agency draws a blank, or gives you generic answers about how happy the client was, that tells you something. If they can walk you through a specific number, a before and after, that’s a much stronger signal.
Check the Speed of Their Past Work
This one is easy and almost nobody does it.
If an agency’s portfolio links to live websites, run those sites through PageSpeed Insights or a similar tool. A Lighthouse score in the 90s suggests the agency cares about performance. A score in the 40s or 50s suggests they shipped something that looks fine but performs poorly, and performance directly affects search rankings, bounce rates, and conversion.
A slow website is one of the most common ways small businesses lose customers without knowing it. Our post on 5 signs your website is costing you customers covers this in detail, a 1-second delay in load time can reduce conversions by 7%.
If the agency built your competitor’s site and it loads in 800ms on mobile, that’s a meaningful signal. If it loads in 6 seconds, that’s a meaningful signal too, just not the kind you want.
Look for Signals of Code Quality
You probably can’t read code. That’s fine, you don’t have to. But there are proxy signals worth looking for.
Do they mention testing? Agencies that write automated tests have to think more carefully about how their code is structured. It’s an indicator of engineering discipline. If testing isn’t mentioned anywhere in how they describe their process, ask about it directly.
Do they mention documentation? Good code documentation means a future developer can pick up where they left off without needing to reverse-engineer everything. If you ever want to update, expand, or hand off your project to an in-house developer, documentation is what makes that possible.
Do they offer a code handoff? Some agencies deliver a finished product but make it difficult or impractical to take the code elsewhere. They host it on proprietary infrastructure, use custom frameworks nobody else uses, or simply never hand over a clean codebase. A good agency gives you the code at the end, organized, documented, and ready for any developer to pick up.
Do they describe their QA process? Quality assurance is the work of finding and fixing problems before they reach production. An agency that treats QA as a distinct step in their process has built that discipline in. An agency that describes shipping and then fixing bugs as normal isn’t describing discipline, it’s describing a broken process with a workaround.
If you want a full picture of the questions worth asking a potential agency before you commit, our guide on what to look for in a dev agency covers the green flags, red flags, and specific questions for every intro call.
Ask About Client Retention and Repeat Business
One of the most reliable signals of quality in any service business is whether clients come back.
Ask the agency: “What percentage of your clients do a second or third project with you?” or “Can you point to a client you’ve worked with multiple times?”
A high repeat rate means clients trusted the agency with something, it went well enough that they didn’t need to find someone else, and they came back voluntarily. That’s not a manufactured review, it’s a decision made with real money on the line.
The inverse is also telling. An agency that has done hundreds of projects but struggles to name clients who came back for more has a pattern of one-and-done relationships. Sometimes that’s the nature of the project type. But often it’s a sign that the experience was good enough to finish but not good enough to repeat.
You can also ask for references, not the names the agency leads with, but someone from a project two or three years ago. That person is no longer in the honeymoon phase and can tell you what the experience was actually like over time.
Red Flags That Should Give You Pause
Not every red flag is obvious. Some of the most common ones are designed to look professional.
Stock photos in the portfolio. If the “screenshots” in a portfolio are mockups on a laptop with a stock image background, rather than actual screenshots of real software running in a browser, the agency may be showing you concepts they pitched rather than products they shipped. Ask to see the live URL.
No case studies, only screenshots. A screenshot tells you what something looked like. A case study tells you what problem existed, what was built to solve it, who the client was, and what happened afterward. Portfolios full of screenshots with no context are designed to look impressive without being accountable to specifics.
Vague results language. “Our client was thrilled” or “the project was a huge success” tells you almost nothing. If outcomes are mentioned, they should be specific. “We reduced their manual data entry time from 3 hours a day to 15 minutes” is a claim someone can verify. “They were really happy with the results” is not.
Work that’s all from the same time period. If every portfolio item is from 2021 or 2022 and nothing is recent, ask what they’ve built lately. Agencies that were busy two years ago and are heavily pitching now may be experiencing a quality or reputation problem that caught up with them.
No public pricing or range. Agencies that won’t give you even a ballpark before you sign an NDA often don’t have enough experience with their own service types to know their own pricing. That’s a scoping problem that will show up later.
What Good Portfolio Evaluation Actually Looks Like
You’re not trying to find the agency with the prettiest work. You’re trying to find the agency that has solved problems like yours before, can show you the results, and has a track record of clients who trusted them enough to come back.
That means looking beyond the surface: asking about outcomes, checking technical quality, verifying recent work, and asking the question most people skip, “who comes back?”
When you find an agency whose portfolio answers those questions, the rest of the evaluation gets much easier.
What We Show, and Why
Our work page shows specific projects with context: what the client needed, what we built, and where we can point to results. We don’t pad it with screenshots of things that aren’t our work or outcomes we can’t support.
We build MVPs, AI integrations, workflow automations, and performance websites for small businesses and startups, and we’ve done enough of those that we can give you a real answer when you ask whether we’ve built something like what you need.
If you’re evaluating us alongside other options, that’s exactly what you should be doing. Come to the call with the questions from this post. We’ll answer them directly, show you relevant work, and tell you honestly if we’re not the right fit.
Key Takeaways
- Relevant industry experience matters more than portfolio volume, look for structural similarity to your project
- Ask about outcomes (business results), not just deliverables (what was built)
- Run portfolio sites through PageSpeed Insights, performance scores reveal engineering discipline
- Ask about testing, documentation, and code handoff as proxy signals for code quality
- Repeat clients and long-term relationships are the most reliable indicator of quality
- Stock photos, vague results language, and case-study-free portfolios are worth questioning before you sign anything
Ready to See What We’ve Actually Built?
Book a free 30-minute consultation. We’ll walk you through relevant work, answer the hard questions, and give you a clear picture of what working with us looks like from proposal to handoff.