The shift

Stop doing the same web tasks by hand.

Downloading reports, filling in forms and copying data between sites takes hours, and one skipped step can throw off your numbers.

A macro on one laptop breaks when a site changes. We set it up to run reliably and show you exactly what happened.

The outcome

What you get

Where it earns its keep

Use cases

  • A weekly file into a report

    The same export arrives every week. The run places it in the report you already read, and it stops if a column is missing.

  • A form that should arrive once

    A request already captured on a page is entered into the system of record. The visitor is not asked to send it again by email.

  • A check against a public page

    A status, a price, or a listing you are allowed to read is compared with the copy on file. A mismatch is raised. A match is left alone.

Automation run with a step checklist beside a captured page.

The operating model

How it works

From first conversation to a system that runs itself.

  1. Plan

    We map how the work gets done today, including the calls only a person should make, and agree on it before anything is built.

  2. Build

    Built on Cloudflare and connected to the tools you already use, so nothing has to move.

  3. Review

    Tested on your real work from last week before any customer sees it.

  4. Launch and run

    We launch with close monitoring, keep it running, and you can change the rules at any time. It’s yours to keep.

The decision

How it compares

Three ways to handle repetitive web work.

Off the shelfHire in-houseAbracadabra
When the page movesThe plugin breaks on that laptop.The person notices, or they do not.The run stops and the log says which step failed.
Who can see itWhoever sits at that computer.The person, plus whoever they told.The log, for the people you grant access.
What happens to the odd oneIt is skipped, or it is entered wrong.They handle it if they notice.It waits for a person. The clear runs finish.
When you don’t need usThe task happens once a month, the page is stable, and a person can spare the ten minutes. A reminder and a checklist are enough. A site that changes every week is a moving target and should stay with a person.A hire to click a stable monthly form is a poor use of a person. A hire to handle the exceptions is still right.A path that keeps changing stays with a person. It’s worth it when the same task comes up often.

Named work

Proof

StrongFoam website

The StrongFoam website takes the request on the page: a visitor can start an estimate and book, so the details stay with the request. That is the public shape of this service. Figures and quotes stay off this page.

Read the StrongFoam website note

Finished run card showing the steps that completed and the page they touched.

Running in production today.

Pricing

Priced to the project. Tell us what you need and we’ll quote it.

Start a project

Questions, answered

FAQ

faq-title

Will it log in as one of your staff?

It uses an account created for the job, with only the access that job needs. It does not use a person’s password.

What if the site shows a captcha or a surprise prompt?

The run stops and a person receives it. A control the site put there to block automation is not bypassed.

Can it click through a site you do not own?

Only where you have the right to act, with an account you control or a page that is public. A system you are not allowed to use this way is left alone.

How does a step change?

We rewrite the path and you try it on last week’s file before it replaces the old path.

What if it writes the wrong value?

The log shows the value and the field. The runs on the list can be reversed. A write that is hard to undo waits for a person.

Is this a bot that browses the web all day?

No. It only runs the tasks you set, on your schedule.

Start a project

Tell us about a web task someone did by hand this week, and we’ll show you how to automate it.

Start a projectAI Readiness Check