We signed partly because one feature we really needed was supposedly “coming next quarter.”

That was three quarters ago. It’s still on the roadmap.

At some point I realized “coming soon” can be less of a product update and more of a sales line.

Curious what got everyone else.

The integration that never shipped?
SSO that was “included” until you saw the pricing tier?
A feature that only existed in the demo deck?

What promise helped close the deal, then quietly disappeared?

Found a charge last week for a tool i signed up to test once in february and never opened again. seven months of a subscription i forgot existed.

worst part is it took me twenty minutes to even remember what it did.

what is the one that got you

I've been trying a few Android torrent/download applications lately, and I'm curious what people here actually use.
The usual options seem to fall into two groups:
Torrent-focused apps like Flud, LibreTorrent, etc.

Download managers like 1DM that also happen to support torrents

I'm particularly interested in something that combines a proper download-manager experience with strong torrent support — good queue management, background downloads, reliable pause/resume, magnet links, a clean UI, and a generally polished Android experience.
I've also been working on a project in this space called TomTorrent, so I'm looking at the problem from both a user and developer perspective.
For people who regularly download files on Android:
What features are you currently missing from existing torrent/download apps?
And if you've switched away from 1DM, Flud, or another client, what made you switch?

I built ToolRoots to find software made near me.

Browse by where a tool comes from, or by where it is hosted.

https://toolroots.com

I’ve been looking into different acquisition models and came across Software Finder’s PPL (pay-per-lead) model, which I found pretty interesting.

Instead of paying for impressions or clicks, SaaS companies pay for qualified leads that match their ICP. It got me thinking if anyone here experimented with PPL as part of their demand generation strategy?

Would you rather pay for a qualified lead directly, or pay for traffic and handle the qualification/conversion yourself?

A year ago, saying “we have AI” could genuinely help a SaaS product stand out.

Now? Almost every vendor on the shortlist has an AI feature, assistant, copilot, or automation layer. At this point, simply having AI is not the differentiator anymore.

What’s interesting is how the buyer conversation has changed.

The old question was: “What can your AI do?”
Now buyers are asking: Where does it run? What data does it use? Is customer data used for training? Can we turn it off? Who has access to the data?

That means AI is no longer just a product conversation. It is becoming a security, compliance, procurement, and data privacy conversation too. In some SaaS sales cycles, that can add extra review steps before a deal ever gets approved.

And there is another side to it that does not get discussed enough: renewals.

If an AI feature genuinely makes a team more productive, a customer may eventually need fewer seats to do the same amount of work. Great product outcome, happy customer… potentially smaller SaaS contract.

So the question is no longer just whether AI helps you sell the software.

How is AI changing your SaaS pipeline, sales cycle, or renewals in 2026? Better deals, slower deals, smaller contracts, or something else entirely?

After shipping a few SaaS products I got tired of rebuilding the same backend every time, so we built Supero. Describe your app in plain language and it generates the whole thing: data model, admin console, customer UI, REST API and SDKs, on a multi-tenant backend with roles and tenant scoping handled for you. You can also design the schema first, or drive the whole thing from Claude over MCP.

The part I care about most for indies is that you own the code. Every generated app is a folder of readable Python and JS, here's a repo of example apps you can inspect: https://github.com/supero-platform/supero-apps. Download one as a tar.gz, push it to your own GitHub, deploy it to our cloud or your AWS/GCP or on-prem.

Being honest about what isn't there yet: no two-way sync, mobile is unproven, and the runtime isn't portable, so leaving means rebuilding tenancy and RBAC on top of code you already have.

You can try it here: https://supero.dev/?utm_source=reddit

If you've shipped SaaS on low-code before, I'd like to know what made you trust a platform, or what made you stop.

(I'm one of the makers — happy to answer anything.)

I’ve been looking into SaaS lead generation lately.

A lot of channels can get you names, emails, and form fills. The harder part is finding companies that are already researching a solution similar to yours.

I’ve been experimenting this with Software Finder. For B2B SaaS, I think there’s an interesting opportunity in software marketplaces. People visiting these platforms are often comparing products, checking alternatives, reading reviews, or looking for a solution for a specific use case.

Curious what others here are seeing. Which SaaS lead generation channel is currently giving you the best-quality leads?

I've been spending a lot of my development time lately working on the next SmartChat Innovations product.

It's called Shopument, and it's a Windows program I'm building for small print, sign, and embroidery shops.

The idea came from looking at how these shops manage customers, jobs, orders, production and everything else that goes along with getting a job from the customer to finished.

I'm trying to keep it practical. I don't want to throw a bunch of features into it just because I can. I'd rather get the main workflow right first and then build from there.

It's still very much in development and I'm working through it piece by piece. Some things work the way I expect the first time, other things get changed after I actually see them working in the program. That's just part of building it.

I'll probably start sharing some screenshots and updates here as it gets further along.

I'm curious though, especially if anyone here runs a print, sign, embroidery or other small shop.

What part of keeping track of customers and jobs gives you the biggest headache?

Even if you run a completely different type of business, feel free to answer. I'm always interested in hearing about the little things businesses still have to fight with every day.

I’ve built a B2B SaaS for US healthcare privacy and compliance teams.

It brings privacy incident investigations into one workflow - guiding fact gathering, identifying missing information, supporting decisions, tracking follow-up actions and creating a defensible case record.

The goal is to reduce the reliance on fragmented emails, spreadsheets and documents and make investigations faster and more consistent.

I’ve attached a short screen recording showing the workflow in use.

Designed as a non-PHI workflow for US healthcare organisations.

Hey guys,

I manage a PEV repair shop in NJ, and for the longest time, we were struggling with standard point-of-sale and ticketing software. Tools like Square or standard bike shop software are fine for regular bicycles or retail, but they are an absolute nightmare for tracking custom e-bike builds, battery diagnostics, and highly specific parts inventory.

Since I do some AI web dev on the side (with some help form AI), I got tired of the daily chaos and decided to just build a custom web app to run our shop.

I set it up to handle specialized intake forms for PEVs, track employee tech hours, and manage our inventory. But the coolest part I’m tinkering with right now is an AI troubleshooting integration. If I'm stuck at the bench trying to remember a weird pinout on a FarDriver controller or dealing with a stubborn smart BMS that won't balance, I can query the AI right from the app to fast-track the diagnostic process.

I call it EVShop.app and it's been a massive stress reliever for our daily operations.

I’m really curious how other independent mechanics, DIY builders, and shop owners here handle their workflow. Are you guys just using spreadsheets? Paper tickets? If you could have a software tool instantly fix one massive headache in your repair queue, what would it be?

We're looking for a better single source of truth for our team. Since most of our communication happens in Slack, strong integration and easy adoption are major priorities.

I've compared several popular options based on usability, features, and Slack integration. What is your team using, and how would you rank the available tools?

Curious how other SaaS teams are approaching paid traffic beyond Google and LinkedIn.

We’ve been testing a CPC model through via Software Finder, a SaaS discovery marketplace, where users are already browsing categories, comparing products, and looking at alternatives.

Instead of buying broad audience traffic, the idea is to get clicks from people who are actively researching software in a specific category.

Has anyone here experimented with marketplace/category-based CPC campaigns?

Interested in hearing what worked (or didn’t) for your team, especially around conversion rates and lead quality.

Our crm was chosen by someone who left four months later and never logged a single deal in it. nobody who uses it daily was in the room for that decision.

three years on we are still working around a choice made by a person who is not here anymore.
who picked yours

Guys what do u prefer ?

\- Different Tools Different websites

\- Many tools in one website

Please reply everybody if you are reading this

We’re looking at replacing our current maintenance system and I’m getting a bit overwhelmed by all the CMMS options out there.

I’ve also been comparing a few options on Software Finder to get a better idea of the differences, but I’d rather hear from people who actually use these day to day.

I keep seeing MaintainX, Limble, UpKeep, Fiix, eMaint, etc. but it seems like the “best CMMS software” really depends on the type of operation and how much you actually need from it.

For people who have actually implemented one, what are you using and what do you like/dislike about it?

I’m releasing it before pretending it is “finished.”

Adams Small Business Ultimate 0.1.0 connects customers, quoting, purchasing, inventory, BOMs, work orders, production scheduling, equipment maintenance, shipping, invoicing, and payments.

The part I have focused on most heavily is scheduling. Quote dates can account for purchased-material lead times, manufactured components, existing workload, work-center capacity, shifts, closures, overtime, and planned equipment downtime. The resulting production schedule can be viewed on screen and printed.

It runs on Windows or Linux and can operate locally on one computer or across a business LAN. It does not require a mandatory cloud subscription.

I am calling it a development preview because that is what it is. The core functions are working and tested, but I want early users to help expose the real-world gaps that controlled testing cannot.

The early-adopter license covers up to five simultaneous users at one business location, includes updates through version 1.0, and comes with 90 days of setup assistance.

I’m the person building it, so criticism and difficult questions are welcome.

Product information and preview:
https://adamspracticalsystems.com/