Weekly business reporting digest

Monday's numbers without Monday's spreadsheet hour: revenue, refunds and the week's movement, assembled on schedule and posted where the team already looks.

Talk to us Read the docs

The brief

Written like you’d brief a person.

This is the whole setup - a procedure in plain language, with tools and specialist agents referenced inline. When it runs is not written here: that’s the trigger, configured beside it.

Pull last week's invoices with #yekar.stripe.list-invoices, append the week's numbers to the report with #yekar.google-sheets.append-rows, and post the digest to the leadership channel with #yekar.slack.send-message.

How it runs

From trigger to logged outcome.

Trigger

Schedule - Mondays at 7:00 in your business's timezone

Pull the numbers
Collects the week's payments, refunds, and outstanding invoices.
Update the record
Appends the week to the running report sheet.
Write the digest
The week in one post: the numbers, the movement, the outliers.

Where people stay in control

Nothing consequential runs on its own.

The digest is read-only reporting; it changes nothing and can be reviewed before posting.

Tools it uses

Runs on accounts you already have.

Stripe
Google Sheets
Slack

Connected once, governed per agent - this use case gets only the tools listed here.

Illustrative savings

$400–$1,100 / month

Assumes a weekly reporting ritual of 2–4 hours across the people who feed it.

Illustrative monthly savings, estimated from typical handling time at public salary benchmarks, reviewed August 2026. Not a promise or a guarantee - your numbers depend on volume and process.

What makes this dependable

Put it to workRun recurring work on the business's clock Put it to workControl schedule catch-up Operate and improveSee which agents are reliable - and which are slow

All use cases →