MILabs
Tools

Browser Use for small business web automation

How MILabs sets up Browser Use, an open-source framework that lets an AI agent work through websites that have no API.

Updated 2026-07-22

What Browser Use is

Browser Use is an open-source framework that lets an AI agent operate a web browser much as a person would. The agent opens pages, reads what is on screen, clicks buttons, fills in forms and moves through multi-step websites. Developers use it for tasks that have no API, such as checking a supplier portal or collecting listings from a directory. Because the software can run on the business's own infrastructure, it suits work where browser sessions touch private information. Browser agents are less predictable than fixed scripts, so the output needs a person's review before it reaches a customer or a ledger. At MILabs, a Sydney agency that works remotely and runs sessions by video call, we treat Browser Use as one part of a wider workflow rather than a finished product. The right fit depends on which sites the business needs to reach, how often those pages change, and who reviews the results.

Browser Use: official site

Browser Use in plain language

Many business websites were built for people, not software. A supplier portal may show prices in a table, a government register may return results only after a search form is filled in, and a directory may offer no download. Browser automation tools were designed for this gap. They control a real browser session, so the software can load a page, read what is visible, select an option and move on to the next screen.

Fixed scripts often break when a button moves or a pop-up appears. An agent-style approach has a language model read the current page and choose the next action, which handles changing layouts more gracefully but is less predictable. The model can misread a label or act on the wrong row, so the work is bounded by a clear task, a small set of sites and checks before results are used.

For a business owner, the useful question is less about the technology and more about the task. Is there information on the web that is needed regularly, that has no export, and that a person currently copies by hand? If so, a browser agent may be a reasonable option. Where a site already offers an API or a feed, that route is normally simpler and more stable.

What businesses use it for

  • Gathering prices and stock levels from supplier websites that offer no export
  • Confirming licence or registration status on government and industry portals
  • Collecting listings or competitor details for sales research
  • Completing repetitive online forms with data from the CRM
  • Watching a site for changes and sending a summary to the owner

Who it suits

  • Operators who rely on a few web portals with no API
  • Teams that carry out repeat research across listings or directories
  • Owners who are comfortable reviewing each run before results go live

How MILabs sets it up

The easiest first step is to say hello through the enquiry form, and we'll take it from there. The conversation with the owner or team lead settles which websites matter, which tasks the agent performs and which steps need approval before submission. MILabs then chooses the hosting arrangement with the owner, since Browser Use can run on infrastructure the business controls. Next we connect the systems the business already uses, such as the CRM or inbox, and set permissions so the agent holds only the logins it needs. Logins stay out of prompts and are held in a store the owner can revoke. Finally, the owner and MILabs agree who looks after the agent, who reviews flagged results and who updates the workflow when a site changes its layout.

Builds it fits

Industries it fits

Browser Use in practice

In a business that uses a browser agent well, the work sits alongside an existing process rather than replacing it. Consider a wholesale distributor that checks stock and pricing on three supplier portals as part of its routine. Staff currently log in, copy figures into a spreadsheet and flag anything unusual. An agent could handle the navigation and copying instead, writing each value to a staging sheet beside its source page and capture time. Staff then review only the rows marked as changed or unclear, which keeps a person in the loop where the stakes are highest.

This arrangement tends to have three layers. The agent handles the browser steps, a separate part of the workflow decides what happens to the captured data, and a reviewer checks the output before it reaches the pricing file or purchase order system. Each layer can fail on its own, so the owner knows which one to inspect when a run looks wrong. A run that returns zero rows, for example, often points to an expired login rather than a supplier with no stock.

Over time the useful habit is logging. Each run records pages visited, data captured and items flagged, so a changed supplier layout appears as a pattern of failures rather than a gap.

good questions, straight answers

Frequently asked questions

Can MILabs build on top of Browser Use?
Yes. MILabs can build a workflow around Browser Use, with the agent handling web steps and the surrounding logic running in the systems the business already uses. We would define the task, the target sites, the fields to capture and the checks a person makes before results are used. The first conversation confirms whether the tool fits those sites before any build is agreed.
What does a Browser Use setup need from me?
A setup needs a list of the websites involved, the steps the agent should take on each, and the people who will review its output. It also needs a decision on where the software runs, since it can be hosted on infrastructure the business controls. You will need to provide the logins the agent will use and confirm which accounts can be limited in scope. Access is reviewed whenever staff change roles.
What does Browser Use not do?
Browser Use leaves the choice of what to automate with the business, and it does not check its own answers. A browser agent can misread a page or miss a changed button, so a person's review remains the check on anything that reaches a customer, a payment or a legal record. It is rarely the best route where an API exists, and its strength lies in reaching websites that offer no better route.
Is Browser Use suitable for a small business?
Yes, for a business with a defined set of websites and a person who checks the results. It suits repetitive research, data collection and form work on portals that have no export or API. It is less suited to a business that expects the agent to run unattended across many changing sites. A small team can start with one workflow, review it closely and widen scope once the results hold up.
Is Browser Use safe to use with customer data?
Yes, provided the software runs on infrastructure the business controls, which lets customer records stay within systems the owner manages. MILabs confirms this during setup. MILabs limits the agent to the logins and fields it needs and keeps credentials out of prompts. A retention rule for sensitive records is agreed with the owner before any such records are involved.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.