Pre-Launch Intro
Hi, SaaS Hive! I'm Ashley, and after years of trying to "optimize" myself with wellness apps, I realized something:
I had become really good at collecting data...
but not much better at understanding myself.
That question eventually turned into Somyn, an AI-powered reflection platform built around curiosity instead of judgment.
I'm launching on SaaS Hive on Wednesday next week, but more importantly, I'm excited to become part of this community. I love talking about AI, behavioral science, and the future of digital health, so if any of those topics interest you, I'd love to connect.
What's something you've built (or are building) that started with solving your own problem?
Fabio AI Chatbot
AI Chatbot for Wordpress
Comments (9)
Welcome to the community, Ashley! Looking forward to your launch! How does your app read data? From a smart watch? 🤔
As to your question - I am building SimploMail.com. It is an email newsletter delivery service. I send an email newsletter every 4 months once I have a new video course created and want to share it with my subscribers.
And the reason I started building SimploMail is because I did not want to pay subscription fees when I do not send a newsletter.
All existing email marketing services charge subscription every month even if you do not send anything. SimploMail is pay-as-you-go service. So if there is nothing to send for 4 months, I do not pay anything.
I am my very first user and I use it to send email newsletter to my subscribers 🙂. I can't do my business without my SimploMail.
Sounds like a great offering!
Thank you for your question! Somyn is more of a judgement-free reflective journaling app - no other device connection required. It helps people reflect on the emotional patterns for why they make the choices they do about their bodies; from food, movement, and even relationship interactions!
"Good at collecting data, not much better at understanding myself" is such a sharp way to put it, and honestly it applies to businesses too, not just people. I built FounderFlow after realizing I had dashboards for three businesses full of data but no real sense of what any of it meant day to day. Curiosity instead of judgment is a great design principle for AI — I ended up landing on something similar: grading insights as Verified, Very Likely, Needs Review, or Monitor Only instead of pretending to have a definitive read on everything. Good luck with the launch next Wednesday, and welcome!
Stacy, it's interesting you make that point about businesses needing to understand their data because I've built a "Somyn for Work" section that gives employees a private space to reflect on their energy, stress, an emotional wellbeing, while giving People/HR leaders anonymized visibility into organizational trends. https://somynjournal.app/SomynForWork
That's a smart extension, Ashley. Anonymized org-level trends from individual reflection data is a good way to make it useful for HR without it feeling like surveillance. That balance between privacy for the individual and visibility for the org is basically the same tightrope we walk with FounderFlow, deciding what surfaces to a founder versus what stays as background context. Would love to hear how you decided where to draw that anonymization line.
So sorry I didn't address this for you, Stacy! The short answer to your question is that it's a layered boundary rather than a line drawn at a single point. Each layer exists to make the data useless for surveillance while still useful for HR. The guiding question was: what would make an employee hesitate before being honest? The answer is identifiability — the sense that their specific words or specific feelings could be traced back to them. So the line is drawn at the point where data loses individual identifiability while retaining population-level signal. That requires all four layers working together: enough participants to dilute any single voice (bottom floor of 10 per department/team), coarse enough categories to defeat reverse-engineering, narrative excluded entirely, and trend framing instead of point-in-time exposure. The result is that HR gets a thermometer like, "the culture is running hot in this department," rather than a personnel file. The employee gets a journal that feels like theirs alone, because the things that make it theirs (the specific words, the specific feelings, the small group inference) are structurally absent from anything an employer can ever see.
Welcome Ashley! Every product I've built started with solving my own problem. SaaS Hive happened because I couldn't get my products found by AI and wanted a community of like-minded founders. Unhid happened because my vibe-coded sites were invisible to AI crawlers and I had no idea until I checked. Fabify happened because I was spending too much time figuring out what to wear. The pattern is always the same: frustration first, product second. Excited for your launch next week!
Thank you, Olga, for your support so far! I look forward to seeing how far SaaS Hive can take all of us!
Ashley, I never got back to hearing how you drew that anonymization line, hope launch week ran away with your time. We hit the same tightrope building FounderFlow, deciding what surfaces to a founder versus what just stays background context. I would love your take on how we handled it, especially since you have already thought hard about that exact line with Somyn for Work. Would you be open to taking a look sometime this week?
Sign in to comment or upvote.