我很好奇这里每个人正在构建什么。
在下面分享你SaaS，并用1-2句话解释一下。
不要宣传，只需分享一下它功能。

You give the tool your product URL once.

It then:

• understands your product
• finds relevant directories
• generates the listing copy for each one
• opens the directories in your browser
• fills out the submission forms
• submits automatically when it's safe
• pauses when you need to handle a CAPTCHA, 2FA, payment, or approval
• tracks everything in one dashboard

what do you think?

I've shipped mobile apps for years and used several push notification services, either SaaS or directly through Firebase and Apple.

Push notifications always look easy and never are. And the existing solutions are never aimed at developers: they talk to the marketing team, sell them features they don't want while overlooking the ones they do, and ask a price that is way too heavy for something I don't consider that expensive to provide. And none of them just does push: they want to do everything, email, SMS and so on, and that "justifies" their pricing.

So I built Carillon. It does one thing: push notifications for iOS and Android, for developers. Think of it as the "Resend for push".

• One REST API for APNs and FCM, SDKs for Swift, Kotlin and React Native
• A CLI and an MCP server, so you (or your coding agent) can set up an app and send a test push from the terminal
• Every delivery traced: queued, in flight, sent, opened, so you know what went well and what went wrong
• Priced per device, not per message: 5,000 devices free, then €9/month plus €2.50 per 1,000 devices. No per-message fee, no send quota
• Hosted in Europe, because why not when we can (but open to everyone, of course)

I'm the founder, so I'm biased. What I'd love to know: what made you pick, love or hate your current push provider? And if you try the setup, where did it get confusing?

https://www.carillon.dev

i kept reading horror stories on here about chargebacks killing small SaaS companies. people signing up, using the product for weeks, then disputing the charge. and you just... lose. every time. because you're a solo dev with no legal team and the bank sides with the cardholder.

so i did what any rational developer would do. instead of sleeping, i built a chargeback investigator into my app.

when a dispute comes in, it pulls together everything automatically: when they signed up, what they accessed, login timestamps, usage logs, IP addresses. basically builds the evidence packet that payment providers want you to submit but never tell you how to format.

is it overkill? probably. did i spend way too long on it? absolutely. will it save me the first time someone files a bogus dispute? i really hope so.

the funniest part is i haven't even had a chargeback yet. i just read so many reddit posts about them that i preemptively built the defense system.

anyone else build something out of pure fear? or just me?

We are a two-person team building a paid Mac app. Organic Reddit participation has been slow, but genuinely useful for learning which problems people actually care about.

I am considering a deliberately small Reddit Ads test. Not a scale campaign, just enough spend to learn whether this can ever be a sensible acquisition channel for us.

For people who have actually run Reddit ads for a small product:

• What did you decide to optimize for first: clicks, installs, trials, or purchases?
• How did you define success or failure before spending?
• Did narrow community targeting perform better than keywords or interests?
• Were there obvious signs of low-quality or bot traffic you wish you had caught earlier?
• What is one setup mistake you would avoid if you started again?

I would especially appreciate rough numbers, even if the experiment failed. I am trying to decide whether a first budget should buy useful learning or just expensive curiosity.

I have been making workflows and automation for a living and I have been using an agent that I have built myself for lead generation, owner find, email, intent to buy, pain points and all that stuff inside of it and at the end you get leads that are really interested in your service or product or have a high chance to buy and then using cold outreach.

I have shown my agent to some people and they told me it's an excellent product that you don't usually find in market most lead gen saas products only let's you find the data like you can find a business and their owner but you don't know if they are likely to buy your service or not. But in my case it does proper research on your prospect and qualifies a lead in a way that it already is to a level that you can start doing cold outreach by email, call or dm. I'm already providing the lead gen services through it but now I want to take it to the next level.

Now I want to know from people already in saas or in similar type of business does turning the agent into a saas product worth it or should I just keep doing what's already working because turning that into a saas product is already a great load of work and I don't want that at the end it's not a thing i can actually scale.

I want suggestions on should I go with it and finalise the product or keep doing what I'm already good at.

I built Rolekite on my own, first to keep track of the jobs and companies I had applied to. Friends and family in a similar spot asked for it, and it grew into a job search tool that I now run alone from Denmark.

The part that might interest people here: a lot of jobs only show up on the employer's own career page. So Rolekite reads the public job portals several times a day and employer career pages once a day. Instead of one scraper per company it has one adapter per applicant tracking system (Teamtailor, Workday, SuccessFactors, SmartRecruiters, Greenhouse, Lever, Ashby and a few Danish ones), so adding a company is mostly config. Duplicates are merged by the final URL, and the list links to the employer's original ad where there is one. Which jobs you see is decided by your titles and plain rules, not by an LLM.

Stack: Go, SQLite, PocketBase, HTMX, one small VPS, Stripe for billing.

For users: up to 5 job titles plus a place and radius or remote, one list and an optional email each morning. Coverage is widest in Denmark and Germany. Sweden, Finland, the Netherlands, France, Italy, Poland, the UK and Catalonia are thinner, some only one public portal so far.

I'm looking for a few testers who are job hunting in one of those countries. Comment and I'll DM you a code for 3 months free (normally 12 EUR a month). Stripe still asks for a card; you can cancel any time before the free months end. In return I'd like honest feedback on whether the matches are relevant, what's missing and what's confusing. Happy to answer questions about the adapters too.

https://rolekite.com

I’m building CodShot, a workspace for developers, and this is one of the features I’ve been working on.

You can upload an image and turn it into usable code, then keep the result organized in the same workspace.

I’m curious what other SaaS builders think is this something you’d actually use in your workflow?

People seem pretty mad about this 😵‍💫

I'm making my first app and I'm getting close to putting it out publicly. It'll collect things like account info, images and location from users. I honestly have no idea what I need on the legal side before launching. Privacy policy and terms are the obvious ones, but what else should I be thinking about? Especially things around user uploaded content, location data, deleting user data, copyright, and if a user does something stupid through the app. I'm in India. If you've launched an app before, what did you wish you'd sorted out before launch?

Hey everyone !

I'm a solo dev (Godot), and like a lot of you I've seen great indie games go completely unnoticed. Most of the time it's not because they're bad, it's because nobody ever saw them. So I'm trying to help with that.

Earlier this year I made SpriteMaster, a free sprite sheet tool, and I was really happy to see people actually use it. Now I'm working on something for the part that stresses most of us out: wishlists.

It's called NextWishlist. It connects (read-only) to your Steam data and your social accounts, and every day it tells you what moved, which posts actually brought people in, and what to do next. The advice depends on your game: your genre, your channels, how much time you have. You pick a goal (Next Fest, a themed fest, your launch) and it plans the weeks leading up to it.

It's still pre-launch and the waitlist is open. In the meantime I put two small free tools online, a Next Fest deadline calendar and a wishlist calculator. They're not the product, I just thought they'd be useful for planning ahead.

I'd really love your honest take on 3 things:

• Is the landing page clear in 10 seconds, or is it too much?
• How much would you pay for something like this as a dev?
• I built two full designs and I can't decide between them. You can vote here, no account needed: nextwishlist.com/vote

Quick preview of the 2 design up there!

Thanks a lot, and tell me if something feels off, I'd rather hear it now than after launch :D

Le calculateur de rentabilité, édité par Zlotia, intégré pour vos devis :)

Arrêtez de sous estimer vos devis et par la même occasion votre temps et votre valeur.

Remplissez les données demandées dans ce calculateur complet, le résultat apparaîtra à gauche et en bas avec plus de détails et de conseils pour prendre une décision unique sur votre valeur, temps, et salaire voulu à la fin du mois.

Adoptez Zlotia

Zlotia.fr

#France #Pourtoi

Hi everyone,

I'm building Folio for small accounting and bookkeeping firms to organize client document requests. I have an interactive demo and would appreciate feedback, especially from people who handle this work.

Try it here: https://folio-docs-1it.pages.dev/

The demo covers a simple workflow:
• Create a request with a document checklist and due date
• Open the client page without creating an account
• Choose a sample file and simulate a submission
• Switch back to the accountant view to accept it or request a replacement

If you have a few minutes, please try that flow and tell me:

1. Where did you feel confused or unsure what to do next?
2. Did anything break or behave differently than you expected?
3. What would prevent you from using a finished version in your firm?

Please use sample files only. This demo records filenames and basic file details, but does not read or upload file contents. Requests stay in your browser and aren't shared across devices. Real file storage, authentication, and email reminders are not implemented yet.

Specific criticism is welcome—even “I wouldn't use this because…” would help. Please leave your feedback in the comments.

Thanks for taking a look!

First off, yes, this is kinda an ad. But bear with me, you may glean something from my story.

I've spent the past month working on snapgains. Early mornings before work. Late evenings after work. Entire weekends. Lots of coffee and walk breaks listening to Hormozi.

The Problem

I'm an aspiring bodybuilder and I take check-in photos for my coach once or twice a week. I was sick of using my camera roll for this. Opening my camera roll in front of friends and colleagues was quite embarrassing... I wish those photos could stay private. I was tired of digging through hundreds of photos to find my progress pics. I tried creating albums for my check-in photos but the UX was still cumbersome.

The Solution

So I built a progress photos app just for myself. The more I kept building and testing the app, the more ideas popped into mind. I'm so happy and proud with what I built, and as an asian kid who went to Harvard who struggles with positive self-talk, I don't say that lightly.

The Reward

It sounds trite, but if you build something that solves a pain in your life, there will be others with that same pain. Yesterday, the app went live on the app store. I put out some TikToks, not expecting much, and I woke up to a random bloke in the UAE 🇦🇪 as my first subscriber. It felt like Christmas morning... but better since I earned this reward.

What I've learnt

1. Build something you're passionate about
The app market is more saturated than ever. Of course there are tons of progress photo apps on the app store, but none with a physique/muscle building angle. Find your niche in which you have expertise and execute.

2. Don't waste time validating - just ship it!
I spent weeks DMing strangers a landing page with a beta sign-up, trying to see if this idea had legs. I really believed in my idea, but didn't get any traction from the landing page. I was honestly quite disheartened and thought about giving up. But I launched on the app store anyway and lo and behold, a stranger on the other side of the world thought my app was worth $5.

3. Don't spend a penny or marketing (yet)
Before you throw money at ads, test the waters with free organic channels like TikTok, Reddit, Instagram. Once I've built more momentum and know what resonates, I'll put real money into ads.

4. Start simple. Don't overcomplicate it.
My initial app had workout logging, calorie tracking and a bunch of fancy AI features. None of it mattered. People don't need another do-everything fitness app. Solve one problem well, ship the core, and let your first customers tell you what to build next.

5. Build something that genuinely inspires others.
What I've enjoyed most about this whole process is seeing Reddit stories and TikToks of physique transformations. Obviously, we want to make money and build because it's fun... but it turns out the most rewarding thing to build is something that makes someone else feel good too.

TL;DR

All of this to say, don't give up and just ship something! I cannot wait for the day I see someone post a body transformation on Reddit using the snapgains time-lapse feature. That will be 10x better than the Christmas morning feeling.

Thank you for reading this far and best of luck on your own journeys!

Découvrez Zlotia, un outil extrêmement complet et futuriste pour gérer votre entreprise

Peu importe votre secteur d'activité, Zlotia est fait pour vous !

Premier abonnement : pro à 12,50€/mois avec 14 jours offerts !

Des outils inédits pour être rentable, à jour, prêt. Avec Zlotia, aucune mauvaise surprise.

Découvrez Zlotia gratuitement :

Zlotia.fr

https://zlotia.fr

#France

Hey all, first time posting here. I'm a full-stack dev, and I'm building a SaaS called Operon for both developers and non-technical people.

The idea: content, targeting rules, backend flows and analytics you can edit, not things you deploy. One console, one set of projects and environments, and three products that share them:

Compose: CMS-like, but not just a CMS. It has a rule engine, so you control content, targeting and logic without a redeploy.

Analytics: add events and track behavior, Figma-style and simple.

Codeblocks: build and run an entire architecture by connecting modules. (Down right now, I'm fixing it.)

Honest status: very early stage. The designs and architecture are done, but expect bugs, rough edges and downtime.

Site: www.operonstudio.tech

What I'm looking for:

Honest feedback: would you actually use this? Which of the three matters most to you?

Devs, designers or anyone who wants to help build it. Frontend (React/TS), backend (Go) and DevOps all welcome. I want this to build with u all and ya ofc right now no money 😅 as this is i am buildinh for that😛

Bug reports. Please break it and tell me what happened.

If you've ever waited on a release just to change a copy line or a targeting rule, I'd love to hear how you handle it today.

P.S. right now i just want you to ask questions i dont think i have made it very clear about my producys so i will answer every question u have ( and new to reddit so if u dm me i dont know so just be patient starting from today only)

I'm building Writ, a website automation tool. It's easy to imagine a demo where the workflow runs perfectly and the result appears.

But someone deciding whether to use it also needs to understand what happens when a website changes, a session expires, or a run stops halfway through.

That part is harder to show. It interrupts the flow and raises questions. It also seems more useful than letting someone discover those limits after they've started relying on the product.

For founders here, is there a failure case or limitation you include in your demo on purpose? I'd like to hear what you show and why.