Claude in Chrome, the browsing agent that can act inside your browser rather than just chat alongside it, gets pitched most often for marketing tasks. The admin use case is quieter but arguably bigger for a typical Australian small business: form-filling, portal navigation, and the repetitive browser-based tasks that eat an afternoon without ever showing up as a headline feature.
What a browsing agent actually does for admin work
This is a genuinely unglamorous category of work to automate, which is exactly why it's underexplored: nobody writes a case study about form-filling the way they do about a flashy customer-facing chatbot, even though the office-manager time saved is often just as real.
Document which tasks are cleared for unsupervised running and which still need a human watching, and revisit that list periodically as trust builds, rather than leaving the boundary as an informal, unwritten understanding that different staff interpret differently.
A short weekly check-in, five minutes, on how the pilot task is going keeps the rollout honest and catches any drift in reliability before it becomes a bigger problem.
Rather than reading instructions and doing a task yourself, you describe the outcome and the agent navigates the actual pages, clicks the actual buttons, fills the actual fields, the same way a person would, just faster and without the friction of context-switching between fifteen browser tabs. For admin-heavy roles, that covers a specific, tedious category of work: updating a supplier portal, checking a government registration status, submitting a routine form that has no API and never will.
Portal navigation: government sites, supplier portals, anything without an API
Form-filling: repetitive submissions using data you already have on hand
Status checks: logging in somewhere just to confirm one piece of information
Not suited to: anything requiring genuine judgment calls mid-task
Where it earns its keep versus where it doesn't
The clearest win is on tasks that are simple in judgment but tedious in execution: checking the status of twelve supplier accounts, updating an address across several government portals after an office move, submitting a batch of routine forms with data pulled from a spreadsheet. Tasks needing genuine judgment mid-task, deciding how to respond to an unusual field on a form, or interpreting ambiguous instructions from a portal, still need a human watching, at least until the agent's handled that specific task enough times to be trusted with it.
A worked example: office relocation admin
A Melbourne professional services firm moving offices used Claude in Chrome to update its registered address across nine separate government and supplier portals, a task that would normally have taken an office manager most of a day logging into each system individually. With the agent handling the repetitive navigation and form-filling, and a human spot-checking each submission before final confirmation, the same task took under two hours, most of which was the spot-checking rather than the actual work.
The trust-building curve
Most businesses start by watching every step closely, then loosen oversight gradually as the agent proves reliable on a specific, recurring task. That's the right order. Treat the first few runs on any new task type as supervised, and only extend more autonomy once there's a track record on that specific kind of work, rather than assuming broad trust from day one.
What this is worth in hours, not just novelty
For a business paying an office manager or admin coordinator around $35 an hour, reclaiming even three or four hours a week from portal-navigation drudgery is worth roughly $500 to $600 a month, which is a modest but real number once it's tallied rather than treated as a vague productivity gain nobody actually measures.
The value compounds for businesses with genuinely repetitive admin cycles, monthly supplier reconciliations, quarterly registration renewals, recurring compliance check-ins across multiple portals, where the same pattern of tedious navigation repeats predictably enough that setting it up once pays off every cycle afterward.
For an office manager or admin lead drowning in portal logins and form submissions, this is one of the more immediately useful applications of Claude in Chrome, even though it rarely gets the same attention as the flashier marketing use cases.
Start with whichever recurring portal task currently causes the most quiet frustration in your office, and treat that as the pilot before expanding to a broader set of tasks.
It's a smaller, less glamorous win than a customer-facing feature, and often a more reliably delivered one.
That documentation takes an hour to write and saves a much longer conversation later about why a task ran unsupervised when it shouldn't have.
Small habit, real hours back every week.
