B150 Product Marketplace

B150 Product Marketplace

The platform where builders build the future

Product Overview

B150 is building infrastructure for this new generation of builders. The vision: a community-showcase flywheel where you can discover people building in topics you care about, follow their journey, and showcase your own work/projects,all in one place.

Timeline

2025 (Coming Soon)

Tools

Figma, Cursor, Figma MCP, Typescript, WebGL, NextJS

Role

Product Designer | Design Engineer

TLDR

I designed and built a marketplace platform that would help the new generation of founders list their products, and grow post-launch. Current platforms fragment their story: Product Hunt captures launch hype, LinkedIn shows a professional persona, and Discord buries products under noise. My challenge: Build a platform that would empower builders post their tools and products, provide support for them post-launch and leverage B150's existing community flywheel.

The Challenge

Building has changed. The tools got better; the ecosystem didn’t. A solo founder can validate a problem on Friday, build with AI over the weekend, and ship by Monday. But the platforms meant to support them are stuck in old patterns:

  • Product Hunt ≈ launch hype, no context
  • LinkedIn ≈ career story, not builder story
  • Discord ≈ community chaos, product gets lost
  • Reddit ≈ feedback, but scattered
In our research, builders kept repeating the same frustrations:

In our research, builders kept repeating the same frustrations:

“I can build fast, but getting credible feedback is almost impossible.” “Everything is hype. No one tells you the hard truth.” “I want to find people building what I actually care about.” “There’s nowhere to show the story behind the product.” We saw a gap: a platform that captures who’s building, why, and how the product evolves over time PLUS a community to support too. This became the core hypothesis behind B150.

Understanding Who We're Building For

Kat led our research phase, starting with "How Might We?" questions: - How might we help builders get credible feedback? - How might we surface high-signal products without gatekeeping? - How might we design for trust that builds over time? Through surveys and user interviews, four personas emerged. Each group had different needs. Builders wanted discovery and collaboration. Investors wanted to see traction over time, not just launch-day hype. Creatives needed category-specific attributes (BPM for music, resolution for art). The audience wanted curation without gatekeeping.

Design and build the marketplace layer for B150:

Design and build the marketplace layer for B150:

A space where you can discover softwares, tools, resources and creative assets created by fellow builders. The focus was to build in a way that ensures that post-launch, builders and creatives find consistent value in the product. My responsibilities:

  • Define the MVP scope
  • Shape the marketplace experience through the UX research
  • Design + engineer core flows (listing, product pages, launch, review system)
  • Stress-test design decisions through real implementation with Cursor + Figma MCP
  • Keep the UX grounded in research and category nuance

We made an early strategic call;

We focused the MVP on Products & Startups. The decision was a largely strategic decision because of so many factors like;

  • The AI-building boom is happening right now which empowers more individuals to be builders
  • We can build for product discovery; connecting builders with those that need their products and users with the perfect products.
  • There is an established market and need for what we provide and offer.
  • Stronger footing for early monetization
  • Immediate, real pain points to solve
We made an early strategic call;

Decision 1: Custom Categories over Templates

I tested a universal template for all product types. It broke immediately. Different categories have different technicalities. MCPs, for example, care about tech stack, compatibility, and functions while Music/Sound has BPM, mood, and licensing. SaaS? A different ballgame - features, team, and product info. The variability of all the required information for each product type means we had to build for each scenarios and use cases. So I designed flexible category schemas. More work, but foundational to building trust.

Decision 2: Pricing Transparency

When we started building for pricing, we knew that we had to think of the flow. We were offering three processes - reviews, sponsored listing, and a mix of both. Each of these processes involve user flows that are independent of each other; and should be treated So I redesigned it. Transparency shifted the emotional tone from “why this price?” to “okay, this is fair.” This only emerged when I built the actual UI, which showed the power of being designer + developer.

Decision 2: Pricing Transparency

The Design–Dev Feedback Loop

Working in Cursor + Figma MCP meant I could move from idea → pixels → working code in hours, stress-testing designs before they hit engineering. Owning both sides let me catch subtle UX issues:

  • Cards too dense: Reorganized hierarchy, added progressive disclosure
  • Forms felt painful: cut 40% of fields, made tone conversational
  • Pricing unclear: added transparent breakdown
  • Listings overwhelming: added filters, infinite scroll, “Recently Updated”

What We Built

Listing Page — Discovery with Context - Builder profiles shown inline - Filters for topic, category, trends and popularity - “Last updated” signals active development Community indicators - Product Page — Trust Over Time - Builder profile - connected to main platform - Signals for investors (features, traction, team) Launch Flow — Lightweight + Clear - Minimal required fields - Preview before publishing - Transparent pricing breakdown

Although pre-launch, this project produced clear outcomes:

  • A working community–showcase flywheel: Builders can showcase their product, investors can track progress, and the audience can discover projects based on genuine activity—not hype.
  • A flexible, scalable category system We can expand from Products → Sounds → Art without breaking UX or dev architecture.
  • A differentiated review model High-signal, platform-authored reviews set us apart from every “launch + hype” alternative.
  • A strong foundation for future community and investor tools B150 now has a marketplace layer that can support profile growth, product evolution, and meaningful discovery.
Although pre-launch, this project produced clear outcomes:

Reflection: What I Learned

This project is ultimately about context. A product isn’t just something you launch; it’s something you build, and most recently, in public, over time. B150 gives builders a place where their journey is finally visible. Building the experience myself changed the way I design:

  • I caught friction that doesn’t appear in mockups
  • I made more pragmatic decisions
  • I moved faster in early iteration
  • I gained a deeper understanding of implementation tradeoffs