Marketplace Design Review
Does a first-time visitor know within 5 seconds what kind of listings are here, how to start comparing, why to trust what they find, and where to go for depth?
When to Use
Use this checklist when building or auditing a site whose primary job is presenting business listings, venture ideas, tools, offers, or content packages for discovery, comparison, acquisition, or commitment.
The test: Cover the nav and logo. Can a visitor in 5 seconds identify (a) what kind of listings are here, (b) how to start comparing, (c) why to trust the listings, and (d) where the deeper know-how or proof lives? If no to any — fail.
Marketplace vs Gateway vs Chooser
Not every marketplace is trying to sell a product immediately. Some are gateways into ideas, know-how, proof, or implementation. Name the surface job before reviewing the page.
| Surface type | User job | Page must expose | Failure mode |
|---|---|---|---|
| Marketplace | Buy, invest, subscribe, acquire | Price, trust, availability, comparison attributes, checkout path | Looks interesting but cannot convert |
| Chooser | Compare options and pick the next action | Sort/filter, same mini-IA per item, proof state, disqualifiers, CTA verb | Becomes a gallery of identical cards |
| Gateway | Route to the right depth surface | Destination types, idea vs know-how vs proof, route labels, escape path | Mixes all content jobs into one confusing surface |
| Portfolio index | Decide what deserves attention | Stage, model, score, target, kill signal, next action | Rewards browsing instead of commitment |
| Data catalog | Find a specific record or trusted dataset | Search, filters, freshness, source, schema, download/API path | Forces manual scanning and unverifiable reuse |
Research Basis
This checklist applies three external UX findings to Dream surfaces:
- NN/g list-entry guidance: a list entry should behave like a small webpage, with attribute priority reflected in the mini-information architecture and visual design.
- NN/g faceted-search guidance: filters should be appropriate, predictable, jargon-free, and prioritized.
- Baymard product-list research: product lists, sorting, and filters determine whether users can reduce a large set to a manageable, relevant set.
Interpretation: a venture, offer, or idea card must expose the same decision attributes in the same order. Otherwise the reader or agent cannot compare honestly.
1. Hero Section
| Check | Threshold | Measure |
|---|---|---|
| Outcome-led headline | Headline says what the user gains, not what the product is | Read aloud — does it say "learn/find/acquire" or "we are a marketplace for..." |
| Headline length | ≤10 words | Count words |
| One primary CTA | Single above-fold action, unique color | Squint test — one element stands out without focusing |
| Subheading bridges pain to benefit | Pain → solution → outcome structure | Does it name a real friction before offering the answer? |
Diagnosis:
| Symptom | Fix |
|---|---|
| Headline starts with "We" or "Our" | Rewrite: lead with what the visitor walks away with |
| Two CTAs compete above fold | Pick one. Demote the second below the fold. |
| Subheading explains features | Replace with the problem it solves |
2. Listing Card Anatomy
| Check | Threshold | Measure |
|---|---|---|
| Specific names | Real company, founder, or idea name — no "Major Retailer" | Scan 10 cards — any generic title fails |
| Demand signal on card | ≥1 quantified signal per card (votes, downloads, revenue, search volume) | Count cards without a number |
| Problem-first hierarchy | Card text communicates what it solves, not just what it is | Cover test: strip visuals — does text alone communicate value? |
| Card scannable in 3 seconds | Key info visible without hover or expand | Time yourself reading 5 cards cold |
| Same mini-IA | Every comparable item uses the same attribute order | Compare five cards — attribute order must not drift |
| Discriminator above fold | The highest-value decision attribute is visible before body copy | Cover lower half of card — can you still compare? |
Diagnosis:
| Symptom | Fix |
|---|---|
| Cards look identical | Add demand signal as the differentiating visual element |
| Generic listing titles | Require actual name + one-line problem statement in listing submission |
| Users hover to understand | Promote the hover content to the card face |
| Cards compare poorly | Define a mini-IA contract before styling: tension, descriptor, proof, metric, action |
3. Trust Signals
| Check | Threshold | Measure |
|---|---|---|
| Named testimonials | CEO/investor/founder quotes with name and title — no anonymous | Count unnamed quotes |
| Media logos | Top-tier publications only, ≤6 logos | Remove any logo your target audience would not recognise |
| Usage metrics | Concrete numbers (600K listeners, 200+ listings, $4M raised) | No "thousands of users" — find the exact number |
| Methodology transparency (data tools) | Explain how data is sourced and validated | For AI/data-driven tools — show the method, not just the output |
Diagnosis:
| Symptom | Fix |
|---|---|
| Logo wall without quotes | Logos signal category; quotes signal conviction. Add a quote or remove the logos. |
| Vague social proof ("loved by teams") | Replace with a specific number and a specific named person |
| Data source unexplained | Add one sentence: "Data sourced from X, validated by Y" |
4. Discovery and Navigation
| Check | Threshold | Measure |
|---|---|---|
| Nav items ≤6 | Minimal header navigation | Count nav links |
| Multiple discovery paths | At least: recent, trending/ranked, and search | 3 entry paths minimum |
| Return mechanic | Daily email or notification opt-in visible | Is there a low-friction way to come back? |
| Mobile-first CTA | Email signup preferred over app install | App install adds friction on mobile — email captures intent first |
| Sort/filter controls | Required when 6+ comparable items exist | Count comparable cards; controls must appear before the grid |
| Result count | Visible when filtering or sorting exists | Change filter; count updates clearly |
| Reset path | One action clears filters | Filter to zero results; reset must be visible |
| Empty state | Explains what the filter means | Force no-match state and read message |
Diagnosis:
| Symptom | Fix |
|---|---|
| List-only discovery | Add a ranked/trending sort — not all visitors know what they want |
| Nav with 10+ items | Collapse into 6 or fewer; route the rest to footer |
| No return mechanic | Add email capture — even a "new listings" digest is enough |
| Filters mirror internal jargon | Rename to user decision attributes, or add explanatory labels |
5. Trust, Proof, and Kill Signals
For idea, venture, and agent-facing marketplaces, trust is not only social proof. It is evidence state.
| Check | Threshold | Measure |
|---|---|---|
| Evidence state | Every claim says proven, validating, projected, unvalidated, or consumed | Count cards without an evidence label |
| Commercial basis | Revenue, price, or ROI includes time basis and avoids false precision | "$36k/yr projected" beats "$692.31/wk" |
| Kill signal | Each unproven opportunity names what would stop it | Scan cards for disqualifier, deadline, or constraint |
| Proof route | Strong claims link to proof, case study, receipt, or methodology | Click proof cue; route must explain why to believe |
| Destination type | Idea, know-how, proof, demand, and implementation are visibly distinct | First-time visitor can say which route they are opening |
Diagnosis:
| Symptom | Fix |
|---|---|
| "Conviction" presented as proof | Label as projected or validating; link to what would prove it |
| Revenue looks precise but untested | Round the number and add projected / actual / target |
| All CTAs say "View" | Match verb to stage: inspect, pressure-test, see proof, compare, commit |
| Gateway links all look interchangeable | Label each destination by job: idea, know-how, proof, demand, build |
6. Pricing (SaaS and Tool Marketplaces)
| Check | Threshold | Measure |
|---|---|---|
| Freemium activation | Free tier with daily or limited access — removes "I'll try later" | Does the page let someone start without a card? |
| Pricing visible | Not hidden behind an email gate | Homepage or one click away |
| Launch urgency | Time-limited or seat-limited pricing if early stage | Real constraint only — no fake countdown |
| Tier differentiation | 3 tiers with feature differences readable at a glance | Cover test: can you explain each tier in 5 words? |
Diagnosis:
| Symptom | Fix |
|---|---|
| No free tier | Add a limited daily access tier — even 3 free views/day qualifies |
| Pricing hidden | Move above the fold or add persistent "Pricing" nav link |
| Tiers have 20 feature rows | Reduce to 5 rows; move detail to a comparison page |
7. Anti-Patterns
- Logo carousels without quotes — logos signal category, quotes signal conviction. If you have logos, add a quote from that organisation.
- Generic listing titles — "Interesting opportunity in logistics" is not a listing. Require actual company name and one-line problem statement.
- Pricing hidden on content sites, shown on tool sites — match visibility to monetization model. Membership sites can gate pricing; tool sites cannot.
- List-only discovery — always offer ranked or trending as an alternative sort. New visitors do not know what to search for.
- "Coming soon" on a premium tier without a waitlist — kills urgency and captures no intent. Add waitlist capture if the tier is not ready.
- Hover-dependent card content — mobile users cannot hover. Promote key information to the card face.
- Decorative taxonomy colour — colour must encode model, stage, risk, or action; arbitrary gradients are visual noise.
- Gateway without depth route — if a card raises a method question, the page must route to know-how instead of trapping the reader in more cards.
- No disqualifier — an opportunity without a kill signal is a pitch, not a decision surface.
Component Decision Checklist
Record these decisions in the implementation PR, page comment, or design receipt before closing.
| Component | Decision to record |
|---|---|
| Hero | What decision does this page help the visitor make? |
| Gateway doors | Which destination types are intentionally separated? |
| Control bar | Which attributes are sortable/filterable, and why those attributes? |
| Listing card | What is the mini-IA order, and which attribute is the discriminator? |
| Trust/proof cue | What evidence state appears before the click? |
| Kill signal | What stops this option from consuming more attention? |
| Empty state | What does a no-match result teach? |
| Mobile layout | What remains visible without hover or wide-screen comparison? |
| Agent-legibility | Which data-*, schema, or route labels make the page machine-readable? |
Verification Loop
Run this after implementation:
- 5-second gateway test: identify listing type, comparison start, trust basis, and depth route.
- Mini-IA scan: compare five cards; the same attributes appear in the same order.
- Filter test: apply one model/stage/type filter, confirm count, reset, and empty state.
- Mobile test: card content remains understandable at 375px without hover.
- Proof test: every strong claim links to evidence or labels itself as projected/unvalidated.
- Agent test: inspect
data-*, JSON-LD, route labels, or semantic headings for machine-readable decision attributes.
Context
- Product Design hub — Hard Thresholds Table (touch targets, CTA uniqueness, conversion benchmarks)
- Landing Page Design — generic conversion patterns for single-product pages
- Data Interfaces — table and list design for dense listing views
- Interaction + Accessibility — search, filter, and keyboard UX
- Responsive + Performance — mobile marketplace and LCP targets