I Built ManyLinks in 11 Days to Fix My Broken Bookmark System
I was saving 20+ links a day and finding almost none of them later.
Articles, tools, GitHub repos, AI resources. I was dumping them into browser bookmarks, Notes, chats, and random docs. Then when I actually needed something, it was gone.
So I built ManyLinks.
The Problem
My "save for later" system was chaos:
- Bookmarks I never reopened
- Links spread across too many apps
- No reliable way to search everything in one place
The main pain wasn't saving links. It was rediscovering them when it mattered.
Why I Decided to Build It
I couldn't find a simple tool that did all three things well:
- Save any URL fast
- Organize it automatically
- Make it easy to find later
So I started building my own solution in public.
From Idea to Launch in 11 Days
I shipped it quickly and iterated daily.
Day 3: First real version
- Basic UI working
- Link ingestion in place
- First folder flow implemented
Day 4: Public feedback
I shared it early and got direct feedback from my audience. That helped shape what mattered most in v1.
I also asked people to vote on the domain. The winner was manylinks.app.
Day 11: Launch-ready
- Core product experience stable
- Pricing and onboarding polished
- Security and rate limits added
- Product live for real users
What ManyLinks Does
ManyLinks is built around one promise: stop losing useful links.
From the live app today:
- AI-powered categorization: paste any URL, and AI extracts metadata, categorizes it, and writes a concise summary
- Folder-based organization: keep links cleanly grouped and easy to manage
- Markdown export: move your library into tools like Notion or Obsidian
- Full-text search: search across titles, summaries, and tags to rediscover links instantly
If you save lots of content to "read later," this is exactly what it's for.
What I Learned Shipping This Fast
1. Build for your own daily pain first
The feedback loop is much faster when you're the first power user. I used ManyLinks while building it, so priorities stayed obvious.
2. Building in public improves product decisions
Public updates and quick feedback made the product better in days, not months. It also made launch less scary, because people were already following the journey.
3. Speed comes from focus, not rushing
I didn't build everything. I built the core loop: save -> auto-organize -> find again.
That single focus made the launch possible.
Try ManyLinks
ManyLinks is now live.
If your bookmarks are a mess and your "saved links" never get reused, try it:
I'm documenting the full build-in-public journey on X/Twitter, including what I ship, what breaks, and what I learn.