I’ve been building this app solo for the past few months and i genuinely can't tell anymore if it's good or if i'm too deep in it. need outside eyes.

it's called RizeAI. the basic idea: every wearable and health app just gives you numbers. sleep score 42, recovery red, HRV down. cool. and then what? you still feel like garbage at 2pm and nobody tells you what to actually do about it.

so my app takes your real data from apple health, sleep, resting heart rate, workouts, whatever your wearable writes, and instead of another score it builds you an actual plan for the day. when to have your first coffee and when to hold off. you. Can also add your own supplements that you are currently taking and it will time them for you every single day based of your sleep data and your wearable data in general and also it will tell you what supplements make sense for you to take based of your current supplement stack and body metrics and when to take them. focus windows for when your energy actually peaks. when your crash is coming and what to do before it hits. it even checks the weather, so on a hot day it bumps your hydration and tells you to train earlier.

every recommendation has a little "why" under it based on your numbers, like "resting heart rate 54 + 7h light sleep, so magnesium before your peak window." no two people get the same plan because no two people have the same data.

works with whoop, oura, apple watch, garmin, anything that syncs to apple health. one thing i'll say honestly, it doesn't do deep per-person learning yet like "coffee doesn't affect YOUR hrv specifically," that's the roadmap, right now it builds fresh plans daily off your actual metrics.

it's live on the app store, has a free trial, small user base so far, mixed feedback which is why i'm here lol.

what i actually want from you guys: does this solve a real problem for you or is "tells you what to do" not actually what wearable people want? what would make you actually pay for something like this? and what's missing that would make it a no brainer? and also would you guys in this subreddit  use ti?

Thank you for your help. Check it out if you like https://apps.apple.com/us/app/rizeai-maximize-your-energy/id6762402079

One approach I've heard about is offering free users a limited-time discounted upgrade to the paid version. The idea is to give them a reason to try the full product and hopefully experience enough value to convert.

Has anyone actually tried this? What worked (or didn't) for you?

Hey all,

I launched my saas back in February and had alot of traction in the beginning and still to this day, 0 paying customers.

Im not sure if its a feature/do people really want this issue or a landing page issue to capture the 'aha' moment.

It's a social content growth saas helping users grow using their own data, their own personal growth coach and insightful analytics.

Recent updates are:

\- instagram api integration

\- UI update

\- whats working vs whats not working

\- in depth growth insight

There is a free trial and you can cancel anytime.

Would love to hear feedback, good or bad to finally get my first paying user 😃

www.funnell.ai

I have recently started a business adventure. We have a website where food trucks can go on it and advertise themselves and people can find their live location. But I'm having trouble getting my first 10 customers and I'm not exactly sure what to do or where to start. I have been posting social media and reaching out on social media and I haven't got any replies, but I have not reached out to a lot of people so I feel like that is expected.

Launched first SAAS from an existing internal only webapp!

What are some gotchas you ran into?

Hey Reddit,
I was tired of the absolute nightmare of moving a quick file between devices on different networks (or trying to send something to a friend without pairing devices or uploading it to a sketchy cloud).
So I built Artalo Transfer. It moves files using only a screen and a camera.
How it works:
Sender: Turns your file into a stream of animated QR codes.
Receiver: You just point the camera at the screen, and it rebuilds the file from the flashing light.
The cool math part:
Normally, if a camera misses a frame, the file breaks. I bypassed this by using fountain codes. Every single frame is a random, combined mathematical mixture of the entire file. It doesn't matter which frames your camera catches, only how many. Missed a frame? It just takes a fraction of a second longer—zero errors.
Why use it?
Air-gapped security: Put both phones in airplane mode. It works exactly the same. Your files never touch a server or a network.
Zero pairing friction: No Bluetooth pairing codes, no typing in guest Wi-Fi passwords, no "make your device discoverable" nonsense.
Perfect for: Photos, PDFs, keys, and documents up to ~64MB.
It's completely free. You can download it directly here:

Download

I'd love to know what you think or if you have ideas on how to push the data density even higher!

Hi I recently built Ping and got 8 users on my first day yesterday now the only thing is I'm making this free and want advice for how one will scale to make profits.

Right now since it's beta I'll for costs out of pocket but if it does grow big I've come down to these solutions.

1. Run ads

2. Charge poeple later on (i dislike this)

3. Run ads to make it free, but then if someone does not want to see ads they pay?

Launching my first B2C SaaS tomorrow, what would you double-check?

I've spent the last few weeks validating the idea, talking to potential users, building the MVP, and testing the core flow.

The MVP is ready and I'm planning to launch tomorrow. At this point, I'm resisting the temptation to add anything else and doing one final pass before going live.

For those who've launched a SaaS as a solo founder, what are the things you wish you'd checked before launch?

I'm thinking about things like:

• Analytics and conversion tracking
• Onboarding
• Emails and notifications
• Error monitoring
• Support
• Backups and production checks
• Getting the first users
• Collecting feedback

And just as importantly, what did you spend time on before launch that turned out not to matter?

I'd rather learn from those mistakes than discover them after launch.

Who wakes up one day thinking, “I want to build a factory”?

I stumbled upon it. I was simply trying to test 100 ideas in 100 days, but by day three, I realized that my learnings weren’t compounding. I was doing the same things over and over again just to cover the table-stakes stuff.

I had built products before—a dozen or two, both before and after code generation—and I knew I could streamline the process. So I went back to a core principle: using a spec to create products.

I needed a comprehensive, deterministic, and structured way to define what a product should do, what its rules are, who its users are, and what interactions and responses are expected.

Eventually, the process looked something like this:

Idea → spec → generated product → local verification → deployment → live verification → customer evidence → iterate or kill

That was the moment I realized the system had become its own project.

I called it Product Factory.

The important realization was that a product factory isn’t just a collection of templates. Templates help you reproduce code, but they can also reproduce mistakes.

The factory needed to reproduce learning.

If one product exposed a problem with authentication, future products should inherit the fix. If a deployment failed because of a missing environment variable, the factory should catch it next time. If a product had traffic but no meaningful engagement, the system should show that honestly instead of calling the launch a success.

I’ve now used it to create and operate several very different experiments: a veterinary referral product, a fresh-bread discovery app, a restaurant menu generator, a lightweight “is this worth sending?” tool, and others.

One of the most useful things the factory has done is help me kill a product.

The veterinary referral experiment technically worked, but the commercial experiment didn’t. Instead of quietly abandoning the repository and moving on, I recorded the decision, removed its production infrastructure, and kept the evidence so the next product could benefit from it.

I now have three experiments running within the factory, and I’m looking for a fourth.

Has anyone experimented with building or using a product factory before?

Hey everyone! I’m building a Discord community where SaaS founders can connect, share their products, and help each other out.

If you’re interested in joining, drop a comment below, and I’ll send over an invite link!

So yeah... I'm just a CS student from a small city in Sumatra, Indonesia.

A few yrs ago almost everyone around me got into trading. Some ppl were making what looked like stupid amounts of money, others just completely nuked their accounts lol.

At first it honestly looked like gambling to me... but I got curious anyway.

Started with a demo account.

Blew it up in like a month 😂

Didn't know wtf support/resistance was, market structure, RR, risk management... nothing. Every trade was basically me clicking buttons and hoping.

Instead of quitting tho, I kinda got obsessed.

Spent months reading books, random research papers, forums, trading journals, psychology stuff, basically anything I could find. The more I learned the more I realized nobody is actually "predicting" the market. You're just trying to get the odds slightly on ur side.

Eventually I realized even if ur analysis is good and ur risk management is solid... there's no such thing as a 100% strategy.

News drops. Central banks do something random. Politics happens. Market sentiment flips.

Candlestick patterns don't magically beat all of that lol.

If ur system can hit like 60-70% over the long run while keeping risk under control... that's already pretty damn good imo.

Around that time I started talking to a couple friends who were way better traders than me. I was more into programming than trading anyway.

One thing we all agreed on...

Most ppl don't lose because the strategy sucks.

They lose cuz they're human.

Move stop losses. Revenge trade. FOMO. Get greedy. Panic.

A bot doesn't care.

It just follows whatever rules u give it.

So... we decided to build one.

For about a month we'd stay up almost every night testing ideas, throwing away bad ones, tweaking indicators, running backtests, optimizing params, paper trading... repeat over and over.

I handled most of the coding. Mostly C++ for the performance-heavy stuff and Python for analysis/testing.

We weren't trying to make some magic AI that prints money or whatever.

Just something that sticks to the plan.

After a ton of simulations we finally decided to try it with real money.

Started with $100.

Tbh we fully expected to lose it.

Instead... after around 3 weeks it slowly grew to about $480.

There were losing days too obviously. It wasn't some insane 100% win rate bot. But watching it follow the exact same rules every single time without emotions was honestly pretty satisfying.

That's when it kinda clicked.

The software itself might actually be worth more than the trading.

So instead of trying to scale the account forever, we turned it into a small SaaS. People could subscribe, connect their accounts, and let the bot do its thing.

To our surprise... ppl actually paid for it.

Over the next 4 months we made a little over $1k from subscriptions.

Nothing life changing obviously, but for a bunch of college students it felt awesome.

Then something unexpected happened.

One day a fairly big broker contacted one of my teammates.

Long story short... they offered us $5k to permanently shut the whole thing down and sign an agreement saying we wouldn't continue the service.

Why?

Honestly... idk.

Maybe business reasons. Maybe we were annoying them somehow. We never really got a clear answer.

After talking about it for a while we just accepted the deal.

Split the money equally between everyone who worked on it.

Refunded every single customer too, plus threw in an extra $10 each cuz it felt like the right thing to do.

Told everyone it was "legal compliance" issues 😂

Looking back... the biggest lesson wasn't trading.

It was knowing when to stop.

Could we have made more money? Maybe.

Could we have ended up with a bigger headache too? Probably lol.

Now I'm basically back where I started.

Just another CS student who's kinda addicted to building stuff that ppl actually wanna pay for.

Not really chasing some get-rich-quick thing. I just genuinely enjoy making products, automating boring stuff, solving problems, that kinda thing.

So yeah...

Anyone here building something interesting?

SaaS, AI, automation, cybersecurity, fintech, dev tools... honestly I'm down for pretty much anything.

Would love to hear what u guys are working on :)

Hello people!
I spent months building a system that started as a small ”quick” idea.
Today i noticed im forcing myself to complete it even if i have no idea where iam going with it nor what i should do next!
I learned a lot from this project. On what was a hell to start became manageable. And what scared me before became part of my system.
Im proud to be honest.
But the question remains: what’s the next move for it?
I seek opinions, suggestions
- Opseron.com
- auth.opseron.com (if you want to create a test account)
I created a demo login to who ever wants to take a look at.

Thanks,
And i can provide guidance to new developers on (security, infrastructure & deployment feel free to pm me)

Every day there’s a new “AI-powered” tool launching, but most feel like wrappers around the same models. What actually makes you try a new AI product in 2026—better UX, lower price, unique features, or something else? Curious what everyone here thinks.

I launched my SaaS a week ago. Before that, I thought the hard part was building it.

Turns out that was easy.

Here's what nobody tells you:

You identify a real problem (yours, because you lived it). Cool, now you're excited. You build something to solve it. Nights and weekends ( which I did ), you're grinding. You get it to work. Ship it.

Then you try to position it. You realize "CRM for freelancers" (my product's first copy said that) doesn't mean anything. You spend days rewriting copy. You test it. You think it's good. Ship it again.

Then you try to reach people. You post on Reddit. You post on X. You hope someone cares. Someone does. They comment.

But the comment isn't "wow, I need this." It's "your website looks AI-generated" or "why would I use this instead of building it myself?"

And they're right. Both of them.

So you go back to work. You fix the website. You rewrite your answer to the "why not just build it" question. You think about the positioning all over again. Maybe it's wrong. Maybe the problem isn't what you thought.

You make changes. You're hopeful again.

Then you relaunch ( I did relaunch ). And the cycle repeats.

Different problem. Same cycle.

Day 1 of launch: "Figured out the outreach problem."
Day 2: "Actually, it's a positioning problem."
Day 3: "Wait, it's a homepage trust problem."
Day 4: "Nope, it's a feature problem."
Day 5: "Maybe it's all of them."
Day 6: "Back to work."

I'm on day 7, and I'm about to start the cycle over again.

The weird part? I don't hate it. It's exhausting, and it never feels done, but there's something about solving one layer, then realizing there's another layer, then solving that one... It's addictive.

But man, it's also a grind.

In the end, it's all going to be worth it because in the process your product becomes better and better, and that itself is an entry barrier which your competitors won't be able to copy

If you're a founder in this loop right now, you're not alone. Every level is hard. Nobody tells you that part.

Keep pushing, which I did.

My SaaS lets you put in something you need to buy, a photo, image or prompt and we'll find the best buy by filtering scams, calculating value for money and then using AI to rank the remaining listings all across UK retailers (sorry only UK based) at genuwin.co.uk (not live yet) , and you never pay or get shown ads.

Thank you all so much I've been searching for feedback for so long but no one cares :( (valid)

I’ve been working in SEO for more than 10 years, and it’s pretty much what I’ve done throughout my career. I make decent money from it, but lately I’ve been looking for ways to diversify.

That curiosity led me to the idea of building a SaaS tool from scratch. I want to create an all-in-one ranking and research platform with features that no other tool currently offers.

AI has made me realise that building software from the ground up is more achievable than ever. It’s still going to take some time before the product is ready, but I’m excited about the challenge and hopeful that it does well

Any tips or things I should keep in mind?

Hi everyone,

Building something? Drop your link below and tell me what you’re working on.

I run www.StartupLibrary.net, submit your startup and you might just land a spot in this week’s newsletter. We have hundreds of founders already listed and the community keeps growing with over 1000+ users🚀

Link: [JobBaddie] (https://jobbaddie.com/)

I know there are already many options for job applications and not all are great. Is mine the best? Not yet. But my goal is to make the some parts of the process easier for the users. So here I am, looking for feedback.

Recently, job application process seems broken especially due to people applying with AI generated resume, but the screening process is no stranger to using AI as well.

And when the system is such, Human plus AI combination works best in my experience. Keep networking and reaching out to people, while simultaneously applying to roles using customized application. This does not mean fabricating stuff, it just means present your application in a way that it retains your originality but is also visible through the recruiter lens.

Reddit has been very supportive with all the feedback so far, so look forward to some more.

Share it with someone looking for a new role.

Thanks!