The outline from our video on permission levels: how one app gives the owner, the office, the crew, and the customer each their own view, without handing anyone the whole farm. Download it and hand the folder to Claude: it asks who logs in to your app and what each of them should see, writes that down on one page with you, and builds it once you say yes. Made in Lake Charles, Louisiana.
Every page, field, and button is a door. Each person who logs in carries a ring of keys. We plan every portal around four rooms.
The owner and the office get everything. The crew logs their work and reads the internal notes. The customer sees progress and a PDF. One or two people on the customer's side get a deeper look. Nobody signs themselves up: the office creates every login.
“Can see the daily log” and “can see internal notes” are two different ticks. Read and write are different ticks. New ticks start off until the office turns them on, and the office can preview the app as any login.
Who is this? What keys do they have? Then it asks the database for only that slice and sends nothing else. The database holds the same rules underneath, so a page built wrong someday still can't hand over a row it shouldn't.
Job progress, a report to download, approve or hold items, and a button to report a problem, so customers aren't calling your phone to ask where things stand.
The tempting shortcut is one page for everybody with the private parts painted over. But if the data reached their phone, there are ways to peel the paint back. So the cut happens before anything leaves.
Unzip it into your app's project, open the folder in Claude Code (the Claude desktop app's Code tab is the easiest way in), and type:
We're two brothers in Lake Charles who build custom software for local businesses. The drawings in the video come from a real job-tracking app we built for an industrial services company. This download fits any business building its own app or portal with AI, from tree services and contractors to inspection firms, where the crew, the office, and the customer each need a different view.
Want to see what we build for paying clients? Look through our work.
Yes. No card and no trial. The files are yours to keep and change.
No. The files are plain English. Your AI asks you who logs in and what they should see, and it writes the code. You answer in your own words.
A computer, a Claude account, and an app to put it in (or a plan for one). Claude Code comes with the paid Claude plans, and the Claude desktop app's Code tab is the easiest way in.
It's how we plan permissions, not a security review. The test list catches the common mistakes, and you should still have someone you trust look at any app that holds customer data before real people log in.
Yes. We're based in Lake Charles and build custom portals like this for local businesses. Book an AI audit and we'll tell you honestly whether it's worth it for you.
Start with an AI audit. We'll look at who needs to see what in your business and tell you honestly whether custom software is worth it for you.
Book your AI audit →