I’m stuck on what to build next for Crazy Sajangnim
I’ve been building Crazy Sajangnim, a community-based fashion shopping platform focused on the moment between “I found this” and “should I actually buy it?”
The original idea started with discovering discounted fashion, but over time I’ve been trying to make the community side much more important. Instead of just browsing products, users can share finds, ask for opinions, talk about fit, quality, styling, price, and whether something is actually worth buying.
At this point, though, I’m a little stuck.
The basic product works, and I have a clearer idea of what makes it different from a normal shopping site, but I’m not sure what the next meaningful feature should be. I don’t want to keep adding features just for the sake of making the product look bigger.
Some ideas I’ve considered are better co-shopping tools, voting or “buy / skip” reactions, shared shopping lists, stronger user profiles, price tracking, product comparison, more detailed discussion around items, and ways to bring products in from any shopping website.
But I’m not sure which of these would actually make people come back regularly.
So I’d really appreciate suggestions from other founders and shoppers:
If you were using Crazy Sajangnim, what would you want me to add next?
Especially curious about:
What would make the community genuinely useful rather than just another comment section?
What would make you post a product and ask other people for opinions?
What feature would make you come back every week?
Is there anything I should actually remove or simplify instead of adding more?
I’m at the stage where outside perspective would probably be more useful than another week of me brainstorming features alone.
Comments (3)
The next thing to build isn’t a feature — it’s making one loop actually close: ask → fast answer → decision → outcome. Most of your list is either a piece of that loop or a distraction from it.
Two things kill “should I buy this?” communities:
Silence. Someone posts, gets nothing in 30 minutes, never posts again. Your retention lives and dies on response latency, not on how many tools you ship.
No resolution. Advice evaporates. Nobody finds out what happened. That’s what makes a community feel like a comment section. The thing a retailer can never build and you can is a record of what people actually did and whether they regretted it.
So I’d make the “should I buy this?” post a real object instead of a text box, with four parts shipped together:
A decision deadline. “Sale ends in 6 hours.” Native to discount fashion, so the urgency is real. Gives responders a reason to answer now and the asker a reason to come back.
Structured context. Size, measurements, budget, occasion, what it’s replacing. Bad advice almost always comes from missing context, and free-form posts never include it.
Buy / Skip tally with a required one-line reason. Voting alone is shallow. Voting attached to a reason is a scannable verdict.
A forced outcome follow-up. Two weeks later: did you buy it? Did you keep it? This is the whole game. It turns opinions into a track record, makes advisors accountable, and gives you data nobody else has.
That’s one coherent feature, not five, and it answers all three of your questions at once.
Supporting work, in order:
Paste-a-link import — cheap version first, just a URL parser for image/price/title. If people can only ask about your catalog, the loop is capped.
Fit profile, not user profile — sizes, measurements, brands that fit, past keeps and returns. A bio is dead weight; a fit profile makes every piece of advice better.
Price tracking — worth building, but be clear about what it is: a return-trigger for when the community is quiet. It’s a commodity. It won’t differentiate you.
What I’d cut or defer: product comparison tables (utility feature, no community leverage), shared lists and co-shopping (they need a social graph your early users don’t have yet), and a general product browsing feed (you’ll lose the browsing fight to real retailers on catalog and price — your feed should be questions and verdicts, not products).
Two risks worth naming:
Cold start is a service problem, not a product problem. Before you ship any of this, decide who guarantees an answer within an hour. At your stage that’s you plus 5–10 recruited people doing it by hand. Concierge is fine. Silence is fatal.
Monetization can corrupt the advice layer. If revenue comes from affiliate on purchases, “skip” works against you, and users eventually notice. Decide now how you’re handling that and say it out loud in the product.
The metric that tells you it worked isn’t DAU. It’s two numbers: the percentage of posts getting 3+ substantive responses within 60 minutes, and the percentage of posts with a recorded outcome. If both are high, you have a business. If they’re low, nothing else you ship matters.
Love that you said you don't want to just add more features, that's the right call.
You've had a lot of feedback in this community over the last few weeks and you still feel stuck. Sometimes feeling stuck is a useful feeling that stops us going in the wrong direction.
When I don't have clarity, I go back to the drawing board and start from basics as if I don't have a half-baked product at all. I write down who it's serving, what their pain is, and what they want instead of that pain. The product is the bridge from where they are today to where they want to be. Then I draw the solution from scratch.
On features, I like the Steve Jobs approach. Instead of adding, think about what can be removed.
But the thing that would help most right now is talking to your real audience. I suspect that's Korean American, fashion-aware, 20s to early 30s. Get on Zoom calls with them, record the meetings, ask what their actual problem is when shopping, how community affects it, what would solve it. Find the patterns and build around those. Ten of those conversations will give you more clarity than another month of feature lists.
Jinny, try this:
- Find around 10 people who would agree to try using your website. But don't tell them about it. Don't tell them what it is and how to use it. Dont' tell them the main purpose of your website and why you created it.
- Meet with each of them, let them open your website and ask them to have a look at it. Don't talk. Listen. Don't try to explain. Don't try to help them find things. Listen and take notes. You can do this in person or on Zoom or Google meet while they share their screen. Listen what they say. Watch where they tried to find a link or a button. Watch what was difficult for them to find, understand, or do. Take notes.
- After they are done, you can talk to them and ask your questions.
- Do not rush to make changes until you talk to enough of people. I would talk to 5-10 not less.
These will give you ideas what to work on. I am pretty sure about it.
But don't focus on building only. Once you see that it is pretty easy for people to find things on your website and use it. Stop building and start marketing.
Sign in to comment or upvote.