Build a weekly before-and-after scoreboard from a Google She

How this helps you

You can prove whether a change worked with before and after numbers that update each week.

✦ Try it

Build a weekly scoreboard Page from [sheet link]. Compare baseline weeks with the weeks since [change] went live on [metrics]. Put a short what-changed summary at the top. Refresh it every Monday at 8am from the sheet.

What they did

To show whether a change worked (again with an invented business), Kacper Rutkiewicz gave his Bot a Google Sheet link and asked for a weekly scoreboard comparing baseline weeks with the weeks since the change: follow-up time, share of quotes followed up, jobs booked and revenue booked, with a short what-changed summary at the top, refreshed every Monday at 8am. The page shows the comparison, charts and the table. He then added a row to the sheet and asked the Bot to run the routine, and the numbers updated. He said building and refreshing his pages barely moved his usage on a higher plan, and that it may differ on cheaper plans.

Who it's for: Anyone proving the effect of a change to a client or team.

How to try it

Keep the data in a Google Sheet (or export a CSV) with a date column.
Ask for a scoreboard with the baseline period and the change date clearly defined.
Ask for a short what-changed summary at the top, then charts and the table.
Ask for a Monday refresh routine.
After adding data, ask it to run the routine and check the data-as-of date shows your newest row.
Share it only with the people who need it.

What to expect

A page with before and after numbers, charts and the source table.

Common mistakes

Not checking the data-as-of date after a refresh. In his demo it did not show the newest date he expected.

Related tips

Turn a messy CSV into a report that says what to fix first: Hand your Bot a messy export and ask for a cleaned, scored report with a do now / do later list.
How Pages stay up to date (and what they cannot do): Pages are not live: a routine rewrites them. Know the limits before you build many.
Share a Page by link, and know who can see and edit it: Anyone-with-the-link pages open without sign-in, viewers cannot edit, and team sharing needs a Teams plan.
A Sunday leadership brief from meeting transcripts and Slack: Once a week, a Bot reads your team's meeting transcripts and Slack and tells you what each team discussed, what was decided, and where it drifts from your priorities.