Open-Source Tool

A contractor is hiring bots for five portals with no API

A field-service company is hiring someone to build bots that copy about 100 jobs a day into five client portals with no API, at a posted $4,000 to $6,000 a month. Every contractor whose big clients run their own portals has that chore, and free browser agents make it a service.

Published Oct 23, 2026

The Wow

What someone built

The job post on X (Oct 20, 2026) asks for browser bots that move job data from AroFlo, the company's job system, into five client portals without APIs, automating forms, uploads and status updates, plus an AI voice agent for inbound bookings. The tooling exists in the open: Browser Use (MIT, about 118,900 GitHub stars) lets an AI agent log in, fill forms and upload files.

Open-Source Tool

Original repository
Browser Use on GitHub
License
MIT License
What you need
  • Python 3.11 or later
  • An API key for a supported AI model
  • A browser the library can drive (it installs Chromium through Playwright)
Install
`pip install browser-use`, then follow the repository's quickstart to connect a model and run a first task in a test portal account.

Why it's remarkable

It's a buyer describing the exact job, the exact volume and the price of doing it in-house, in public. Re-keying the same job into a client's portal earns the contractor nothing, so every hour saved goes straight back to them.

The Opportunity

The business it reveals

A portal-sync service: a monthly fee per portal to keep a contractor's job system and its clients' portals in step, with fixed scripts for the steady screens, an agent for the ones that vary, and a daily exceptions list for a person.

Who would pay

Facilities and trade contractors serving retail chains and commercial property managers, the clients most likely to require their own portals. A one-portal pilot is easy to scope and price.

The Flip

3 ways you could turn this into a business

Compliance-portal uploads for specialty subcontractors

Who pays
Electrical, mechanical and plumbing subcontractors that work for several general contractors
How it would earn
A monthly fee per general contractor's portal (our hypothesis)
Why it might work
Each general contractor can ask for the same insurance, safety and payment documents in a different portal; the upload chore repeats across every one.
What already exists
Office staff do it today, and the compliance platforms general contractors choose offer their own tools.

Vendor-portal updates for small suppliers to big retailers

Who pays
Small manufacturers and distributors whose retail buyers only offer a web vendor portal
How it would earn
A monthly fee per retailer portal (our hypothesis)
Why it might work
Order confirmations, shipping notices and invoices go into each retailer's portal by hand when the supplier has no EDI connection.
What already exists
EDI providers and web-EDI services already serve many suppliers; the opening is suppliers whose buyers offer only a portal.

Why we'd try "Portal sync for facilities contractors with commercial clients" first: A buyer is already paying for it in public, the volume is concrete, and a one-portal pilot is easy to scope.

Build It

How you could build it

A per-portal sync bot with a daily exceptions list: read new jobs from the job-system export, enter them in the portal, attach photos, and log what it did.

First step: Ask three local contractors who serve retail or commercial property clients one question: how many client portals do you update by hand each week, and how long does it take?

Agents and tools

  • Browser Use (MIT)
  • An AI model (ChatGPT, Claude, Gemini, Grok Bot or similar)
  • Playwright
  • The contractor's job-system export
  • A shared exceptions sheet

Setup

  1. Map one portal's fields to the job system's export with the contractor.
  2. Get the portal owner's written OK and a dedicated login.
  3. Script the fixed steps in Playwright; use the browser agent only for screens that vary.
  4. Run in shadow mode for a week: the bot fills the form, a person checks and submits.
  5. Switch to live entry with a daily exceptions report.

What the agent does

  • Reads each new or changed job
  • Fills portal forms and uploads photos
  • Flags mismatches and failed logins
  • Writes the daily run log

What you do

  • Sells and scopes
  • Gets portal permissions
  • Reviews exceptions daily
  • Fixes bots when portals change

Your first customer: A local facilities contractor with two or three portal clients.

Test demand first: Ask ten facilities or trade contractors how many portals they update and how long it takes. Success: three or more spend five or more hours a week on it and one agrees to a paid one-portal pilot. Failure: fewer than three.

Your starter instructions

Paste this into the AI agent you use (ChatGPT, Claude, Gemini, Grok Bot or another) as your first message. Copying it starts work in your own agent; it doesn't create or deploy a business by itself.

Get a launch plan

Running it

What stays human: Mapping each portal's fields with the contractor; getting the portal owner's written permission; keeping logins in the contractor's own password manager; reviewing exceptions daily; fixing bots when a portal changes; the client relationship.

Startup cost (estimate)
About $0 for the software (estimate) (Estimate: Browser Use and Playwright are open source; model usage and a small server are the running costs. Not measured)
Running cost
Model and server usage per portal (estimate pending a pilot) (Unknown until a pilot measures runs per day; the post's volume is about 100 entries a day across five portals)
How much the agent runs
Agents run one core part; people run the rest.

Pricing your own version? Use the free startup-cost worksheet.

The evidence

What the source shows: The employer's job post on X (Oct 20, 2026); the pay is a posted range for a hire, not service income. Browser Use's public repository and license.

What's ours: The portal-sync service and its per-portal pricing are our application; we found no one selling it this way and haven't built it.

Worth planning around

  • Some portals' terms forbid automated access, so get each portal owner's written OK first.
  • Portals change without notice; bots need upkeep and a person watching failures.
  • Work orders can include tenant or site contacts, so move only the fields each portal needs.

Sources

Sources reopened Oct 22, 2026. Spot a mistake? Tell us and we'll correct it in public.

Keep reading

The Daily Paycheck: one remarkable AI business at a time, and exactly how you could build around it. Free; unsubscribe anytime.

Get new AI business discoveries by email.