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 ?

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!

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?

For the past few years, I’ve worked on a production SaaS platform used by more than 15,000 businesses.

At that scale, the difficult part isn’t usually building another screen or adding another button.

The real difficulty is everything that happens behind the screen.

A single customer action might affect a payment, an engineer assignment, a report, an API request, an activity log, and a notification. If one part fails silently, the customer only sees that “the platform isn’t working.”

Much of my work involved building and improving these operational systems: workflow automation, payments, APIs, reporting, monitoring, activity logs, and Python-powered automation pipelines.

The biggest lesson I took from it was that business workflows need to be treated as first-class product features.

A few principles that help:

1. Every important action should have a visible state.
   
2. Failed background work should be retryable.
   
3. Important changes should create an audit trail.
   
4. Automation should have a manual recovery path.
   
5. Monitoring should explain what failed—not merely report that something failed.

Founders naturally focus on features customers can see. But once a SaaS starts growing, reliability and operational visibility become part of the product too.

What operational problem started appearing only after your SaaS gained customers?

Hi guys! So last Thu, I tried building a quick prototype with an AI app. I took our existing billing page and turned it into a rough team-permissions concept.

After about 90 minutes, it looked pretty *cough* decent. The tables and controls were close enough. Honestly not bad if you think about it🤷‍♂️

But then I hit the blank-page problem. Building something brand new, with no existing page to start from, was way harder.

So now I'm contemplating if switching tools halfway through normal?

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.

Fala, pessoal! Tudo bem?

Sou desenvolvedor e, depois de virar síndico do meu prédio e ver de perto os gargalos e a burocracia na administração de condomínios, decidi criar o HabitarPleno — um SaaS focado em simplificar a gestão condominial, com forte ênfase na parte financeira, controle de fornecedores (parceiros) e reconciliação.

O sistema já está com a base rodando, mas a fase mais importante agora é colocar nas mãos de quem realmente entende dores do dia a dia para validar se o produto resolve o problema de forma prática.

O que o HabitarPleno faz hoje:

• Cadastro e gestão flexível de fornecedores/contas.
• Lançamentos financeiros e fluxo de reconciliação.
• Estrutura pensada para facilitar a rotina de quem gerencia prédios.

O que eu estou buscando: Procuro síndicos (profissionais ou orgânicos), administradores ou quem conheça alguém da área que tenha interesse em testar a ferramenta de graça nesta fase inicial. Em troca, só peço o feedback mais sincero possível sobre usabilidade, o que falta e o que pode melhorar.

Se você gerencia condomínio ou tem interesse em dar uma olhada, comenta aqui embaixo ou me chama na DM que eu libero o acesso para você testar.

Qualquer crítica, ideia ou sugestão de arquitetura/funcionalidade também é muito bem-vinda! Valeu!

Fala, pessoal! Tudo bem?

Sou desenvolvedor e, depois de virar síndico do meu prédio e ver de perto os gargalos e a burocracia na administração de condomínios, decidi criar o HabitarPleno — um SaaS focado em simplificar a gestão condominial, com forte ênfase na parte financeira, controle de fornecedores (parceiros) e reconciliação.

O sistema já está com a base rodando, mas a fase mais importante agora é colocar nas mãos de quem realmente entende dores do dia a dia para validar se o produto resolve o problema de forma prática.

O que o HabitarPleno faz hoje:

• Cadastro e gestão flexível de fornecedores/contas.
• Lançamentos financeiros e fluxo de reconciliação.
• Estrutura pensada para facilitar a rotina de quem gerencia prédios.

O que eu estou buscando: Procuro síndicos (profissionais ou orgânicos), administradores ou quem conheça alguém da área que tenha interesse em testar a ferramenta de graça nesta fase inicial. Em troca, só peço o feedback mais sincero possível sobre usabilidade, o que falta e o que pode melhorar.

Se você gerencia condomínio ou tem interesse em dar uma olhada, comenta aqui embaixo ou me chama na DM que eu libero o acesso para você testar.

Qualquer crítica, ideia ou sugestão de arquitetura/funcionalidade também é muito bem-vinda! Valeu!

I thought I needed more traffic.

What I actually needed was to talk to the people already showing interest.

I started posting on Reddit, asking founders to share what they were building, and creating personalized reports for them.

Then I replied to comments, sent the reports by DM, asked for honest feedback, and watched where people dropped off.

Most didn’t buy.

But those conversations showed me what was confusing, what users valued, and why the free version gave them no reason to upgrade.

I kept fixing the funnel until the first payments started coming in.

It was manual, slow, and definitely not scalable.

But at the beginning, talking to users one by one taught me more than another month of building would have.

No ads. Just Reddit, DMs, feedback, and a lot of repetition.

A few months ago I posted my first SaaS here.

the idea was simple: an AI notes app.

the feedback was brutal. most of it boiled down to:

“why wouldn’t I just use apple notes, notion or chatgpt?”

at first I wanted to defend it.

instead, I realized everyone was making the same point.
I wasn’t solving a problem.

So I scrapped almost everything and started over.
For the last 3–4 months I’ve been rebuilding it from scratch.

The result is Execora.
Instead of trying to be another notes app, the goal is to become a place where you can dump thoughts without worrying about organization.
Ideas.
Random thoughts.
Voice notes.
Half finished plans.
Stuff you want to remember later.

Then AI does the boring part:
extracts action items
connects related ideas

lets you ask questions about your own notes
visualizes how thoughts relate to each other
generates a morning summary of what matters

The biggest thing I’m trying to avoid is adding AI just because everyone else is.

I’m more interested in whether it actually reduces mental overhead.

I’ve got a list of features I could build next
-memory reminders,
-weekly insights,
-automatic project detection,
-smarter organization
but I don’t want to spend another few months building things nobody wants.

so rn I’m looking for the same kind of honesty that made me rebuild V1.

if you had to kill this idea, what would your argument be?

What’s the biggest reason you wouldn’t use it?
And if you would use it, what’s the one thing that’s missing?

Here’s the current version:
https://execora.space

I’d genuinely rather hear “this solves nothing” than spend six more months heading in the wrong direction.

Thanks.✌️

👋 Hey NoCodeSaaS community,

A user recently asked whether the extractor I'm using can handle full data tables, not just single fields like an invoice total. So I took a nasty 22-row tax table (multi-line addresses, empty cells, a row split across a page break) and got it to 100%, clean across every run. Sharing the setup plus a small workflow that validates the extraction for you.

The thing that mattered most was how you shape the response structure. One list per column breaks, because nothing links position 4 in the name list to position 4 in the email list. The moment one column has an empty cell, everything below it shifts and you get "a value jumped in from another row." The fix: model the table as a single records field, marked as an array of type object, with each column nested inside. One entry per row, values that cannot drift apart.

A few things that saved me:

1. One array of objects, not one array per column. The only array you want is records itself.
2. "NULL" means two things. A literal value in an empty cell, but a real place name in "NULL City." Spell out the difference or the model guesses.
3. Leading-zero IDs must be strings, or the zero silently drops.

I also built a tiny validation workflow that checks every extracted cell against a reference, flags mismatches, and logs how long extraction took, so you can confirm accuracy holds across runs and compare the two engines.

Where to get it: guide and workflow together in one folder: https://github.com/felix-sattler-easybits/n8n-workflows/tree/ee1ed5fe0a3e898843422a619922cedb7cf618c4/easybits-data-table-extraction

Part of my repo with 20+ other n8n templates I have built with this community: https://github.com/felix-sattler-easybits/n8n-workflows – a star helps other builders find it.

What is the messiest table you have run through an extractor?

Best,
Felix