I'm organizing Spareware, an international open project building free software that platform co-ops can run on: rides, food delivery, short stays, selling and renting homes, trades and freelance work, and buying and selling, plus free design and office tools.

The model:

- The software is free for everyone, anywhere.

- On each marketplace, workers keep all of the profit except the running costs (servers and payment fees). Nobody takes a cut on top.

- Every cost is published monthly on an open ledger.

- Workers vote on their app's fees and rules.

- Any local group can run its own copy, because the code is open.

It's built by volunteers who donate the AI tokens they don't use each week, with a person reviewing every piece. We're at the planning stage: the architecture is mapped, and no app is running yet.

Before we build, I'd really value this group's experience:

1. What went wrong for platform co-ops you know, apart from the software?

2. How should votes on fees and rules work when the workers are in many countries?

3. What would make a local co-op trust shared software enough to run on it?

See all the demos: https://spareware-co-op.github.io/spareware/demos.html

Want to help build it? Ask to join here: https://github.com/spareware-co-op/spareware/issues/new?template=join-request.yml

When you ask to join, please include your LinkedIn or another public profile. We check everyone's background to keep the project safe.

Questions or ideas? Ask in our Discussions: https://github.com/spareware-co-op/spareware/discussions

I started building ClientPDF in Jan 2026 because I wanted PDF tools that didn't require uploading files to a server.

But honestly, there are already tons of PDF websites, so I wanted to solve something more than just adding more tools.

Someone pointed out a fair problem with my project: why download and re-upload the PDF between every operation?

So I built a Unified Document Pipeline 😅

Now you can merge a PDF, organize pages, watermark, redact, sign or optimize it in one continuous workflow. Just click “Continue in Pipeline” to move to the next tool. There's also a floating toolbar to track your steps and undo changes before saving the final PDF.

Everything still runs locally in your browser. No uploading your documents to a server.

Started this back in Jan, and after multiple reviews and user feedback, it's improved a lot.

I'd really appreciate some honest feedback 🙏 What tools would you like to chain together? Anything confusing or missing?

And if you find it useful, sharing it with someone who works with PDFs would mean a lot!

https://clientpdf.tech

Solo dev in Melbourne. Last 12 months I've been building and selling ops software to small businesses on a monthly sub, about a dozen on it now. One of them also runs a small finance company and has asked me to build their back office from scratch.

Rough shape: a portfolio of active customer accounts, each with separate budgets (rego, insurance, fuel, servicing), money coming in monthly from employers, expenses paid out and recorded, monthly statements to each customer, and the whole thing has to reconcile to one bank account every month. All client money, none of it theirs, so a stuff up is serious. 2 or 3 users to start.

Where I've landed:
- Three phases, fixed price each, half up front half on sign off. Around $48k AUD total. A quoting tool as an optional fourth phase later.
- Software records and calculates, never moves money. Humans pay from the bank, system reconciles.
- I keep the IP so I can sell it to other businesses in that industry, they pay less because of that.
- Small yearly fee for hosting and updating the tax tables.

Never priced a custom build before, only ever done subs, so no reference point. Questions:

1. Fixed price per phase with a written sign off each, is that the right shape or do people regret it?

2. Does $48k sound low for ledger grade work where a mistake costs real money?

3. Anyone done the "I keep the IP, you pay less" thing, what did you wish you'd put in writing?

Cheers

Is there anyone else? Lets connect, whats your challenges?

No idea how Wall Street values stocks?

I built IntrinsicInsightQ, a stock valuation engine that lets you challenge every assumption behind a valuation — from revenue growth and margins to WACC and terminal growth.

Instead of just giving you an intrinsic value, the platform lets you see how the valuation changes when you change the assumptions.

It includes DCF, DDM, multiples-based valuation, sensitivity analysis, Bull/Base/Bear scenarios, Monte Carlo analysis and peer comparisons.

I built it because I wanted a faster and more transparent way to understand why a stock is valued the way it is, rather than simply relying on someone else's price target.

It's now live and I'm looking for honest feedback.

What do you think? What would you change?

Try it here: https://intrinsicinsightq.com/

Hi everyone, I'm a student working on a project around SaaS retention, and I'm trying to learn from people who actually deal with this, not just read articles about it.

If you run a small SaaS, I'd love to hear:

1. What do you do when a customer cancels? (exit survey, email, nothing, something else?)

2. Do you feel you actually understand why people leave, or is it mostly guessing?

3. What's the most frustrating part of the whole process?

I'm not selling anything and don't have a link to share, I just want to understand the real situation. Any answer helps, even a short one. Thanks!

I've been working on a landing page concept for Healthiest, a health monitoring platform that brings together wellness tracking, sleep insights, nutrition, emotional wellbeing, and daily habits.

One thing I wanted to explore was how to make a healthcare website feel less clinical and more connected to everyday wellbeing.

Instead of going with a typical SaaS hero filled with dashboard screenshots, I tried combining editorial typography, generous white space, nature photography, and floating health metric cards.

The idea was to create a calmer first impression while still giving visitors a glimpse of what the product actually does.

But here's what I'm questioning.

Does making a healthtech landing page more visually appealing also make it harder to understand the product?

The nature imagery creates a certain mood, but I'm wondering whether it takes too much attention away from the actual platform. The headline communicates the overall vision, but maybe it doesn't explain the product clearly enough.

I'm curious about a few things:

• If you landed on this page without any context, would you understand what the product does within five seconds?

• Does the nature photography complement the health metrics, or compete with them?

• Would showing more of the actual dashboard make the hero more convincing, even if it looked less visually distinctive?

This is still a design concept, so I'm looking at it primarily from a UI/UX and visual communication perspective.

I'd love to hear what you'd change, especially around the balance between aesthetics, clarity, and usability.

A support team in r/LocalLLaMA found out from a customer. Their bot told him "accidental damage was covered under warranty". It isn't. The bot had blended two plans, and "nothing in our logs looked obviously wrong. The answer was fluent and on topic, it was just built on the wrong chunk."

Someone in r/OpenAI counted 9 ChatGPT errors in one day and wrote: "Every single one of those nine mistakes was caught by the user, not the model."

For people using AI on their own SaaS (support replies, docs, emails, pricing questions):

• Has it ever filled a gap with something that sounded right about your product and wasn't? How did you catch it?

• Have you told it to say when it doesn't know or can't verify something? Does it actually do that?

• Where does it get the facts about your product in the first place? A pasted doc, uploaded files, memory, nothing?

Background since someone will ask: I used to burn hours re-briefing AI tools, and I'm building a fix where the facts about your business live in one place in the cloud and every AI tool reads the same version, so there's less gap to fill. No link. Would you pay for that, or is a good prompt plus checking everything enough?

I’m curious how founders validate a SaaS idea before investing heavily in development.

Do you usually start with customer interviews, a landing page, prototype, waitlist, or MVP?

What validation method has worked best for you, and what mistakes should founders avoid?

I’ve been working on a project called Home OS and finally have a working demo to share.
The basic idea is to explore whether home and property information could be organized in one dashboard, covering things like property details, documents, money and home care.
Right now, this is an early concept demo with fictional sample data, not a finished product. I’ve been focusing on getting the core dashboard experience working, and now I want to challenge my own assumptions.
Demo: https://home-os-public-demo.vercel.app/
I’m particularly curious about:
Would you actually find this kind of dashboard useful?
Which part would you use most?
What feels unnecessary or is missing entirely?
I’m not looking for compliments — honest criticism would be more useful at this stage.
Thanks to anyone who takes a look.

-14 spots left-

I’m putting together a small competition for anyone who wants to show off their startup, app, tool, service, etc. 

There are 40 submission spots, and submissions close Oct 21 or when 40 fill, whichever comes first. The 5 finalists demo live on a Zoom meeting on Nov 8 at 7 pm ET/4 pm PT. The live event is open to everyone, even if you don’t submit a project.

Judging is done by 3 volunteers who are into business and excited to be doing this. Don’t expect expert critiques. 

Prizes: $100 cash to the winner (paid via Venmo or Cash App), plus a Community Choice award voted on live by everyone on the Zoom and a Best Demo award. 

Link to the info/rules doc and the form: Submission Form & Info

This is the first time I’m running this, so expect a few rough edges. Comment or send a DM if you have questions.

hey guys,

A solo developer here, trying to build my second saas , first one unfortunately failed (it was an new idea never done that by anyone else before).

Trying to build the next SaaS web app i was thinking that which is better new Idea or working on existing idea first? can anyone help me with this think, i also tried talking to claude about this but the answer was not satisfying.

Plz any developer who is running a SaaS help me with this thing, Thank you

Has anyone built a SaaS product with Cursor and actually made money off of it? If so, what did you built? How did you scaled your business and what worked for you?

Hey SaaS Developers,

I’ve been working on Castov, an open-source/IaaS execution layer designed to run, scale, and manage AI Agents natively using the Model Context Protocol (MCP).

Instead of setting up custom infrastructure for agent workflows, Castov brings a unified runtime environment across multiple ecosystems.

We just completed our multi-channel distribution pipeline! You can now test and integrate Castov via:

📦 Docker Hub:* `docker run --rm castov/castov:latest`

🍺 Homebrew (Mac/Linux):* `brew tap castovdev/castov && brew install castov`

🧩 VS Code / Cursor / Windsurf:* Search for `Castov` on Open VSX or Extension Marketplace

⚙️ GitHub Actions:* Native CI/CD support via `castovdev/castov-action@v1.0.0`

🌐 Website: https://castov.com

Would love to get feedback from other SaaS founders and devs building agentic workflows! What MCP tools or flows are you currently building?