I've worked at a few startups now, some of them very successful, and the key has always been understanding user feedback, friction points and needs. That's why we've built HeyDeacon.com . It's now possible to speak with every new user to your app and assist them as if you were sitting next to them. Hey Deacon does this for you at scale - combining user onboarding, with market research, and UX feedback. Understanding your users needs is key to growth. Drop one line of code into your app and you're up and running for free. Heavy users will get asked to pay. Give it a go and let us know what you think! Thank you for the support
The bit about speaking with every new user instead of just collecting passive feedback is what stood out to me. With $1K MRR already this feels like it could be pulling in a lot more organic traffic than it probably is right now. That seems especially interesting while you’re still seeing which parts founders actually keep coming back to. Have you noticed a particular use case taking off?
We started Hey Deacon focussed on AI customer support - helping founders help users to remove friction points. But quickly realised that AI can now do much more than that. Every started or vibe coded app needs to get feedback from users, onboard users, manage support, conduct surveys etc. which is why we expanded Hey Deacons scope
The broader scope makes a lot of sense, especially with onboarding, support and feedback all being closely connected. Curious which of these is getting the strongest response from founders so far?
This comment was deleted 16 days ago
The interesting part is the feedback loop, not just onboarding. If Deacon can consistently turn real user conversations into patterns founders can act on, that seems much more valuable than simply automating a welcome flow.
That's what we're trying to do. If founders put it into the flow of the app - they get a load of feedback going very quickly. Like having user interviews in some sense. We're still working on how to improve this and make it more seamless (and less intrusive to users)
That makes sense. The “less intrusive” part seems important if the feedback is going to stay useful over time.