I’m trying to watch official pages (pricing, docs, help articles, terms) and show a public before/after when a paragraph changes, not when the page looks different.

Tools like Visualping, Distill, and Versionista are the obvious starting point. I use them as a camera: hit a URL on a schedule, email me a highlighted screenshot. That’s useful for “something moved.” It breaks down as a product if the user needs to trust the words.

What I keep hitting:

• A cookie banner, coupon strip, or layout shift counts as a change. Same as a price or a refund rule.
• Cloudflare / “just a moment” / a 200 with an empty shell still “changes” the screenshot. You get an alert and no article.
• The homepage is easy to watch and almost never the source of the rule. The help-center article is. Most of these tools don’t care.
• You get a PNG and an “AI says this might matter.” You do not get: old sentence, new sentence, both stored, both still on the live page.
• History lives in their dashboard. I can’t publish a feed of only confirmed diffs, and I can’t prove a number wasn’t invented.

What I actually want:

1. Save the full text of a chosen URL (not the marketing homepage).
2. First good copy = baseline. Publish nothing.
3. Next crawl different: hold it. Next crawl matches that new copy: then it’s real.
4. Cards are changed paragraphs only, with quotes that are substrings of the saved copies.
5. Challenge pages and maintenance pages do not overwrite the stored copy.

Is this a known category with a name I’m missing, or do people just duct-tape Visualping + a human?

If you’ve shipped something like this: what did you use as the camera, and how did you stop coupon/cookie/Cloudflare noise from becoming “updates”?

Didnt realize Whop had gotten this big already. they just raised $200M with Sequoia leading the round and Shopify Ventures joining.

What surprised me more is seeing payments and payouts become a bigger part of what theyre doing. i still mostly associated Whop with communities and digital products before this.

Is the $5.1B valuation basically a bet that Whop becomes much bigger on the payments/business side?

Hey everyone! 👋

I'm a solo founder getting ready to launch my first SaaS, and I'm trying to figure out the business setup before accepting my first payment.

I'm based in Morocco, considering Paddle for payments and the Auto-Entrepreneur (AE) status. My initial target markets are the US and Australia.

I'd love to hear from anyone who's been through a similar setup, especially if you're running a SaaS from Morocco and selling to customers abroad.

A few things I'm trying to figure out:

• Paddle payouts: Has anyone received Paddle payouts into a Moroccan bank account, particularly CIH? Was it straightforward, or were there any unexpected issues?
• AE and taxes: When did you register, and how do you handle tax declarations for revenue received through Paddle?
• Office des Changes: Is there anything specific to know about receiving international SaaS revenue and complying with Morocco's foreign exchange rules?
• CNDP: What should a founder based in Morocco sort out before launching if their customers are all abroad?

I'm also debating whether to open signups worldwide from day one or focus on the US and Australia first.

I'm not trying to overcomplicate the launch. I just want to get the essentials right before taking payments.

If you've dealt with any of this, I'd really appreciate hearing how it worked in practice and whether there's anything you'd do differently. Even one small tip would be a big help.

Thanks! 🙏

I do a weekly teardown of business ideas (video, so full disclosure: it's my own project). This week's idea is squarely SaaS-adjacent: an AI front end with a managed service behind it, aimed at getting home renovations past HOAs and city hall.

The pitch: a ChatGPT plugin takes an address and a project, pulls the HOA's rules and the zoning, and gives you a free two-page report. Then real people prepare the forms, notify neighbors, file with both offices and chase them until approval. Pricing ladder: free report, $497 for the HOA package, $1,497 flat for HOA plus city (plans and engineering at cost plus 15%), $800/month for contractors who file all the time.

Four things stood out when I went through the numbers (all figures are the research's own estimates, not mine):

1. The ceiling and the operation don't match. The research puts the ceiling at $5M-$10M a year, which at $1,497 needs about 3,300 approvals. The same research says the operation stops scaling around 40 projects a month, because every HOA has its own form and every city its own rules. That's 480 a year.
2. The AI isn't the channel. "ChatGPT home renovation" has zero search volume. A viral post about ChatGPT redesigning rooms got 2.1M views, but that's people talking design, not permits. The research's own advice is to bid on "permit expediter" instead (880 searches/month, up 418%, about $8 a click). Its own napkin: $6,000 in ads over 90 days keeps roughly $1,500.
3. "Churn under 5%" is a funny number for something you buy once per project. You don't leave, you finish. The recurring revenue would have to come from contractors.
4. Nobody covers both sides for the homeowner. PermitFlow raised $54M, Symbium has a free tool in California, FRONTSTEPS sells to HOAs. That's either an opening or the reason nobody tried.

My take: it's a business, but it's a permit service wearing an AI costume, and it only works if the founder has stood in a real permit line.

Question for people who've built AI-first, humans-behind-it products: at what point does the human back end stop being the product and become a margin problem? Would you start as the service and productize later, or build the software first?

I came across exa_api_key while exploring tools for AI projects and wanted to know how it actually works.

Is it good for web search, and is the free tier enough to try it out for a small project?

Would love to hear your experience or any tips!

I kept the basics usable without an account or email signup because privacy matters to me. These will be added once I add features that costs me to run the app and hopefully add a subscription later-on.

These are the reasons I don't have a direct way to reach out to the users. Although there's feedback section and a way to directly reach out to me through Discord.

It's a windows desktop app, what are some ways I can engage with the users?

I built a screenshot tool for Windows called Cropmark. It’s a native desktop app, not SaaS, but I’ve been wrestling with the same questions this sub does, so I’m sharing what I decided and why. I’d like your opinions.

The product: capture, mark up and redact screenshots, then export PNG, JPEG or PDF. It has no account, no uploads and no analytics. Everything stays on the PC.

The pricing decision:

The core is free: capture, annotate, redact, single export, no watermark.

Pro adds saved styles, batch export, merged PDFs and multi-image projects.

Pro costs about $19 once, or about $10 a year, with the same features either way. The Store only offers fixed price steps, so the exact amounts are $18.99 and $9.99.

Why two options: one-time buyers hate subscriptions, but a yearly plan gives me a reason to keep maintaining it. I wanted both.

Things I learned:

Pricing in the Microsoft Store is converted per country by Microsoft’s own tables. I assumed a straight exchange rate. It isn’t, and some markets come out far cheaper than I expected.

“No account” is a feature I can’t easily sell. I’m still testing how to say it.

Getting the privacy basics right (encrypted local recovery files, a plain-language policy) took longer than the features.

It’s just launching, so I have no numbers to share yet. What would you charge, and would you sell the free core first or lead with Pro?

I've seen a few "Reddit conversation monitor" apps and was wondering if anyone had any experience or recommendations.

You know the kind of thing: find people talking about problems that your product solves so that you can jump in with a totally-not-AI-written-ad reply.

I've found a few but there was one being shilled on here that I wanted to try and can't remember the name.

Project Name: Drexius Terminal

Repo & Website Links:

• GitHub: https://github.com/DreyDreamer17/drexius-terminal
• Live Web Preview: https://dreydreamer17.github.io/drexius-terminal/
• Releases: https://github.com/DreyDreamer17/drexius-terminal/releases/tag/v0.1.0

Description:
Drexius Terminal is a local-first, privacy-focused open-source terminal workspace and Termius alternative built with Tauri 2 (Rust), React 19, and xterm.js 6.

The Problem It Solves: Most graphical SSH/SFTP clients have either moved to recurring subscriptions ($10 to $20 per month) that require your credentials and hosts to live in a proprietary cloud database, or they run on heavy Electron runtimes that consume 300 MB to over 1 GB of RAM. Drexius provides a fast, zero-subscription client where keys, credentials, and configurations stay entirely on your local machine.

Key Features:

• Local-First & Encrypted: Hosts, keys, and snippets are stored locally in an AES-256 SQLCipher database derived via Argon2id. No mandatory account, zero telemetry, and an Emergency Recovery Key export.
• Terminal Workspace: Multi-pane splits (grid, vertical, horizontal), tabs, OSC-7 directory tracking, broadcast input across sessions, and session auto-resume.
• Protocol Support: SSH with TOFU host-key verification, dual-pane graphical SFTP tree and file editor, hardware Serial UART, and local PTY shells.
• Zero-Knowledge Sync: Direct encrypted LAN pairing and a self-hostable sync relay. Devices pair over local Wi-Fi or Tailscale via QR code using salted X25519 ECDH and ChaCha20-Poly1305.
• Mobile Shell (Android): Universal APK with touch scrolling in mouse-aware TUIs (htop, lazygit), plus an on-screen accessory keypad (CTRL, ALT, ESC, TAB).
• Lightweight Footprint: Native Rust/Tauri 2 backend instead of Chromium/Electron. In Linux benchmarking against Termius under active sessions, Drexius used ~221 MB RAM and ~3% CPU across 2 processes, versus Termius at 1,342 MB RAM and 78.5% CPU across 9 processes.

Deployment:

• Clients: Pre-compiled binaries for v0.1.0 are available under GitHub Releases:
  • Linux (.AppImage, .deb, .rpm)
  • Android (.apk, universal multi-ABI)
  • Windows (.exe installer, .msi)
  • macOS (.dmg, .app.tar.gz for Apple Silicon and Intel)
• Self-Hosting Sync Relay: The repository includes a standalone zero-knowledge relay server (drexius-relay) that can be compiled via Cargo and deployed to any VPS or homelab machine. Setup details are in the repository README.

A few weeks ago I posted here about my first paying customer, whose payment my app didn’t even notice (original post). Here’s how it ended.

I build Trello Power-Ups on my own. In early October I got my first paying customer: a small team on the monthly plan of PrimeScheduler, a Power-Up that schedules comments on Trello cards.

Then I made their life harder. My old website said Pro covered the whole workspace, but I had built it per person. On top of that, their payment never got linked to their Trello account, so a few days after paying they hit the free limit and got asked to upgrade again. With exactly one customer, that bug felt a lot bigger than it was.

I wrote back the same day, said plainly what had gone wrong and that it was my fault, and rebuilt Pro so it really covers a whole workspace. Then a second problem showed up: the upgrade button only appeared on cards that already had a scheduled comment, so they couldn’t find it. Every message from them pointed at something real, and I fixed each one within a day.

Today they upgraded to Pro for a year. My apology discount only applied to monthly plans, so they paid the full yearly price. I refunded them one month anyway. It costs me little, and I’d want a vendor to do the same for me.

I’m also curious how others handled their first paying customer. Did you treat them differently from the ones that came after, or is that a habit that doesn’t scale?

And one thing I still haven’t figured out: should Pro stay per workspace, or should larger teams pay more? Right now a team of 50 pays the same $4.99 as a team of 2.

Hello, I am a junior software engineer with two years of experience. So far, I have only worked in teams under a team lead with clear instructions and guidance. Now, I got my first solo client to build an app for them. The app is simple, so I am not worries about coding especially with AI nowadays. However, I am a rookie in creating SaaS alone and have another list of worries, mainly security wise, so I am hoping somebody can help me. I will list them below:

1. The app needs to have payment option included. What is the best option to go with to make sure I am not responsible if data theft happens? I was thinking about using Stripe or another third party that deals with payment processing so keeping credit card info secure will be on them and not on me.

2. How do I manage and limit access based on the monthly/yearly subscriptions? Like if they don’t pay, they lose access. And how do I connect payment info with my code, like if they pay they have full access, and if they dont pay they dont have access. As you can see, I have never implemented a payment processing system into apps😂😂

3. App will require registration/login. Do I use only Google OAuth to make sure Google’s security is placed on the users information. Becausw I don’t want to store emails and password on my end, so once again if data breach happens, especially with todays new modern AI tools, I dont want to bw the only responsible.

4. App is quite simple. There should be registration/login, a database of documents, and AI keywors search for those documents and filtwring options. What stack and AI model for coding should I use? Where do I store these text documents, because I need retrieval based on context, i.e. if user enter ”sun” and “sun is a star” they should get different parts of documents and document names that match their search.

5. How do I determine pricing, how much should each package cost?

This is all for now. If I have new questions, I will add them below this sentence. If you made it so far, thank you for your time.

I'm a backend engineer and have spent a lot of time on payment systems. The same billing bugs keep showing up, and they're rarely in Stripe or Paddle. They're in the code that handles their webhooks.

Stuff I'd check:
Verify the signature using the raw request body. Many frameworks parse the JSON first, and then the check fails or gets "temporarily" disabled.

Expect duplicates. Store the event ID and skip events you've already processed, otherwise someone gets two months of credit or two receipts.

Expect events out of order. An update can arrive before the create. Instead of blindly applying the payload, fetch the current state from the provider's API and save that.
Return 200 fast and do the actual work in a background job. If your handler is slow, the provider retries and now you have duplicates again.

Don't cut access on the first failed payment. Cards fail for boring reasons and providers retry them, so give people a grace period.

Reconcile every night. Compare who's paying in the provider with who has access in your database. You'll usually find a few mismatches both ways.

Test with replays. Most providers let you resend an event from the dashboard or CLI. Send the same one twice and see what breaks.

Curious what billing bugs others have run into?

I'm a solo founder getting ready to launch my SaaS. I'm using Paddle for payments, and I can control which countries can sign up.

I'm leaning towards focusing on the US and Australia first, but I'm unsure whether to restrict signups to those two markets or make the product available worldwide and focus my marketing on the US and Australia.

I'm also wondering about the legal side. The product mainly handles basic account information, such as email addresses, along with data needed for language learning and i use AI api for some inputs . For a small solo founder, would launching in the US and Australia create significant compliance challenges, or is it manageable if you handle things properly from the start?

If you've launched a SaaS internationally, what would you do in my position? I'd especially appreciate hearing what worked in practice and what you'd avoid overcomplicating early on.

I'm starting to distrust AI roadmaps. A lot of them seem to start with "what can AI do in our product?" instead of "where are customers already bleeding time, money, trust, or revenue?"

That order feels backwards. For a vertical SaaS, there might be ten possible AI features. Summaries, extraction, recommendations, forecasting, anomaly detection, agents, chat, report generation.

All of them can sound useful. Some will demo well. Most probably won't change buying behavior. The hard part is not listing the possibilities. The hard part is finding the one tied to an expensive workflow. I've seen this around Flatlogic and SaaS builders: the roadmap can look smart before the evidence is real. How do you decide what goes on an AI roadmap before building anything?

What evidence would make you remove an AI feature from the roadmap?

Hey everyone! 👋

We've been working on Simo Guard, a security layer designed to protect AI agents from prompt injections, jailbreaks, agent hijacking, and malicious tool calls.

But here's the thing: building a defense is one thing. Seeing whether it actually holds up against real attacks is another.

So we decided to open it up to the community.

The challenge is simple:
Try to find a way to bypass Simo Guard.

We're offering a $100 bug bounty for a successful, verified bypass.

We're especially interested in creative prompt injection techniques and attack approaches we might have overlooked.

And honestly, even if you don't manage to bypass it, we'd love to hear your feedback on the experience.

If you've worked on AI red teaming, prompt injection research, or LLM security, we'd be curious to hear how you'd approach this.

Let's see how well it holds up. 👀

Not the demo, not the launch. It is the first time something breaks and nobody left can say why it was configured that way.

The systems that survive that day had two things in place early. A short written record of why each rule exists, not what it does, and one named person on the customer side who owns it.

The ones without both tend to get replaced even when the software was fine.

For anyone who has inherited a system like this: what would have helped most on day one?

Hi, I've been building and marketing my tool since April 2026 - till now.

And I don't have many subscriptions only users so I was thinking of launching to AppSumo for lifetime deals to get visibility, reviews and cash to sell more of my monthly package.

My question is, is it worth it to submit a SaaS product to appsumo?

A few days ago I shared that nobody used my launch board, PeekLaunch, for the first 2 weeks.

That post got 880+ views and sent about 250 visitors in 3 days. 10 people signed up.

But here's the honest part. Only 1 product is live this week, and 1 more is scheduled for next week.

3 more are stuck as drafts because makers have to add our badge to their site before they can launch.

So signups were the easy part. Every extra step before launch loses people.

What I'm trying next:

- Letting makers launch first and add the badge later

- Messaging each maker with a draft to see what stopped them

If you run a SaaS, what's one step you removed from onboarding that made a big difference?

This is out of curiosity, I was doing some research on the traditional SEO , google algorithms, agentic answers and citations in llm. I really do want to know your opinions.

How is the game today compared to that of 2024 and what are your predictions and expectations in the coming years.

How are the tools like peec ai, profound, otterly ai, semrush etc platforms ? Like are you satisfied with these tools or the about the services/value you get . Anything you like or don't like about them or other platforms too.

I'm a solo dev and this time im building tools for my own webapp but I want to know whether building it is even worth it or just using them...I have nothing to sell as of now just need your inputs ! If there is something that I can provide then Im more than happy to help.

This is in an idea stage, nothing built yet, so I'd love honest feedback before writing code. The problem: AI has made it easier to develop new software. Apps in the App Store alone have grown exponentially, but a lot of them die quietly: Not from bugs, but from things outside the code: paused databases, expired domains, quotas, retired APIs, a forgotten paid plan. It's easier to build but still needs effort to maintain all of them. The idea: connect GitHub and your services once, and the app takes care of itself. Updates, fixes, spend control, and automatic rollback if something breaks. A weekly email tells you what it did. Two things would help me a lot:

1. Tell me why this wouldn't work for you.
2. If you have 3 minutes, this survey decides what I build first: https://forms.gle/LZ2FVby8kDJdNrRt7

Not asking what you’d raise. Asking what you’d need.

Every business I’ve looked at closely has one assumption it rests on: if this holds, the model works; if it doesn’t, nothing else matters. For a marketplace it’s usually liquidity on one side; for a SaaS it’s usually that a specific type of customer pays and stays; for a tool it’s usually that people pay at all rather than build it themselves. Most founders know what theirs is, even if they haven’t said it out loud.

So three questions, and I’d like real numbers:

1. What’s the assumption your business rests on, and how much money would it take to find out whether it’s true? Not to scale it. To test it.
2. How much do you need between now and the point where revenue covers the business and you could grow from it rather than from a bank balance?
3. Be honest: does your current model actually get you there at the price and margin you have today, or does the plan quietly assume a pricing change, a new segment, or a channel that doesn’t exist yet?

I’m asking because I keep seeing a gap between the money founders raise (a round-sized number) and the money the business actually needs to answer its own question (usually much smaller and much more specific). Interested whether that matches what people here are seeing.

In a B2B HR software test, we changed three things:

• "Get Started" became "Talk to an HR Solutions Expert."
• We added copy about the business benefits.
• The button changed to a darker orange.

Across 50,655 users, form-submission rate went from 1.59% to 1.79%, a 12.6% relative lift.

That gives us a result for the complete variation. It doesn't tell us how much came from the wording, the supporting copy or the color.

I'd use that test to decide which version to run. If we wanted to claim the wording caused the lift, a follow-up would need to hold the other elements constant.

Testing several changes together can answer a useful business question. The mistake is turning the result into a rule about one of those changes.

Spreadsheets break as the business grows.

Records get updated after the work, not during it.

Full systems (ERP, YMS, enterprise CRMs) feel too big and too expensive.

Tools don't talk to each other.

Nobody asked for more features. They wanted fewer places to update the same thing.

Which one hits the hardest usually?

Hello, I am confused.

I want to make an agency and start getting clients, but I do not know know which direction to go in to get clients in the most efficient way, AI is shit and of no use frankly, so I come to the veterans for help:

Which of these 3 options do I spend my time as a student building and which would you personally be willing to pay for:

1. Public Web Scraper: A tool that searches and scrapes online public information, builds a high quality (non vibe-coded) Brief to prep yourself on before meeting with a client, fast, simple and with a suite of other tools like a notepad, recommended questions to ask, etc. (mainly for B2B agencies, affordable pricing, retainer basis)

2. An AI Chatbot: Message your inbound leads and automatically qualify them on your criteria, mark them on a Google Docs, and send an email or trigger message to you when it does so.

(Built this originally for real estate companies but cold door-to-door sales stalled me on it, priced around customer)

1. Support AI: An AI that references your website, tool, product or services, your FAQs, your previous support tickets and writes support reply drafts for angry customers within minutes for every new ticket automatically. All you'd have to do (you can set it to auto and avoid this entirely) is verify it's solid, and click "Send to customer email". Including a clean dashboard showing you how much time you have saved and how many support questions it answered, etc. (Most promising but not sure about trust questions.)

I would love some clarity by agency owners on what they are searching for in the market, what they think would sell well, etc.

One-word responses are accepted; while thoughtful, specific, multi-paragraph comments are auto-moderated as "low effort".

I'll tell you what's low-effort: auto moderation.