09/24/2026
The Login Tax: What Admin Screens Really Cost
Part of No Login Required, a series about running a business by talking to your systems instead of clicking through them. The series opener on belchamber.us asks whether we'll need admin panels at all. This piece asks what they cost you now.
Most owner-run businesses I talk to don't have one piece of business software. They have a dozen, each chosen for a good reason at the time. Each comes with its own login, its own menus and its own idea of where the "Save" button should go.
The subscription fees are on the invoice. The time it takes to get to the button is not. That second cost is what I call the login tax, and unlike most taxes, you can actually cut it.
Count the logins
Take a normal week for a small business with a website, some marketing and a bit of cloud infrastructure. The tour tends to look like this:
- The website editor, whether that's WordPress, Drupal or something heavier, to post an update or fix a typo.
- Google Analytics to see whether anyone read it, and Google Tag Manager when a tracking tag needs changing.
- Google Search Console to check whether Google is showing the site at all.
- The web host's control panel for DNS and email settings. Mine is DreamHost.
- Google Cloud, if anything runs there, even just the service accounts behind your other tools.
- The email platform, the privacy and consent tool, the ad server: a vendor like Ketch for consent, or Kevel or open-source Revive Adserver for ads, if you run your own.
None of these is bad software. But every stop on the tour carries the same overhead before any real work begins. If "Forgot password?" were an employee, it would be up for a promotion.
The toll at every stop
- Sign in
- Get past the second factor
- Find the right account
- Find the right property
- Open three menus
- Discover the setting movedLast quarter's redesign moved the one you came for.
The same overhead, paid again at each of a dozen tools, before the change you came to make.
Before and after, from my own systems
I run my own businesses on this kind of stack, and I've been moving the work out of the consoles and into a conversation with an AI assistant (Claude, in these examples). Four real cases follow.
Google Cloud
On August 12 I asked to stop using the Cloud Console. My reason at the time, in my own words: "their admin is slow and clunky." We set up Google's gcloud command-line tool so the assistant could run it for me. Its first job was switching on the Google Analytics Data API that my reporting connector needed. No menus.
Honest footnote: a couple of Google's sign-in setup screens have no command-line equivalent, so I did those by hand, once.
Search Console
On August 30 I asked whether we could read my Search Console data without opening Search Console. We could, through a service account (a login that belongs to the software rather than to a person).
One of my sites wasn't connected yet, so I spent about two minutes adding that account as a user inside Search Console. After that the data came straight into the chat, and what it showed reshaped the marketing plan we were working on.
DNS at my web host
On September 7 I was typing email-security records into DreamHost's control panel by hand and fighting its form. It inserted a character I hadn't typed, then wouldn't save when I removed it.
Two weeks later, on September 21, the same kind of work took one answer in a chat. The assistant read every domain's records, laid out the gaps and, after I said yes, wrote new records on four domains. It worked through DreamHost's API with a key I created once, one that can list and add records but deliberately cannot delete them.
Google Analytics
This one is still waiting, and it's worth saying so. Google won't let the command-line tool's own sign-in request access to Analytics. The route that works needs me to grant access once, inside Google Analytics itself.
As of this writing, in late September 2026, I still haven't done it. That's the login tax in miniature: one small grant, deferred for about four weeks, because it means another console.
Where the time actually goes: finding, not doing
Look at any of those "before" versions and a pattern shows up. The change itself is small: a record, a setting, a user, a post. The time goes to everything around it.
- Finding the place. Which account, which property, which menu, which tab.
- Re-learning the interface. A tool you open once a month is a tool you partly relearn every time.
- Translating. Vendor vocabulary rarely matches the plain question you came in with.
- Checking your work. Many consoles bury the confirmation.
No single visit feels expensive, which is why the tax is easy to underestimate. It accumulates across a dozen tools and a whole year. And it lands on the owner, whose hour is usually the most expensive one in the building.
What a conversational layer changes, and what it doesn't
When your systems can be reached through their APIs, you ask for the outcome in plain language, and the assistant does the finding, the translating and the checking. That removes most of the tax on routine work. I made the broader case for why software overhead is shrinking in how AI is erasing small business software costs; this is the day-to-day version of it.
Here's what it does not change, and any honest pitch for this approach should say so up front:
- Setup still needs you, once per tool. Every example above started with a one-time step in the vendor's own screen: an access grant, a key, a consent page. "No login required" means you stop logging in for routine work, not that you never log in.
- Credentials stay out of the chat. Keys live in the tooling, scoped narrowly. My DNS key can't delete a record, by choice.
- You still audit. When something changes, you want to see it in the system of record with your own eyes. Admin screens don't disappear; they become the place you go to verify.
- Anything new and public waits for a human. On my own sites, a new AI-written article never goes live until I've approved it. The approval moved into the conversation; it didn't go away.
- The code needs review. Much of what connects an assistant to your tools is itself written with AI help. Review it as thoroughly as your goals and time allow. Automated tests and checks are welcome, but they come in addition to that review, not instead of it.
A one-hour audit to price your own login tax
I won't hand you a number for what this costs, because it depends entirely on your stack and your week. Here's how to get your own in about an hour.
Minutes 0-15: List the doors
Open your password manager (or your browser's saved sites) and write down every business tool you sign in to. Names only; don't copy any passwords out.
Minutes 15-30: Write down the verbs
Next to each tool, write what you actually do there, as a verb: "publish a post", "add a user", "check traffic", "update a DNS record". Then mark how often: weekly, monthly or rarely.
Minutes 30-40: Time three real trips
Pick three routine tasks from your list and do them now with a stopwatch running. Note two times for each: when you reached the right screen, and when the task was done. The first number is your time-to-the-button. The rest is the actual work.
Minutes 40-50: Check for an API
For each tool, search for the vendor's name plus "API" and see whether the thing you do there can be done through one. Mark each tool yes, partly or no.
Minutes 50-60: Do the math
For each routine task:
visits per year x minutes to the button / 60 x what an hour of your time is worth
Add the rows up. That total is your login tax. The tools marked "yes" in the last step are where it can be cut first. The ones marked "no" are worth remembering the next time a renewal comes around.
Keep the list. It doubles as a map of which tasks are routine (a fixed right answer, ready for automation) and which need your judgment.
What to do with the number
If the total is small, good: your stack is lean. If it isn't, you now have a line item instead of a vague sense of being busy, plus a shortlist of tools that can already be reached without the tour. The companion piece on enterprise platforms shows the same approach working on some of the most menu-heavy software there is.
Deciding what to automate, what to replace and what to leave alone is the kind of expensive-to-reverse call a business growth consultant exists to help with. Bring your audit. It makes for a much shorter first conversation.
More in No Login Required
- Will We Even Need Admin Panels?, the series opener, on belchamber.us
- Enterprise Platforms Without the Guided Tour
- Buy Software That Has an API
Ready to find out what your own software stack is costing you?
A business growth and technology consultant looks at your actual systems, not a generic playbook, and tells you plainly what is worth fixing first.