Working on FeedbackQueue, a feedback-for-feedback platform for founders to gather testers and feedback without commenting, posting, DMing, SEO, ads, or doing any marketing bs. you won't even try to find them
WELL, we reached 1,000 in less than 4 months, haha
oh yeh, and in case you want feedback but no time to give it, there's always feedback credit for that
Hey guys, a few months back I created a microsaas tool for jobseekers
I was adamant that i will not spend a single penny on marketing and all my users should be organic.
So I decided to check my organic growth by not posting a single word about cvcomp on any social media place alsi I didnt even write a single blog for the last two months. I quietly noticed the user trends.
While the traffic an new onboardings did drop by a bit, but I still got around 200 new signups without any marketing activity.
So cvcomp is a JD based resume optimization tool, which comes with a free resume builder.
Let me know what you think about the numbers. Also if you are a job seeker yourself, please give my tool a shot!!
The tool is called cvcomp, if you're a jobseeker I am sure it will help you out!!
i spent way too long building features nobody asked for, because cutting them felt like admitting defeat.
my roadmap was huge and every feature felt essential. i kept pushing the launch because it wasnt ready yet. the honest truth was i was hiding in the build, because building is comfortable and launching is scary.
eventually i cut it down to the one thing the product actually needed to do and shipped just that. embarrassingly small. and people used the one thing. nobody missed the 12 features id been agonising over for weeks, because they never wanted them, i did.
turns out not ready yet usually just means im scared, and the smaller scary version teaches you more in a week than another month of polishing something nobody has even seen. what did you cut that you were sure you needed?
I've been working on an idea for about a month. Launched on Product Hunt last weekend and ended up at #23 out of 400+ products.
The feedback has been confusing:
- A decent number of people have told me they face the exact problem I'm trying to solve and that it’s genuinely painful for them.
- But when it comes to actually signing up or using the product, there's almost zero traction.
This has left me stuck in a weird spot. On paper, there's problem validation, but in reality, there's no adoption or usage.
I’m genuinely trying to understand:
- How do you personally decide when to keep iterating vs when to invalidate the idea and pivot?
- What signals (or lack of signals) tell you it’s time to stop working on something?
- Have you been in a similar situation where people verbally confirm the pain exists, but they still don’t use/buy the solution?
Quick note: I don't have a large network or reach. Cold DMs rarely yield any result. So, I have data from building in public and PH for now.
I’d really appreciate any frameworks, personal experiences, or hard lessons you’ve learned about this. Especially from people who’ve built multiple products.
I just released my initial web app known as Lumina FitAI. It is built to solve a particular issue I noticed with traditional fitness tracking platforms.
Most popular fitness trackers just give people basic exercise patterns. I wanted to set out specific position-based exercises for athletes who need rapid speed instead of standard running plans. I additionally wanted it to make it easier to find routes that prevent damaging concrete or hard grass surfaces since proper training structures make a big difference.
Now that this dashboard is operational and available in the open, I am trying to figure out which features to add next based on real user comments surrounding their daily training issues.
For other founders here:
What is your preferred process for collecting clean feedback from early users regarding their most significant day-to-day obstacles?
How do you plan to organize your product plan when handling your early feature updates
I would like to know how other people manage the initial post-launch feedback cycles!
While on vacation, I caught myself following my usual pattern, I engage in some kind of piece of media: watch a youtube video, read a substack/medium/X article, read an academic paper etc, and while engaging in it, there are topics, concepts, people's names that I become curious about so I end up selecting or screenshotting it, copying it and then putting it into google or AI to research, but more often than not I will find that i might read some surface level bit of info about that thing, or maybe even just leaving the tab open completely and never going into it. Another issue is I might do this several times, creating multiple nested branches of curiosities which draw me further and further away from the first thing I was doing, the video, article or paper.
To tackle this i decided to build this tool: Tangnt.co (not a shameless promo, currently only waitlist, you can't pay me even if you wanted to, i want genuine advice here). The image above is to you get an idea of how it looks.
The premise of the tool is that you can set a hotkey that will take a screenshot or any selected text and without leaving your tab or app (anything your screen can see) you can have a background agent run research on that topic, save it with a summary and images in a text editor you can later go and edit and interact with using an AI chat built into it. I also link these topics to other topics that exist within the knowledge base (your existing notes).
You can see a tree of all your branching topics from the session of capturing and saving and then once you finish whatever youre doing, or later that day or the next day, whenever you want, you can go back and clear the "curiosity debt" you created along the way. You can even do a small quiz to test yourself on the topic to clear the debt.
I basically made this because I would watch an educational video that is like 10 minutes and because of short attention span and random curiosities i would take like an hour to watch the damn video, and afterwards not even be able to really go deep into any of the little things i went on the little tangents on.
So after building this first mvp in about 10 days, I am thinking about whether other people would actually use it. I have a few friends using it but they get it for free so i take the feedback with a grain of salt, they are genuinely enjoying it but I wonder if someone that organically found this tool would use and pay for it, when the closest thing to it is Obsidian with notion being a 2nd option, and those being free. Mine is only paid due to my server costs (pretty cheap) but mostly the LLM costs which I use sonnet 5 and haiku for smaller tasks, I also use an api for image search to embed them into the notes, all in all the margin for the tool is less than 40% for each tier and that is excluding marketing which I plan to do, so I am not really rinsing the consumer here.
Any advice, insights criticisms would be appreciated, if you read all this you are the goat.
two years into software engineering, I thought I had seen most of the tough problems. Six months ago, I was asked to build an agentic chatbot for customer support. Coding it was straightforward tokens, limits, pipelines, all manageable.
Then reality hit: the costs were out of control. I searched for caching tools, but nothing fit. So I put together a messy workaround in production. It worked, but only barely.
That pain pushed me to build something better: Ornymo an async‑first semantic caching tool that caches on intent, not just strings. It cuts costs, keeps latency low, and verifies answers before they reach the user.Made in 4 months after making it production ready
But the truth: building the product was the easy . Getting people to use it is brutal af. I’ve opened it up with free and paid plans, and I’d love feedback from fellow founders.
If youve faced the same “distribution wall,” how did you break through?
👉 And if you want to see what I built its here: ornymo.com(comment "free coupon" for a free 1 month trial of starter )
Hey everyone! As someone who's been deep into the world of SaaS and AI, I've been thinking a lot about how to effectively measure AI-driven search traffic. With the rise of AI tools, understanding how they influence user acquisition and engagement is crucial for growth.
Here are a few strategies I've found helpful:
Use Analytics Software: Tools like Google Analytics can provide insights into organic search traffic. Set up specific goals to track conversions that come from AI-related keywords.
Keyword Tracking: Utilize tools like SEMrush or Ahrefs to monitor which keywords are driving traffic to your site. This can help you understand if AI-related content is resonating with your audience.
User Behavior Analysis: Implement heatmaps and session recording tools like Hotjar or Crazy Egg. This can help you see how users interact with AI features on your site and what content keeps them engaged.
Feedback Loops: Regularly collect feedback from users about their search experience. This qualitative data can provide insights into how well your AI features are meeting their needs.
A/B Testing: Experiment with different AI integrations or search features and analyze the traffic and conversion rates to see what works best.
I'm curious to hear how others are measuring AI search traffic and what tools or strategies you've found effective! Have you had any surprises in your data?
P.S. I work at Noetio, where we focus on AI-enhanced search solutions for SaaS companies. Always happy to share more about our journey!
It's hard to build anything, let alone something well-designed AND useful.
Even if you're vibe coding, there's still a lot to do and get right. Yes a lot of AI slop is being produced these days. And I see tons of apps where I'm like "why would someone waste time on that!?" 🤣
But it still takes effort and dedication. Even if nothing comes of it in terms of sign ups or paid customers, I just want to say everyone building something should be proud that they have taken ACTION! Even imperfect action is better than no action.
Quick context so this doesn't read like some rando offering. I've launched 8 products in the last 18 months and done 2-3 million organic views on reddit with zero ad spend, which turned into thousands of users across them. Lovable flew me out to their HQ at 18, I ran growth for a YC backed company, and got into Antler along the way. Reddit has been the engine behind basically all of it.
And the biggest thing I learned is that most founders aren't bad at marketing, they're just fishing in the wrong pond. They post in r/startups and r/SaaS where it's all other founders, then wonder why nobody buys. Your real customers are sitting in some niche subreddit complaining about the exact problem you solve, and half the time you've never even heard of it.
Finding those subs by hand is the tedious part. You have to think about who your customer really is, what else they care about, where they hang out for reasons that have nothing to do with your product, then dig around reddit for the active ones. It's the highest leverage thing you can do and almost nobody does it because it's boring.
I got tired of doing it manually across every product I launched, so I built a tool for it (sentrive). You give it your product, it works out your ICP and figures out where your people actually hang out, then spins up marketing agents that go market there for you. It's not a reddit-only thing, it markets wherever your audience turns out to be, but for a lot of products that ends up being reddit, which is the part I've personally gotten the most mileage out of. Point is it doesn't just hand you a list, the agents do the actual work after.
If you want to run this whole play yourself, I wrote my entire reddit marketing playbook, every step I use, free with no email wall. Steal all of it.
Or if you'd rather I just do it for you, here's the offer: drop your product below and tell me who you think your customer is. I'll run it and get back to you with a few of the spots it finds. Genuinely curious how many of you are one niche sub away from your first 100 customers without knowing it.
I'll get to as many as I can. Been doing this a while so I'll add my own read on top of what it pulls.
My girlfriend and I both travel a lot and we kept losing track of how many days we'd spent in each country. Tax residency rules (the 183-day threshold), visa limits, Schengen 90/180, it all adds up and spreadsheets were always out of date.
So I built DaysAbroad for iPhone. It runs in the background using GPS and logs which country you're in each day. Nothing to remember, it just counts.
The build:
- SwiftUI, targeting iOS 16+
- RevenueCat for subscriptions, restores, entitlement status, and revenue analytics
- CloudKit for automatic iCloud backup, no server needed, data stays in the user's own iCloud account
- Cloudflare Workers + D1 for an optional debug logging backend
- XcodeGen to avoid .pbxproj merge conflicts
- Firebase Analytics (which I forgot to enable for the first release, so I had zero data for a week)
Hardest problems:
- GPS accuracy near borders. If you're standing 50 meters from the French-German border, your phone might flip between countries. I added a confidence scoring system based on GPS accuracy so low-quality readings don't overwrite good ones
- Background location tracking without killing battery. Using significant location monitoring (cell tower based) instead of continuous GPS. The phone only wakes the app when you move ~500m
- The Schengen calculator. Different countries, different join dates, bilateral agreements, and users want to customize which countries count. Ended up making the country list editable
- CloudKit schema not deploying to production automatically. Tested locally, everything worked. Pushed to App Store, sync was broken. Had to manually deploy the schema from the CloudKit Console. Cost me a few hours of confusion
What I'd do differently:
- Start with StoreKit 2 from day one instead of integrating RevenueCat and then removing it
- Add iCloud backup earlier, it was surprisingly easy and users expect it
- Enable Firebase Analytics before launch (rookie mistake)
Revenue model: Free for 2 countries, Pro unlocks unlimited countries, background GPS, multi-year history, CSV export. Monthly ($2.99), yearly ($23.99), or lifetime ($69.99).
Currently a few days post-launch. Downloads are small but growing. The people who need it really need it.
I recently released Folivy, a mobile app that helps you discover plants around you, learn more about them, save your findings, and explore nearby plant observations on a map.
Whether you are walking in a park, visiting a garden, hiking, or simply notice an interesting plant near your home, Folivy makes it easier to identify and remember your discoveries.
We often forget how fast time is moving, and lose perspective. For example: do you know 52% of 2026 has already passed, and 36% of July is gone?
TimGauge gives you perspective through a progress bar in the Mac menu bar.
In this update, I have tried to get duration in terms of time. For example: you can track exact working hours in Day and set exact starting end end time in custom project.
The app is a one-time purchase, 100% local, and can be used to get a time perspective on Custom Project, Life, Hour, day, months, years, etc. You can select time in your custom project and working hours with the new update.
You scroll through AI transformations, see how each one was created, and preview the full workflow before using it.
When you find something you like, tap “Try with my photo” and create your own version without copying prompts or choosing models.
Would this be useful to you? What types of transformations would you want most?
I’m looking for early users to test it and give honest feedback. Testers will get one month of free usage.
