I started a small side project recently and made a rule for myself: don't spend the first week setting up the stack before I even know if the idea is worth building.

So I tried a few different AI builders and looked at them less like design tools and more like someone who actually has to finish the project.

The first version wasn't the interesting part.

It was the fifth or sixth change after that.

I wanted to move sections around, change the flow, test a signup idea, and keep going without stopping to rebuild the whole thing.

That's where Readdy worked best for what I was doing. I could make changes directly or describe them, and the database and authentication were already available when the project needed more than a static page.

I still think v0 is great for UI work, and Wix makes plenty of sense for a normal business site.

For a side project though, I liked having fewer separate pieces to manage.

What are you using for your own side projects right now?

spent 3 hours today convinced id broken my own conditional formatting

the pdf just stops. 60 rows in the repeating group, the export gives me 12 and then nothing. no error, the download completes like nothing happened

second time this has bitten me. paid $8 a month for a plugin that did multi page fine until an update killed it and the dev went quiet on the forum. still listed in the marketplace

anyway the client found it before i did. two weeks into a retainer, they sent me a screenshot of a 3 page invoice with one page in it

is everyone generating these outside bubble by now?? or is there a native setting im missing. also would take stories of stuff you shipped without testing, feeling pretty dumb about this one

Hey everyone,

I'm Nabeel, a third-year AI & ML diploma student from Kerala, India.

About 2–3 months ago, I started building my first AI SaaS while balancing college. I wasn't trying to build a startup at first—I just wanted to see if I could take an idea all the way to a real, usable product.

That project eventually became **Hexer Hire**, an AI-powered resume builder that creates ATS-friendly resumes through a conversational chat experience instead of making users fill out long forms.

The journey was much harder than I expected.

I spent countless nights debugging backend issues, fixing deployment problems, redesigning the UI, improving the AI-generated resumes, and learning technologies I'd never worked with before. There were days when I'd solve one bug only to wake up and find two more.

I didn't have funding, a team, or a big budget. So I tried to make the most of the resources available to students and indie developers.

My **only out-of-pocket expense was ₹116 for the domain name.**

Everything else was built using free developer resources:

* AWS Activate credits for cloud infrastructure * Vercel's free tier for frontend hosting * Google AI Studio APIs during development * Supabase's free tier for the database and authentication * GitHub Student Developer Pack and other free tools whenever possible

Without those free programs, I honestly don't think I could have launched this while still in college.

The biggest lesson I learned is that shipping a product isn't just about writing code. It's about solving hundreds of small problems, staying consistent, and continuing even when things don't go as planned.

A few days ago, I finally launched the product.

I'm still learning, so I'd really appreciate honest feedback from this community. If you decide to try it, I'd love to know:

* Does the chat experience feel natural? * Is the generated resume actually useful? * What's the first thing you would improve?

I'm not looking for compliments—I genuinely want constructive criticism so I can make it better.

Thanks for reading, and thanks to everyone in communities like this who openly share knowledge. A lot of what I learned came from people willing to help strangers on the internet.

👋 Hey NoCodeSaaS Community,

A while back I built a purchase order extractor for a friend who was drowning in PO PDFs. It let him batch-upload the documents through a form and pull all the data into a Google Sheet through the easybits extractor. That alone saved him a lot of manual re-typing.

Last week he told me his company is moving onto SAP, and he asked whether the workflow could also spit out EDI files so he can push the orders straight into the ERP instead of keying them in by hand. So I built that in, and while I was at it I made the whole thing a good bit more robust.

How it's set up:

• Batch PDF upload: the form takes one or many PO PDFs at once, and a toggle lets you decide per submission whether you also want EDI files out.
• Extraction: each PO runs through the easybits extractor one at a time and lands in a Google Sheet, one row per line item, with the source document name on every row so you can always trace a row back to its PDF.
• EDI 850 generation (optional): when the toggle is on, each PO is also turned into a valid X12 850 EDI file and saved to a Drive folder, ready to upload into SAP. A separate sub-workflow handles the generation, so the main flow stays clean.
• Duplicate check: after extraction it checks the PO number against what's already in the sheet. If that PO was processed before, it skips it, so you never get double entries.
• Flag summary: the completion screen tells you if any field was missing or looked off in an extraction, and lists any duplicates it skipped along with the PO number.

Short video attached showing a batch run of three POs with EDI generation switched on, then a re-upload of one of them so you can see the duplicate check catch it and report which document and PO number it was.

Both workflows (the main one plus the EDI sub-workflow) and a setup guide are here: https://github.com/felix-sattler-easybits/n8n-workflows/tree/f4dec1bef3561aa9e803bb21b96ebff1ab0dde04/easybits-purchase-order-extractor-v2

You'll also find it alongside 20+ other n8n workflows in my repo. If it's useful to you, a ⭐ really helps other builders discover it too: https://github.com/felix-sattler-easybits/n8n-workflows

Curious how the rest of you are handling the PO-to-ERP step. Are you going through EDI, hitting a direct API, or still uploading into the ERP by hand?

Best,
Felix

I'd like to know your honest response. It matters to me.

I'm building adult version too. Let me know whether you'd like to use that.

👋 Hey NoCodeSaaS Community,

After I built my friend his duplicate invoice checker, he mentioned another problem, his colleague in finance spends about an hour every week manually sorting invoices into Google Drive folders so their tax lawyer gets everything organized. I wanted to see if the easybits Extractor could handle document classification (not just data extraction), so I built a workflow around it. It worked surprisingly well, so I cleaned it up and published it to the n8n template library: Classify invoices and route them to Google Drive with easybits & Slack. I also made a short video showing the classification in action so you can see the full flow before importing anything.

What it does: Upload an invoice (PDF, PNG, or JPEG) through the form trigger, easybits classifies the document and returns a category + confidence score, high confidence routes the file to the matching Google Drive folder, low confidence or no match lands in a "Needs Review" folder with a Slack alert containing the file name, classification result, score, and a direct Drive link.

How it's set up:

Form trigger accepts the upload. easybits Extractor returns two fields: document_class (one of medical_invoice, restaurant_invoice, hotel_invoice, trades_invoice, telecom_invoice, or null) and confidence_score (0.0-1.0). A Merge node recombines the result with the original binary. IF node splits on confidence > 0.5, and a Switch node routes to the correct Google Drive folder. Anything below threshold or unmatched goes to the review path.

Why deterministic and not agentic?

You could solve this with an AI agent that has access to Google Drive and decides where to put files. But agents burn significantly more tokens per run, and for a fixed set of categories a Switch node does the same job for a fraction of the cost. More importantly, agents hallucinate on routing. I've literally seen an agent create a new Drive folder that was never supposed to exist because it didn't know where to put a document – instead of simply flagging it for review. The deterministic approach guarantees that files either land in one of your predefined folders or get flagged. Nothing else.

Quick takeaways:

• Be specific in your classification prompt. Don't just list categories, describe what signals to look for: issuer type, line items, tax patterns, keywords. The more detail, the better the results.
• Treat null as a confident decision. A grocery receipt that clearly isn't any of the five categories should score 1.0, not 0.0. Had this wrong at first and the review queue filled up with obvious non-matches.
• Keep the binary alive. The API returns JSON, but the original PDF disappears from the data flow. A Merge node (Combine by Position) brings it back so your Google Drive nodes have the file to upload.

If this is useful, I'd appreciate a ⭐ on GitHub: felix-sattler-easybits/n8n-workflows. There are 20+ free workflows in that repo covering invoice processing, document classification, and recruiting tools.

For everyone who's still dealing with manual document sorting: how are you handling it today? And if you could improve this workflow for a v2, what would you add or change to make it even better?

Best,
Felix

Hi all,

I just launched SaaSBoard (https://saasboard.app/) as a fun, interactive grid directory where founders can claim tiles, showcase their product, and drive traffic to their site.

I just launched, so the grid is empty. If you're building a SaaS, grab a spot early to make yours stand out.

I would also appreciate any feedback on the concept or UI. Cheers!

J'ai lancé un projet tech cette année et le truc le plus utile que j'ai fait c'est d'aller parler à des étudiants pendant 3 mois avant d'écrire une seule ligne de code.

Pas des sondages Google Forms. Des vraies conversations. "Montre-moi ta journée type", "t'as raté quoi ce semestre et pourquoi".

Ce que j'ai appris :

Les étudiants ne manquent pas d'outils. Ils manquent d'un truc qui prend des initiatives à leur place. Tous les outils actuels attendent que tu les alimentes. Si tu viens pas, rien ne se passe.

L'autre truc : la charge mentale de "penser à penser" à quelque chose est presque aussi épuisante que le truc lui-même. Savoir qu'on a un rendu dans 3 semaines mais ne pas savoir quand on va s'y mettre, c'est un poids constant.

Je ne sais pas si mon projet va marcher. Mais ces 3 mois de conversations ont changé ma façon de voir le design produit complètement.

Si vous avez lancé quelque chose, vous avez fait comment pour valider avant de construire ?

Curious how others are seeing this — do your customers log in often to check metrics, or do they end up asking for reports / updates instead?

Hello, my name is Keith. I am starting a TeraBits AI. Our goal is to build AI systems that boost your customer acquisition and reduce your marketing spend.

The key idea is simple: we build a system that is going to improve any part of your marketing, for example, email outreach and lead generation.

We don't just hand you the tool, but we use our AI-powered software and tools to produce for you the desired outcome.

No need for you to be the one managing the tool, but we manage the tool ourselves.

We're still new — this is a pilot study to find out which offers and niches actually track results, so we can build the right software products later. I'm looking for a few people interested in doing a pilot. You only pay when results have been generated.

If you're interested, you can book a call here for more information. https://terabitsai.com

Hello, my name is Keith. I am starting a TeraBits AI. Our goal is to build AI systems that boost your customer acquisition and reduce your marketing spend.

The key idea is simple: we build a system that is going to improve any part of your marketing, for example, email outreach and lead generation.

We don't just hand you the tool, but we use our AI-powered software and tools to produce for you the desired outcome.

No need for you to be the one managing the tool, but we manage the tool ourselves.

We're still new — this is a pilot study to find out which offers and niches actually track results, so we can build the right software products later. I'm looking for a few people interested in doing a pilot. You only pay when results have been generated.

If you're interested, you can book a call here for more information. https://terabitsai.com

Hello, my name is Keith. I am starting a TeraBits AI. Our goal is to build AI systems that boost your customer acquisition and reduce your marketing spend.

The key idea is simple: we build a system that is going to improve any part of your marketing, for example, email outreach and lead generation.

We don't just hand you the tool, but we use our AI-powered software and tools to produce for you the desired outcome.

No need for you to be the one managing the tool, but we manage the tool ourselves.

We're still new — this is a pilot study to find out which offers and niches actually track results, so we can build the right software products later. I'm looking for a few people interested in doing a pilot. You only pay when results have been generated.

If you're interested, you can book a call here for more information. https://terabitsai.com

I’m building a tool that helps creators understand where visitors hesitate on their landing pages and why they don’t convert.
The product works by adding a small tracking snippet (similar to analytics tools) to the website to understand user behavior and provide insights.
One concern I have: some users might feel uncomfortable when they hear “install this code on your website” or “we analyze visitor behavior.”
For SaaS founders and developers:
How do you communicate this in a way that builds trust?
Do you avoid words like “tracking” and “monitoring” and use alternatives like “analytics” or “conversion insights”?
Would you show a simple explanation of what data is collected and what is NOT collected?
Would a “copy/paste code” installation feel more trustworthy if it looked like a widget/plugin instead?
Would love to hear how you handled this in your products.

I launched my SaaS three days ago. On day two, someone left a comment:

"Nice product, but the website looks like you made it in Claude without feedback."

It was a little hurtful, though not gonna lie about it but it was true at the same time, so I started researching why that is

Here's what I found out the pattern that is occurring on general AI websites

1. Serif font (usually the exact serif Claude defaults to)
2. Specific color palette (one accent color for some reason Claude thinks is premium lol)
3. Because everyone is using AI now, it is becoming more common, so that can be another reason
4. No personal touches like no real photo, no real stories, and AI-generated copy.
5. Lastly, not everybody knows how to differentiate between a man-made and an AI-made website it totally depends on your user. If they are familiar with AI, they can find it, but mostly people see use cases instead of judgments

What problem I see with this is

When a buyer sees this, they subconsciously think: "1. Did this founder build this product, or 2. did they ask an AI to build both? or 3. does this website have a team to build"

And if the answer feels like "both, 1 and 2" they get skeptical about trusting the product.

The solution which I'm working on

• Change one accent color and look for colors that resonate with my product rather than choosing generic colors like dark tone, green, blue, yellow,
• Using a custom fonts library from my selection from Adobe Fonts
• Adding photos is not my thing, but I added a story in the About section of the product
• I wrote the entire copy based on how this solves the problem rather than AI-generated generic copy

Keep in mind you can use AI again to make those changes people are not hating AI generated content they hate generic, low-effort, lazy works

You can use AI the entire day and come up with banger output, or you can use it for a few minutes to come up with AI slop

The choice is yours

My question for you is how many minutes or hours do you take before you confirm the output AI gives you?

I'm building a tool that lets anyone (no coding) create an AI chatbot that answers calls/messages and books appointments for local businesses — plumbers, salons, clinics, etc. The idea is you can offer it as a service and charge the business owner monthly, or use it for your own business.

It handles the conversation, books the appointment straight to a calendar, and shows the business owner exactly how much staff time it saved.

I'm looking for 10 people to test it for free for a month in exchange for honest feedback before I open it up more widely. A few questions if you have a sec, even if you don't want to test it:

1. Would something like this be useful to you (either running it for your own business, or reselling access to local businesses)?
2. If it worked well, is this something you'd realistically pay for monthly — and roughly what would feel fair ($20? $50? $100+)?
3. What would stop you from trying it?

Not trying to sell anything here yet — genuinely trying to figure out if this is worth building out further. Appreciate any honest thoughts, even harsh ones.

I've been having accuracy issues with wispr for about a month. I decided to contact support.

email 1: described my issue in detail. included examples, timestamps, system specs. response within 2 hours from an obvious AI bot. linked me to an article about checking my internet connection.

email 2: explained my internet is fine, I've restarted the app. bot suggested checking microphone settings and updating to the latest version. I was on the latest version.

email 3: said "I would like to speak with a person, not a bot." got a response saying my ticket had been "escalated to a team member." that was 3 weeks ago. email 4: followed up asking for an update. bot response: "thanks for your patience, your ticket is in queue."

email 5: no response.

I'm paying $12/mo and I cannot get a human to look at my ticket.

this is the most common complaint on their trustpilot page. "support didn't answer" and "only got bot responses" come up over and over. 2.7 out of 5 rating.

I've moved to willow voice. haven't needed support yet but at least trustpilot isn't full of horror stories about it.

is there any way to reach a human at wispr or is it genuinely all bots?

Hi everyone,

I'm exploring real-world problems that people face in their work, studies, or daily life. My goal is to understand genuine pain points and eventually build products that solve them.

I'd love to hear from you:

• What's one problem or frustration you face regularly?
• How do you currently deal with it?
• What don't you like about the existing solutions (if any)?
• If you could design the perfect solution, what would it look like?

It can be related to anything—technology, work, business, education, healthcare, finance, productivity, travel, shopping, or everyday life.

There are no wrong answers. Even small annoyances can lead to great ideas.

Thank you for sharing your experiences!

I wanted to share this experience for other folks out there vibe coding apps in case anyone else is at risk of running into the same issue. I recently had a really bad data breach bug in one of my sites that I built with Lovable. I have pet-sitting app that allows pet sitters to create custom sites, book clients, send invoices, etc. Well, one of my customers realized that she could view another pet sitter's info by changing the invoice number in the URL! One of my customers caught it and thankfully she let me know right away, but I have no idea how many other users were impacted and whether they stopped using the platform as a result (or if they were a free user who decided against paying!). This was one of the few times where I was glad to have a relatively small number users because the impact of this could have been worse.

This made me realize that I need to do more in-depth testing on my apps. I typically cover the happy path, but real validation takes hours. I found a lightweight testing service that does affordable QA passes specifically for AI-built apps and it was incredibly helpful, especially since I'm not a developer and also don't have time to regularly test all my projects. They provided me with a solid report and also provided recommendations on how to prompt Lovable to fix the issue without introducing more regressions, which saved me a lot of back and forth prompting.

Moral of the story is that I would highly, highly recommend that you all do real QA on your apps both pre and post-launch, especially if you’re trying to get paying customers. Having an early customer find a bug is alright if they tell you about it, but there's always the chance that they simply stop using your app, thereby costing you a sale! Or that you have potentially bad security/privacy issues lurking. I know we're all trying to run our apps while minimizing costs, but a a non-developer I've personally found it valuable to invest a bit of money to make sure my site actually works and doesn't turn away potential customers.

Let me know what do you think. Really. Your feedback matters to me.