The Part Built Last And Used Most
An admin system is the set of screens your own staff use to run a product or service: look a customer up, fix an order, issue a refund, change who can see what. We design and build them as part of our custom software development work, either for a product we are building or as a replacement for the one your team puts up with now.
Every customer-facing product has a back office behind it, and it is consistently the part that gets least attention. The customer experience is designed carefully; the screens your team spends all day in get whatever time is left.
That trade is understandable and it is usually wrong. Your team uses the admin system more hours per week than any customer uses the product, and every friction in it is paid daily, forever.
Admin System, Admin Portal Or Admin Panel?
People search for all three, and builders use the words loosely, so it helps to know what you are asking for.
An admin panel usually means the screens bolted inside one product: the settings area of an app, or the dashboard that came with a WordPress or Shopify site. It manages that product and nothing else.
An admin system (sometimes called an admin management system) is the wider back office. It may sit behind a customer-facing product, or it may be how the business itself runs, pulling orders, customers, payments and staff tasks into one place instead of five tools and a spreadsheet.
An admin portal is an admin system reached through a browser by people who are not in your office: franchise owners, regional managers, partner firms, a client’s own administrator managing their staff’s accounts. The extra work is in the edges. Each organisation sees only its own records, and someone has to decide who can invite whom.
If the screens are for your customers rather than the people who serve them, that is a client portal, a different brief with different failure points.
What Belongs In One
Finding things fast. Search that works on partial matches, wrong spellings and the identifiers customers quote down the phone. Sounds minor; it is the single most-used feature.
Seeing the whole picture on one screen. Whatever the person answering a query needs, without opening four tabs.
Doing the awkward thing safely. Refunds, corrections, manual overrides, resending something. These exist in every business and if the system forbids them, they happen in the database instead, which is worse.
A record of who did what. Especially for the awkward things above.
Impersonation, carefully. Seeing what a customer sees resolves support conversations quickly, and it needs to be logged and limited.
What One Looks Like In Practice
Take a subscription business with six people on support. A customer rings to say they were charged twice. In a poor back office, the agent checks the payment provider in one tab, finds the account in another, asks a developer to confirm which charge is the duplicate, and emails finance to refund it. Twenty minutes, three people.
In a good one, the agent searches the customer’s email address (or the last four digits of the card), sees both charges against the account on one screen, and refunds one. The refund is under the limit their role allows, so it goes through straight away and is written to the audit log with their name and the reason. Above that limit, it waits for a manager’s approval. Nobody touches the database and nobody else is interrupted.
None of that is hard to build. What it needs is someone who has listened to that phone call before drawing the screens.
The Access Question
Admin does not mean unrestricted, and this is where these systems most often go wrong.
The people answering queries need customer records but rarely need pay data, margins or the ability to delete anything. Blanket admin access is convenient on day one and becomes the reason you cannot safely give a new starter the tools to do their job.
Deciding the roles before building is cheap. Retrofitting them into a system where everything assumed full access is one of the more painful changes to make later.
What Moves The Price
Number of roles, and how differently each sees the same record.
Whether actions need approval. Some should. Refunds above a threshold, permission changes, anything irreversible.
Search sophistication. Exact-match lookup is trivial; forgiving search across several fields is a feature.
Bulk operations. Acting on one record is simple. Acting on four hundred safely, with a preview and a way back, is a build.
Audit depth. What the audit trail records, for how long, and whether an administrator can edit it.
Organisations as well as users, for an admin portal, because separating one partner’s records from another’s touches every screen.
Where These Go Wrong
Designed by developers for developers. Screens that mirror the database rather than the job, so every task takes six clicks and two tabs.
No bulk actions. So somebody does the same thing two hundred times, or a developer gets pulled off other work to run a query by hand.
Everything editable by everyone. Convenient until it is not.
No audit trail on the manual overrides. The one place it matters most.
Questions To Ask Whoever Builds It
- Have you watched somebody use the current system?
- What are the five things done most often, and how many clicks each?
- What can a support user do, and what can they not?
- Is impersonation available, and is it logged?
- What happens when somebody needs to correct a mistake? There should be a supported route.
A Brief You Can Send Anyone
Who uses it: [roles and numbers]
The five most common tasks: [in order of frequency]
What they open now to do those: [systems and tabs]
What each role must not see or do:
The awkward operations: [refunds, corrections, overrides]
What must be recorded: [and for how long]
Volume: [records, and how many per day are touched]
How We Build Them
Around the tasks rather than the tables, with the five most common operations reachable in as few steps as possible, roles decided before anything is built, and an audit trail on everything consequential.
Where the requirement is a set of tools for internal work rather than the back office of a product, internal tools development is the closer fit. The other things we build are on the services page.
Get in touch and tell us what your team does most often.