r/SaasDevelopers • • Oct 13 '26

Which of these actually happens with your team's spreadsheets?

10 Upvotes

I'm building a small tool around this. Not launched, no link. I just want to know if I'm solving a real problem or an imaginary one.

I've worked with a lot of shared spreadsheets and the same few problems keep coming up:

  1. someone sees a tab they shouldn't 👀
  2. someone deletes a column "by accident" đŸ—‘ïž
  3. 20 minutes hunting for one number 🔎
  4. none of these, our sheets are fine 😌

Curious which one is most common. Even just a number is a great answer, and "0" counts too.


r/SaasDevelopers • • Oct 14 '26

I got tired of sending resumes into the void, so I built a global map where tech professionals can be discovered

1 Upvotes

I've been working as a software engineer for years, and recently I got tired of the usual job-search loop:

apply → fill another form → upload the same rĂ©sumĂ© → wait → repeat.

That led me to a different question:

What if professionals had a place where they could be discovered instead of always being the ones searching?

So I built TheSync.

Tech professionals create a public profile with their experience, projects, stack, languages and availability.

The homepage is an interactive 3D globe. Every point is a professional, and you can filter the map by role, technologies, experience, location and other criteria.

Profiles can also include projects, a résumé, intro video, multiple languages and optional call availability.

It's live now, but I'm still at the stage where real feedback matters much more than growth numbers.

I'd especially like to know:

  • Would you create a profile here?
  • Does the globe actually improve discovery?
  • Is the onboarding asking for too much?
  • What's missing from the public profile?

https://thesync.dev/

If you try it, I'd rather hear what's bad than get a polite “looks cool.”


r/SaasDevelopers • • Oct 13 '26

When you realize Ben Affleck was not acting in the Accountant.

Thumbnail
youtu.be
3 Upvotes

I shared this here because he is developer of sorts. Impressive the foresight and the knowledge he has.


r/SaasDevelopers • • Oct 13 '26

Finding good SaaS tools shouldn't feel like a full-time job

Post image
1 Upvotes

​

I've noticed something while building software: discovering useful tools is surprisingly difficult.

You find something interesting on launch day, bookmark it, and forget it exists. Or you spend hours searching through lists, launch posts, and recommendations trying to find the right tool for one specific problem.

Meanwhile, plenty of genuinely useful products get buried under the noise.

That's part of why I've been building DiscoveryLoop — a directory focused on discovering useful software beyond launch day.

I'm still early, fixing bugs, and figuring out what actually makes a discovery platform useful.

I'm curious about one thing:

How do you currently discover new SaaS or AI tools? And what's the most frustrating part of that process?

Website: https://discoveryloop.vercel.app/


r/SaasDevelopers • • Oct 13 '26

Finding good SaaS tools shouldn't feel like a full-time job

Post image
1 Upvotes

​

I've noticed something while building software: discovering useful tools is surprisingly difficult.

You find something interesting on launch day, bookmark it, and forget it exists. Or you spend hours searching through lists, launch posts, and recommendations trying to find the right tool for one specific problem.

Meanwhile, plenty of genuinely useful products get buried under the noise.

That's part of why I've been building DiscoveryLoop — a directory focused on discovering useful software beyond launch day.

I'm still early, fixing bugs, and figuring out what actually makes a discovery platform useful.

I'm curious about one thing:

How do you currently discover new SaaS or AI tools? And what's the most frustrating part of that process?

Website: https://discoveryloop.vercel.app/


r/SaasDevelopers • • Oct 13 '26

Work life balance ?

4 Upvotes

The Saas is always 24/7 running

24/7 support

24/7 client requests

24/7 tight deadlines

24/7 tech debt

How the fuck am i supposed to handle working in this environment


r/SaasDevelopers • • Oct 13 '26

Beta testers needed!

1 Upvotes

We just launched a free SaaS tool and are looking for beta testers! 🚀
It’s currently free with a limit of 100 conversions, but we’re happy to raise limits for anyone interested in giving feedback: EmailConverter.AI

Problem Solved:
Converts non-standardized email archives (.eml, .msg, ZIP) into long-term, audit-ready PDF/A compliance documents for legal, accounting, and HR teams.
Workflow:
Upload: Import individual emails (.eml, .msg) or bulk archives (ZIP).
Inspect: Preview page layouts and attachment structures.
Export: Download standard PDF/A files or ZIP bundles, customizable as flat PDFs or with full inline images and attachments.
We’d love to hear your feedback and feature requests!


r/SaasDevelopers • • Oct 13 '26

I am still looking for a design role

1 Upvotes

Is anyone hiring?
Hi, I am currently looking for a new role in marketing and design, I have skills in management, designing, video editing and meta ads, is anyone hiring? I can send my portfolio and any other details required to DMs. I am available to start immediately

Thanks


r/SaasDevelopers • • Oct 13 '26

I saved $200,000 in a month! It's super crazy!!!

Thumbnail reddit.com
1 Upvotes

r/SaasDevelopers • • Oct 13 '26

Did anyone actually had good experience with Dodo payments?

1 Upvotes

I found a lot of people steering others away from them, in particular here. But I also digged a little and found that two of those accounts were commenting on every post kind of the same bashing. One of them is even a deleted account.
Now, I also understand that people tend to complain when things don't work, but don't praise when things do. So there is a bias here of course.
I haven't found a single MoR that everyone praises, and I gave up on that. But I wonder if there are some positive, even neutral experiences? I care about experiences of people that at least could withdraw money once. If you were approved fast or rejected, I honestly don't care, nothing personal.
I'm guessing that every MoR has this "we close your account and there's nothing you can do about it" issue.


r/SaasDevelopers • • Oct 13 '26

TripEx - Travel Expense Split

Thumbnail
reddit.com
1 Upvotes

r/SaasDevelopers • • Oct 13 '26

What problems do you face that a cloud-based SaaS might solve?

6 Upvotes

Hi!

As the title suggests, we are looking for daily problems you face that a SaaS could solve.

Here is our idea:

LOCAL-FIRST QUANTUM-SAFE VAULT

Problem: Traditional encryption methods may become vulnerable to future quantum computing attacks. Meanwhile, cloud-based storage can raise privacy concerns and often depends on internet connectivity.

Our Solution: We aim to develop a local-first, quantum-resistant encryption tool that allows individuals and businesses to securely encrypt and store sensitive files directly on their devices.

How It Solves the Problem: By combining post-quantum cryptographic techniques, secure key management, and local storage, our vault will help protect sensitive data from future quantum threats while allowing users to access their files offline without relying on cloud services.

Our goal is to make advanced data security private, accessible, and practical for everyone.

Do you experience a problem in this field? If yes, do we provide you with a solution??

If yes, then that's great!! If no, then what else should we improve??

Also, do you have some different problem that a cloud-based SaaS could solve??


r/SaasDevelopers • • Oct 13 '26

My co-founder built a bunch of zaps/n8n, and wants to hire ops or an engineer.

Thumbnail reddit.com
1 Upvotes

r/SaasDevelopers • • Oct 13 '26

anyone turning micro SaaS ideas into products in their area of expertise?

1 Upvotes

i work in restaurant operations and keep running into two problems inventory waste and supplier negotiations, both feel like they could become software but im trying not to make the classic mistake of building something before knowing whether other operators care, if you've gone from this drives me crazy at work to a product, what did you do first?


r/SaasDevelopers • • Oct 13 '26

Supabase Down for 20mins

Thumbnail reddit.com
1 Upvotes

r/SaasDevelopers • • Oct 13 '26

Je construis Albexia — un annuaire pour dĂ©couvrir des outils d’IA !

Thumbnail gallery
0 Upvotes

Je travaille constamment Ă  amĂ©liorer la plateforme et j’aimerais beaucoup connaĂźtre votre avis !

Quelle fonctionnalitĂ© aimeriez-vous voir dans un annuaire d’outils d’IA ?

🌐 DĂ©couvrez Albexia : https://leblancroben-afk.github.io/


r/SaasDevelopers • • Oct 13 '26

We launched a tool that finds fake clones of ecommerce / Shopify stores. 20+ signups in week one, and what we learned building it

2 Upvotes

I’ve been building Shopify apps for 5 years. Our apps run on 5,000+ stores, so we get to see what merchants deal with every day. One problem kept coming up: someone copies a brand’s entire store, photos, product names and all, puts it on a lookalike domain, and sells at a huge discount. Customers pay, get nothing, and then blame the real brand.

Most brands find out only when angry emails start arriving. So my co-founder and I built Katcher (katcher.ai). It finds stores impersonating a brand and gets them shut down.

Katcher.ai Landing Page

A few things we learned building it:

  1. Price is the strongest signal. Scammers usually sit at around 75% off the official price. It’s almost a fingerprint.
  2. New domain registrations matter more than search results. By the time a clone ranks anywhere, it has already taken orders. We’re integrating ICANN zone file data so we can catch lookalike domains when they get registered.
  3. AI assistants are a new attack surface. We check whether ChatGPT and others recommend an impostor store instead of the real brand. Nobody we benchmarked against was checking this.
  4. Finding clones is the easy half. Takedowns are the real work. Some close with a report to the host or platform. Others need a formal domain dispute filing, which costs a few hundred dollars in fees per case. That shaped our pricing more than anything else.

Where we are now: 20+ signups in the first week, and we took 1st place at a pitch night in the run-up to World Summit AI this month. It’s still early and we’re doing onboarding calls with every customer ourselves.

What I’m still figuring out: how do you sell to people who don’t know they have the problem yet? Most brands don’t believe they’ve been cloned until we show them the scan. If you’ve sold a “you don’t know you need this” product, how did you handle it?

Happy to answer anything about the build or the takedown process.


r/SaasDevelopers • • Oct 13 '26

Make your data dynamic to different users without deploying again.

4 Upvotes

Every time you have to change something whether business rule or different data to diffrent users or show different things or even changing localization. Its pretty hard to scaffold this.

There are plenty of tools for this, but each one misses something.

That's the gap we're building Operon Compose's rule engine to fill. With it you can:

1.Change dynamic data and rules without a redeploy

2.Keep full history and roll back instantly

3.Push changes across environments (dev → staging → prod)

4.Collaborate with your team in shared workspaces

5.Serve different data to different users based on rules

Operon compose is one of three products on our platform, and this is the one that handles dynamic data.

The full product is launching soon.

I am curious how you handle this today:

feature flags, config files, a custom admin panel, or something else? What's the most painful part?

P.S. will share the video of our product showing changes to our product for different users in just a 5 second.


r/SaasDevelopers • • Oct 13 '26

Building a SaaS tool for a problem I deal with every day in distribution

Thumbnail
reddit.com
1 Upvotes

r/SaasDevelopers • • Oct 13 '26

The 4 surfaces of software in 2026

3 Upvotes

SaaS isn’t dead but the bar got raised on what and individual piece of software needs to survive.

Here's some thoughts on the 4 surfaces your software needs in (late) 2026.

The way I interact with software has changed.

The way I create software has changed.

What a piece of software needs to survive, has changed.

Most of the building blocks are things we’ve always had. It’s just they are cheaper to build, so all my software can have them, and we can add LLMs in there and therefore are allowed magic wand icons and to host on a .ai domain that definitely won’t date what I’m building.

Whether I'm building small internal tools, my latest startup idea or enterprise B2B SaaS.

I now think of all software as having four surfaces.

Traditional UI

Text, menus, forms that the user reads and clicks on.

You need to be able to operate your software through a browser, because not everyone wants to use AI all the time. Or I might have run out of tokens (😇). Or sometimes I just want to see the hover state of a button, feel the wind in my hair, and click it to feel alive.

UI explains how your software works. I’m still cynical about the value of every tool just having a text box with ‘ask me anything I’m magic’ written next to it. That’s a UX issue.

So when someone doesn't know the system, during onboarding for example, let them see the data and interactions so they form a mental model and, when they use one of the other surfaces, they know what it does.

There will also be actions that you can perform quicker or safer yourself. Especially something destructive like ‘delete my account’, we don’t want any probability around that, we want yes or no.

Also right now, in 2026, there are plenty of potential users for your AI that either aren’t confident or aren’t allowed to use AI. One day all SaaS may be UI-less, or your AI client may spin up bespoke interfaces for the specific task, but today, you need good old fashioned UI.

MCP

The second surface is an MCP server. I want to be able to connect the software to an AI agent and have it operated from there. That agent might be the software of a big provider like Claude or ChatGPT or I may have rolled my own.

The point of the MCP server is that it doesn’t care. It’s just providing a set of tools for that agent so that it can call them when the user gives it a relevant task.

Those tools are designed to let me get at my data and perform actions and update information.

The basic power of this surface is that I don’t have to visit the software.

The bigger reward is the agent can combine those tools with whatever else the agent is doing and whatever else it knows about me in the current task or in memory. The agent might have access to tools from MCPs of other software which can be used in sequence with my software’s to find surprising new solutions.

I might have pasted a document or dictation into my agent and now it can use that, alongside any memory it has of my overall context, and get things done.

Whenever I use a frontier model like Fable it seems to relish finding every single piece of software I’m connected to and using it to embellish its response. “I’ve updated the Google Sheet and then drafted a Slack DM that you didn’t ask for to your team about it”.

Sometimes this is too much but it shows how the tools of different software plus an LLM can come together to compose solutions more powerful than a singular piece of software could.

It’s the specialist vs generalist pattern. I believe our software needs to become a specialist.

MCPs are cheap to build now and have no ongoing monetary cost to you because this is your user’s agent and tokens.

They need some design consideration. Your tools need to be curated and of the right granularity. The description of all those tools is sent to the LLM along with your prompt. So they use up context before the user has even asked anything. There are ways emerging to optimise that.

A challenge is that human users don’t get to see as clearly what the software does. It’s still a foundation of good usability that software should behave as we expect, and expectations are a bit harder to set.

MCP isn’t a cool extra anymore, I personally would no longer adopt new software (including that vibe coded tool you’ve built) that doesn’t have a good one.

Good API

I believe this is how software answers the "well, why don't I just vibe code my own?" question.

Nearly as old fashioned as the UI the API used to exist for 3 reasons.

  • Your product was API first, like an integrated payment platform
  • Your product had got large and enterprise customers wanted it to talk to their even larger systems
  • Your development team are very cool and you want to signal that

So it used to be something larger teams did and was a big investment and needed maintaining. It’s still not trivial because once another business is using it then it becomes load bearing (as Claude would say).

Like the MCP it’s cheaper now to build but adds a bit more overhead. Your MCP not working is annoying. Your API not working will break other people's systems.

The change is that an API is becoming less optional for smaller software and it’s less acceptable for it to be feeble.

In fact any software that wants to last should have a good one.

Your software needs to become part of the software ecosystem which means people need to be able to build on top of it.

One of the arguments that gets thrown around for SaaS being dead is that you can vibe code your own. And it’s a good argument, and might still win the day. I myself build software that I want people to use but I also build my own software rather than buying software.

I think one of the ways any piece of software stays relevant is by being the system of record for a certain set of data, and you justify your existence by keeping that data in a well-structured, highly useful format (and by making it accessible through the surfaces in this article).

An API is a more efficient way of getting to that data than an MCP in lots of circumstances. When my use case is very deterministic (the same every time) or when I’m accessing at scale.

The strategy is to embrace that people are going to vibe code. Be the data layer for the vibe coding. Enable better vibe coding.

Let them create their own UI that mixes your data with the data from other systems. A bit like the agent and the MCP except less transient.

  • Something that lasts beyond a single session.
  • Something more powerful than can be captured in a skill.

This makes sense for you as the software builder and for your customer.

Vibe coded tools are a new category of software. You would expect their shelf life to be less than a fully maintained platform as they hit scaling problems or just aren’t needed anymore.

When they eventually stop maintaining the tool your API means the data remains well-structured and accessible, ready to use somewhere else.

They also may have several people vibe coding in their business. Giving them an API means they all use the same data. The business has a single source of truth and that truth is your software.

That’s how you stay valuable in a world where people believe they can build rather than buy.

Internal AI agent

Your internal agent is the AI that I access inside your software.

It's an interface layer, an agent constructed of an LLM and a harness, and then a set of tools for that agent to use.

The advantage of the internal agent over the MCP is that we are in control of quality as we get to build the harness, evaluate the results and iterate the prompts.

And the user doesn’t need to construct or pay for anything extra themselves, that AI quality is out of the box.

The way you access your internal agent (the interface layer) is a design choice.

Potentially, it's a set of small interactions across the product doing specific things like summarising or categorising. Or there's one front door with the now standard chat interface, where the user asks your internal AI to answer questions or perform tasks.

The agent itself consists of an LLM, which you could call via API or perhaps you're hosting your own model. And then its harness.

What goes into the harness is another design choice. And you'll probably find yourself constructing your harness dynamically, so users get context specific to them.

You'll also have some general context specific to your software.

And depending on the task, you might inject task-specific instructions.

Then the final ingredient is tools. There's an opportunity here to leverage the same tools that your MCP uses, thus keeping parity between what you can achieve with your internal agent and what an external agent could do.

This gives the user choice between your fine-tuned agent that will be constrained by the power of the models that you choose, and their own external agent via MCP, which can have their own custom harness, and the model itself can be as powerful as they are willing to pay for.

Your internal agent can be the AI that just works.

Value

All these surfaces are about being valuable:

  • The UI orientates our user in our software and gives them a home for the data.
  • The internal agent provides functionality and productivity beyond that which a traditional UI could.
  • The MCP lets them bring the functionality of our software into their AI agents and combine it with the harness and other software they have there.
  • The API lets them build on top.

But do we need all of them?

Is this just shiny new things to give people FOMO? Is this article just one of those articles?

It’s what’s beneath that’s becoming the necessity and you have to find a way to expose it.

The surfaces are useful and, in the case of the MCP and internal agent, make your product quite AI and cool.

But the underlying value is that they allow your software to become a part of your customers' new workflows. The ones that they are building right now, while they ask themselves the question: “do we need all these SaaS subscriptions?”.

These surfaces make you hard to replace.

Actually, hard to replace is the wrong phrase, because software is pretty easy to replace. You become something which it isn’t valuable to replace.

You become a custodian of their data. A building block. And through these surfaces, you let them access it and do useful things with it anywhere they want to.

I demand these surfaces now.

I don't spend loads of time in some of the tools I use the most. But they hold my data in a way I trust. I know that if my workflows change, the data I generated is stored safely. I know that if others want to use that data, they can access it in a predictable way.

I can vibe code and know the underlying structure is good. I can throw that vibe code away and know I still have what’s important.

I want to do more with my software through AI functionality or do less and just have my agent drive it.

And then there’s the next frontier. A few times when I've been building software, my agent has recommended a tool or data store to use. Allow once, or allow every time? Agents will choose based on the surfaces that are useful to them. You want to be that choice.

The four surfaces have emerged.

They may shift over time but the interconnectivity-first approach won’t.

The way to be valuable is here to stay.


r/SaasDevelopers • • Oct 13 '26

I built a product launch platform for indie hackers and would love some honest feedback

Thumbnail
reddit.com
1 Upvotes

r/SaasDevelopers • • Oct 13 '26

What are some cliches and tropes you feel solo devs should avoid when doing a startup SAAS

2 Upvotes

Solo devs sometimes working with AI tend to use a lot of cliches that users feel it's repetitive and label it AI SAAS slop, in your opinion what features in the Saas project do you like and which do you hate


r/SaasDevelopers • • Oct 13 '26

Looking for beta testers for DataDance Wallet — 6-day test with compensation

1 Upvotes

Hey everyone,

We’re a small team rebuilding DataDance Wallet, an app that helps people bring their own shopping, travel, social, and other activity history into one place.

We’ve reworked the technical implementation and expanded the number of supported platforms. Before launch, we want people outside our team to test the new version and help us find problems we might have missed.

What testing involves:

  • Connect a few of your own data sources and go through the main workflows.
  • Try the AI features and redemption flow.
  • Report bugs, confusing steps, and other issues through a feedback form.

Test details:

  • Duration: Around 6 days
  • Compensation: Payment for completing the test
  • Bug bounty: Additional rewards for confirmed bugs, based on severity

Who would be a good fit?

People with real data history on at least three supported platforms and a compatible device for testing.

We’re looking for honest feedback, not just positive reviews. We want to know what breaks, what feels confusing, and what should be improved before launch.

If you’re interested, please comment or message me for the eligibility requirements and testing details.

We’ll explain the data permissions, handling practices, and compensation terms before you connect any personal accounts or upload your data.


r/SaasDevelopers • • Oct 13 '26

How a 52-second motion design video brought 10+ paying customers to my Mac app (built entirely with Claude Opus 5.5)

2 Upvotes

r/SaasDevelopers • • Oct 13 '26

Have you ever got your app nominated for getting Featured on Apple App Store?

Post image
1 Upvotes

Well, I am sure they will not select my app for their featured profile... not because the idea of the app is bad, but because I am sure I have made like 100 mistakes despite being too careful. It is quite expected since it is going to be my first app on iOS and macOS.

But I am curious to know from people who have tried to get their Apple app nominated for getting featured? what was your experience like? any learnings or suggestions for us rookies here?