Book a free 30-minute call

Solutions · For operations

Portal robot

Works a tool that has no API the way a person would, and logs every step.

2–3 weeks to build

The problem

Some work lives in portals with no API: supplier sites, carrier tools, government forms, platforms on a plan without access. Someone logs in and clicks through the same screens every day.

At a glance

Where it sits in your day.

  1. It starts withA schedule or a requestOn a timetable, or when something happens
  2. The systemPortal robot
    • Signs in and clicks like a person
    • Uploads, downloads, fills in, checks
    • Logs every step
  3. Hands off toYou, for risky batchesAnything you mark as risky waits for approval
  4. You end up withThe portal work, donePlus a report of every run

What changes

The same work, before and after.

  • TodaySomeone logs in to the carrier site and clicks through the same screens every day.

    With the systemThe robot repeats the same clicks in a browser, on a schedule.

  • TodayDetails are copied by hand from a spreadsheet into the portal.

    With the systemIt reads your sheet and fills in the portal for you.

  • TodayIf a step gets skipped, nobody can say what happened.

    With the systemEvery step is logged, and each run ends with a report.

  • TodayA risky change goes in with one click and no second look.

    With the systemBatches you mark as risky wait for a person to approve them.

Watch it work

Portal robot, step by step.

An insurance broker, Monday evening. Policy changes have to be entered on a carrier’s website that has no API.

  1. YouMon 4:40 pm

    You list the changes in a spreadsheet

    Five requests from clients. Two are cancellations, which you have marked as risky, so they will not go in unseen.

    Google Sheets5 requests
    • Harbor BakeryNew delivery van addednormal
    • R. MorenoAddress changenormal
    • Delta AutoDriver addednormal
    • Pine Street CafeCancel policyrisky
    • K. LindqvistCancel policyrisky
  2. The systemTue 7:00 am

    The robot works the portal

    It signs in with the login you gave it and enters the three normal changes, one screen at a time. The two risky rows it leaves alone.

    Carrier portal · run log7:00 am

    Run 7:00 am

    7:00 Signed in with the login you gave it

    7:02 Harbor Bakery: vehicle form filled in and submitted

    7:04 R. Moreno: address changed, confirmation downloaded

    7:06 Delta Auto: driver added, confirmation downloaded

    7:07 Rows 4 and 5 are marked risky. Waiting for a person

  3. The system7:07 am

    It asks before the risky ones

    You get a short message with exactly what it is about to do. Nothing is cancelled until a person says so.

    Your inbox7:07 am

    Approval needed: 2 cancellations

    Pine Street Cafe: cancel policy

    K. Lindqvist: cancel policy

    Both are marked risky in your sheet.

    Reply approve to go ahead, or hold to leave them.

    Waiting for a person

  4. You8:20 am

    You check them and approve

    You look at the two rows, see they match the client requests, and reply. The robot carries on from where it stopped.

    Your inbox8:20 am
    • AI agent · 7:07 am

      Two cancellations are waiting for approval. Reply approve to go ahead.

    • Dana · 8:20 am

      Approve

    • AI agent · 8:20 am

      Thanks. Submitting both now.

  5. The system8:26 am

    You get the report of the run

    Each request is marked in your sheet with what happened and where the confirmation is saved.

    Google SheetsRun report
    • Harbor BakerySubmitted, confirmation saveddone
    • R. MorenoSubmitted, confirmation saveddone
    • Delta AutoSubmitted, confirmation saveddone
    • Pine Street CafeApproved by Dana, submitteddone
    • K. LindqvistApproved by Dana, submitteddone

What you get

  • The portal work done without anyone clicking through it
  • Approval before any batch you mark as risky
  • A report of every run
  • a portal with no API
  • a spreadsheet
  • your inbox

How we build and run it

  1. We write down the steps a person takes today, screen by screen.
  2. The robot repeats them in a browser, on a schedule or when something happens.
  3. Batches you mark as risky wait for a person to approve them first.
  4. Every step is logged. When the portal changes, the robot stops and tells you.
What we run ourselves

We run one on our own cold-email platform, which has no API. It uploads, pauses, resumes and reports unattended, and a person approves every batch.

IN OUR OWN BUSINESS

What it costs

A fixed price, in writing, before you pay for a build.

What it costs depends on how many of your tools it connects and how much it decides on its own. The map works that out for your business. The first call is free.

Build

from$2,500per system

One system, built to the map, at the fixed price quoted in it.

  • Built in accounts you own
  • Connected to the tools you use, or built new
  • Run on your real work in a test mode first
  • Runbook and brain notes handed over
Book a free 30-minute call

Fixed quote in writing before work starts

Run and improve

from$500/month

We host it, watch it, fix it, and turn what it gets wrong into rules.

  • Hosting and monitoring
  • Every miss logged as a lesson
  • A monthly note on what changed
  • Month to month, stop any time
Book a free 30-minute call

Priced per system in the map

Free 30-minute call

Tell us how this work is done today.

Bring the tools you use and the steps your team repeats. You leave the call knowing whether this system is worth building for you, roughly what it costs, and whether we are the right people to build it.

Pick a time on the calendar. It is a 30-minute call, and the invite lands on your calendar when you book. Prefer email? [email protected]

We reply by email within 24 hours.

AI systems call30 MIN
October 2026
MoTuWeThFrSaSu

Checking the calendar…

Questions

What people ask about this system

The robot stops and tells you, rather than clicking through a screen it does not recognise. We then update its steps.

No. It signs in only with the login you give it, and it does not get around a CAPTCHA or any other security check. Those stay with a person.

Yes, on our own cold-email platform, which has no API. It uploads, pauses, resumes and reports unattended, and a person approves every batch.

Every step is logged, and you get a report of every run. You decide which batches wait for your approval first.