Does your small business need a custom admin panel?

The website is finished and it looks great. Then the first price change comes along, and you realise you have to email your developer, wait, and hope it's done before the weekend. Then your opening hours change. Then a new treatment, a new product, a holiday.

An admin panel is the answer to that: a private part of your website where you and your team change things yourselves. But not every business needs a custom one, and a bad one can be worse than none. Here's how to tell, and what a good one looks like.

Signs you need one

You'll probably benefit from your own admin panel if:

• Things change every week, not every year. Prices, availability, stock, opening hours, menus.
• Several people need to make changes, and they shouldn't all see everything.
• You keep the real information somewhere else, in a spreadsheet, a paper diary or a notes app, and copy it to the website by hand.
• Small edits mean contacting your developer, and you've started putting them off.
• Your work has its own logic. Appointments that can't overlap, products with options, orders that move through steps. General tools struggle with that.

Signs you don't

Be honest with yourself here, because a custom panel is real work to build and to look after.

• If your site is mostly pages that change a few times a year, a content management system like WordPress, or the editor built into your website platform, is all you need.
• If you sell online, Shopify's own admin already handles products, orders and customers very well. Build on it rather than around it.
• If the job is already done well by an app your team likes, connecting your website to it is usually smarter than replacing it.

What a good admin panel does: a real example

For Markiza, a beauty studio with three specialists, we built the website's online booking and, behind it, a private admin panel for the team. Each piece of it exists because of something the specialists do every day.

Everyone sees their own day. Each specialist signs in with their own passcode and lands on their diary for today. They don't see each other's clients, and they don't have to scroll past them either.

The day is drawn to scale. On the day view, an appointment's height is how long it takes. A 20-minute treatment is a short block, a two-hour one is a tall one, and gaps look like gaps. You understand the day at a glance instead of reading a list.

Changes take a moment. Someone calls to move their appointment: drag it to the new time. A booking comes in by phone: tap the free gap and add it. The website updates straight away, so the slot disappears for everyone else.

Prices and treatments belong to the people who do them. Specialists add treatments, change prices and set how long each one takes, without calling us. Bookings already made keep the price they were made at, so nobody's history changes behind their back.

Holidays close themselves. Working hours, days off and vacations live in the panel. Block out a week, and the website stops offering those days.

It works on a phone. Most of this happens between clients, standing up, phone in hand. So the screens are designed for a phone first, and they also work at a desk.

Built around tasks, not tables

The easiest admin panel to build is one screen per database table: a list of bookings, a list of services, a list of staff, each with an edit button. It's also the hardest one to use, because nobody's job is "edit the bookings table".

A good panel starts from the jobs people actually do. "See my day." "Move this appointment." "Change a price." "Take next week off." Each of those should be one obvious screen, a couple of taps from the start. When we plan a panel, the first thing we ask for is a list of what your team does on a normal week, and the screens follow from that.

Safe by default

An admin panel holds the details a public website never should: client names, phone numbers, what people bought or booked. So:

• nothing in the panel is visible without signing in
• every change is checked on the server before it's saved, not just in the browser
• the database can't be reached from the public site
• people only see what their role needs

None of that is visible when things go well, which is exactly the point.

Custom panel or off-the-shelf tool?

A general tool is quicker to start with and cheaper upfront. It's the right choice when your needs are standard. A custom panel costs more to build, but it speaks your business's language, does exactly what your team needs and nothing they don't, and changes with you.

A useful test: if your team spends real time every week working around a tool, with copied data, workarounds and "don't touch that setting", you're already paying for a custom panel, just in staff time instead of in a build.

How we'd start

We'd begin with a short conversation about your week: what changes, who changes it, and what's annoying right now. From that we pick the three or four screens that would save the most time, build those first, and get them in your team's hands. The rest follows once we've seen how they're used.

If online booking is part of the picture, read Online booking for a beauty salon: what it takes for the client-facing half of the same system.