Browsing on Zaar, with category filters, search, and real student listings.
01 — The problem
A marketplace built for college students
My co-founder and I came up with the idea for Zaar as seniors at Brown. Moving into our apartments, we were frustrated by how hard it was to buy and sell things with other students. People listed items in Facebook groups or on Instagram accounts, so it was nearly impossible to search for what you wanted. Some students even built Google Slides presentations just to list what they were selling.
We weren't trying to build the next eBay. We wanted to build the right tool for one community with needs that came back every year: buying furniture at move-in, selling it at move-out, finding textbooks, and getting rid of things before summer.
02 — Research
Four things students told us
Before designing anything, I interviewed students about how they bought and sold things on campus. Their answers were remarkably consistent.
Students trust other students, not strangersMany students, especially women, were uncomfortable meeting strangers from Craigslist or Facebook Marketplace. Knowing the other person went to their school made a big difference. That became the basis of Zaar's trust model: verifying a university email at signup.
Ease and proximity matter more than priceStudents didn't mind walking to pick up something from another student nearby. The cost and hassle of shipping made apps like Depop and Poshmark less appealing than a local exchange.
Facebook groups don't work for thisThere was no search and no filters, just endless scrolling to find a couch, only to learn it had already sold. Students were frustrated with the tools they had.
Students prefer secondhandCollege students move every year, so spending money on furniture they'll leave behind in twelve months felt wasteful. Buying secondhand wasn't just about budget. It made more sense.
03 — Design
Starting with the core loop
I made every design decision, including the brand, information architecture, listing flows, browsing and search, messaging, and the transaction experience. My co-founder handled engineering. We had no funding, no team, and a deadline of six weeks that we set ourselves.
We launched with listings, search, category filters, messaging, and a way to arrange a local exchange. We left out a personalized feed, shipping, and payments, and focused on the core loop: list, find, message, and meet.
The most important decision was about trust. Requiring a university email at signup changed how both buyers and sellers behaved, and it made meeting in person feel safe. That's what made local exchange work, which shipping-based apps couldn't offer.
Browsing, searching, and listing an item on Zaar.
04 — Reflection
What I still use from Zaar
Zaar didn't become the company we hoped it would. We ran into the classic marketplace problem: buyers and sellers had to grow together, and we didn't have the resources to support either side long enough. But the product worked. Students used it, sales happened, and the YC interview told us the problem was real.
The habit I've kept from Zaar is asking how to get 90% of the value with 10% of the effort. At Zaar, that meant search and categories before personalization, local exchange before payments, and a university email check before any more complex trust system.
I use the same approach in enterprise software. For task management at Storable, we started with just launch and retrieval, because those two task types covered most of what operators needed. The system was built to support more later, but the first version didn't try to do everything.
Zaar taught me that deciding what to leave out is often harder, and more important, than deciding what to add.