Skip to content
Insights/Article

When You Only Have a Few Case Studies, Do You Really Need Complex Portfolio Filters?

Key takeaway

When a B2B website has fewer than 15 public projects, avoid multi-axis filter bars or granular industry subpages that expose empty states and single-card categories. Instead, match structure to volume: show 1–5 cases on one page, and use a single-row filter with multi-tag cards for 6–15 projects.

Comparison illustration showing an over-filtered empty portfolio grid versus a clean single-row filter with information-rich project cards

When planning the "Projects" or "Case Studies" section of a corporate website, many B2B teams copy the interface patterns of global consultancies or large software vendors. Even with only 6 to 10 approved, publishable case studies on hand, they ask designers for an elaborate filter bar at the top of the page: eight industries, five service lines, and four project years. In a static mockup, that filter bar looks comprehensive. In a live browser, a buyer clicks two tags and immediately hits "No matching projects found"—or sees a single lonely card floating in an empty grid.

If your website has 15 or fewer public case studies, your portfolio page does not need multi-dimensional combination filters or a dozen industry subpages. Filters exist to reduce search friction. When a visitor can scan your entire body of work in two scrolls, complex filtering does not help them find proof faster—it actively exposes every category where you lack public projects. Right-sizing your top-level categories to match actual project volume, while moving industry and scope details onto the project cards themselves, creates a far more credible browsing experience.

Why Over-Categorizing a Small Portfolio Undermines Buyer Trust

In B2B services and manufacturing, having a small number of public case studies rarely means a company lacks experience. Strict NDAs, internal-only software deployments, or legacy visual assets often limit what can be shown publicly (for structuring individual cases under strict evidence and permission boundaries, see How to Write Credible Customer Case Studies: Evidence, Permissions, and Failure Boundaries). However, first-time visitors only see how your portfolio page behaves when they click around. Over-segmenting a small portfolio creates three immediate problems:

1. Multi-Axis Filter Bars Become "Empty-State Machines"

Consider the math of a multi-row filter bar. Suppose an industrial software provider launches with 8 approved case studies and places a filter bar at the top with 6 industries and 4 delivery types. That creates 24 possible combinations. Even if those 8 projects are distributed evenly, more than two-thirds of the combinations a visitor can click will return zero results. Hitting "No projects found" twice in a row makes a capable team look inexperienced in the exact niche the buyer cares about.

2. Single-Card Categories Look Thinner Than an Unfiltered Grid

Even with a single row of tabs, slicing 8 projects across 7 narrow industry tabs means almost every click leaves a single card sitting alone on the page. Displayed together in a unified 8-card grid, those projects look like a solid track record. Isolated one by one under granular tabs, they subtly suggest to a procurement lead that your company has only ever completed one project in their sector.

3. Thin Category URLs Dilute Both User Experience and Search Quality

Some teams generate separate indexable URLs for every minor project tag, hoping to capture search traffic across twenty industries. Yet as explained in Google Search Central's guide to creating helpful, reliable, people-first content, page quality depends heavily on whether the main content fulfills the page's purpose and delivers a satisfying user experience; creating thin pages primarily to target search queries runs counter to people-first principles. Furthermore, the Google Search Central SEO Starter Guide recommends organizing directories logically while reducing duplicate or near-duplicate URLs showing the same content.

Four Volume Tiers for Structuring Your Portfolio Page

Whether your portfolio needs filters—and how granular they should be—depends on how many verified, publishable projects you have ready today. Match your layout directly to one of four volume tiers:

Tier 1: 1–5 Public Projects — No Filter Bar; Use a "Selected Works" Showcase

When you have 1 to 5 public case studies, placing them into small three-column cards beneath a filter bar makes the page look unfinished. Instead, remove category filters entirely and design the page as an editorial showcase. Give each project a wide horizontal band displaying the visual preview, client context, specific scope of work (such as discovery, UI design, or system engineering), and a link to the full breakdown.

Tier 2: 6–15 Public Projects — One Row of Core Tabs (3–4 Groups) + Multi-Tag Cards

Once your portfolio reaches 6 to 15 projects, browsing everything takes two to three screen heights. A single-level, coarse-grained tab bar works well here if you follow two rules:

  1. Group by core service lines (3 to 4 tabs maximum), with at least 2 projects per tab. Merge any single-project category into a broader group until more cases are published.
  2. Show item counts and material expectations upfront. On ChengXuYuan's Projects page, for example, 8 public projects are grouped under four top-level tabs—"All (8)," "Websites & Standalone Sites," "Business Systems," and "Content & Interactive"—paired with clear notes explaining whether each card shows live pages, anonymized screens, or project identity marks.

Tier 3: 16–30 Public Projects — Primary Tabs + One Secondary Facet (Zero-Result Safe)

With 16 to 30 projects, you can pair primary service tabs with one secondary dimension (such as industry vertical), provided the interface prevents dead ends: when a visitor selects a primary category, any secondary filter option with zero matching projects should automatically hide or disable itself.

Tier 4: 30+ Public Projects — Featured Top Row + Multi-Facet Filtering and Search

Full multi-axis filtering, pagination, and keyword search become genuinely useful once a portfolio exceeds 30 public entries. Even then, pin 3 to 6 "Featured Projects" at the top of the default view so first-time buyers immediately see your strongest work.

Move Granular Dimensions from the Top Filter Bar Onto the Project Card

Information on one project card
  1. Authorized project visual
  2. Project type and name
  3. Scope of work
  4. Context and evidence boundaries

Sales teams often ask: "If we don't list eight industries in the top filter bar, how will a buyer from manufacturing, education, or travel know we have relevant experience?"

The answer is to print those industry and scope labels directly on each project card rather than turning them into top-level filter switches.

In a hypothetical scenario where a B2B digital agency has 8 public projects spanning hardware, education, travel, and advertising software, each card can carry four layers of information:

  • Layer 1 (Material Scope Badge): A badge on the thumbnail indicating visual evidence type (Live Page View, Anonymized System Screen, or Project Identity).
  • Layer 2 (Primary Service Category): A clear label matching the top tab bar, such as Corporate Website, Business System Development, or Interactive Mini-Game.
  • Layer 3 (Project Title & Context): A concrete title naming the client context and deliverable rather than an internal code name.
  • Layer 4 (Read-Only Scope & Industry Micro-Tags): Two or three scannable tags at the bottom of the card—for example, Cross-Border Travel · Bilingual Standalone Site · CMS or Education · Academic Scheduling · Role Permissions.

When a logistics operations lead scans that 8-card grid, they do not need a "Logistics" filter button. They can immediately spot cards tagged with Role Permissions or Resource Management and recognize that your team has built workflow systems of comparable complexity.

Portfolio Layout and Filter Selection Matrix by Project Volume

Use this matrix during website scoping to align your team on the right portfolio structure:

Public Project Count

Recommended Page Layout

Top Category Granularity

Filtering & Discovery Interaction

URL & Search Indexing Approach

1–5 Projects

Wide editorial showcase (split-screen or full-width cards)

No category tabs; present as "Selected Projects"

Direct vertical scrolling; zero filter clicks

Single canonical portfolio URL (e.g., /en/projects); no category sub-URLs

6–15 Projects

1 featured hero project + 2- or 3-column card grid

Single row of 3–4 core service tabs (≥2 projects per tab)

In-page tab switching with item counts; multi-attribute read-only card tags

Main portfolio URL as primary indexable page; avoid thin tag subpages

16–30 Projects

2- or 3-column grid + progressive "Load More"

1 primary service tab row + 1 secondary attribute

Linked filtering that disables or hides zero-result options automatically

Only create indexable category URLs for stable groups with substantial content (≥5 projects)

30+ Projects

Pinned "Featured Projects" row + filterable grid with pagination

Multi-dimensional taxonomy (service, industry, deliverable)

Combined filters + keyword search + one-click reset

Dedicated directory URLs for major categories; canonicalize or noindex filter parameters

Small-Portfolio Pitfall & Acceptance Checklist

Before signing off on your portfolio wireframe or staging build, run through this checklist:

[Small-Portfolio Page (15 or Fewer Projects) Design & Acceptance Checklist]

1. Inventory & Category Thresholds
- [ ] Counted only approved, publishable projects ready for launch (no "coming soon" placeholders).
- [ ] If total projects ≤ 5: removed top filter bars and switched to a wide showcase layout.
- [ ] If total projects are 6–15: consolidated top tabs into 3–4 core service categories, with at least 2 projects per tab.
- [ ] Removed granular filter rows for project year, region, or single-item industry niches.

2. Card Information Density (Replacing Heavy Top Filters)
- [ ] Every card displays a clear primary service/deliverable label.
- [ ] Card titles or summaries state the business scenario or industry context in plain language.
- [ ] Projects using anonymized screenshots, historical views, or brand marks include a clear material-scope note.

3. Filter Behavior & Empty-State Safeguards
- [ ] Clicking any visible top-level category tab never results in "0 projects found."
- [ ] If secondary filters exist, any zero-match state displays a clear message and a one-click reset to "All Projects."
- [ ] On mobile viewports, category tabs scroll horizontally or wrap cleanly without pushing the first project card below the fold.

4. Detail Page Handoff & Next Actions
- [ ] Every card links to a working project detail page and maps to the matching locale when switching languages.
- [ ] The bottom of the portfolio page provides a clear next step—such as exploring service scope or starting a consultation.

A portfolio page earns trust not by showing twenty filter dropdowns, but by ensuring every click reveals substantive, well-documented work. If you are planning a website build or redesign and want to structure a focused set of case studies effectively, explore our Corporate Website & Standalone Site Services or bring your current project list to our consultation page to discuss the right layout for your scope.

Sources

Let's talk about your project

Websites / Business systems / AI applications

Chat on WhatsApp