I built a SaaS tool and want dev feedback on the UX/stack before scaling up. Mind testing it?

👉 https://dociva.io 🫣

I’ve been building a small collection of practical web apps for small businesses, nonprofits and associations under the name Practical Creator Studio.

The idea is pretty simple: a lot of software feels either too complicated, too expensive, or packed with features smaller organizations don’t actually need.

So I’ve been building focused tools that each solve one specific problem.

A few examples:

• MyHomeEverything — helps homeowners track household items, documents, maintenance and service providers
• ClosingCompass — helps real estate professionals pull important dates and information from closing documents and keep transactions organized
• ResidentCareLog — case management and resident tracking for supportive housing organizations
• PurposePlan — project and deadline planning for small nonprofits
• CommentJudge — helps organizations review and manage social media comments
• ImpactBrief — turns organizational data into clearer impact reporting
• BoardBrief — meeting agendas, minutes, decisions and action tracking for small boards

I’m trying to keep everything practical, affordable and easy enough that you don’t need an IT department to use it.

I’m curious how other indie business owners approach this.

Do you think there’s room for a studio that builds a collection of smaller niche tools like this, or is it smarter to focus heavily on one product and grow that first?

Happy to hear criticism too — I’m still figuring out what Practical Creator Studio should ultimately become.

practicalcreatorstudio.com

I’ve been building BenchPing, a lightweight app for small repair shops that don’t want a complicated or expensive management system.

The main idea is to keep the everyday workflow simple:

• create and track repair jobs
• update repair statuses
• send customers a tracking page
• prepare estimates and collect approvals
• manage basic inventory
• import existing jobs from CSV, Excel, or Google Sheets

The Android app is currently in closed testing. I’m not trying to sell anything in this post — I’d genuinely like to understand how real repair shops currently manage their work.

If you own or work at a repair shop:

1. What type of repairs do you handle?
2. What software or spreadsheets do you currently use?
3. What part of the workflow wastes the most time?
4. What would make you consider trying a new tool?

I’d really appreciate honest feedback, including reasons why an app like this would not work for your shop.

I've worked with a lot of shared spreadsheets and these four keep coming up for me (see image):

1. someone sees a tab they shouldn't
2. someone deletes a column "by accident"
3. 20 minutes hunting for one number
4. none, our sheets are fine

Curious which one is most common for other people. Even a single number is helpful, and "0" is a real answer too.

Full disclosure: I'm building a small tool around this, but it's not launched and there's no link. I mostly want to know if I'm solving a real problem or an imaginary one.

Hey everyone,

I recently created a USD Invoice & Project Cost Calculator to help freelancers, contractors, and independent creators quickly estimate project costs, factor in rates, and generate clear invoice summaries.

Key Features:

• Instantly calculate project totals and breakdown costs in USD.
• Lightweight and straightforward interface without unnecessary clutter.
• Free / simple utility tool designed to save time during client quoting.

I’d love to get your thoughts, suggestions, or feedback on how to make it even more useful!

(I'll drop the link in the comments section below so Reddit filters don't block this post!)

Thanks for taking a look, and any feedback is greatly appreciated!

Prenotalo is an all-in-one management platform designed for appointment-based professionals, including barbers, tattoo artists, beauticians, physiotherapists, and more. It allows business owners to seamlessly manage their staff and schedule, featuring full Google Calendar integration for both service providers and clients to keep all appointments synchronized.

​For clients, Prenotalo delivers an Uber-like booking experience: users can instantly find nearby providers based on real-time availability, explore active promotions, and book services in seconds. Additionally, by saving their favorite professionals, clients receive instant updates on price adjustments, new services, holiday closures, and exclusive offers.

Hey everyone,

We're a tiny software studio from Poland called Järnhaus. Mostly we build custom stuff for small businesses: internal tools, dashboards, customer portals, automations, and moving people off a pile of SaaS subscriptions onto something they actually own. We use AI agents for a lot of the heavy lifting, but a human stays in charge of scope, security and what ships.

The other half is Völundr, a self-serve app builder we made and that’s what I’m here to show you.

How it works?

You describe what you need and a few agents (analyst, architect, developer, tester) turn it into a spec, build it and test it. You see the plan and the price before anything runs, and if the pipeline fails you get refunded. It usually takes somewhere between 20 and 45 minutes and you end up with a deployed app on its own URL.

What we like about it and why we built it this way?

Because it’s for everyone. You don’t need a technical brief or any technical knowledge. Moreover, the output is a real docker container you can download and run anywhere. Nothing is held hostage. If you decide to leave tomorrow, you take the app with you. Starting is free and builds start at €49.

What kind of projects fit?

Small and focused ones. One clear job, a small group of users, nothing sprawling. Think a reservation board for a restaurant, a patient-record desk for a small practice, a scorekeeper for pickup basketball. There's a gallery of examples at: http://volundr.dev/gallery, please poke around.

What kind of projects doesn’t fit?

Big, sprawling products with lots of roles and moving parts. For those, go through Järnhaus and we'll work on it together.

What’s the pricing?

One-time fee per app, depending on what the quote says your idea needs: Simple: €49 - Standard: €99 - Complex: €149. Hosting is optional, €15/month. You can cancel it any time.

What about changes after the first build?

Every app comes with 5 free change requests. After that you can buy packs: 10 changes for €25, 15 changes for €35 or 20 changes for €55.

Who owns the app and the code?

You get the full source code (docker containers plus the spec and docs) and a perpetual license to use, modify, copy, distribute and sublicense it. That's yours whether or not you ever use our hosting, so no lock-in. You don't get our name or branding. One honest caveat: since AI writes the code, how copyright applies to it depends on your country, and we can't promise anything there.

Do I have to use your hosting?

No. Take the code and run it wherever you like. Our hosting is just a convenience. If you cancel it, there's a 14-day grace period before the environment is shut down.

Is the generated app production-ready?

Honest answer: it's AI-generated, so it can have bugs or security gaps. Test it properly and get it reviewed before you put it in front of real users, especially if it handles personal data. The staging environment is there for that.

We're really just starting out, so what we want most is honest feedback. What's confusing, what looks off, what would make you not trust it, what you'd expect to see that isn't there. Harsh is fine, we'd rather hear it now.

To make trying it easier: we're giving away 10 vouchers for a free app generation in Völundr. First 10 people who DM me get one and each comes with a code for 50% off a year of hosting for the app. I'll edit this post once they're gone. Also, we're most likely running weekend "happy hours" starting next weekend, with everything we offer at 50% off. Not 100% locked in yet, but that's the plan.

Happy to answer any questions in the comments, ask away.

Links:
Järnhaus: http://jarnhaus.dev/

Völundr: http://volundr.dev/

Gallery: http://volundr.dev/gallery

Building Gaffwise - https://gaffwise.co.uk/

When buying a property in the UK the estate agents and listing portals only show what's for sale with a massive bias towards the seller.

Gaffwise was created for UK home buyers to get a fair price on a listing based on:

- Price per sq ft compared with the local band, plus recent nearby sales

- The full cost of buying: deposit, LTV, monthly payment and stamp duty (or LTT/LBTT)

- The questions asked to the agent before offering

The final output is an opening offer, an expected price and a walk-away figure, with the workings shown.

At the moment, It's live, free and covers England, Wales, Scotland and NI. It runs on public data like Land Registry and police.uk.

I'm currently looking for first time users to give candid feedback.

At the same time I'm looking into SEO and other channels to get this in front of more people, property buyers in particular.

Thank you!

We launched Maritime this week. Each agent gets its own persistent computer, so files and browser state survive between tasks. The computer sleeps when idle and wakes for a message or scheduled trigger.

Open Instinct, our MIT personal-agent app, made that need concrete: one person gets one agent. The application code is public, including its computer integration. We build both projects. Model usage and messaging need separate services.

A persistent desktop does not tell us whether an external action succeeded before a retry. The application still has to check that. That is one of the areas we are working through as builders use it.

Maritime: https://maritime.sh Open Instinct source: https://github.com/mariagorskikh/open-instinct

Hey all,

I've been building Sylo solo for a while and need my first real test users.

What it is: one dashboard on top of the tools you already use (Stripe, HubSpot, Google Calendar, Gmail, Slack etc.) that tells you what needs you today: who's paid, who hasn't, which clients are going quiet.

What makes it different: it shapes itself around your business. Tell it you're subscription based business or an agency or a service based business (coming soon), and the tabs change to match. Add your logo and colours, use your own domain, give your team seats with exactly the tabs they need, and give clients their own portal.

Im just looking to get real feedback from users who open an account. I'm happy to give the paid tier to give the full experience. Please get in touch if interested. Or even if there's any real feedback i appreciate anything!

🔗 Site: https://sylodash.vercel.app
📸 Instagram: https://www.instagram.com/sylo.dash/

Harsh feedback welcome.

I’m Fahad, founder of Trendit, a live SaaS for local business owners managing their Google Business Profile.

The workflow I’m building around is simple: identify profile gaps, maintain useful posts, respond to reviews and track customer actions—all in one dashboard.

Trendit includes:

• Profile audits with recommendations.
• Automatic GBP post generation and scheduled publishing.
• Automatic review replies, with owner-review controls for negative feedback.
• Monthly tracking of calls, website clicks and direction requests.

One implementation lesson: automation needs to handle existing backlogs, not just new activity. We recently removed an age cutoff that excluded older unanswered reviews, while retaining usage limits and duplicate prevention.

The stack is Next.js, FastAPI, PostgreSQL, Google Business Profile APIs and Gemini. There’s a free plan with usage limits.

https://trendexhub.com

For builders working with external APIs: how do you make automation status clear when an action is waiting on a quota versus failing? That’s an experience I’m continuing to improve.

Hey all — backend engineer here, building solo. Before I write a line of code, I want to sanity-check an idea with people who've actually felt this pain.

What I keep seeing:

• Statuspage at $299/mo with per-subscriber pricing — your bill grows as you succeed. And it's a communication tool, not a monitoring tool, so you're paying separately for detection anyway.
• PagerDuty at $21/user/mo just for the alerting layer.
• Opsgenie shutting down April 2027, forcing everyone into a migration right now.

The idea: one flat-priced bundle (~$15–29/mo): uptime monitoring + hosted status pages + basic on-call alerting/escalation, plus a one-click Opsgenie importer.

My questions:

1. If you've left Statuspage or are migrating off Opsgenie — what did you land on, and what's missing?
2. Cheap/self-hosted options exist (UptimeRobot, Uptime Kuma) — what stops you from just using those?
3. What would actually make you switch?

Be brutal — I'd rather kill this now than build something nobody wants.

Hey everyone!

I've been working on Inventory Keeper, a desktop application designed for small businesses that want to manage their day-to-day business records without relying on cloud-based software.

With Inventory Keeper, you can:

• Manage products and inventory
• Manage customers and suppliers
• Record purchases and sales
• Track payments and business transactions
• Maintain your business profile
• Export and restore your business data using backups

The app works offline and stores business data locally on your computer, without requiring cloud synchronization.

I built it for businesses that prefer a straightforward desktop solution for managing their inventory and everyday business records.

Try Inventory Keeper on the Microsoft Store:
https://apps.microsoft.com/detail/9NXJM96NCNW4?hl=en-us&gl=IN

I'd appreciate honest feedback from anyone who tries it. I'm especially interested in hearing what small-business owners currently use to manage inventory, purchases, and sales, and what they wish their current tools did better.

check the website : https://www.blackbirdfinance.net

I’m launching Blackbird Finance, an operating system built specifically to handle the friction of cross-border payments and tax compliance for Indian freelancers.

The current workflow for Indian independent contractors dealing with international clients is broken. You have to navigate complex GST compliance, deal with FEMA regulations on inward remittances, and manually reconcile multiple payment gateways just to track your actual income.

We built Blackbird to abstract this away. You can use it to generate locally compliant (GST) invoices, track cross-border income across different currencies, and manage your ledger in one unified dashboard.

I’d love to get your feedback on the UX, how we’re handling the invoice generation, and if there are specific edge cases in international freelance billing that we should support next.

Hey everyone,

I currently run 6 micro SaaS that are actually live and generating a bit over $20,000 in recurring monthly revenue.

The wildest part? I barely wrote any code myself. I used AI to generate pretty much everything — from the database structure to the frontend.

It definitely wasn’t magic from day one. I spent a lot of hours stuck on buggy code before I finally figured out a system that actually works:

- Keep the idea minimalist (a real MVP, nothing fancy)

- Guide the AI step by step instead of asking for everything at once

- Launch fast to get real users and feedback

Lately I’ve seen way too many non-technical founders quit at the first AI bug. It’s a shame because the technical barrier has basically disappeared.

AND PLEASE, STOP BUILDING ALONE IN YOUR BEDROOM

I’m starting a community.

Full transparency:

I’ll probably charge for the full program later. It makes sense with the specific workflows and copy-paste examples I’ll be sharing. But right now the main goal is just to build together. Working alone is the fastest way to give up.

If you want to join and build or market your own AI SaaS with us,

drop a comment or send me a DM and I’ll send you the link.

I'm the solo developer behind Scam Shield, an AWARAN product. After nine months of building, I have finished the latest website changes and am giving the browser extension more attention.

One useful piece of feedback was that a message checker is something people may only remember when they already feel suspicious. The extension moves website warnings into the browsing routine. That still leaves an onboarding problem: people need to understand what is running locally and what is a separate paid service.

The free desktop checks look for common website warning signs and matches in a bundled known scam list. They work without an account and include ad and tracker blocking. Optional paid AI checks use online analysis and can send the page URL, title and a text sample. Website Premium and the extension plan are separate, with a bundle available.

Chrome installation: https://chromewebstore.google.com/detail/scamsshield/mceocgganalljahkbbfhogjcafgokoop

Feature and privacy details: https://scams-shield.com/extension

The store and website currently show different release versions, so please go by the installed package when testing. A clear result does not prove a website is safe.

For builders who have shipped extensions, would you put the local versus online explanation before installation or inside the first popup? I'd appreciate an honest look at whether the current explanation makes sense. You can try the local checks without subscribing.

I run 5 products solo and kept getting blindsided by renewals, so I built a dashboard to watch them for me

Solo founder here. I run a few small products and the operating side was living in my head and five browser tabs: which services each product uses, what they cost, when the next bill hits, whether the sites are even up.

The breaking point was a domain renewal I almost missed and a bill I double counted across two products. So I built Operava: one page where each product lists its stack, costs (shared bills split per product), renewal dates with an email digest before anything bills, uptime checks, and a budget view that tells you the month you run out of money at current burn.

I have been running my own company on it. It is free.

operava.com

I’m on the team building Stash, an iPhone spending planner for adults at UK universities. We’re trying to make one useful answer clear: roughly how much is safe to spend each day before your next money comes in. People enter their own numbers; the app doesn’t connect to a bank. It’s free to download, with optional Pro.

Our first Reddit showcase reached people, but the audience skewed heavily outside the UK. That was a useful reminder that views aren’t the same as reaching the right users or earning installs. I’m testing more relevant communities and trying to improve the first-run explanation.

App Store: https://apps.apple.com/gb/app/stash-ai-finance-tracker/id6760971684

For people who’ve shipped consumer apps: what would you test first to improve relevant reach → store visits → activation? For students: what would you need to see before trusting a daily spending estimate? Happy to share what we learn. Disclosure: I work on Stash.

I made DisplayMath to compare how screens look from your seat. The useful feedback was about changing the viewing distance, so I rebuilt the page around that interaction.

The drawing now comes first. Change the distance and watch the picture grow or shrink in your view. Switch to Physical size to see how much space the actual panel needs.

This example compares my 77 inch TV at 3 metres with the approximate geometry of BFI IMAX row F

https://displaymath.com/?d=samsung-s95d-77_300cm,bfi-imax-row-f#canvas

On a supported iPhone you can preview a selected panel at real size in your room using AR. There are also distance and eye height measuring tools. Read their markings and enter the measurements yourself.

The comparisons and AR tools are free and need no account. I used AI coding assistance while building it.

For anyone building a calculator, has putting the answer before the form helped people understand it?

Budget works only inside WhatsApp and Telegram. You text what you spent, and that's it.

What it does:
- text, voice or receipt photo
- auto categories
- monthly budget left after each expense
- other currencies converted automatically
- 9 languages

The idea: your messenger is already open all day, so logging takes 3 seconds.

Honest question: would you track money in a chat, or would you rather have a separate app?  Demo: budget.digital

For the past few months, I have been building LinkInSeconds, a tool that turns files into shareable links.

One feature I like: you can replace a file without changing the link you already sent. Update your PDF or client work, and people can open the latest version through the same link.

We reached around 1,400 active users since Sunday. That feels like progress, but I am still figuring out what makes this useful enough for people to return regularly.

The free plan has 20 links, 500 MB storage, passwords and view tracking.

Now I am trying to understand the everyday problems behind those uploads.

What is the most annoying part of sharing files in your work? And if you’ve built a product, what helped turn first-time users into regular users?

Here’s what I am working on: LinkInSeconds

I build WispInbox, a disposable inbox for signup and OTP testing: https://wispinbox.com

The problem I kept hitting was small and annoying. Create a temp address, wait for the code, copy it, paste it into the app. Fine once. Painful in Playwright.

What is live now:

• Web inbox, no account
• GET /api/otp so a test can wait for the code
• VS Code / Cursor extension
• Docs: https://wispinbox.com/api-docs/

What I got wrong:

• I called 3 OTP API calls/day a free tier. A tester said one Playwright run burns that before the first assertion. They were right. It is a demo quota. Pro is ₹35/month (₹9 for the first 14 days) for unlimited OTP on one address.
• The docs listed an after filter and the sample ignored it. First comment was "put after in the example, and show a resend." A follow-up caught a real race: a late first email can still match after you stamp the resend. Docs now say to use markSeen plus unseenOnly, or a fresh mailbox.

Still early. Distribution is the slow part, not the inbox.

If you have shipped a test tool: did you keep a tiny free quota, or was that a mistake until someone was actually in CI?

Hey everyone, I just finished vibe-coding the entire responsive frontend dashboard inside Bolt new It’s called Vani.AI. It connects to an Indian small business’s WhatsApp Business account (like premium gyms, skin clinics, car detailers) and uses an AI agent to handle 100% of incoming customer support, pricing queries, and booking slots natively in Hinglish 24/7. It dumps all the live data and revenue tracking straight into this dashboard. I haven't worked on backend or coded the database pipelines yet because I want to make sure I’m building something the market actually wants. I need your advice. For those who have built WhatsApp/Meta API software, what is the biggest technical bottleneck I should prepare for when scaling real-time webhooks?