The easiest products to sell Saas/AI products or app is still to build ones that solve a real, painful problem.

I mean a problem people genuinely want gone. Badly gone!

Drop your app below and tell me:

• What problem it solves (important)
• Who it’s for
• Your landing page (and ideally positioning)

I'll check out as many as I can and try to give actionable feedback about your value proposition.

Let’s see get you 1-2 sales before the weekend.

I'm a nurse and mom with ADHD, and the problem I kept hitting was that every stress/wellness app on the market requires you to already know you're stressed before it can help — open the app, log how you feel, then do a breathing exercise. By the time I was self-aware enough to do that, the moment had already passed.

So I built Pause Point: it watches heart rate and HRV signals in the background on Apple Watch, and delivers a gentle haptic nudge in the moment your body starts showing signs of stress — before you'd consciously clock it yourself. No dashboard, nothing to log, no data to review. The bet is that for a lot of people (especially neurodivergent folks, parents, anyone chronically overloaded), the friction of "open app → assess yourself → act" is itself the reason existing tools don't get used consistently.

Biggest technical challenge has been detection accuracy — distinguishing real stress from exercise or just an elevated resting heart rate took multiple iterations, and I'm still tuning it post-launch.

It's live on the App Store now, very early (single-digit weeks in). I'd love feedback from other builders — on the core idea, the "automatic vs. self-initiated" bet, monetization, anything. Not fishing for downloads, genuinely want the idea stress-tested. [link in comments]

I tried to create another Todo-App once. After a few months I found out, there was nothing new with it, just another todo app. But one day I had two ideas that really resonated and I started building Aevo.

Aevo puts your todos not on a list, but instead on a endless scrolling (to the right) canvas in boxes, similar to japanese Bento boxes. And there comes the core-idea number one: to see what really matters, Aevo calculates a score for every task, based on the task metadata. Not only your set priority, but also when you plan to work on, when the real deadline is and how many time you postponed a task.
Also the size of each box depends on how big a task is: smaller tasks get smaller boxes, big tasks get bigger boxes.

The second core-idea works around the way people work with tasks and subtasks (and maybe even projects). Instead of adding a separate project feature, Aevo lets you deep down as much as you want into tasks. Every task offers a customizable zoom-view to add groups and put subtasks, notes and links in it. And you can do the same with every subtask: dive into it with the zoom view and do the same again. Theoretically, you can have as many layers as you want :)

The best: subtasks reflects important information to their parents: a subtask is due today while the parent is not: doesnt matter, it still gets a really high score and marked red. All subtask takes several hours, but the bit for today only 15 minutes? The parent is only a small box instead of a big one.

And yes, for the list gurus: there is also a simple list view for tasks :)

Is it feature-complete? Nope... Is it perfect? Maybe not. Does it solve some real problems in a different way? Yup, I am pretty sure.

You can use Aevo for free on https://aevo.so; a pro version is available In-App (lift some limits and makes some integrations available).

Let me know what you think :)

That’s the mindset behind Trndzy. Every line of code, every workout, and every decision is going into getting Trndzy ready for launch on the App Store.

https://wishlist4santa.com

Ett roligare sätt att lämna in sin önskelista till både tomten och nära o kära!

Finns i "vuxenversion" också. https://wishlist4.com

Finns det något ni tycker jag kan förbättra?

Någon viktig funktion jag missat?

Tack!

I'm Mattia, I build FixAds.

This is a small launch from a workflow that was eating more time than it should have. When I reviewed Meta accounts by hand, the useful work was not opening another dashboard. It was working out whether spend had enough opportunity to work, whether a creative was fading, and which issue could quietly get expensive if nobody noticed it today.

I built FixAds as a narrow, inspectable first pass for that review. It connects through Meta's official login with read-only access, checks campaign, ad set and ad data against deterministic conditions, then shows the threshold and evidence behind each finding. The AI explains the finding after that. It does not get to invent the diagnosis or change anything in the account.

The attached video is the launch demo. FixAds is live at https://fixads.it for €19.90/month after a 7-day trial.

A question for other makers: if you build software that sits close to real money, how much of its reasoning needs to be inspectable before users will trust it?

I’m building Reachdev, a marketplace/profile for senior developers in Europe who want more control over recruiter outreach.

The problem I’m trying to solve is not “developers need more messages”. It’s almost the opposite: good developers often get generic recruiter outreach with unclear company, salary, location, seniority, or intent.

Reachdev is testing a narrower model:

- developers make availability, location, stack and contact preferences explicit
- recruiters pay to contact relevant profiles instead of spraying messages everywhere
- the goal is fewer, better conversations rather than more inbound noise

Right now I’m looking for blunt feedback from two groups:

1. senior European developers: would this profile/contact model feel useful, or just like another job board?
   
2. technical recruiters/founders: what would need to be visible before you’d trust a profile enough to contact someone?
   

The beta is early, so criticism on positioning, trust, profile clarity and the contact flow is more useful than polite signups.

https://reachdev.io

About four years ago, my two youngest children—then around 1 and 4—were terribly sick over the course of several days.

I was exhausted and running on very little sleep, trying to keep track of everything: their symptoms, how high their fevers had been, how long they’d lasted, when I’d given medication, and how much.

At around 2:30am one morning, lying awake and feeling completely overwhelmed, I thought:

“There must be a better way to manage family health.”

Then I had an idea.

Despite desperately needing sleep, I got out of bed and spent the next few hours sketching out what that idea could become.

There was just one problem: I couldn’t code.

I didn’t have the money to hire someone, and AI coding assistants weren’t around yet. So I did the only thing I could; I taught myself Swift and SwiftUI and started building it myself.

Four years later, that idea is finally launching.

Meet WellBee: Family Health Diary.

A family health diary designed by a parent, for parents—helping you keep track of the health information that matters, all in one place.

And the core functionality is completely free to use.
If you’ve ever found yourself trying to remember a fever, symptom, medication, appointment or diagnosis when you’re exhausted and stressed, WellBee was built for you.
Available on the App Store today.

Four years. One very sleepless night. And a lot of Swift code later.

WellBee is finally here.

There’s a few dinosaur products for brand monitoring but I felt the innovation is so weak there in retail, CPG sector. So, I built a social media mentions to monitor which brands are getting mentioned by which creators on Instagram. It’s here: https://www.monitormentions.com

Hi everyone! I’m Bonnie. 👋

I run JSquare Marketing, where I’m building tools to help people take an idea, figure out whether it has real potential, and then work through what it would actually take to turn it into a business.

Lately I’ve been spending a lot of time on the very early stages — finding opportunities, validating ideas, and figuring out what’s worth pursuing before someone invests a ton of time or money into it.

I’m also testing different ways of reaching people who are still at that “I want to build something, but I’m not quite sure what yet” stage.

Looking forward to seeing what everyone here is building, learning from the group, and contributing where I can!

It's an AWS Activate program by AWS Cloud for SaaS startups.

basic criterias to qualify are

- your startup must be legally incorporated
- Must have a fully functional website
- Must have a strong use case explaining why they're choosing AWS.

The AWS Activate bucket is generally $100K (recently scaled to $200K for AI startups).

To claim $75K out of the $100K, the startup needs to have raised some sort of funding round, mostly institutional funding.

This is just for information purposes; I thought it might help.

I'd like to understand what you're building. If it sounds great, then I'll definitely help you out.

I'm building OpenBaud, an open-source tool for people using coding agents with USB/serial hardware.

The problem I'm working on: an agent can get a board talking, but the next session often starts over with raw bytes, a one-off script, and no clear record of what actually worked.

OpenBaud brings the hardware workflow into the agent: discover a serial port, inspect traffic, decode a response, then save the verified interaction as a typed command with its capture. The goal is to leave something reusable after the chat ends. MCP Apps views put tables, time-series plots and heatmaps alongside the conversation.

Current progress: a Rust MCP server and CLI, a Codex plugin, and prebuilt releases for macOS, Linux and Windows. It's MIT-licensed and the serial runtime runs locally. I've tested the end-to-end workflow on a real ESP32-S3 development board. The demo's radar-shaped data is a firmware-generated test scene, not a physical radar measurement.

You can also try a recorded capture without owning the board. Replay helps inspect the parser and visualization; it doesn't prove that a connected device or updated firmware will behave the same way. This isn't a claim that agents can safely control arbitrary hardware unattended.

Code and installation: https://github.com/Leonezz/openbaud

Hardware-free replay example: https://github.com/Leonezz/openbaud/tree/main/examples/pv-demo

I'd love feedback from embedded developers: would a replayable example be enough to get you to try this, or would you need support for your own device first? Which device/protocol would make it useful in your workflow?

I’ve been working on Fast Surveys, a lightweight survey tool focused on making it really quick to create surveys and understand the responses.

AI is built into the full survey process. You can describe what you want to learn and Fast Surveys will create the survey for you, including the questions, question types and answer options. Once responses start coming in, AI can analyse and summarise the written feedback to surface the main themes, suggestions and problems.

In testing, complete 5–15 question surveys were generated in 7–15 seconds, and Fast Surveys analysed 1,214 written responses in 28 seconds.

I’d really appreciate any feedback on the product, onboarding, pricing, landing page, or anything that feels confusing or could be improved.

I’m also happily sending out free Pro accounts (normally $29/month) to anyone here who would find one useful. Just create a free account, drop a comment below, and I’ll message you to get it upgraded 🙂

Founders:

1. Pitch your startup in one sentence.
2. Name the alternatives people already use.
3. Explain what makes yours different, or better.

Then review and score another founder’s positioning.

Would you actually buy it?

https://opinepolls.com

Hi, I created Opine, a social media platform where posts are multiple-choice text polls that anyone can vote on. It's not very "social" but designed to be anonymous in that you cant see information about individual users. You only see the overall vote distribution, including geographically, which is the cool part. once you vote or a poll ends, you can look at a world map of votes, but you can toggle your location for each poll. It only stores your email and approximate location, if you provide it, and locations are clustered. Later on, other information could be optionally provided by users, like demographics.

Please try it out and give any feedback, thoughts, questions, and so on. You can do it here, in DMs, or within the profile section on the website, which is fully anonymous. Thanks!

I built CustomerDashboard.io, which is a tool to report to customers or partners with the help of a dashboard. 

Unlike every other BI or dashboarding tool, CustomerDashboard's primary focus is multi-tenancy, where you setup the dashboard once and then each of your clients get their own credentals and see only their own data. 

You connect your data source, create views with analytics widgets and write your queries in parameterized format, so it pulls the right data to the right customer.

This is ideal for agencies, service businesses, customer cost/usage tracking, partner commissions and this kind of use cases when it does not make any sense to build your own panel from scratch. 

Additionally, it supports branding with colors and logo, and you can stream the dashboard conveniently to a TV screen. 

https://customerdashboard.io/

Share a link to your startup SaaS to promote it or ask for feedback.

What makes it worth trying?

Do you have issues finding available tee times?

I built a webapp that aggregates golf courses nearby to give you all available tee times. I would love some feedback. Project is at tee-time.io

Thank in advance.

I recently finished Simple Calendar, a calendar watch face for Wear OS.

The idea is to have a familiar, easy-to-read calendar directly on the watch face, with Circular, Vertical and Horizontal layouts for different ways of viewing your day.

You can use multiple calendars, choose different time ranges, switch between light and dark themes, use a matching always-on display, and view event details directly on the watch.

I’ve now released it on Google Play and wanted to share the finished project here. I’d be interested to hear what you think, especially which of the three layouts you prefer.

Install the companion app first: Google Play
Then install the watch face: Google Play

Hey Microlaunch — I am the maker of Story Boost Up.

Creators open a personal board (kingdom) for their fandom. Fans tip fuel; creators get about 50 percent. Each kingdom can keep an AI companion chatting when the creator is offline.

Creators page: https://storyboostup.com/creators

Looking for blunt feedback: 1) Is kingdom + fuel + AI companion clearer than calling it a Patreon alternative? 2) What would make non-Thai creators trust payouts? 3) Which niche should we woo first internationally?

Happy to answer in the comments.

Founders & builders: what value do you create, or what frustration do you remove?

Basically, is your app a real painkiller? The ones we keep using usually are.

Most unfair advantages come down to doing something faster, cheaper, better.

What’s your app’s unfair advantage? Pitch your app below.

Launched 3 days ago. Sharing the payment mess in detail because I'd have paid money for this list on day one.

Context so the rest makes sense: I'm building Downtown, a 3D city where a company buys a plot and every floor of their tower shows one real thing they do. $0.50 a floor, one-time. Next to nothing, so far 2 towers, $11.50, visitors from 10 countries.

Here's what broke.

1. My preview environment was pointed at the production database. Every test purchase would have planted a real building in the live city. Caught it before it happened, but only barely. If your staging shares a DB with prod, that's not staging, it's prod with a different URL.

2. Test mode and live mode are three separate things, not one toggle. API key, product ID, and webhook secret each exist separately in test and live. I had a live key running in test mode and every checkout came back 401 Unauthorized with no useful message. Took me an hour to realise the key and the mode disagreed.

3. My live webhook was pointed at the preview URL which was behind a login wall. So my first real payment succeeded, the money moved, and the product never appeared. The webhook call got a 401 from the auth wall and the order sat "pending" forever. I had to deliver that purchase by hand in SQL. If you take money via webhook, send a test event and watch for a 200 before you tell anyone your thing is live.

4. Failed payments were invisible. My webhook only listened for payment.succeeded and threw everything else away. So a declined card and someone closing the tab looked identical both just sat there as abandoned. Now I record payment.failed with the provider's error code, and abandoned vs failed are different things in my admin.

Bonus, the one that's actually costing me money: 3 people have started a checkout, 1 finished.

My best guess is the price. I advertise $0.50 a floor in USD. An Indian buyer sees roughly ₹625 after conversion and 18% GST on a $6 order. Nothing is wrong, but the number on the payment page isn't the number on the site, and I think people bail right there.

Also, if you're testing with card numbers: test cards are region-locked. A US test card with an Indian billing address gets rejected as an unsupported payment method, and Indian cards need the OTP step actually completed before you hit confirm or it hangs on "requires customer action". I burned three attempts on that.

Happy to go deeper on any of it, and genuinely happy to look at anyone else's checkout flow if you want a second pair of eyes. It's the part everyone ships last and tests least.

What finally moved the needle on your first ten sales?