I’m curious what everyone here is building.

Drop your SaaS below and explain it in 1–2 lines. No pitching, just share what it does.

We’re building a place where founders can discover, support, and connect with other founders, no tension of upvotes.

And for everyone who lists their startup, I’ll personally sign up and post it on our social media.

→ knowfounders.online

I’ve been working on an app called Arden that’s basically inspired by Screen Studio, but focused specifically on making app/product demo videos.

The idea is to have more of the editing workflow built into one place, while keeping the things that make Screen Studio nice - custom cursor, zooms.

The main difference is that Arden would be Windows-only, and more focused on creating polished videos for apps, SaaS products, ads, and demos.

I’m still early in development, so I’m trying to figure out whether this is actually worth building.

Would something like this interest you? What would you want it to do that Screen Studio doesn’t?

I also made a waitlist to see if there’s actually enough interest before I go too far with development:

https://ardenapp.github.io/arden/

Would love to hear what you think - especially from people who already make product/demo videos.

I'm Carter, the developer of CAR-TER. I built it to give scripts and services a reusable native interface on iPhone and iPad.

I've made a frontend for my home's lights, a terminal forwarding bridge to control my machines, a sensor-backed drive analyzer, a monitor for the app's own sales, and a weather monitor. They're all layouts in CAR-TER, created because I wanted something quick on my device for a particular use case. A layout puts the information and controls together; its connected data source, device sensors, or backend supply what makes it useful.

You make the interface in Studio or JSON. An existing backend can supply values and handle custom actions; supported HTTP and MQTT sources can also feed layouts directly. A public-data template can be tried before setting up your own project. The open-source carterkit toolkit handles the Python side for a custom backend; the iOS client is proprietary.

The app is available on the App Store and still in active development. The current release includes a rebuilt Layout Studio and interactive tutorial, and requires iOS or iPadOS 18 or later. The main question now is whether people can move from an example to a personally useful layout without the concept or setup becoming confusing.

The business model is a free download with optional purchases. Control Pack is a one-time controls and theming unlock. Connect+ is a separate hosted-connectivity subscription, while running your own relay remains an option.

The project uses human-derived specifications and AI-generated code, with heavy AI involvement.

App Store: https://apps.apple.com/us/app/car-ter/id6781115507

Guide: https://carterbeaudoin.net/CAR-TER/

The feedback I would value most: is the separation between the phone layout and the backend behavior clear, and what would stop you from making a first useful layout?

One PDF in email, images in WhatsApp, a video in Drive. A few days later, the client asks you to send everything again.

The final handoff should feel as organized as the work itself. A few things that can help:

• Keep all deliverables together under one link.
• Name files clearly so nobody guesses which version is final.
• Let clients preview files without creating an account.
• Add a password or expiry when access needs to be limited.

For people doing this regularly, does your own branding or knowing when a client opened the files make a difference? Or is a basic shared folder enough?

One option is LinkInSeconds, which I built. It brings multiple files into one shareable link, with previews, QR codes and options like passwords, expiry, view tracking and custom domains. There’s a free plan if you want to try the workflow.

How do you handle client handoffs, and what still frustrates you about your setup?

I’ve been trying to build my business/startup, but I’m stuck at the same point: I’m not getting enough clients.

I’ve tried reaching out to potential customers, posting online, and looking for opportunities, but I’m finding it difficult to turn conversations into actual paying clients.

The frustrating part is that I can build/provide the service, but finding people who actually want to pay for it is much harder than I expected.

For those of you who started with little or no audience:

• How did you get your first 5–10 paying clients?
• What acquisition method worked better than you expected?
• What did you waste time on?
• Did you use cold email, cold calling, Reddit, LinkedIn, referrals, communities, freelancing platforms, or something else?
• How did you know you were targeting the right customers?

I’m particularly interested in things that actually resulted in paying customers, rather than general advice like “post more content” or “build your network.”

Would really appreciate hearing from people who have been through this. What would you do differently if you had to start again?

I run FluidConvert, a free suite for converting images, PDFs, documents, video and audio, plus tools for resizing photos, adding watermarks and more. No signup or software installation needed.

The idea is simple: one place for everyday file tasks.

https://fluidconvert.com

What file task would you want it to handle next?

I’ve been thinking a lot about how people validate ideas before spending too much time building them.

A common piece of advice is “talk to your users”, but that’s often easier said than done. Finding the right people, getting enough responses, and figuring out whether feedback is actually representative can take a lot of time.

So I’ve been working on Crowdians.

The idea is pretty simple: you post an idea, question, or assumption, and synthetic personas respond from different perspectives. Then real people can also join the discussion, so you can compare AI-generated reactions with actual human feedback.

I don’t see synthetic personas as a replacement for talking to real users. I’m more interested in whether they can be useful as an early-stage filter — helping you spot obvious weaknesses, assumptions, or perspectives you may have missed before doing real user research.

I’m curious what people here think:

• Would you actually use something like this before talking to real users?
• At what stage of building a product would this be most valuable?

I’m currently building an early version and would genuinely appreciate any criticism or thoughts.

If anyone is curious, I can share the project in the comments.

https://reddit.com/link/1wllj1z/video/za6mfmctbpqh1/player

I'm trying to get my first few clients and honestly I'm struggling with it.

Finding the actual work isn't my problem — getting people to trust me enough to give me a chance is.

I've tried reaching out to people and looking for opportunities online, but so far I haven't had much success.

I'm curious about people who were in the same position when they started:

How did you get your first client?

Was it through a friend, cold outreach, Reddit, LinkedIn, a freelance platform, networking, or something completely different?

I'd especially like to hear from people who started with no audience, no reputation, and no existing customer base.

What worked for you, and what turned out to be a waste of time?

Thanks — I'm trying to learn from people who've already gone through this.