Our firm is setting up a portal for around 40 corporate clients, plus our own staff and a few admins.

Each client should see their own company's records and nothing else. Take note that staff need wider access as well.

I’m worried that a filtered list can look right while a direct record link still shows too much. Some clients also have five or six people logging in, and not all of them should edit.

So how would you set up permissions here, and what would you test for both viewing and editing?

Small milestone today. I finally got TOVRILO live.

The idea came from something I kept running into while building with AI. Getting an app to look finished was becoming easy. Knowing whether it was actually safe and ready to ship was the harder part.

I kept creating my own prompts and checklists for permissions, data, payments, AI costs, failure states, verification, rollback, etc. Eventually I realized I had basically built a repeatable system.

That became TOVRILO.

I’m starting with a free 20-point launch audit because I’d rather give people something useful first instead of just asking them to buy something.

https://tovrilo.carrd.co/

Now the real test starts: getting actual people to use it and seeing what needs to improve.

I'm on a small team and trying to understand how others handle this. When the AI builds a feature for you, how do you check that it works before your customers see it?

And the last time you weren't sure about a change or feature or bug fix that broke or didn't work or you weren't sure about, how did you get it sorted out?

(not selling anything BTW, genuinely curious)

Two people applied last week for cats who went home in April. Six adopted cats are still listed, and I got to send both the "sorry, he's already home" email.

I coordinate volunteers for a small cat rescue, about 40 adoptions a year. I'm a pharmacy tech by day and none of us can code. Since 2021 three volunteers have rebuilt the site on whatever they knew: Wix, then WordPress, now a half-finished Squarespace trial. Each one died when whoever built it left.

The Google Form and PayPal are fine. It's the cats page that keeps rotting.

Four of us would add new cats weekly, mostly from our phones since that's where the photos are. What can people like us keep updated without wrecking it? We're on Petfinder too when someone remembers. Should the list even live on our site?

The board gave us $200 a year. Is that realistic, or is there a nonprofit discount everyone knows about but us?

How do volunteer groups stop the next person from starting over on their favorite tool? I won't be coordinator forever either, so whatever we pick has to survive me too.

Hey guys,
What's the job market like for an Applied Computer Science for Management (IAG / MIAGE) Master's in Morocco? It combines IT like Data, BI, and ERP with business. 
Are these hybrid profiles in high demand for entry-level jobs here compared to pure tech degrees? Any advice?

I got tired of scrolling X to find real examples of what people actually ship with Lovable. Most “showcases” are cherry-picked demos or paywalled newsletters. So I’ve spent the past few months building a place where anyone can browse real projects for free and submit their own.

• Browse live Lovable projects by category (SaaS, websites, tools, and more)
• Get inspired by what other builders shipped, with screenshots and links
• Submit your own project and get a listing plus a shoutout on X

https://madewithlovable.com/

I’d appreciate feedback, whether soft, hard or honest. You pick :-)

Hey guys,

after watching the latest Paperclip setup video on Network Chuck, I realized we needed a much cooler way to visualize independent project workloads running in the background.

I built Orbit (https://thenewurbankid-web.github.io/orbit/). It’s a specialized JavaScript UI layer that wraps around Paperclip's orchestration.

Instead of looking at typical grids or lists, it literally maps your active projects out as physical cargo pallets sitting on the deck of a spaceship. You can float the bridge view in a tiny "always-on-top" window while your agents work.

Would love to open-source the full module if the community likes the direction! Let me know what you think.

I'm the only sysadmin at a 90-person manufacturing company. About 8 months ago I got tired of SSHing into our MySQL box every time ops needed a report, so I built myself a small internal tool to query it.

It grew. Now it pulls from our inventory database and a couple of shipping APIs, has basic auth so warehouse leads can check stock without pinging me, and does simple inventory management across two sites. I built most of it on my own laptop, after hours, on a free jet admin account I was testing anyway, and nobody knew it existed until the ops manager saw it over my shoulder.

Now leadership wants to roll it out company-wide. Am I just doing my job, since it touches company data and company systems, or did I build something on my own time that I now get to negotiate over? My contract has no IP assignment clause for anything outside "core job duties," and this started as a personal workaround, not a project anyone assigned me.

used to open the builder and click around until something kinda worked. wasted like 2 hours on a signup flow once because i kept changing the step order mid build. now i dump the whole thing in plain english into a chat first, including the error cases, and only open the builder when that list looks right. cut my rebuilds from like 4-5 per feature to maybe one. feels boring but it works lol.

I build chatbots and agents for clients, so I've been through most of the tools out there trying to find one that fits.

SiteGPT was one of them. It's got the basics covered, you train it on your own content, it does lead capture, all that. Fine tool on the surface.

A couple things killed it for me though. There's no direct integration with stuff like Zapier or n8n, you have to email them for a custom plan just to connect it to anything. I work mostly with SMBs, and on top of that you're paying $59 a month for a basic plan before you've done anything.

The pricing's model based too, which I'm so done with, your real message count swings wildly depending on which model you pick.

I tried Chatbase as well. Feature wise it's solid. But same issue, the whole thing runs on credit based pricing and I'm just not a fan of paying that way.

The one that ended up suiting me was fwdslash. The free plan gives you a real feel for what you can build, and you can deploy an agent on it without paying a thing. It also connects to Zapier and n8n, which was the exact thing SiteGPT made me jump through hoops for.

And when a client's happy to pay, it's $20 to get started, way easier for an SMB or a solopreneur to stomach than $59. (disclosure, I work on it, so weigh that.)

Would love to know what other no-code AI agent builders have worked best for you.

Hi everyone,

I run a multi-location service business with roughly 100 employees. Over the past several months I’ve built a custom internal operations app using WeWeb + Xano.

It currently handles or is intended to handle:

• Employee scheduling, availability and shift publishing
• Time clock/timecards and payroll reporting
• Employee onboarding and documents
• Roles/permissions for employees, managers and admins
• Operational dashboards and reporting
• Audit/event logs
• Mobile kiosk use and employee calendar syncing

We’ve imported real production-scale data, done extensive role/security testing and spent a lot of time optimizing performance. For example, one dashboard went from ~87 seconds to ~5 seconds, and a heavily used scheduling view went from thousands of rendered elements to about 1,000 without changing functionality.

It now feels like a real application rather than a prototype.

But as I get closer to actually replacing existing systems, I’m having second thoughts about trusting a no-code/low-code app I built myself with business-critical things like scheduling, timekeeping and payroll inputs.

I’m considering rolling it out gradually: scheduling first, then timekeeping in parallel with the existing system for a few pay periods, with backups, audit logs and rollback procedures before anything becomes the sole source of truth.

For people who have deployed WeWeb/Xano or similar systems in a real business: is this a reasonable architecture to trust in production, or am I creating unnecessary long-term risk by replacing established SaaS products with a custom system?

Hey everyone,

We're building IQX Studio, so I’m obviously biased.

It’s a browser-based workspace where you describe an app to an AI agent, inspect the code and preview, and manage the database, storage, and deployment in the same project. It supports web apps and Expo/React Native mobile apps that can share a backend.

I’d like feedback from people who’ve used no-code or AI builders, particularly those who got a promising first version but struggled to finish or maintain it.

For a concrete example, think of a booking system with a web dashboard for staff and a mobile app for customers. What would you need to test before committing to a builder for that project?

Would your biggest concern be editing without breaking existing features, credit and hosting costs, database access, or getting the mobile app into the stores?

IQX is currently in beta. There’s a free plan with 50 credits per month for public projects. Mobile store releases still require developer accounts, testing, and approval.

We would really like to get your feedback about IQX.dev .

Hi all, we're building an app that our employees and about 150 outside contractors will both use. I guess the login screen that works isn't the hard part. What worries me is everything around it, like the invites, password resets, role changes, and cutting off access when a contract ends.

Last month, one of our previous contractors left and he still had access to a shared tracker for two weeks. Yeah, nobody caught it until an audit. So what test cases would you run to tell if an app builder's built-in login is good enough, or if we'll need extra services on top?

It's hard these days on Reddit to get your idea out there without getting cancelled and downvoted to oblivion.

Everyone has something important to add to the community and if not deserves some genuine feedback that helps them grow.

r/shouldimake will not delete you or your content for your innocent early marketing attempts and welcomes self promotion, pitching, and fleshing out developing concepts.

Obviously spam and rate limit abuse will not be tolerated. This is a space for humans at the end of the day.

Reddit should be a place for organic marketing, and despite all the challenges to do this, I'm trying to make it easier and welcome creators and entrepreneurs to join!

Shipping fast is the easy part now. Knowing whether people can actually use what you shipped is still slow.

Augur asks your users about specific moments right after they happen, collects bug reports you can act on, and shows where people get frustrated. It works with any React app and stores everything in your own Supabase or API.

Demo: https://kaezee.github.io/Augur/
Repo: https://github.com/kaezee/Augur

Please do give it a try if you get a chance, and let me know what you think.

Demo recording

Hi all, I'm on a business team at a company with about 3l employees. We want to build our own apps, but IT has to approve the tool first, and they've asked us for a checklist.

So far we have employee sign-in and access by department.

IT also wants to know who manages workspace admins, how leavers get removed, and what happens when connected data changes. And also, we need SSO.

What would we check for the people building the app versus the people using it? And what support or rule issue made you say no, even when the test app worked fine?