Monday, 8:40am
At most small companies the weekly report is the same document every week, and it has been since whoever started it left. Somebody opens GA4, then Stripe, then HubSpot, sets each one to last week, and copies sessions, sign-ups, revenue and new deals into a Google Doc. Then a paragraph on what moved, written in the four minutes before standup. Then a link in Slack.
dassi can own that job because it works in the browser where those dashboards are already open and signed in. It reads the numbers off the page the way you do, so there’s no connector to set up per tool, and it puts them wherever last week’s report put them.
Teaching it the report
Do the first run together. Open last week’s report (it describes the format better than any instructions could) and walk dassi through where each figure lives: sessions and top landing pages from GA4 for the last seven days against the seven before, MRR and new subscriptions from Stripe, deals created from the HubSpot deals report. Tell it to copy the doc, swap in the new numbers and write two sentences about anything that moved more than 15%, and to show you the Slack post before it goes to #metrics.
It opens each tab, sets the date range, reads, fills. You check every number against its dashboard that first time, which is tedious and worth it. Then save it as a workflow on a Monday schedule. The recurring browser administration page shows what the run record looks like once a job like this has been going for a few weeks.
Sunday is always short
Google’s own notes on data freshness say GA4 can take up to two days to finish processing. A report run at 8am Monday is therefore reading a Sunday that isn’t done yet, and that one fact explains more odd weekly numbers than any misread figure we’ve come across. We’d run it Tuesday morning. Plenty of teams would rather have it Monday with a soft Sunday, and we go back and forth on which is worse. Dashboards that close the day in different time zones cause quieter drift of the same kind.
Charts are the other trap. When a number only exists as a line, dassi has to hover for the tooltip, so point it at the table view underneath if the dashboard has one. If something jumps past your threshold, the report says so in plain words.
What waits for you
Scheduled runs happen in your own browser, so it needs to be open on Monday; if it isn’t, the run starts shortly after you open it. When a dashboard has logged you out, dassi signs back in with whatever your browser’s password manager fills, and any two-factor prompt waits for you. The Slack post or email can sit behind an approval, and when a run needs a decision dassi pings you by Telegram or email, which beats finding out at standup.
The figures go to the AI provider you picked, or through dassi’s relay on included credits. For revenue numbers we’d choose that model on purpose instead of leaving it on whatever got set up first, though we suspect most people never change it.