Admin screens, made to fit

Custom WordPress Admin Dashboards: Screens Built for the Person Who Opens Them Every Morning

The WordPress dashboard was designed for people who publish posts. Your office manager does not publish posts. She needs yesterday's leads, the orders stuck on hold and a button that sends the bookkeeper a spreadsheet. A custom plugin can put exactly that behind the login, and nothing else.

November 12, 2026 · 9 min read

acmeheatingandair.com/wp-admin · lead inbox
This week's form leads, by status
Nine leads still waiting for a first call
Sample
New, not yet called9 leads
Called, waiting on customer12 leads
Quoted7 leads
Won5 leads
Lost or not a fit3 leads
Illustrative: a sample admin screen for a fictional HVAC company, visible to the office manager role

The short answer

A custom WordPress admin dashboard is a plugin that adds screens, reports and user roles inside wp-admin, so each person sees the work they do instead of every menu WordPress and its plugins add. Each screen checks WordPress user capabilities before it runs. DataCram builds them from $575, depending on complexity, with a fixed written estimate before work starts.

On this page
  1. Thirty-one menu items and the one report nobody can find
  2. Screens we build behind the WordPress login
  3. Capabilities decide who sees which screen
  4. Reports that read the right data, the supported way
  5. When to skip the build and buy something smaller
  6. From a sketch on paper to the first morning of use
  7. What a dashboard costs to build and to keep

Thirty-one menu items and the one report nobody can find

Log in to a typical business site and count the left-hand menu. Posts, Media, Pages, Comments, then one entry for every plugin that wanted to be noticed. A form plugin, an SEO plugin, a slider used on one page in 2021, a backup tool, a cache tool, a cookie banner. Somewhere in the middle is the thing your staff actually came for, three clicks deep, under a name chosen by a vendor in another time zone.

Then come the notices. A yellow bar wants a review. A blue bar announces a sale. A red bar says a license expired, though nobody remembers buying one. WordPress.org's own plugin directory guidelines, read in November 2026, say "Plugins should not hijack the admin dashboard." The rule governs plugins listed in that directory. Plenty of commercial plugins sold elsewhere treat the dashboard as ad space anyway.

None of this is a disaster. It is a tax, paid in minutes, by the people you pay by the hour. A custom admin plugin removes the tax for the jobs that repeat every day: reading leads, checking orders, entering data, pulling a report. It is one of the most practical uses of custom plugin development, because the payoff shows up the first morning someone uses it.

Screens we build behind the WordPress login

Every one of these is a page inside wp-admin, styled to match WordPress so nobody has to learn a second system. Each is written for one business and named in its words, not ours.

A lead inbox

Every form entry in one list, with the source page, the service asked about and a status your team sets: new, called, quoted, won, lost. No more digging through three form plugins' separate entry tables.

An order exceptions report

For WooCommerce stores: the orders that need a human today, such as failed payments, backorders and addresses the shipping rule could not price. Our WooCommerce extensions page covers the store side.

A data entry screen

Price lists, locations, staff bios or service areas entered in a plain form with the fields you need and validation on each one, instead of a page builder where one stray click moves a column.

A one-button export

The spreadsheet your bookkeeper asks for every month, built to their column order, downloadable by the people allowed to download it and nobody else.

A front desk role

A login that can see bookings and leads but cannot install plugins, edit pages or change settings. The menu shows only what that role may use.

A live status board

Numbers pulled from your CRM, field software or email platform through their APIs and shown next to your WordPress data. The API integration plugins page explains those connections, which go live the same day.

WordPress expected this kind of work. Its REST API Handbook, read in November 2026, lists among the API's uses "a plugin to provide an entirely new admin experience for WordPress." We rarely go that far. Most businesses need four good screens, not a new admin.

Glowing cyan and blue bar blocks rising in tidy rows on a deep blue and violet field, crossed by a thin data grid, with one block lit brighter than the rest
A good admin screen shows the few numbers someone acts on today and leaves the rest out.

Capabilities decide who sees which screen

The part of an admin plugin you never see is the part that matters most. WordPress.org's security handbook page on roles and capabilities, read in November 2026, defines them plainly: "User capabilities are the specific permissions that you assign to each user or to a User role." It then gives the instruction we build every screen around: "As you build a plugin, make sure to run your code only when the current user has the necessary capabilities." Its own example checks current_user_can( 'edit_others_posts' ).

In practice that means two checks, not one. Hiding a menu item from the front desk is a courtesy. Refusing to run the export when the front desk types the export address by hand is security. We do both, on every screen and every action. The same handbook warns that "Nonces should never be relied on for authentication, authorization, or access control," so the form tokens that guard against forged requests sit beside the capability check, never in place of it. The plugin security page goes deeper.

A sample role plan for a fictional HVAC company's WordPress site, the first thing we write in a dashboard estimate
PersonWhat their screen showsWhat stays out of reach
OwnerEvery report, every export, settings for the custom screensNothing, though plugin installs stay with whoever maintains the site
Office managerLead inbox, bookings, the monthly exportPlugin installs, theme settings, user management
Front deskToday's leads and bookings, status buttonsExports, prices, anything that changes the public site
BookkeeperOne export screen, read onlyCustomer notes, the editor, every other menu
Marketing contractorPages, posts and the lead source reportCustomer records and order details

The handbook adds a line worth taping to the monitor: "Remember: Even admins are users, and users will enter incorrect data, either on purpose or accidentally." So every field on a custom screen is validated, and every value is escaped when it is shown. A dashboard that trusts the office manager's typing is a dashboard that breaks the first time she pastes from a PDF.

Reports that read the right data, the supported way

A report is only as honest as the query behind it. Stores show the clearest example. WooCommerce's developer docs, read in November 2026, say that from WooCommerce 8.2, released in October 2023, High-Performance Order Storage "is enabled by default for new installations," and that "It's up to the extension developers to add support for HPOS." A report that reads orders the old way can come back empty or wrong on a newer store.

WooCommerce's own guide answers it: "Any code getting posts directly can be converted to a wc_get_order call instead." We write store reports through WooCommerce's order functions and declare compatibility in the plugin, so the report keeps working when the storage setting changes. The same principle holds for form entries, bookings and CRM records. Read data through the owner's supported interface, not through whatever table happened to hold it last year.

  • Name the decision first. Every report answers one question someone acts on, such as which leads nobody has called back.
  • Fix the date range to the job. Today for the front desk, this month for the owner, last month for the bookkeeper.
  • Show the count and the list. A number without the rows behind it invites an argument, not an action.
  • Keep heavy reports off the public site. Admin queries run when staff ask for them, not on every visitor's page load.
  • Write down where each figure comes from. A one-line source note under each report saves a meeting later.

When to skip the build and buy something smaller

Not every crowded dashboard needs custom code. If the only complaint is clutter, an off-the-shelf admin menu plugin can hide items by role for far less than a build. If your reports already live in a CRM your team opens all day, a WordPress copy of them is a second place to be wrong. Our fair comparison of custom and off-the-shelf plugins walks through those calls.

The opposite mistake is common too. A team runs its day out of a shared spreadsheet because the WordPress admin was too cluttered to bother with, and the spreadsheet drifts from the site within a week. If the data is entered on the site anyway, a custom screen usually beats the copy.

From a sketch on paper to the first morning of use

  1. 1

    List the people and their daily jobs

    Who logs in, what they open first, what they export, what they must never touch. This becomes the role plan.

  2. 2

    Sketch each screen

    Rough boxes on paper or a shared page: the columns, the filters, the buttons. Cheap to change now, expensive later.

  3. 3

    Fixed written estimate

    One price for the screens agreed, from $575, depending on complexity, before any code is written.

  4. 4

    Build on a staging copy

    The plugin is written to the WordPress handbook, with a unique prefix, capability checks on every action and escaped output, on a copy of your site.

  5. 5

    Test as each role

    We log in as the front desk, the bookkeeper and the owner and try what each should and should not be able to do.

  6. 6

    Launch and hand over

    The plugin goes live, your team gets a short written guide, and the code and its history are handed over so someone else could maintain it.

What a dashboard costs to build and to keep

Custom admin plugins start at $575 to build, depending on complexity, with a fixed written estimate first, as of November 2026. A single lead inbox with one role sits near the bottom of that range. Several roles, store reports and live API data cost more, and the estimate says exactly how much. Our plugin pricing guide explains what moves the number.

After launch, hosting and maintenance runs from $55 a month and covers what that page lists: managed hosting, updates checked on a staging copy, tested backups, security monitoring and small changes. New screens or features are quoted separately. The plugin maintenance page covers keeping custom code current. If an admin plugin you already own is broken, our fixed-price plugin repairs run from $149 to $399.

DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. Our work shows what we have built. Not sure where the clutter comes from? A free site audit lists every plugin and what it adds. Or call (210) 346-0848.

Questions owners ask about custom WordPress plugins

Yes. Each screen and each action checks WordPress user capabilities before it runs, so a front desk login can read leads without exporting customer data or installing plugins. We hide menu items the role cannot use, and we also refuse the action on the server, because hiding a link is not the same as locking a door.

It should not. Admin screens and their reports run when a logged-in staff member opens them, not when a visitor loads a page. We keep heavy queries inside the admin and load the plugin's scripts only on its own screens. If your public site is already slow, the cause is usually elsewhere, and our WordPress optimization service is the place to start.

Yes, through that system's API. A custom plugin can pull counts or records from a CRM, field service platform or email tool and show them beside your WordPress leads and orders. API connections go live the same day. Whether you should copy that data into WordPress at all depends on where your team already works.

Reports that read orders directly from the old posts tables may need changes. WooCommerce's developer docs say HPOS has been on by default for new installations since WooCommerce 8.2 in October 2023, and that supporting it is the extension developer's job. We write reports through WooCommerce's order functions and declare compatibility.

Custom admin plugins start at $575 to build, depending on complexity, with a fixed written estimate before work starts, as of November 2026. The number of screens, roles, reports and outside data sources sets the final price. Hosting and maintenance from $55 a month keeps it running afterward; new features are quoted.

Then build an application rather than a bigger plugin. If customers need their own logins or the screens have little to do with your website, a separate web app is usually cleaner and cheaper to keep. We will tell you which side of that line you are on before quoting.

Keep reading

Free · No obligation

Describe the screen your team wishes it had

Tell us who logs in and what they hunt for each morning. Someone at DataCram replies with a sketch of the screens, a role plan and a fixed written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote