I built a platform where people can post their already-made projects or even services they are offering.
Also, I built a page dedicated for buyers requesting what they need so devs can search any opportunity.
Right now, I'm in the "chicken & egg" part😅.
Should I focus on the supply first?
What you'd do in my place?
I have a working website meant for people with already-made projects (e.g websites, mobile apps, etc.). They post them to showcase them to other people that might find them attractive.
But as I go deeper into the plan, it seems like I find myself in a 50-50 chance. Cause honeslty the majority don't make projects mindlessly, they instead offer their services as freelancing. But being realistic THERE is people with already finished projects.
website: mehor.com
What are your thoughts on this?
If you were me, how you'd do it?
Fuck yeah, I'm excited because finally I just launched.
I have been making a 2-sided marketplace
I need help with people testing the website though.
I would be appreciated for feedback on any aspect.💯
site: mehor .com
A few years ago, I poured my heart into a SaaS idea that I truly believed would work.
I sacrificed months to build it. Every new feature felt like a step closer to something meaningful. I imagined users discovering it, loving it, and turning it into a real business.
For a while, that dream kept me going.
But slowly, things started to unravel.
The users I expected never showed up. The features I spent weeks building were met with silence. Every launch felt smaller than I hoped. Instead of excitement, I started feeling frustration instead of momentum, I felt stuck.
The hardest part wasn't the lack of growth---it was watching something I cared about so deeply fail to gain traction.
I kept telling myself that one more feature would change everything. One more update. One more push.
It never did. Eventually, I stopped working on it.
For a long time, I saw that project as a failure. Months of effort with little to show for it. It was discouraging, and honestly, it made me question whether I should keep building products at all.
But looking back now, I realize the project wasn't a waste.
What finally worked wasn't building a better product---it was changing my approach.
Instead of falling in love with ideas, I started talking to potential customers before writing code. I focused on understanding real problems instead of assuming I knew what people wanted. I validated demand first and built second.
That shift changed everything.
The next products I worked on weren't driven by excitement alone. They were driven by conversations, feedback, and evidence that people actually needed a solution.
And for the first time, I wasn't building in the dark.
The SaaS I abandoned taught me one of the most valuable lessons of my career; a failed product can still be a successful education.
Sometimes the thing that works isn't the idea you started with----it's the lesson you learn when you're forced to let it go.