u/Grouchy_Box_4487

Built a small client portal last weekend with one of those AI app builders. The demo was gorgeous. Every card had an icon, every list rendered perfectly, the empty states looked designed on purpose. I screenshotted it and sent it to two friends like "yeah this is basically done."
Then i pointed it at a real-ish Postgres table from an old client system. Not even a huge one, maybe 400 rows. Within ten minutes the whole thing got weird in the most boring ways possible:
- three columns that were supposedly strings were 40% null. Cards just rendered empty boxes. - one nested JSON blob that the builder happily wrote `data.address` against turned out to be a stringified mess. Frontend showed `[object Object]` everywhere. - a status field i assumed was always `active` was actually `active`, `pending`, `archived`, plus an empty string someone typed in 2021. Filter dropdown silently dropped half the rows. - one user had a company name that was 78 characters long. Table cell broke the layout and the modal couldn't close. - loading state: the builder assumed the API always returned in under 100ms. With a few joins it takes 1.2s, page just shows a flash of nothing before content pops in.
None of this is exotic. Its literally the stuff every backend engineer complains about. But the AI was confidently rendering fake data the whole time and i never had a reason to look.
Now i'm rewriting that part manually and its painful. The UI was free, the data layer is the actual work. Permissions especially, once real users land and data access actually matters, the demo phase doesn't cover much.
i started testing builders earlier with real-ish data: imports, nulls, weird strings, ugly status values. Enter Pro is one i'm poking at because the docs put database, functions, source export, and backend-ish pieces near the builder instead of making the backend feel like a seperate mystery box. still not magic. you still have to seed messy rows and watch what breaks.
(database migration workflow is the next thing i need to figure out without the AI breaking prod.)

trying to add team onboarding to a small B2B app i'm building. Stack is Supabase + Next.js (frontend came from an AI builder, backend done by hand). got the demo, got the login, got the basic dashboard.
the second i started on "owner can invite teammates, invitee accepts and lands in the right org with the right role" that's where it cracked.
Friction chain i keep hitting:

1. invite link generation: token, expiry, single-use. Supabase has the table helpers but the actual link semantics, edge function, and email template glue is all on me.
2. email verify vs invite acceptance. the two flows step on each other depending on thier order. half my test users land in a half-onboarded state.
3. org binding via RLS. user_id → org_id mapping is what i have to write and test by hand. wrong org on the wrong row = data leak waiting to happen.
4. permissions after leaving the org. revoke flow + cached JWTs + "user can still see this project because its token isn't expired" is the silent broken bit.
5. audit log (who invited whom, when). nobody builds this for you. need it for any B2B sales convo.
   4-5 days of glue code that has nothing to do with my actual product.
   what does the normal stack for this part look like for solo founders landing in B2B? Clerk? WorkOS? roll your own on supabase RLS? is there a builder that doesn't fall apart at the team-onboarding step?
   i'm also checking whether tools like enter handle any of this closer to the backend layer. haven't fully verified it, just reading docs and trying to figure out what people actually use.