1
0 Comments

Build in public week: what we changed in our supplier-matching workflow

Build in public update for MapleBridge:

This week we focused on one thing: reducing bad buyer-supplier intros.

Shipped:

  • Tightened intake form to force target market + compliance notes up front
  • Added a manual quality pass before first intro email
  • Standardized first message format so both sides see the same requirement summary

What broke:

  • We over-filtered at first and slowed first response time

What we changed:

  • Split strict filters (must-have) and preference filters (nice-to-have)

Current baseline: 500+ verified suppliers, 300+ buyer matches.

If you run a two-sided workflow, how do you balance speed vs match quality in early-stage operations?

Context: maplebridge.io

on March 31, 2026
Trending on Indie Hackers
I built a tool that shows what a contract could cost you before signing User Avatar 120 comments The coordination tax: six years watching a one-day feature take four months User Avatar 77 comments My users are making my product better without knowing it. Here's how I designed that. User Avatar 65 comments A simple LinkedIn prospecting trick that improved our lead quality User Avatar 58 comments I changed AIagent2 from dashboard-first to chat-first. Does this feel clearer? User Avatar 39 comments Why I built a SaaS for online front-end projects that need more than a playground User Avatar 18 comments