One platform, many builders, zero chaos.
A US services group ran on scattered spreadsheets, and many staff were building their own tools with AI. I designed, built and run the internal platform that replaced the spreadsheets, and made it safe for everyone to build on.
Languages
Tools & platforms
AI & LLM
Skills
The thinking behind it
- 01 · What I noticed
The real problem wasn't missing tools. Everyone was building their own, in their own shape, with their own database access.
- 02 · What I decided
Build one platform where every app has the same shape, and make the rules part of the build so nobody has to remember them.
- 03 · What I delivered
A governed platform with database-level security, now live and safe for many builders.
Old system vs new system
- Find the right spreadsheet
- Ask for access
- Email a request
- Chase for updates
- Fix broken formulas
- Sign in once
- Admin approves the account
- Open your role's apps
- Track requests live
Watch it run
Click through the four steps. In step 3, click any box to see what it does.
The hardest problem was people, not code.
Many staff were building tools with AI, and each wanted theirs inside the portal. Every tool arrived in a different shape: its own layout, its own look, its own database access. Code review alone couldn't keep up, so I made the structure enforce itself. Pick a mistake to see what the build does.
Also enforced: Git hooks block commits straight to main · a changelog and skill files teach the next person and the next AI session the rules.
The database says no, not just the screen.
Switch roles and try opening an app. Hidden buttons are easy to get around; here every table has its own access rules, so even a direct request for the data is refused.
database check
Built and run by one person
developer
architecture to productionsecurity rules
every one of 64 tables protectedproduction releases
each tested on staging firstdatabase changes shipped
versioned, all live in productiondata domains
isolated by role and business entityserver functions
admin, syncs, email, AISource: read-only query on the live database and the repository, Oct 2026.
Why it's built this way
Access checked in the database, not just the screen
Even if someone finds a hidden page, the data itself refuses to load for the wrong role.
One codebase, separate modules
Each business app loads only when opened, but shares login, design and data code.
Staging before production, every time
Changes go to a test site with no real data, get reviewed, then deploy by hand.
What made it work
- 01
Rules beat reminders
When many people (and AIs) build on one system, put the rules in the build. A clear failing check teaches faster than any doc.
- 02
Design for the next builder
Skill files, a changelog and a runbook mean the next person, or the next AI session, learns the rules without asking anyone.
- 03
Ship small, ship often
125 production releases, each through staging first. Small, reviewed changes are how one person keeps a big system calm.
Have a similar mess? Tell me the step you hate.