You are about to spend six figures on a digital agency. Maybe more. And the primary tool you have for evaluating whether they can actually deliver? A portfolio page with some pretty screenshots and vague descriptions like "increased engagement" and "modernized the digital experience."
That is not good enough. A portfolio should be a window into how an agency thinks, solves problems, and measures success. But most agency portfolios are designed to impress, not inform. Here is how to read between the lines and figure out whether an agency can actually do what they claim.
Results Over Aesthetics
The first thing most people do when reviewing an agency portfolio is look at the visual design. Does it look good? Is it modern? That is the wrong starting point.
Design quality matters, obviously. But a beautiful website that does not convert is an expensive piece of art. What you want to see in a case study is the outcome. Did the project move a business metric? Some specifics to look for:
- Conversion rate changes. "We redesigned the landing page" is a description. "Conversion rate increased from 2.1% to 4.8% after the redesign" is a result.
- Performance improvements. Lighthouse scores, Core Web Vitals, page load times... these are measurable and hard to fake.
- Traffic and engagement data. Organic traffic growth, bounce rate reduction, time on site. Not vanity metrics... business metrics.
- Timeline and scope. Did they deliver a complex project on time? Did the scope change dramatically? Agencies that talk honestly about timeline tell you a lot about their project management maturity.
If a portfolio is all screenshots and no numbers, that is your first red flag. Either they did not measure results (bad) or the results were not worth sharing (worse).
Industry Relevance vs. Range
There is a tension between wanting an agency that has experience in your industry and wanting an agency with broad expertise. Both matter, but the balance depends on your situation.
If you are in a heavily regulated industry (healthcare, financial services, government), you want an agency that understands compliance constraints. HIPAA, SOC 2, WCAG accessibility... these are not things you want an agency learning on your project.
For everyone else, range is often more valuable than deep vertical specialization. An agency that has only worked with SaaS companies might struggle when your content structure or user journey does not fit the typical SaaS playbook. An agency that has worked across B2B, e-commerce, publishing, and enterprise? They have seen enough patterns to adapt.
Look for case studies that show they can solve problems similar to yours, even if the industry is different. The underlying challenges... improving page speed, restructuring content architecture, increasing conversion rates... are often transferable.
Technical Depth: The Part Most People Skip
Here is where you separate agencies that execute from agencies that just design. A strong portfolio should give you a sense of the agency's technical capability:
- What tech stack did they use, and why? An agency that can articulate why they chose Next.js over Gatsby, or Contentful over WordPress, is showing you that they think critically about tools rather than defaulting to what they know.
- Did they solve hard problems? Migrating 50,000 pages from a legacy CMS without breaking SEO. Integrating a headless commerce platform with a custom checkout flow. Building a component library that scales across 12 brand sites. These are the projects that reveal real capability.
- How did they handle integrations? Modern web projects rarely exist in isolation. They connect to CRMs, marketing automation platforms, analytics tools, and commerce systems. Case studies that mention integration complexity tell you the agency operates in the real world.
If the portfolio only shows visual design work with no mention of the technical implementation, you might be looking at a design shop that outsources development. That is fine if you only need design. But if you need a team that can build and ship production software, dig deeper.
The Case Study Structure Tells You a Lot
Pay attention to how the agency structures their case studies. The best ones follow a clear narrative: problem, approach, solution, results. Each section tells you something different about the agency:
| Section | What It Reveals |
|---|---|
| Problem / Challenge | Do they understand business problems, or do they just describe the project scope? |
| Approach / Strategy | Do they have a process, or are they winging it? |
| Solution / Execution | Can they articulate the "why" behind technical and design decisions? |
| Results / Impact | Do they measure success with real KPIs or just show screenshots? |
Agencies that skip the problem section and jump straight to showing off the final product are telling you something. They are more interested in the work than the impact. That might work for award submissions, but it is a warning sign for a client engagement where your goal is business outcomes.
Red Flags to Watch For
After reviewing hundreds of agency portfolios over the years (including our own, honestly), here are the patterns that should make you pause:
- No dates on projects. If the portfolio does not tell you when the work was done, you have no way of knowing if it represents current capabilities. Web development evolves fast. Work from 2018 might as well be from a different era.
- All small projects. If every case study is a five-page brochure site, ask whether they have handled anything with real complexity... content migrations, multi-language support, enterprise integrations.
- The agency's own site is slow or broken. This one is brutal but fair. If their own website underperforms, what does that say about the attention they will give yours?
- Vague or missing client names. NDAs exist, sure. But if every single project is anonymized, you cannot verify anything. A mix of named and anonymized clients is normal. All anonymous is suspicious.
- No mention of ongoing support. Great projects need maintenance. If the case study ends at launch with no mention of iteration, optimization, or long-term partnership, the agency might be a build-and-move-on shop.
Questions to Ask Beyond the Portfolio
A portfolio only tells you what the agency wants you to see. To get the full picture, ask these questions directly:
- Can I talk to a past client? Any agency confident in their work will connect you with a reference. Reluctance is a red flag.
- What went wrong on this project, and how did you handle it? Every project has challenges. Agencies that only tell success stories are editing out the parts that reveal how they actually operate under pressure.
- Who specifically would work on my project? Agencies sell with their senior team and staff with juniors. Ask to meet the actual people who will do the work.
- What does your process look like after launch? The best agencies think beyond launch day. Performance monitoring, content optimization, iterative improvements... these are signs of a mature partner.
What a Strong Agency Portfolio Looks Like
At Last Rev, we try to practice what we preach here. Our case studies include the business problem, the technical approach, the measurable outcome, and the timeline. We show Lighthouse scores, not just screenshots. We talk about the hard parts, not just the wins.
That is what you should expect from any agency asking for a significant investment. Transparency about process. Honesty about tradeoffs. And measurable results that prove the work actually mattered.
If you are evaluating agencies right now and want a benchmark for what good looks like, reach out. We are happy to walk through our work and show you exactly how we approach these problems.