Internal Operations Tooling
A CRUD back office with real search, enforced permissions, bulk actions and exports — designed around the task an operator does forty times a day.
Overview
The team was running the business out of a spreadsheet and a database client. Support was blocked waiting on engineering for data.
I built a keyboard-first back office on top of the existing schema: search that finds things, filtering and bulk actions, permissions enforced on the server and reflected in the UI, and CSV and PDF exports that match what people paste into spreadsheets anyway.
A shared layout system means new admin screens take hours, and destructive actions have confirmations and, where feasible, an undo.
Outcomes
- Operators self-serve data that used to be an engineering ticket
- Permissions enforced server-side; the UI never shows a 403 surprise
- Bulk actions and exports built around the real daily workflow
- New internal screens ship in hours on the shared layout
Tell me about your product
Share a short brief — problem, timeline, and stack — and I'll reply with a candid view on fit, effort, and the fastest path to a shippable milestone.