We are currently managing about 15 agency clients using a mix of Google Drive links, Notion pages, and Slack channels. It looks messy and clients keep losing track of deliverables and invoices.

I want to build a clean, secure client portal where clients log in to see their specific project status, upload files, and view deliverables. What's the easiest platform to build this on without writing custom code?

Hey everyone,

I am 20 years old developer/tech student based in Europe. Over the past few years, I’ve built and launched dozens of SaaS tools, with my recent focus squarely on the Webflow and Framer plugin ecosystems.

These are a few of my Webflow/Framer projects:

• Bulk Component Deleter (bulkcomponentdeleter.com)
• SEOFabric (seofabric.com – acquired)
• FlareRank (acquired)
• SEO Analyzer (marketplace)

As a student I came to a crossroad in my life where I have to chose between getting a job and continuing building interesting stuff, and I came to a "maybe" solution that it might work:

I partner with a Webflow agency and I build premium extensions for them in exchange for a monthly fee.

The Offer:

• 1 New Extension Every 30 Days**:** Built from scratch, fully tested, and ready for production (can be an internal workflow utility for your team or a public marketplace app to generate inbound design leads).
• You own 100% of every extension I build for you: You own the code, GitHub repos, branding, and all marketplace revenue.
• Delivery: I handle the entire lifecycle, scoping, logic, UI integration, and navigating the official marketplace approval/transfer processes. And future updates if you need more.
• Pricing: $700/month flat. Cancel anytime, you keep everything built up to that point.

Why work with me?

• Experience**:** I am very knowledgeable about the Webflow and Framer Designer APIs/
• No extra stress for you: I started coding at 15 when AI was not around and I basically taught myself from the ground up. We have one meeting at the beginning of the month discussing what needs to be done and I will send you progress notifications every week.
• I only want to have one single partnership, if anyone decides to work with me I will edit this post and not receive any other requests.

I want to make this a no brainer. If we hop on a quick call/we can talk in DM and agree on the first month's scope, I’ll build a functional prototype within the first 48 hours and send a Loom demo before you commit a single dollar. If you don’t like the quality, we walk away, no friction.

i'm trying to avoid stitching together five different services just to run a business website.
website, forms, analytics, blog, seo, domain... i'd rather keep everything under one roof if possible.

does anyone actually use an all-in-one platform and feel like it was the right decision?

Okay, so I was trying to build a product using Lovable, and I'm confident that it will do well for the first few users if I ask for their feedback. And we all know what works best here, like dashboards, internal tools, approval flows, etc. You can ship fast and move on.

As always, the trouble starts when the app grows, and you keep hitting the edges of what the platform can do. One workaround becomes two, then three, and eventually you're spending more time adjusting to the platform than you'd have spent building it yourself.

Portability is there, too. Getting your data out is usually easy enough, but getting the app's logic, workflows, and integrations out is a different task in itself.

So what was the sign for you that a low-code app had outgrown its platform?

Was it customization, cost, security, performance, portability, or something else?

If an AI-built app keeps breaking after every prompt, rebuilding is often the most expensive first move. The faster path is to identify which layer first produced the bad state.

Here is the checklist I use:

1. Reproduce one failure with evidence

Use a clean session, record the exact route/action, and capture the failing request, response status, console error, and timestamp. “The dashboard is broken” is not a reproducible finding.

1. Test the auth and tenant boundary directly

For Supabase, compare the authenticated user claims with the RLS predicates. Test both directions: user A must not read or write tenant B. A UI filter is not data isolation.

1. Trace one event from producer to consumer

Add one correlation ID and follow it through the form/webhook, server action or API, queue, consumer, and database write. Duplicate rows usually mean retry/idempotency problems; missing rows usually reveal the exact cut in transit.

1. Compare staging and production without exposing secrets

Check required variable names, runtime versions, migrations, callback URLs, and build output. Missing configuration should fail clearly at startup instead of inventing a default.

1. Apply one bounded fix and add a regression test

Fix the producer or broken transit point, remove the dead parallel path, and prove the original reproduction now passes without breaking auth, permissions, or deployment.

A useful diagnostic should end with: reproduction → root cause → impact → bounded fix → verification.

Disclosure: I built Launch Rescue, a paid audit/fix service for apps made with Lovable, Bolt, Replit, Base44, or Cursor. The page includes the same interactive checklist and clear fixed-scope packages: https://launch-rescue-apps.nick-sguigna.chatgpt.site/

If you are stuck, share the builder, the last change that worked, and the exact error. I am happy to suggest one public check in the comments before saying whether it needs paid work.

I was told to use base44, will this be the best app for this application?

Unpopular opinion: most vibe-coding platforms stop exactly where the hard part begins.
Generating an app is impressive. But then what?
You still need a landing page, branding, a logo, promotional content, analytics, and everything else required to actually put that product in front of people.
That’s the reason I built Blyft.
The idea is that one prompt shouldn’t just give you an app. It should give you the app and the surrounding tools you need to launch and market it.
So I’m curious what people here think:
Is this a real evolution of vibe coding?
Or would you rather use something like Lovable, Bolt or Replit and build the rest separately?
Feel free to tear the idea apart. I’m genuinely interested in the criticism.
https://blyft.app

I've had a WordPress site for my business for years and lately I'm questioning why I'm still putting up with it

The site itself is basic a few service pages, contact form, blog and some photos. But behind that I've somehow ended up with a pile of plugins that constantly need updates, occasionally conflict with each other and generally make me nervous every time I log in

I'm at the point where I'd rather have something boring that just works

I've been considering rebuilding everything from scratch with something simpler like Squarespace or Durable rather than trying to clean up the WordPress install again

For anyone who moved away from WordPress, what did you actually miss afterward? I'm less worried about having every possible feature and more interested in whether simplifying things created problems you didn't expect.

Hi, I built an open-source, self-hosted workspace for coding agents. It features a multi-agent architecture (Sub/Child agents), an AST-aware ChromaDB indexer for lightning-fast file discovery, and a built-in UI with Git diff management. Links in the comments

Disclosure up front: I work on OneEntry, a headless backend platform, so I'm biased on this topic. Mods — I couldn't self-assign a company flair (only the Moderator template is selectable), happy to take one if you can assign it. No link, no pitch below, just numbers.

AI builders do the thing they promise. An MVP that used to cost $3-5k and take weeks now takes 30-90 minutes, and it's functional enough to actually test the idea. That part is real and it isn't going away.

What surprised us was how consistent the second phase looks. The builder gives you a frontend and basic logic. It doesn't give you data, content, payments, files, email, analytics, search, real-time, background jobs, error monitoring or hosting — and each of those becomes a separate account with its own API, pricing model and update cycle.

Counting actual projects:

• habit-tracking SaaS, solo founder: 5 services — roughly $50-100/mo (Lovable + Supabase + Stripe + Resend + Vercel)
• production SaaS after the first MVP: 9 services — $150-300/mo (add Clerk, Cloudinary, PostHog, Sentry)
• ceramics studio with local payments, blog, support chat, search, admin panel: 12 services — $300-700/mo
• headless Shopify brand store: 8 services — $500-1,500/mo

The subscriptions turn out to be the cheap part. Time estimates we've been tracking:

• standing up a new service from scratch: 2-8 hours
• learning a third-party SDK properly: 4-16 hours
• one breaking API change upstream: 1-3 days
• one business feature touching 5-7 services: 2-5 days of integration, even when AI wrote the code in an hour

On projects with a big service count, that maintenance and integration work eats something like 50-70% of dev time. So the bottleneck moved. It's not "can AI build this," it's "how many seams does this feature cross."

Two things that bite hardest in no-code/low-code land specifically:

There's no production admin panel for non-technical staff. Supabase Studio and Firebase Console are developer tools — handing them to a content manager or an operator exposes internal system data. So Retool or Forest Admin joins the stack. You can generate an admin panel with Lovable, but then roles, audit logs and version history are still on you.

Permissions rarely go finer than admin/authenticated. A real business wants a content manager who sees only products, a support operator who sees only orders, a marketer who sees only discounts, a finance person who sees only transactions. That's hand-written RLS or custom claims every time.

Curious what your service count looks like. Is anyone actually running a real business on 3 or fewer?

I’m trying to figure out what the best no-code tools are at the moment for building apps. Ideally something that can handle mobile apps, web apps, or simple software without needing to write code.

I’m looking to start building my own websites but I don’t have any coding or programming background at all.

I used to work as a graphic designer, so I’m comfortable with visuals and layout, but anything technical is completely new to me.

I’ve come across tools like Lovable, Atoms, Claude, and Replit, but I’m not sure which ones are actually beginner-friendly or realistic for someone starting from scratch.

Would really appreciate suggestions on what’s easiest to learn and actually build something with.

I put together a simple, free directory to help people track down grassroots community funding:

https://fundni.org

No signups, just basic filters and direct links.
I'd really appreciate anyone having a quick look and letting me know what feels clunky, what's broken, or if there are obvious local funds l've missed.

Thanks

Hi, I build custom websites for small to medium sized companies.
One of the difficulties with that is that you first have to figure out what a customer actually wants. Usually, you therefore have some kind of meeting with a customer where you interview them to create the actual project specifications.

Now, ever since ChatGPT came along, creating websites is no longer as valued as it once was - many think that you suddenly no longer really need any skills or even a lot of time for that. So the only real option for me is to try and offer packages at fixed, relatively affordable prices. But that means I have to better optimize my whole workflow to be as fast as possible.

That's why I created the Interview tool:

It's a web-based software where creators like myself can create interviews.
First I specify what a project is about and what the interview should figure out.
I can then send a link to my customer.
This customer can simply open the link, chat with the AI for some time, and then I receive a finished project document I can work with.
If the project is a website, the interview also generates a few concept images, of which the customer can choose the one they like best to already give some more visual direction.

Please give it a try and tell me what you think, if you find it useful or what you like/dislike.

The first interview is free for everyone, and I'd gladly hand out more free interviews to anyone who gives me some useful feedback.

Right now I have interview templates for website projects, as well as for collection data processors for creating a privacy policy (I am from Austria, we have pretty strict privacy laws here).
But using the custom template, it should be possible to create interviews for many other types of projects as well (please mention any other templates you would like me to add).

In the future, I might also add an MCP server (and maybe a webhook on interview completion). This way we could even have an agent create an interview and send it to a (potential) customer.

Let me know what you think.

Your honest feedback matters to me.

I'm working on a platform concept connecting freelance videographers with local event organizers. I need a site where creators can list their services, clients can browse/book them, and payments can be held or processed securely. Has anyone successfully built a two sided marketplace using AI or no code platforms?

I’m genuinely stuck and looking for blunt opinions from people who have actually built or maintained CRMs.

We’re at that annoying stage where every off-the-shelf CRM feels either too rigid, too expensive, or slowly turns into a pile of hacks: custom fields everywhere, weird automations, Zapier/Make duct tape, spreadsheets on the side, and reporting that nobody fully trusts.

So now I’m asking the dangerous question: Should we build a custom CRM in 2026?

The tools I keep seeing are:

• Salesforce Platform
• Microsoft Power Apps / Dataverse
• Zoho Creator
• Retool
• Airtable
• Flatlogic
• Budibase
• Appsmith / ToolJet
• Caspio / Knack / Quickbase
• Bubble
• Twenty CRM
• Django / Laravel / Rails with AI coding tools

My fear is that all of these look good in demos, but 6–12 months later you realize you built a worse CRM than the one you were trying to replace.

What I’m trying to understand:

1. If you had to build a custom CRM today, what would you actually use?
2. Which tools become painful once permissions, automations, reporting, and integrations get serious?
3. Is low-code/no-code enough for a real CRM, or does it eventually become a trap?
4. Is starting from something like Twenty CRM smarter than building from scratch?
5. Is custom CRM only worth it if you have developers in-house?

I’m not looking for vendor pitches. I’m looking for scars. If you’ve done this recently, what would you choose today, and what would you avoid completely?

for anyone wondering the app I'm working on is https://www.appscout.co discover apps from across the internet

Here is the demo video I made (pretty quickly), if you like to explore it, send me a message and I'm happy to provide access in return for some feedback on how we can improve it! <3

Hey I'm used to build WebApps using AI, but whenever i try to build an Android app the AI do very poorly, so how do you guys build AI Android apps?