job: weekly-admin · scheduled

Automate recurring browser administration

Monday, 08:00: statements pulled, sheet reconciled, receipts filed, the renewal caught before it lapsed — all done before you sit down. You taught dassi the routine once. Now only the rows that don't add up reach you.

Give dassi this job

Free credits, good for 7 days — no card required

Trusted by 30,000+ Chrome users Rated 4.8/5 on Chrome Web Store Works with Claude, GPT, Gemini, and more

One run, start to finish

Every dassi job has the same shape: an input, work done on real pages and accounts, output you can verify, and exceptions flagged — never guessed. This one is an illustrative example of the job.

run · weekly-admin scheduled · mondays 08:00 illustrative example
input

“Run ‘weekly admin’ — reconcile last week, file the receipts, check the renewals.”

Scheduled Skill — taught once, runs every Monday at 08:00

run
  1. 08:00 dashboard.stripe.com exported last week's payouts, fees, and refunds — 143 transactions
  2. 08:04 yourbank.com read the settled transactions in the business account you're signed into
  3. 08:09 sheets.google.com reconciled payouts against orders and updated the bookkeeping sheet, row by row
  4. 08:14 drive.google.com filed 31 receipts and invoices into /receipts/2026-08, named by vendor and date
  5. 08:17 portal.vendor.com caught the listing renewal due Friday — renewed it after your one-tap approval, invoice saved
output
  • verified: 141 of 143 transactions reconciled — sheet current, receipts filed, renewal handled
  • verified: A one-paragraph summary with links, waiting in your inbox
exceptions
  • flagged: 2 payouts had no matching order — flagged in the sheet with a note, left for your call
  • flagged: The vendor portal showed a new terms-of-service dialog — dassi paused and attached a screenshot instead of accepting it for you
next

Next Monday, 08:00 — same job, your rules. Nothing to re-teach, no macro to re-record.

What you can hand off

Statement pulls and reconciliation

Pull statements from every dashboard you check, match them against orders or invoices, and keep one sheet current — with a note on every row that didn't match.

Filing, receipts, and paperwork

Collect receipts and invoices from portals and inboxes, name them your way, and file them where your accountant expects to find them.

Renewals and expirations

Watch the dates that bite — licenses, listings, domains, insurance — and handle or escalate each one before it lapses.

Government and compliance forms

Fill the recurring filings from your own records, save the confirmation, and stop before anything is submitted unless you've approved that step.

The weekly status report

End every run with a plain summary: what was done, what changed, and what needs you.

The admin that never ends

Every small business carries a second job that nobody hired for. Log into the payments dashboard and export last week. Log into the bank and cross-check. Update the sheet, chase the receipts, renew the thing that expires on Friday, file the monthly form. None of it is hard. All of it is yours, and it comes back every week whether you have time for it or not.

It never gets delegated, either. Explaining the routine takes longer than doing it, and half of it runs through accounts you don’t want to share with anyone.

Taught once, run on schedule

dassi lives in your browser. Do the routine once while it watches, or write it out in plain English, and it saves your procedure as a Skill. After that it runs the whole job on a schedule: the same dashboards, the same sheet, the same filing system, inside the sessions you’re already signed into on your own computer.

What separates this from a script is what happens at the edges. A payout with no matching order doesn’t get force-matched; the row gets flagged. A portal dialog dassi hasn’t seen before doesn’t get clicked through; the run pauses and you get a screenshot. The routine bulk gets done, and the few rows that need actual judgment show up in your inbox with the context already pulled together.

If you searched for “browser automation”

Fair enough, and technically dassi is one. The difference is what you’re left holding. An automation tool hands you a recorder and wishes you luck when the page layout changes. dassi learned your admin, runs it your way, and knows when to stop and ask. You keep the decisions that matter. The clicking stops being your job.

Teach it once

01

Show it the job once

Do your Monday routine while dassi watches, or describe it in plain English. It saves the procedure as a Skill — yours, editable, in your words.

02

Set the guardrails

Choose what runs freely and what waits for you. Submissions, payments, and anything irreversible can require your explicit OK.

03

Put it on the calendar

Schedule the Skill. From then on the work is done before you sit down, and only the exceptions reach you.

Your accounts. Your machine. Your call.

Runs on your machine

The agent works in your browser on your computer, local by design. It never runs in our cloud.

Your logins stay yours

It works in the sessions you're already signed into. No password handoff, no credential vault.

You approve what leaves

Messages, submissions, payments — anything outbound waits for the approvals you set.

Your model, your choice

Claude, GPT or Gemini with your own key or included credits, or a fully local model. On your own key, prompts go straight to your provider; included credits pass through dassi's relay.

Frequently asked questions

Is this the same as a macro or RPA tool?

No. Recorded macros replay pixel positions and break the moment a page changes. dassi reads the page the way you do and adapts — same procedure, current layout. And when something genuinely doesn't add up, it stops and flags it instead of pushing through.

Will it submit or pay anything without me?

Only if you've told it to. Approval gates are part of teaching the job: by default, anything that leaves your browser — a submission, a payment, an email — waits for your OK.

Which portals and dashboards does it work with?

Any site you can open in your browser while signed in. There's no integration list because there are no integrations — no APIs, no OAuth, no Zapier. If you can do it in a tab, you can hand it off.

What happens when it hits something unexpected?

It flags. An unmatched transaction, a new dialog, a changed form — dassi records the exception with context, often a screenshot, and leaves the decision to you. It is taught to never guess on your books.

Where does this run? Who can see my accounts?

On your machine, in your browser, in your existing sessions. The agent is local by design — your logins are never handed to a cloud service. You choose the AI model it thinks with, including your own key or a fully local model.

Give dassi its first run

Install dassi, open the pages this job lives in, and show it the work once. It runs from then on — your way, on your machine.

Add dassi to your browser

Free credits, good for 7 days — no card required

More jobs dassi runs

Sign up — get 10% off

Create your dassi account. We'll email your discount code + the desktop install link.

or