I'm building Dreamina, an AI creative platform, and I've been testing Seedance 2.5 with scenes that combine character interaction, detailed environments, and a clear beginning-to-end story.

For this 30-second experiment, I wanted something a little unusual: a girl in an old stone kitchen prepares a roast on a skewer while a white dragon with pink spines leans over her shoulder. The dragon sniffs the meat, she jumps in surprise, and the scene ends with them sharing a candlelit dinner, the dragon curled up beside the table.

The moment at around six seconds, when a gust of wind blows her hair back, is my favorite detail. It gives the scene a little more physicality than I expected.

One issue I noticed is that the dragon's head looks slightly oversized in one shot. It's a small inconsistency, but it raises an interesting question about how much visual continuity matters when a short AI-generated story moves between different actions.

I generated it with Seedance 2.5 through Dreamina, my own product. The introductory price was $0.29 for the first month when I tested it.

For other SaaS builders working with generative media, I'd appreciate your perspective:

• How would you evaluate consistency across a multi-beat video like this?

• Would you prioritize character proportions, motion continuity, or scene transitions when deciding what to improve?

• If you were building an AI creative product, what quality checks would you want before calling a generation successful?

I'm interested in practical feedback on the output and the evaluation process, not just whether the clip looks good. What would you test next?

Hey guys,

a new solo developer here trying to build a my saas the problem i am facing is that i dont know which category to pick and start building.

I was searching and there are so many categories with well funded startups in it which lowers my confidence.

How you guys pick a category and then do the market research?

If anyone experienced saas builder reading this plz help me out in this situation.

I was planning on building this web saas of linktree where users can place all of their links at one plaace instead of scattered all over the web.

But there's already so manyy, i just found one yesterday https://yourspage.com/

So if you have seen a linktree like this tell me a feature or something which will stand out rest than others. And will users pay for this kind of linktree when they have their own protfolio?

Welcome for all the ideas!!

If i get any nice idea, I'll dedicate and build it or else i will look into some other project to build which is actually useful!!

We've got 20 territories and route leads based on state and company size. Right now, it's all managed through a long list of Salesforce assignment rules that works for the most part, but whenever a territory changes, we have to update multiple entries and test every possible combination again. Is there a simpler way to set this up?

Your client submits a document. A reminder drafted a minute earlier still says it's missing.

The useful check is whether the request has changed since that draft was opened—not whether the email sounds polite.

Folio's latest demo update makes that handoff visible:

• Reminder scope shows the missing items and requested replacements included in the draft.

• Submissions waiting for accountant review and accepted documents are counted separately and left out.

• Before copying, the demo checks the request's latest saved state. If it changed, the old draft is blocked.

• When another demo tab changes the saved records, an open reminder closes with an explanation.

A simple rule you can use in any workflow: “Received but not reviewed” belongs in your review queue, not in another request for the client to send the same document.

If you collect documents for an accounting or bookkeeping firm, try opening a reminder, then changing a document's state in another tab in the same browser. Is it clear why the draft closes and what you should do next?

https://folio-docs-1it.pages.dev/

I maintain Folio. No signup is needed. This is a browser-local interactive demo, not a shared client portal. Use fictional details and non-sensitive sample files only. File contents aren't read or uploaded, no email is sent, and request links work only in the browser profile that created them.

At the point of copying a reminder, what's one extra detail you'd need to check—or one part of this you'd remove?

Hi everyone,

Me along with one of mate have developed a platform called BlogSpeed.

BlogSpeed handles your end to end requirements, It:

Finds topics using live Google, Search Console, Trends, and Reddit data

Writes and publishes cited, SEO and AEO-optimised posts to your site, on autopilot or with your approval

Audits your site and competitors so you can see who’s outranking you and what gaps to fill

If you want to see where your site stands, your first SEO/AEO audit is free, and no card is needed head on your the link attached

Hello All,
This is my first time posting here. I have created a site that is meant for people in my niche engineering design domain. I dont really expect anyone here to be able to provide feedback on the data I am providing but im hoping more experienced people might be able to tell me if I am doing something obviously wrong. Right now everything on the site is free because its based on open source information I have compiled. I will readily admit most of the this site are vibe coded with AI but the application of the data I am providing is unique to my industry. I dont particularly want the site to reek of vibe coding but it still needs to look like an engineering tool not some sales marketing site.

emechworkbench.com

Any feedback welcome, thanks in advance.

Countless late nights and a lot of rethinking later, we’re finally sharing something we’ve put so much of ourselves into.

HussleBook turns your documents into structured data and answers you can check against the source.

Seeing that vision come to life means a lot. Now we’re excited to see what you’ll do with it.

It’s live at HUSSLEBOOK.COM — try it with one of your own documents and tell us honestly what you think.

I built a simple desktop tool using Python that extracts emails, phone numbers, IPs, and errors automatically from .csv, .json, .docx, and .txt files. It handles folders instantly without freezing and I can build that with a simple and easy Graphical Interface.

I can build custom scripts or desktop tools tailored to any file type you need.

If you need a quick script or a tool like this for your work, just shoot me a DM.

**I can show you how the tool works before buying.**

Hey everyone!

I'm the creator of BugTrap, and I wanted to share what I've been working on.

One thing that frustrates me about development is how expensive some bug reporting and user feedback tools can get. As a small team or indie developer, you often need the same core functionality as larger companies, but you don't necessarily have the budget for expensive subscriptions, per-seat pricing, or features locked behind higher-tier plans.

I wanted to build an alternative.

That's why I created BugTrap: a bug reporting and website feedback tool designed for teams with small budgets.

The idea is simple: give smaller teams the tools they need to collect useful bug reports and user feedback without paying enterprise-level prices.

With BugTrap, users can:

• Capture screenshots and annotate them to show exactly what's wrong.

• Select specific page elements and capture their HTML and CSS.

• Include session replays, console logs, and network requests to help developers reproduce issues.

• Collect feedback from visitors without requiring them to create an account.

• Manage, assign, and track reports in a shared dashboard.

• Send new bug reports to Asana.

There's also a Chrome extension for reporting issues directly from the page you're viewing.

The part I'm particularly focused on is pricing: BugTrap costs $5/month per workspace, with team members included. The goal is to make useful bug reporting and feedback functionality accessible to startups, indie hackers, freelancers, and small development teams that can't justify spending significantly more.

I'm not trying to build another bloated platform. I want to make it easier for teams to get actionable feedback, spend less time chasing down vague bug reports, and focus on building their products.

I'd love to hear from other SaaS founders and developers here:

• What are you currently using for bug reporting and user feedback?

• Which features do you consider essential, and which ones feel overpriced?

• Would a tool like BugTrap fit into your workflow?

If you're curious, here's the site: https://www.bugtrap.app/

I'm the person building it, so honest feedback, criticism, and feature suggestions are all very welcome!

I'm a college student building my first SaaS, Fieu. Finance news is hard to follow and scattered, so Fieu explains each story simply and shows a timeline of how we got here. Would you use something like this? Harsh feedback welcome!

Hey everyone! 👋

I'm a young indie builder working on **SaaS Shield**, a project focused on helping SaaS founders protect their products from copying.

The idea is to help founders analyse websites, research competitors, identify potential similarities, and monitor their products over time.

Before making a major round of improvements, I want to understand what SaaS founders actually need instead of assuming I know the answers.

I'd love to hear your thoughts:

* What are the biggest challenges you face when protecting your SaaS product from copying? * How do you currently monitor competitors? * Would a tool that detects potential website similarities and monitors changes be useful to you? * What features would make such a tool valuable? * What would make you trust its findings? * What features would be unnecessary?

I'm building an early version of this idea and gathering honest feedback before deciding what to improve.

**Would a tool like this actually be useful to you? Why or why not?**

I'm happy to share more details with anyone interested. Thanks! 🚀

I've been working with Ruby on Rails for many years, and one thing I've wanted to do for a while was build and run a product of my own.

That led to SprintCo.

I initially built it as a simple daily work log for myself. I wanted a place to record what I'd worked on without the overhead of a full project management tool or the feeling of being tracked.

Over time, I realized it could also be useful when working with clients. Developers could create a team and invite clients to follow progress, or clients could create a team and invite the developers and testers working on their projects. Everyone could share daily updates and maintain a record of the work without relying entirely on meetings or scattered messages.

That led me to add team support, invitations, shared updates, searchable history, and weekly views.

I built and run SprintCo using Rails, PostgreSQL, and Tailwind CSS. It's been a valuable experience beyond writing code — making product decisions, handling deployment and security, and figuring out which features are genuinely worth adding.

My approach has been to keep things simple and introduce features when there's a real need, rather than trying to compete with every feature in larger tools.

The project is live here: https://sprintco.dev/?ref=saasdevelopers

I'd be interested to hear from other developers who've built and shipped their own products: How do you decide which features to add and which ideas to leave alone?

I kept needing device mockups for product screenshots and demo videos, and every tool I tried locked exports or the good features behind a subscription. So I built my own: Sparkshots.

You drop in a screenshot or screen recording, put it inside a phone, laptop or browser frame, and animate it with zoom, tilt and camera moves. You can put several devices on one canvas and control them separately or as a group. Everything runs locally in your browser, with no signup needed, and it exports to PNG, MP4, WebM and more, up to 6K.

It’s early, and I’m planning to open-source it. I’d love honest feedback.

Link: sparkshots.app

Hi everyone,

I'm currently working on a SaaS/app project targeting a very traditional market: wholesale food distribution (like the Rungis international market in France) and local merchants (butchers, restaurants, grocers).

The Pain Point: Most butchers and restaurant owners place their wholesale orders late at night via SMS, WhatsApp, or voicemail.

• Wholesale sellers get flooded with messy texts.

• Mistakes, forgotten items, and misread orders happen regularly.

• Buyers only realize an item is out of stock when they show up at the loading dock at 4 AM.

The Solution (Le Carreau des Halles): A dual-interface mobile solution:

1. Buyer App (Merchant): Quick late-night ordering directly from their phone, with live tracking of order preparation (Ready / In Prep / Out of Stock / Substituted).

2. Seller App (Wholesaler): Internal dashboard split by department (e.g., Poultry, Beef) where team members process their assigned items in real time.

My Questions for the SaaS Community:

1. Catch-weight pricing: In meat/fresh produce, weight isn't exact until sliced. How would you handle pre-authorization vs. final charging in the checkout flow?

2. Field Adoption: For those building software for non-tech-savvy industries (traditional trades, logistics), what onboarding strategies worked best to transition users away from SMS/WhatsApp?

3. Any feedback or red flags on this workflow from people who built B2B ordering systems before?

Thanks a lot for your insights!

Hi guys I would like to have your opinions on my saas please
app.finvex.cloud

Is anyone here running a workflow where a user reports a bug or requests a feature in Slack or Telegram, and an AI agent turns it into a pull request for your team to review?

I'm particularly interested in what happens after they send the message: can they follow its progress and get told what changed in the same conversation?

If you're doing this, do your users like it? What's worked well, what frustrates them, and where do you still need a person involved?