What is an admin portal?

It’s where your team sees what customers do in the app and acts on it. A customer opens the app, signs in, and sends something in. Somebody on your side has to see that it arrived, decide what happens next, and fix it when it’s wrong. The portal is where they do that, in a browser, on a screen big enough for a table.

• 01

  Accounts. See who signed up, reset someone’s access, close an account, merge the duplicate.

• 02

  Records. Open what a customer sent in, correct it, attach a note, mark it handled.

• 03

  Content. Change what the app shows without calling a developer: a notice, a price, a list of options.

• 04

  Permissions. Decide which of your own people can see what, and who can delete.

• 05

  Exports. Get the data out for the bookkeeper, the board, or the spreadsheet that won’t die.

• 06

  Support. Look at exactly what a customer sees when they call and say it’s broken.

None of that is visible to a customer, so people writing a brief from the customer’s seat leave the office side for last, if they mention it at all.

Because it is one. It shares the server and the data with the phone app, so it isn’t a second full build. Everything your people touch is built for them, though: the lists, the forms, the rules about who can do what, and the testing of all of it. The estimator prices it as a separate line, apart from the phone app.

What the brief says

“And the office needs a web page to manage it.”

What gets built

A staff sign-in. A list of every customer, with search and filters because there’ll be a thousand of them. A page for each one. A way to edit what they submitted, and a record of who edited it. Somewhere to change what the app displays. A permission model so the new hire can’t delete a customer on day one. Then every one of those screens tested, in three or four browsers instead of on a shelf of phones.

$11,000 – $15,000, on the reference app at $38,000 – $54,000. Take the portal out and the same app is $27,000 – $39,000. That gap is about 28% of the build, and it’s the largest feature in it.

That’s more than the sign-in, the two user types, and the notifications put together. Portals aren’t hard. They have more screens than people picture, and screens are what software costs.

Run the same description yourself. It’s filled in already. In the result, open “Did we get something wrong?” and switch off “Administrative web portal” to watch what moves.

There’s a cheaper first version, and the estimator offers it unprompted: a small internal management screen at 35% of the full portal’s work, with push notifications left until people are using the app. That release is $29,000 – $41,000, 24% less, and most of the saving is the portal.

A portal is where your people change things. A dashboard is where someone reads them. Briefs often ask for “an admin dashboard” and mean both, and the estimator prices them as two separate features, because they are.

Admin portal

Lists, record pages, forms, and permissions. Built for doing: edit this record, close that account, change what the app shows tomorrow.

Reporting and dashboards

Charts, totals, and filters over time. Built for reading: how many signed up this month, and what’s overdue. The hard part is the data underneath, which is why the estimator prices it apart from the portal.

If the office side is the whole product, you’re building an internal tool, and the spreadsheet guide is about that case. If you want to see the portal move a number on its own, the $25,000 guide adds one to a small app and shows what moves.