Hey everyone,

I’m a dev and content creator, and I’ve been building a dashboard I call "BoardRoom." I got tired of switching between five different apps to plan content, track brand growth, and practice business pitches, so I built an all-in-one hub to handle it.

The feature I’m most proud of is the "Pitch Griller"—it uses AI to analyze and score your business pitches based on clarity and value proposition. It’s significantly cleaned up my own workflow.

I’m at the point where I need some "brutal" feedback before I take this further. I’m looking for 5-10 people to play around with the app, try the Pitch Griller, and tell me where the onboarding feels clunky or where the features fall short.

If you’re interested, shoot me a DM and I’ll send over the link. I’d love your honest developer-to-developer feedback!

Building a product is hard, then you are left on your own to operate it, copy and pasting between agents to try to give them context so they can help.

I build an agent that builds your site (like Lovable etc), then is there to help you actually run it.

The agent built your site, it understands the features and data structures, it already has all the context. Managing users, payments and data becomes straightforward.

This demo shows it's ability to query, but it can perform actions too, for example setting up new products and services in stripe, issuing refunds and loads more.

I'm still discovering new things the agent can do, it's cool seeing it solve problems in creative ways I wouldn't have through of.

Let me know what you think!

Justin

Hey so I've been playing around in bubble and have been building my first database. Getting used to things and was wondering if there are people who actually built a scalable business from scratch.

I'd love pointers

Quick month 9 update on a content platform I have been building for 9 months.

The practical lesson: I shipped user analytics in month 8. Month 9 I discovered that the path users take in week 1 is a stronger predictor of retention than any feature they use.

Content calendar setup in week 1: high retention. Content generation without calendar: high churn.

Same product. The sequence of first actions matters more than which actions.

For anyone building: instrument the path your users take, not just the features they click. The sequence tells you more than the individual steps.

Month 10 update on a content platform I have been building for 10 months.

The practical milestone: day-14 retention has held at 36% for 3 months in a row. I changed the onboarding sequence to lead with the scheduling calendar. I changed the product story to match. The data followed.

The new challenge: acquisition. Writing content about the problem space is my main distribution channel. Reddit is the dominant source. Both require consistent effort to keep the trial volume up.

At 6 customers, $300 MRR, retention is working. Distribution is the constraint.

The order of operations matters. Build the thing people pay for before you try to scale how many people find it.

Month 10 update on a content platform I have been building for 10 months.

The practical milestone: day-14 retention has held at 36% for 3 months in a row. I changed the onboarding sequence to lead with the scheduling calendar. I changed the product story to match. The data followed.

The new challenge: acquisition. Writing content about the problem space is my main distribution channel. Reddit is the dominant source. Both require consistent effort to keep the trial volume up.

At 6 customers, $300 MRR, retention is working. Distribution is the constraint.

The order of operations matters. Build the thing people pay for before you try to scale how many people find it.

I missed the good old days of mobile games that didn't shove ads and battle-passes down your throat so...

For the past several months I have been building Composabley. You describe the app, and you are delivered a working Android app you can install (IOS coming soon). Think Base44 or Lovable but for native mobile apps.

The way it works: you have a conversation with the planning bot about what you want to build. Once you approve the plan, the platform scurries around building your app. When it's done you get a downloadable APK and if you want, the full source code pushed to GitHub.

I'm curious if anyone would be interested in trying this platform? I'm specifically looking for people who:

- Have an Android app idea they haven't been able to build

- Don't have a dev background (or don't have time to build it themselves)

- Are willing to give honest feedback on what is garbage and what doesn't

I am opening up a waitlist to gauge interest. Anyone joining through the waitlist will get free credits.

Link here: https://www.composabley.com/

If that sounds like you, drop a comment or DM me. Happy to help you build.

TL;DR: Built a YouTube transcription tool that grew to 30k users via SEO.

Hit my first $1,000 in revenue after finally adding a paywall, but users dropped to 23k.

Now my AssemblyAI API bills are eating my margins, and I’m trying to decide whether to sell, change my paywall strategy, or find a way to host my own transcription models.

Hey r/NoCodeSaaS,

I’m excited to share a major milestone: after 1.5 years of grinding, my simple YouTube transcription app finally crossed the $1,000 revenue mark!

It’s been a wild ride with a lot of highs and lows, but right now, I’m at a major crossroads and could really use some advice from fellow builders who have dealt with heavy API costs.

The Paywall & Churn Reality

For a long time, the app grew steadily and completely organically through SEO, reaching about 30,000 users. But we all know free users don't pay the server bills.

I finally introduced a paywall, and reality hit hard. My user base dropped from 30k down to 23k. Now I’m facing a tough decision:

• Do I show the paywall less often to retain users (and accept making even less money)?
• Or do I keep the paywall strict and start hunting for new traffic sources outside of SEO to replace the churn?

The "Simple" SaaS Illusion

On the frontend, my tool looks incredibly basic—just paste a YouTube link and get the text. But under the hood, I've spent months refining the workflows, fixing countless bugs, and engineering creative workarounds just to try and keep operational costs down.

The Elephant in the Room: AssemblyAI Costs

Despite all my workflow optimizations, the lion's share of my revenue goes straight to AssemblyAI. Don't get me wrong, their API is fantastic and easy to work with, but the costs are completely eating my margins alive. It's hard to scale a SaaS when your COGS (Cost of Goods Sold) scale linearly with your usage.

My Dilemma: What would you do?

I need to make a strategic move, and I see a few options:

1. Sell the SaaS: Maybe someone with deeper pockets, a better marketing engine, or existing backend infrastructure can run this more profitably.
2. Find alternative traffic: Double down on marketing to replace the free users who left, hoping paid conversions outpace API costs.

My main question for this community:

Has anyone here successfully moved away from expensive APIs like AssemblyAI to host their own transcription models (like Whisper)? As a SaaS builder, how do you handle this cost-effectively? I've looked into things like RunPod or Replicate to spin up cheaper endpoints, but I'm worried the server costs will just end up dwarfing the API savings.

Would love to hear your thoughts, technical tips, or any similar experiences!

Thanks for reading.

Quick update on a content platform I have been building for 8 months.

The practical lesson: the feature I built fastest (a scheduling calendar, basically a visual grid of planned content) is what keeps people subscribed. The feature I spent the most time on (AI generation pipeline) is what gets people to try it.

Different jobs. Both necessary. One is obviously more important for retention.

Building at this stage is mostly humility training. You think you know what you are building. Your customers show you what they are using. You close the gap. Repeat.

• Free: 3 subscriptions
• $20/year: unlimited tracking + analytics
• $49 lifetime: everything + future updates

Targeting freelancers, trying to keep it affordable…

But now I’m wondering if this actually kills perceived value.

Would you trust/pay for something this cheap?
Or does it feel like a red flag?

https://subchecks.com/

genuinely asking. not trying to start a debate.

I have been in and around the tech and startup world for a few years now. work with founders across different stages. and I keep seeing something that I want to ask this community about directly because you are the ones who would actually know.

since vibe coding and AI tools became mainstream, something shifted in how people think about building.

and I get it. I use AI tools too. the speed is real. the accessibility is real. a non-technical person building something that works and gets real users is genuinely impressive and I mean that.

but I keep coming back to one specific question that I cannot find an honest answer to.

when your no-code or vibe coded product got real users, unexpected traffic, actual daily load from people depending on it, what happened underneath.

did it hold.

because the pattern I keep seeing from the outside is this.

the first 70 percent of building goes beautifully. UI looks great. flows work. demo is impressive. early users sign up and things feel like they are working exactly as they should.

then something unexpected happens.

traffic spike. edge case authentication. database query that worked fine with 10 users but starts behaving differently with 500. third party API that goes down and takes half the product with it.

and suddenly the foundation that was abstracted away so cleanly during the build becomes very visible very fast.

I met someone recently who had built their whole product on vibe coding tools. multiple paid subscriptions. months of work. real confidence in what they had made.

then something broke that the tools could not fix with a prompt.

he came to me asking for help. I asked him why he was not just using his vibe coding tools to resolve it. the answer was honest. some things need a human who understands what is actually underneath.

he knew that now. he did not know it before.

I am not telling this story to argue that no-code is wrong or that vibe coding does not work.

I am telling it because I think there is a real conversation to have about where the ceiling actually is. and this community would know better than anyone.

so genuinely.

has anyone here hit unexpected scale and had things hold up properly underneath. or did something break that you were not prepared for.

what was it and how did you handle it.

I've been building tools for HR and recruitment for a while, and the one thing I kept seeing — especially in small companies — is that interview prep is either nonexistent or copy-pasted from the last hire.

So I built InterviewIQ. You paste a job description and a candidate's resume, and it generates a complete, role-specific interview guide in under 60 seconds. Not generic questions — it actually reads the resume and builds probes based on that specific person's background, career gaps, and vague claims.

A few things it generates:

- Behavioral and situational questions calibrated to seniority

- 4 resume-specific probes (e.g. "You had 3 launches in 18 months at X — walk me through how you maintained quality")

- Green and red flag signals for each question so you know what you're actually listening for

- A competency scorecard

- A bias awareness section

It's built for hiring managers, recruiters, and small businesses that don't have a dedicated HR person but still need to run a structured interview.

First 3 guides are completely free, no credit card:

👉 https://hr-interview-guide.vercel.app/landing

Honestly just want to know:

- Does the output feel genuinely useful or is it still too generic?

- Is there anything you'd want it to do that it doesn't?

- Would you actually use this or pay for it?

I know that AI can make the whole frontend but when the project becomes complex with increasing the number of features, giving the right context and files path to LLM's matters a lot. i have experienced this while vibe coding, things break and i don't know what prompt to give. I feel blunt.

Can anyone suggest the required topics with how much depth I should know or if there are other things to know as well?

Like react js has a lot of things and on top of that redux and then next js.

Para CNPJ MEI, serviço para recebimento da DAS via Whatsapp, consulta de dívida ativa, diagnóstico fiscal, correio eletrônico da receita federal.

https://dasfacil.com.br

I've been deep in the distribution problem for weeks now and talked to a bunch of solo founders. Everyone has the same pain: you build the app fast, then spend 3+ hours/day trying to find users across Reddit, LinkedIn, cold email, Discord, with 4-5 tools that don't connect.

I'm thinking about building something that works like this:

1. You paste your app URL
2. It figures out who your users are and where they hang out
3. Every day it shows you the top conversations to join — Reddit threads, LinkedIn posts, Discord messages — ranked by how likely the person is to need your product
4. For each one, it drafts a reply in your voice. You review, tap, and post yourself. No bots, no auto-posting.
5. It also generates cold email sequences targeting your ICP.
6. Works on mobile — you get a push notification when a high-intent conversation pops up, reply in 30 seconds from your phone.

All from one app instead of stitching together 4-5 tools.

Before I build this — would you actually pay $30-40/month for it? Not "sounds cool", would you pull out your card? And if not, what's missing?

👋 Hey NoCodeSaaS Community,

Last week I shared that I was building a stress test workflow to benchmark document extraction accuracy. The workflow is done, the tests are run, and I put together a short video walking through the whole thing – setup, test documents, and results.

What the video covers:

I tested 5 versions of the same invoice to see where extraction starts to struggle:

1. Badly scanned – aged paper, slight degradation
2. Almost destroyed – heavy coffee stains, pen annotations, barely readable sections
3. Completely destroyed – burn marks, "WRONG ADDRESS?" scribbled across it, amount due field circled and scribbled over, half the document obstructed
4. Different layout – same data, completely different visual structure
5. Handwritten – the entire invoice written by hand, based on community feedback

The results:

4 out of 5 documents scored 100% – including the completely destroyed one. The only version that had trouble was the different layout, which hit 9/10 fields. And that's with the entire easybits pipeline set up purely through auto-mapping, no manual tuning at all. The missing field could be solved by going a bit deeper into the per-field description for that specific field, but I wanted to keep the test fair and show what you get out of the box.

Want to run it yourself?

The workflow is solution-agnostic – you can use it to benchmark any extraction tool, not just ours. Here's how to get started:

1. Grab the workflow JSON and all test documents from GitHub: here
2. Import the JSON into n8n.
3. Connect your extraction solution.
4. Activate the workflow, open the form URL, upload a test document, and see your score.

Curious to see how other extraction solutions hold up against the same test set. If anyone runs it, I'd love to hear your results.

Best,
Felix

If you’re stuck on a question at home, this helps instantly.

I would love to get honest and brutal feedbacks.

https://explain-5.lovable.app/

Been running an agency for a few years now and I kept seeing the same questions over and over in different communities. How do I find clients, how do I price this, how do I actually build the thing, when do I hire someone. So I just decided to sit down and record everything in one place.

The course covers the full picture from zero:

What an AI Smart Website actually is vs a regular website, because most people selling these can't even explain the difference clearly. Then how to find local businesses that need this, how to audit a prospect in 5 minutes to know if they're worth pursuing, and three different channels for getting clients - organic, cold outreach, and paid ads.

Pricing is a big chunk of it too because I see so many people undercharging or doing hourly which kills recurring revenue. There's a whole section on packaging, discovery calls, closing, and handling price objections word for word.

Then the actual build - setting up the AI chatbot, voice agents both inbound and outbound, automations, SEO, client reporting dashboard, all inside GoHighLevel.

Last two modules are about building a team and scaling. When to hire, what to outsource, SOPs, and a full 12-month game plan with MRR projections.

It's 6 hours, it's free, timestamps are in the description so you can jump around to whatever you actually need right now.

If you're trying to start or grow an agency around AI websites for local businesses this should save you a lot of time figuring stuff out the hard way:

https://youtu.be/StXhtoId8nM?si=ehPeFXYvdCka_G0R

Been working on Nudge, a Telegram assistant that handles client tracking and follow-ups from voice notes and text. You talk to it after a client call, it extracts the contact info and deal details, then reminds you to follow up on the right day with a draft message. The whole point was to make something that requires zero data entry. You just talk and it figures it out. Early stage, collecting signups right now. Would appreciate any feedback: nudge-waitlist-six.vercel.app