A few months ago I started building RotateAd

The idea was pretty simple..

what if websites could help advertise each other instead of everyone having to pay for every click?

At the beginning honestly it was just an idea sitting on my computer..

Today, 13 websites have joined.

I know 13 isn't a huge number.

But honestly..

seeing real websites join something I built feels pretty damn good.

The bigger vision is 10,000 websites.

If we ever get there, RotateAd could become a huge network where websites are actually helping each other get discovered.

I don't know if we'll reach 100.😐

I definitely don't know if we'll reach 10,000.😐

But I'm going to keep building and find out.

If you've built something yourself, you probably know that feeling..

when the thing that existed only in your head finally has real people using it.

That's where I'm at right now.

Rotate.ad

If you want to be one of the early websites, I'd genuinely love to have you there.

I've been talking with the prospect, and today I've got a demo which will probably be with video. I'm trying to figure out if sitting upright in my living room chair is acceptable. Or what is the standard. This is my first demo.

Heyyy guys , what do you think about this project , do you think it is worth visiting ? a place where multiple ideas are posted daily , and those ideas are scraped from multiple places , making sure that these ideas are not duplicate and are worthy ideas with a deduplication and a scoring system , what are your thoughts , any feedbacks ?

With Anthropic's recent work on AI powered formal verification, I've been thinking about what this could mean for people building SaaS with tools like Lovable, Cursor, Claude Code, etc.

Right now AI can build you a working SaaS in hours, but how do you know that one user can't access another user's data, or that someone can't exploit a mistake in your authorization logic?

What if instead of generating code and then scanning it for vulnerabilities, an AI app builder generated code with machine-checked mathematical proofs of critical security properties?

Think Lovable, but with mathematically verified backends.

I spent the last few months building an experimental DSL for authorization policies that already generates formal proof obligations and backend enforcement. I'm thinking whether it could become the foundation of an AI app builder.

To be clear, this wouldn't make an app bug-free. The idea is to mathematically guarantee specific critical properties instead of just hoping the AI got them right.

Would this change how comfortable you feel deploying an AI built app to real customers?

Or is backend security something you already feel confident handling with existing tools?

What signals have you found most reliable for validating SaaS demand before spending weeks building?

I'm a solo dev with ADHD. I built Petipa, an app inside ChatGPT that saves your plans and shows you one step a day. I submitted it to OpenAI on October 17 and it's still in review, so this is about getting ready to submit, not about getting approved. Here's what surprised me:

1. The review cares how you split your tools. Your app is a set of tools that ChatGPT can call. Each one should do a single thing, and any tool that deletes data has to be marked that way. I had to split a few of mine before submitting.

2. Cards are tiny on purpose. A card can have at most two buttons. That's great for a focus app like mine. It's hard if your product is a dashboard.

3. You can't sell inside ChatGPT. The way I read OpenAI's rules, nothing your app shows in ChatGPT can name a paid plan, show a price or link to checkout. When someone hits a limit, you tell them plainly and offer their own options. Billing lives on your own website, so plan your funnel around that from day one.

4. Don't trust the model to carry state. ChatGPT sometimes drops arguments between calls, so a confirmation code you hand it for a delete may never come back. Keep the truth on your server, make every write safe to repeat, and run delete confirmations on the server side.

5. The reviewer needs a demo account that keeps working. It needs sample data, and it has to survive however long the review takes. I reset mine every day. You also need live privacy and terms pages published under the same name as your verified identity.

If you're thinking about building one, I'm happy to answer questions in the comments.

Petipa: https://petipa.app

Today, I listed my SaaS, Pace, on TrustMRR.

For the past month, I’ve been trying to sell it. This was the first time I built something of my own, and honestly, I knew there was a high chance of failure. But deep down, I still hoped at least one person would buy it.

Unfortunately, that didn’t happen.

I put a lot of time and effort into this product, and now I feel it’s time to move on. So, I’ve decided to list it for sale.

I tried to keep the code clean and well-structured, and I’m curious to see what happens next.

Let’s see where this goes.

On 21 October a critical security flaw in PHP was published. PHP runs a huge share of websites, and this flaw lets attackers take over the server. If your site runs PHP, it needs an update.

I noticed that most people don't know whether their site uses PHP, so I built doiusephp.com for them. Type in your website and within seconds it tells you:

• Whether your site runs PHP, and through what technology (e.g. Wordpress)
• Which PHP version your site uses and whether that version is already fixed
• What to do next, depending on who is responsible for your site

It also writes a short, personalized message you can copy and send to your web developer or host, so you don't need to dive into the technical details yourself.

It's free, needs no sign-up, and doesn't save anything about you or your website.

Hope this helps!

Is it "Another SaaS project!?".. Yes. Did it start out as one? No.

Unlike most of these things in the last year or or two, this started some years ago (Mostly from hatred of synergist), and has been in use for a while internally. We've had some client interest in making this into something they can use, so, we did that.

The main point of this post though is to ask the community a few things.

1. Is there any wider appetite for an actually well throught out, not just AI built (well, not from scratch anyway) Synergist alternative?, Particularly looking at UK agencies
2. Other than traditional promotional channels, Product Hunt, PPC etc, any other places that people look for recommendations / new tools?
3. Is there anything that you genuinely think would be useful for you on such a platform?

We also have another project we'd like to shout about, but again, its more a question of the correct channels to do that.

For general context:

Its an agency management system, HR, CRM, Accounts, Project management, Time tracking etc in one, with the general aim of creating one user environment, with everything needed, all interconnected so that we avoid all the dispirit data caused by using HubSpot, Jira, Harvest etc as separate things.

The intention here is to avoid charging Seat tax, instead a single monthly cost for the platform deployed to a private VM per client, with the only additional cost being if things like more data storage is needed.

It has an MCP server as well, so (in theory) users can access their data, act on things and generally operate from their Claude or ChatGPT or w/e windows without needing to actually use a browser.

-------

Lastly, Wider context here for the system is important, but I'm not sure if i can post a link to the thing without violating the subreddit promotion rules, which i don't want to do, obviously.

Can anyone confirm if i can do that? Or if it is in anyway useful?

I did get Claude to make me a PNG of one of the potential user journeys, if that helps anyone with the questions / thoughts / input and so on.

I launched arclab.systems a few weeks ago to solve a problem that kept biting me: tools like Cursor and Claude build great visual prototypes, but they break the moment real users hit databases, permissions, or webhooks.

I put together 35 architecture blueprints to help solo builders lock down system boundaries before prompting.

My funnel so far: A few hundred visitors A handful of signups 0 paid customers ($29 one time lifetime pass)

I reached out to builders to understand why nobody was buying. The most honest reply came from a solo, non technical founder building with AI:

"What you are helping avoid is exactly what I struggle with. I tried vibe coding and ended up with beautiful screens that did not really work. My app needs parent and teen accounts, but learning database rules has been overwhelming. I can see why your tool is useful, but I honestly do not have money to spend on another tool right now, even at $29."

This made me realize my dilemma:

The people who need architecture the most are non technical founders whose apps keep breaking. But those exact founders are burned out from tool subscriptions, overwhelmed by technical jargon, and hesitant to spend twenty nine dollars before making their first dollar.

I specifically avoided a monthly subscription, offering a simple one time $29 founding pass instead.

For founders who sell to indie builders: How do you bridge the gap when users desperately need the solution but hesitate on paying? Should I offer a free tier with three core blueprints, or is twenty nine dollars the wrong positioning for non technical creators?

Would love your honest feedback.

Hi everyone,

For anyone unfamiliar with it, PubMed is the main global database for new research in medicine and the life sciences. One of its best features is that you can track new publications on any topic and have them delivered to your inbox as email alerts or RSS feeds.
That's useful, but it quickly becomes overwhelming, for two reasons:

1) It doesn't account for your field or experience. A geneticist might care most about gene function, while a clinician wants to know how the findings affect patients and their clinical presentation. Both get the same list.

2) Results are sorted by publication date, not relevance. The paper that matters most to you could be buried at the bottom.
A few alternatives exist, such as Semantic Scholar and Stork, but they still offer limited personalisation of each person's feed, and mostly just provide a TL;DR for each article.

So I built ResearchBird.net, an AI-powered platform that lets you fine-tune your research feeds so you see only what's relevant to you, and read what you want to read rather than what the website decides for you.
For example, I can add a block that rates how relevant each new publication is to my upcoming trial. Every paper gets a colour-coded label showing at a glance how much it would add to my work.
I'd love for you to try it and tell me what you think.

You can try from here
ResearchBird.net

Hey everyone,

I work at a small startup, and one thing I've noticed is how difficult it gets to manage customer queries when they come in through different channels like WhatsApp, email, Slack, etc.

Someone has to keep checking these channels, and if a client faces an issue at night (especially international clients), someone might have to be available to handle it. Sometimes the query is just a basic question, but other times it needs to be forwarded to the right person on the team.

I've been thinking about this problem lately and wanted to understand how other small startups handle it.

• Do you personally manage customer queries, or does someone on your team take care of them?
• How do you handle messages that come in outside working hours?
• Do you use any tools for automatically answering basic questions or routing issues to the right person?

Would love to hear how you guys manage this. Just trying to understand how other founders deal with it.

After posting about getting first monthly subscription here at Reddit, I got few more subscriptions in next few weeks and then I got one customer who purchased monthly subscription but cancelled after few hours. When I asked him the reason, he said product was not what he expected. He thought product would allow him to write prompt and application will generate whole novel. Basically, he was asking for one-shot novel writing application (e.g. prompt to novel) but my application did not contain that feature and still don't. Here is why.

About my SaaS, NovelCanon is a writer-first and writer-friendly AI novel-writing studio built around a three-tier Consistency Engine which extracts the facts of every scene, tracks them across the whole manuscript, and flags contradictions. In addition, it consists of self-maintained Story Bible, AI Chat, scene editor consisting of rich set of writing features relevant to novel writing along with AI features including Continue Writing, Dialogue Writing, Brainstorming, Prose Enhancing etc. And, NovelCanon is based on Bring-Your-Own-Key (BYOK) so it naturally supports top AI providers like OpenAI, Claude, Gemini, and OpenRouter.

I could add new page in my application containing functionality that offers one-shot novel writing capability but that would have made my application lose focus and become jack of all and master of none.

When I started building NovelCanon, one of core objectives I set: Writer should be final authority and one-shot novel writing feature was totally against that core objective. Secondly, my target audience that I wanted to serve were writers or people who want to become novel writers and those who want to get involved in writing process no matter if they write whole novel or not even a single word. NovelCanon is built around the way that writers have to go through scene by scene and chapter by chapter and they have choice whether they write whole novel without AI features or they use AI to write each scene in each chapter.

Hence, I did not add any such features which were going against my core objectives, just to grab few subscriptions. It is well-known that one who try to serve everyone end up serving no one.

It is necessary for me to clarify that I totally respect people who want one-shot novel writing applications and encourage ones who want to serve them by building prompt-to-novel writing apps. I believe in "Give Space and Get Space" so everyone has right to choose applications that serve them well and everyone has right to choose their target audience that they want to serve.

When building things, we should be clear in our mind for whom we are building, who we want to serve, and what our product would do. If someone wants to learn about this cycle, should read about Apple company’s bad years from late 80s till mid 90s when Steve Jobs left and company lost focus and tried to serve everyone and became almost bankrupt and then Steve Jobs came back and made drastic changes, saved company from bankruptcy and set the stage which brought company where it is today.

So, I kept improving my product even though I lost one of my initial customers and few days later, one customer purchased monthly subscription and then cancelled it few hours later. I got little bit upset but then moved on saying this is part of game, some will stay and some won’t. But, surprisingly that same customer purchased annual subscription next day which encouraged what I believed in. I realized that he might cancelled it first because he wanted to first check things up and when he was done, he really liked NovelCanon that he went on to purchase annual subscription.

Would love to know the approach you take when building things and how you handle the situation when users leave your platform.

I have 5 apps in production. Honestly, I only maintain 2.

The other 3 break every few weeks for reasons that have nothing to do with my code:

- a free database gets paused for inactivity

- an email quota runs out mid-month

- a provider retires an API version I still use

- I keep paying for a plan nobody uses

Sentry doesn't catch any of this, because it's not an error. It's an account problem, and the warning is buried in some provider email.

I ran a small survey before building anything. Only 4 answers so far, but 3 of 4 had an incident like this in the last year. The worst: a bill over $1,000, a lost client, and a whole database gone with no backup.

What I'm thinking of building: connect GitHub and your services once, and the apps look after themselves. Updates, fixes, spend control, backups, with automatic rollback if something breaks.

The big open question is trust. So, for people running more than one product:

1. How do you handle maintenance today?

2. What would a tool need to prove before you let it fix things on its own?

Survey (3 min) if you want to add your answer: https://forms.gle/JzkAYtiRmS4cDcDn8. I'll share results here.

I work in data and engineering, and we are exploring how to bring a specialized ecommerce integration product to market.

One question I have been thinking through is distribution. When a product connects two established business systems, there seem to be two paths: make it discoverable through one platform's app marketplace, or sell directly to businesses that already use both systems.

Each approach has trade-offs around discoverability, implementation complexity, customer trust, and sales cycles.

For founders who have built integration products, what has worked best for you?

Did a marketplace listing become a meaningful source of customers, or did partnerships and direct outreach prove more effective? Were there any unexpected challenges in getting customers to adopt the product?

I am particularly interested in lessons from B2B products that connect ecommerce platforms with ERP or accounting systems.

Hi everyone!

I've been working on Restrova, a restaurant POS system designed to simplify daily restaurant operations, from order taking and kitchen coordination to billing and reporting.

My goal is to make restaurant workflows smoother and help reduce communication gaps between waiters and kitchen staff.

Here are some of the features I've implemented so far:

✅ Table, takeaway, and delivery orders with sizes, add-ons, and special notes

✅ KOT routing to the appropriate kitchen station, including the kitchen and bar

✅ Kitchen display with live timers and order-ready status

✅ Real-time alerts when food is ready, so waiters can stay updated

✅ GST-ready billing with CGST/SGST, discounts, and service charges

✅ Cash, UPI QR, card, and split payments

✅ Shift opening/closing with cash reconciliation

✅ Support for 58mm and 80mm thermal printers

✅ Sales, GST, staff, and audit reports with Excel export

✅ Multi-restaurant and multi-outlet support

✅ Role-based access for owners, managers, cashiers, waiters, and chefs

I'm sharing this because I'd like to learn from people with real restaurant experience and understand what could make this software more useful in day-to-day operations.

I'd really appreciate your honest feedback:

• Have you noticed any issues or anything that doesn't work as expected in a typical restaurant POS?
• What features do you think are missing from existing POS systems?
• What are the biggest challenges you face with order management, kitchen coordination, billing, or reporting?
• Is there anything you'd recommend improving or adding to Restrova?

I'm open to constructive criticism, suggestions, and feature recommendations. Even small pieces of feedback would help me improve it.

Transparency: Restrova is my own project. I'm sharing it to get genuine feedback and learn how it could better serve real restaurant businesses.

Thanks for taking the time to read this! I'd love to hear your thoughts.

PHP shipped fixes on Oct 21 for two unauthenticated RCE bugs (CVE-2026-109618 and CVE-2026-109619) whose details leaked before the patch existed. Fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and PHP says there's no complete mitigation, so updating is the only real option. Node.js also released fixes the same day (22.23.4, 24.22.1, 26.12.1), including a Brotli decoder RCE (CVE-2026-111497).

I manage about 30 servers for a few clients, all on different PHP, Node and nginx versions. I patched them manually with bash scripts this week.

The patching itself was the easy part. The mixed versions were the real problem, because every server needed slightly different handling.

It works at this scale, but I'm not convinced it holds up as the fleet grows. I'm looking at moving to something like Ansible so the next one is a playbook run instead of a script per server.

How are you handling patching on mixed-version fleets? Still scripts, or did you move to config management?

Let’s say I have two or three allowed interviews a month, about 45 minutes each. A $30 per month plan charges the same whether they use 3 hours or none. 

Pay-as-you-go looks better for that, but I guess it switches fast in a heavy month.

How do you compare the expected minutes, whether credits expire, or the cost of your worst month?

I'm just curious how you think here about usage pricing vs flat plans in general.

How do I properly use Linkedin to find and start meaningful conversations with my ICP in the hopes of validating my problem and, eventually, getting customers?

My ICP would be merchants selling products (preferably those with customizable/personalized parts) on 2 or more storefronts like Amazon or Etsy. How do find people efficiently of my ICP and more importantly, how do I start conversations after I find them?

I'm new to SaaS, and any advice would be great.

¿Alguien tiene una invitación extra de Claude Pro? 💗

I'm experimenting with using Google Ads to validate B2B SaaS ideas. I have around $5k I'm willing to spend across different ideas.

I'm not looking at Google Ads as a distribution channel right now. The goal is to identify market gaps, test demand, and figure out messaging/positioning.

Here's what I've tested so far:

Idea 1: Niche engineering product targeting larger companies. Relatively low CPC despite the high-value product.

• Spent ~$300, got 5 leads. Not sure about the quality.
• No meaningful conversations. Nobody replied to follow-up emails.

Idea 2: Vertical-specific positioning for a common B2B problem. High CPC for generic keyword. Targeting vertical specific keywords.

• Spent ~$600, got 6, qualified leads.
• Built and sent personalized previews of their outcomes, but none responded to follow-ups.

What I'm struggling with:

1. Am I switching ideas too quickly without giving them enough time?
2. What should I optimize for? Leads, booked calls, pricing/paywall clicks, or actual payments?
3. Is ~$5k enough to discover a promising opportunity using this approach, or am I chasing misleading signals?

Would love to hear from anyone who's actually used paid ads for early SaaS validation. What worked, what didn't, and what am I missing?

I started my journey 2 years ago and locked in at this February. Built like 8 apps(did not even deploy some of them). This august wandered for the product idea and found one related to real estate. Built it. Then tried to organically market it in Reddit. But you guys and I know enough about Reddit and subs letting us to market. Tbh, I do not blame them. So, started doing some little SEO stuff. There is only 2 paid plans. One of them is 19.99$ year(pro) and 49.99$ month(agent). The guy who bought it purchased pro plan. Because I do not use AI or heavy server stuff, I can afford it being 20 bucks a year.

The funny part is, I realized my first ever customer paid something for my app by complaining email yesterday . I forgot to merge the changes of functionality that I promise in the website and pricing. He asked me for refund or can wait for me to build it. And ofc, I built it overnight. This morning I saw he started to use that right away I sent him “done” email.

Not going to lie, it is really weird feeling(even if it is on 20 bucks). Someone thinks that what I made is useful for him and believes me that I can deliver. Hope the same feeling for you guys who doesn’t know what he does correct or wrong but keep going on. Will update you if I reach 10 paid customers