Start with the Monday numbers
Every Monday somebody opens Google Analytics, squints at last week’s sessions, sign-ups and conversion rate, and types them into a KPI sheet that three other people glance at on Tuesday. Six minutes, maybe eight if a filter got reset. Nobody has ever enjoyed it. Handed to dassi, which works in the browser you already have open, it looks like this:
- With the report open, you type: “Put last week’s sessions, sign-ups and conversion rate into the next empty row of the Weekly tab in my KPI sheet.”
- dassi reads the three figures off the report, switches to the Google Sheets tab, finds the first empty row and fills it in.
- You check the row against the report. Do it properly on the first few runs; after that a glance is plenty.
- You save it as a Skill and schedule it for 8am on Mondays.
Next week the row is there before you’ve found your coffee. The weekly analytics summary page covers the wordier version, where the same dashboard becomes a written update you can send.
Other jobs with the same shape
The Monday job suits this because it’s the same two sites and the same steps every time, plus a sliver of judgment no macro can supply (which row counts as “next” when someone left a blank one in the middle?). Logging LinkedIn conversations in Salesforce is like that, since somebody has to decide whether “sounds good, circle back in Q3” is a live lead or a polite no. So is filling a long web form from a spreadsheet, or sorting forty unread emails into the piles you actually use.
Our rough rule is to save anything you’ve done by hand three times this month and could explain to a temp in one paragraph. Jobs that change shape every time are murkier. dassi will do them, but you end up rewording the instructions so often that clicking through yourself might be quicker, and we haven’t found a clean line between the two.
Zapier, recorders, and pages with no API
If both apps have an API and the data arrives clean, use Zapier. It’s faster and cheaper than anything that reads a screen, and for a thousand orders a day we’d send you there ourselves.
Most of the tedious stuff doesn’t live there, though. It lives in the portal your supplier built in 2011, or in a report that only exists as a web page once you’ve logged in, and the usual tool for those is a recorder or RPA bot that replays clicks at saved positions until the week somebody moves a button. dassi reads the page fresh on every run and finds the field labelled “Invoice number” wherever it has wandered off to, working inside the accounts you’re already signed into.
Before it acts
All of this runs in your own browser on your own machine, which is also why a scheduled run needs that browser open when it’s due; close the laptop on Friday night and Monday’s run waits until you open it again. The instructions and page content a task needs go to whichever model provider you pick, whether that’s Claude, GPT, Gemini or a local model, and with included credits they pass through dassi’s relay. If you already pay for an API key, the key-only plan is $10 a month.
You choose which actions need your approval first. Sending email and submitting forms are the obvious ones, and deleting anything belongs on the list. dassi stops at each and shows you what it’s about to do. Two-factor codes and CAPTCHAs are always yours. On LinkedIn the weekly cap on connection invites is a hard ceiling, and dassi paces itself under it the way a person would (a fairly unhurried person).