home / use cases / web automation and research / web-watchlist

Watch web pages, get real summaries

An Aivell opens every page on your watch list twice a day — tender portals, regulator pages, key clients' terms — compares them with the last visit, ignores cosmetic churn, and emails a five-line summary of what actually changed, deadlines pulled out and bolded. Every version is kept for later.

Watch the demo

starts when: At 08:00 and 16:00, the round begins

The problem

The tender was published on the portal for fourteen days. You found it on day twelve. The regulator amended a rule in March; you heard about it at a seminar in June. A key client rewrote their procurement terms and told nobody — the page just changed. None of this was hidden. It was all public, on pages you knew about, that nobody had time to keep re-reading.

The usual fix is to make it someone’s job: a bookmark folder and a Friday routine of pressing refresh. It survives three weeks. The alternative — change-detection pingers — cries at every rotating banner and still leaves the reading to you.

How your Aivell does it

  1. The round runs twice a day. Morning and afternoon, the Browser Agent opens every page on the list — tender portals, regulators, client terms — and reads each one whole.
  2. Change is judged by meaning. The new version is compared with the stored one, onboard. A shifted date stamp, a visitor counter, a cookie banner — ignored. A new tender, a reworded clause, a moved deadline — that’s a change.
  3. The summary does the reading for you. Five plain lines on what changed and why it matters, with any deadline in the text pulled out and bolded. Not a link and a good luck.
  4. Urgency is routed by rule. New tenders reach Miriam the moment they’re found; everything else collects into the evening digest. The line between the two is a sentence in the chore.
  5. Every version is kept. When someone asks “what did their terms say in April?”, the answer is on the box — dated, stored, comparable.

The guardrails keep the chore exactly what it claims to be: it reads listed pages and mails your own people, nothing more. A colleague who never gets bored of checking — and never tells anyone outside what you’re checking.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · watch the tender pages ● active

at 08:00 and 16:00, open every page on the watch list

the tender portals, both regulators, and the big clients' procurement pages

compare each page with the stored copy from the previous visit

cosmetic churn — dates, counters, cookie banners — doesn't count as change

a new tender or an amended rule? summarize what changed in five lines

any deadline found in the text goes into the summary, bolded

new tenders go to Miriam immediately; the rest waits for the evening digest

keep a copy of every version, so "what did it say before?" has an answer

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Schedule runs the round, morning and afternoon
Browser Agent opens each page, reads it whole
Email delivers the change summaries

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Browser Agent Reads only the pages on the watch list. No logins, no form filling, no clicking beyond them.
Email Delivers to Miriam and the tenders list only — never to anyone outside the company.

Questions, answered.

How is this different from a page-change pinger? +

A pinger tells you some pixels moved — usually a date stamp or a banner — and you still have to go read the page. The Aivell reads both versions and tells you what changed in meaning, deadline included. Most rounds it correctly tells you nothing.

Can it watch pages that sit behind a login? +

Yes, if you hand it the account and add the domain to its whitelist. The guardrails still define everything else — a watchlist chore reads pages; it doesn't get to fill forms or click into account settings.

Who can see what we're watching? +

Nobody. A watch list is revealing — the tenders you'll bid on, the clauses you're worried about. List, stored copies and summaries all live on the box, behind your firewall; no monitoring service holds a mirror of your interests.

What happens when a watched page is down? +

It's noted and retried on the next round. Only after repeated failures does it become a line in the digest — a dead link is worth knowing about, just not worth an alarm at 08:05.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee