What should a B2B software design portfolio show?
A useful portfolio for B2B software shows workflows, data-heavy screens and the reasoning behind them. Landing pages and mobile concepts show little about the ability to design an ERP module.
Much B2B work is under NDA, so a portfolio may show anonymised examples and describe the problem in words.
Table of Contents
Summarize with:
Key facts
- Data density, several roles and redesigns of live products show B2B design ability.
- Much B2B work is under NDA.
- Anonymised examples with a description of the problem, constraints and decisions are common.
- Visual style alone is a weak basis for choosing.
- A conversation about one of your own workflows shows more than images.
What to look for
- Screens with real data density: tables, forms, line items
- Several user roles in one product
- Before and after for a redesign of a live product
- Design system components and rules
- A description of the problem, the constraints and the decisions
Portfolio evidence
Assess completed projects, reviews, enterprise experience, long-term partnerships and relevant domain expertise.
Reading a case study
| Look for | What it tells you |
|---|---|
| The problem in the client’s terms | Whether the team understood the business |
| Constraints | Whether the design was made to be built |
| Several roles and states | Whether the work goes beyond the main screen |
| Results reported by the client | Whether the work changed something measurable |
| Duration of the relationship | Whether clients come back |
Portfolio evidence
When work is under NDA
Anonymised entries describe the type of software, the scope and the constraints without naming the client. A discussion can test the team’s reasoning, but does not independently verify authorship or results. Ask for client-approved evidence or references where available, without requesting disclosure that breaches an NDA.
Common mistakes
- Judging by visual style alone
- Expecting named clients for every project in a field where NDAs are common
- Skipping a conversation about one of your own workflows
Where we’ve worked on this