
Vestron — IG Save Organizer
Intelligent Curation for Modern Creators
Six months ago my Instagram saved folder had 500+ reels I'd never gone back to.
Recipes I meant to cook. Places I wanted to visit. Outfits I kept telling myself I'd wear.
The saving felt intentional. The forgetting didn't.
So I built Vestron. An app that AI categorises every reel you save and tells you who you are on Day 7 based on how you actually behave.
Here's everything honestly. What worked, what broke, and what I'd do differently.
The product
Vestron works through an Instagram bot. You DM it a reel. It gets categorised instantly — fashion, food, travel, tech, cinematic. Your vault organises itself while you do nothing.
You build a 7 day saving streak. On Day 7 Vestron assigns you one of 28 personality titles based purely on your saving behaviour. Not a quiz. Not a form. Your behaviour, observed.
"Keeper of Midnight" if you save after 11pm most nights. "Bringer of Storms" if you dump 15 things in 20 minutes. "Closer of Loops" if you actually act on what you save. "Collector of Intentions" if you commit to things and never do them.
We also shipped Wander. A community discovery feed showing what people with your aesthetic are saving globally.
The numbers
Total installs: 248 Monthly active users: 84 Daily active users: 6.6 Store conversion rate: 30.4% Firebase bill this month: ₹250 Marketing budget: ₹0
The 30.2% conversion is the number I'm most proud of. 1 in 3 people who find the Play Store page download it. The page is doing its job. The problem is almost nobody is finding it.
The night Meta broke everything
48 hours after V2 shipped, Meta deprecated the API we built our entire video experience on.
Old system: user DMs reel to our bot, webhook sends a CDN URL, we download and host the video, plays in app.
New system: Meta sends only the original Instagram URL. No downloadable file. No MP4. The reel lives on Instagram's servers and that's it.
We rebuilt the entire architecture in 48 hours.
New system: store the media ID, caption and thumbnail. When user taps to view, deep link directly to Instagram.
Honest take: it's actually better. We were hosting video files which meant storage costs, bandwidth costs, Firebase costs. Now it's just metadata and thumbnails. The bill is lower. The architecture is cleaner. Vestron was never meant to be a video player anyway. Instagram plays the reel. Vestron organises your life.
What I got wrong
I spent 6 months building before talking to a single user.
My first real user interview happened 2 weeks ago. One person. That's it.
That one interview told me the AI categorisation was defaulting to wrong categories when content was cross category. A bug I didn't know existed. Took 30 minutes to fix.
I should have talked to 10 users in month 1. I didn't. That's the honest gap.
What I got right
Event driven architecture from day one. All computation triggers from user saves, not scheduled jobs. 94.2% throttling efficiency on Firebase functions. Cost stays flat as usage grows.
The title system only evaluates once on Day 7 at the streak milestone. Cached for 20 hours. The system literally doesn't run unless it needs to.
What's next
Getting from 84 to 1,000 MAU.
First: the title card share feature. A Strava style transparent PNG sticker users post to Instagram Stories after their Day 7 reveal. That's the distribution engine.
Then intent capture, one tap chip on every save asking what's this for. Then Actualized %, did you actually do the things you saved. Then Brain Map, your saves visualised as an interest graph.
In that order. Not all at once.
The one thing I'd tell myself from 6 months ago
Talk to users before you build features. Even 5 conversations would have saved me months of going in the wrong direction.
Happy to answer anything. What are people building here that's in a similar space?
The problem: Saved 600+ Instagram reels over 2 years. When I actually needed something (cake recipe for mom's birthday), spent 12 minutes scrolling through Collections. Never found it.
The realization: Instagram Collections are a graveyard. No search, manual organization, you forget why you saved things. 80% of users save content, <5% can find it later. The solution: Vestron — first mobile app that organizes Instagram saves automatically. Share to @vestron_bot → AI categorizes → Search by description → Find in 5 seconds.
Tech: React Native, Python backend, Claude API for AI, Instagram bot integration. Journey: Built solo while freelancing. 6 months development. 2-week beta (25 users, 350+ saves organized, 92% success rate). Just launched on Play Store: https://play.google.com/store/apps/details?id=com.vestron.app
Current challenge: Getting first 100 users with $0 marketing budget. What's worked: Reddit, LinkedIn, beta user WOM Trying: Product Hunt, micro-influencers, SEO content
Questions for IH: - When to launch freemium paid tier? - Best growth tactics for mobile apps? - Launch iOS now or wait for Android traction?
Biggest learning: Building is easy. Distribution is brutal. But when users say "Found a reel I saved 3 months ago in 5 seconds" — worth every late night. Try it: https://www.vestron.in/ (free, Android, iOS coming soon)
Happy to share lessons on building while freelancing, AI integration, or Instagram's bot platform!
5 Likes
11 Comments
11 Comments
-
2
The way you framed the problem makes a lot of sense. People save things thinking that’s the solution, but the real issue is finding them later. Most of us have felt that exact frustration, so it’s easy to immediately understand the value here.
For growth, I’d lean into really specific moments like the cake recipe example. Those kinds of stories make people stop and think “yeah, that’s me.” Screenshots, short clips, or even casual replies in threads where people complain about saves will probably work better than anything broad.
On pricing, I’d wait a bit and watch how people actually use search. What they come back for, what they repeat, what they struggle with. That usually makes it clearer what’s worth paying for and what should stay free.
And honestly, the fact that users are already saying they found something they saved months ago is a great signal. That kind of feedback is what makes the long nights feel worth it.
-
1
Thanks for acknowledging.
Would look forward for you also to try the app and give me your personal feedbacks on how you find it.
-
-
2
Hey Indie Hackers 👋
I’m currently learning email writing, specifically for early-stage founders and indie makers.
My focus is on writing simple, human emails — not spammy, not salesy — just clear messages that founders can actually send to users or leads.
Right now I’m practicing on:
cold outreach emails
Follow-up emails
short onboarding emails
I’m not selling anything here — just trying to get better by learning from real builders.
If you’ve launched a product recently:
What kind of emails worked for you?
What emails did NOT work at all?
Happy to share a short example email if anyone’s interested.
Thanks for reading
-
1
For the first 100 users, I’d avoid pitching this as “AI organizer” and make the hook extremely concrete: “send us one saved Reel you can’t find, we’ll find it.” That gives you a fast before/after demo.
I’d also wait on iOS until you know Android activation is solid. If 25 beta users already saved 350+ items, the next thing I’d measure is week-2 repeat usage, not installs.
-
1Hey john, thanks for you comment, i really appreciate it, Just wanted to let you know, the particular post was when i was just getting started, at the moment the app is at 700+ users and over 60k+ saves. and for the retention rate its moving aroud 79% with 1 of our user completing a streak of 100+ days.
-
-
1
the cake recipe moment is gold - that specific story will outperform any generic "organize your saves" message on social by a mile. for early mobile growth at zero budget, reddit threads where people are actively complaining about the problem tend to be the most efficient channel since they're already primed. on freemium timing, i'd watch for one thing first: are users coming back to search within a week? if yes, that's the signal the core value is landing and it's safe to add a paywall. what's your d7 retention looking like so far?
-
1
Congrats on the launch 👏
How was your Play Console review process?
I’m currently in closed testing with an Android app and the subscription + tester requirements have been… educational 😅
Anything that surprised you post-launch? -
1
Congrats on the launch 👏
Curious — how was your Play Console review process?
I’m currently in closed testing and the 12-tester requirement + subscription setup has been… educational 😅
Anything you wish you knew before launch? -
1
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?
-
1
for starters i am using social media marketing and some outbound reach, not really good at marketing and sales, but yeah thats the plan.
-
1
I completely understand. Most founders face similar challenges in the early stages. Building a product is already a significant undertaking, and marketing and sales often take a backseat.
Using social media and outbound strategies is a good starting point, but it can be quite unpredictable, especially when you're still figuring out who truly connects with your product.
One approach that has worked well for me with early-stage products is leveraging Reddit. Rather than using it for promotion, I recommend it as a platform to test your messaging and the core problem you're addressing in genuine discussions. This way, you can receive honest feedback quickly without needing strong sales skills.
If you're interested, I can help you conduct a small, low-risk pilot on Reddit. I would take care of selecting the right subreddits, crafting discussion-style posts, and engaging early on. This would allow you to focus on product development while still gaining insights into what users really care about.
I'm happy to explain how this process would work and see if it aligns with your current needs.
-
-
About
I built Vestron because I was tired of losing content I saved. 600+ Instagram reels saved. When I needed a recipe for my mom's birthday, I spent 2 hours scrolling and never found it.







Comment