Build versus buy for internal admin panels
A decision lens we use in tooling strategy assessments when teams argue about custom admin screens.
Custom admin panels feel inevitable once a spreadsheet collapses. They are also where internal tooling budgets disappear. During assessments we push teams through a short lens before endorsing a build.
Prefer buy when
- The domain is generic (user roles, simple CRUD, standard approvals)
- Compliance features (audit logs, SSO) matter more than unique workflows
- Nobody on staff wants long-term UI ownership
Prefer build when
- The workflow encodes proprietary judgment that vendors flatten poorly
- Integration cost to existing systems dwarfs the panel itself
- You already have a maintainer pair with capacity — not aspirational capacity
Prefer neither (yet) when
Ownership is unclear or the process still changes weekly. In those cases workflow automation planning or even temporary manual checklists beat a half-finished panel.
Site Brook Hub will recommend retiring a panel as often as expanding one. Strategy is allowed to say no.