Building StackHR publicly from beta to launch 🚀
Hi everyone,
I decided to build StackHR in public because I believe real user feedback, rather than assumptions, shapes the best products.
StackHR is an AI-powered HR platform that brings hiring, employee management, leave tracking, payroll, and performance management together in one workspace.
We're currently in beta, and over the coming weeks, I'll be sharing:
Product updates
Features we're shipping
Lessons from talking to users
Growth experiments
Wins and mistakes along the way
Metrics and milestones, where appropriate
My goal isn't just to launch another SaaS product—it's to build something businesses genuinely rely on.
If you're building a startup too, I'd love to follow your journey and exchange feedback.
Nemo & Anna
Create IoT devices that don’t exist yet — no firmware, with built-in safety.
Comments (4)
Hi Mubarak 🙋🏻♂️ May I ask how you found companies to conduct interviews with? 🤔 LinkedIn outreach or these are local companies you could actually meet with? I tried to find people on LinkedIn to review my product and it was pretty challenging.
Hi Sergey! Thanks for the question.
For me, it was a mix of online and offline outreach. I started by reaching out to founders and HR professionals on LinkedIn with short, personalized messages asking for feedback rather than trying to sell the product. I also attended startup events and networking sessions, where I was able to speak with founders directly and follow up afterward.
The conversations I had in person were generally the most valuable because people were more willing to share detailed feedback. My advice would be to start with warm introductions where possible, join founder communities, and ask for 15–20 minutes of feedback instead of pitching your product.
↳ Replying to Mubarak Ahmad
Thank you, Mubarak! Yes, in person conversations are the best. This august I attended/presented at the WebSummit in Vancouver, BC and it was amazing. The first day I talked to more than a hundred people probably. During this kind of events people are curious and are willing to share... No upcoming events for me these coming weeks, so I will try reaching out to people on LinkedIn again. I am interested to chat with developers to learn how they use AI in their development workflow.
Bringing hiring, leave tracking, payroll, and performance into one workspace is the same instinct I had building FounderFlow, except my scattering problem was across multiple businesses rather than multiple HR functions — same underlying issue of important stuff living in five different tools with no single source of truth. Curious what's been the hardest part to get right in beta: getting users to trust the AI parts of HR decisions (like performance or payroll), or just the plain workflow/UX of consolidating tools they already have habits around?
Sign in to comment or upvote.