Why I stopped building admin panels from scratch.

Most of what I ship has two halves: the thing customers use, and the thing the business owner uses to run it. The second half — the admin — is where most of the real work lives. Orders, payments, payouts, moderation, reporting. It's also the part that looks the same across wildly different products.

By my third or fourth panel I noticed I was rebuilding the same primitives every time: a data table with server-side paging, a moderation queue, a KPI row, a chart, a role-gated sidebar. So I stopped. I built one solid template — opinionated, themeable, with the boring parts already solved — and now every new project starts from it.

The payoff isn't just speed, though a panel that used to take three weeks now takes one. It's consistency. When every dashboard shares the same skeleton, fixing a bug or adding a capability happens once, everywhere. The client gets something that feels considered on day one instead of assembled under deadline.

The lesson generalises: abstract on the second or third real use, never the first. The first time you solve a problem you don't yet know its shape. By the third, you do — and that's when a template earns its keep.