Nothing leaked when we attacked it
We used an anonymous key from outside to read the tables behind every live design — 653 tables. Nothing came back that should have been private.
Internal tools
The tool five people need and nobody has time to build
Internal work never wins the sprint, so it stays in a spreadsheet and a group chat. Describe what the team does, get a screen with logins and roles, and stop asking for a slot.
Out of the box6 roles
- roles you can assign
- tables probed from outside
- that leaked
- checks before publishing
- designs to start from
- credits to start from one
Permissions are decided on the server. Anything a role cannot do is refused, not just hidden.
The situation
It never wins the sprint, so it never gets built.
Everyone agrees the leave requests should not live in a chat thread. It still loses to customer-facing work, every quarter, correctly. So the team keeps a spreadsheet, someone maintains it in their own time, and it breaks when they are away. The cost of building this properly used to be a sprint. Now it is an evening, which changes the answer.
How it goes
Describe the process, set the roles, hand it over.
The boring parts — logins, permissions, an audit of who did what — come with it.
- Describe the process
"Staff file an expense, a manager approves it, finance exports the month." The tables and screens follow from that sentence.
- Decide who can do what
Up to six roles. Filing, approving, and reading can be three different people, and the server enforces it.
- Give the team the link
They sign in with an email and password. Nine checks run before it goes out, and a serious finding blocks the publish.
Start from one of these
Three that show up in every company.
Each one has a live demo. Starting from one costs no credits.
- Inventory & Purchase Orders (Internal Tool)
What is in stock, what is on order, what needs reordering — without a shared sheet.
- Time Off & Attendance (Internal Tool)
Requests, approvals, and the remaining balance in one screen instead of a chat thread.
- Expense Reports
File with a receipt, approve in one place, export the month when it closes.
All 336 have a running demo. Open one before you copy it.
Straight answers
What we measured, and what we did not.
Internal tools hold staff data. That deserves a straight answer, not a badge.
Publishing is blocked, not warned
Nine checks run before a publish. A serious finding stops it, and dismissing the finding does not unblock it — only a clean re-scan does.
Company sign-in is not connected
User provisioning from a company directory is written and tested against the spec, but has never been connected to a real identity provider.
Approval chains stay simple
One approver, one step is what these handle well. A five-stage chain with conditional routing is more than we would claim here.
Start
Build the one everyone complains about.
Pick the process that generates the most messages and replace that first.