Skip to content
Konsul
Menu
All examples

Example: Monthly report

Last month on one page, by the 2nd.

Sales, expenses, payouts and pipeline come together from the tools you already use, into one report in your inbox. Every number says where it came from and how fresh it is. A source that is out of date gets flagged, not counted.

By hand

Building the monthly report. About 120 minutes each time, every time it comes up.

With a build

Handled for you, and nothing reaches a customer in words you have not approved.

What a diagnostic would check first

The diagnostic decides what gets built, or whether anything should. What follows is one way it could look.

  1. Which decisions the report is for
  2. Which numbers change those decisions

One way it could look

Open the working example

Quick look. The full example has every screen. Made-up bike shop and numbers. Nothing is sent from this page.

Want one shaped around your business?Tell us what's breaking

How it would work

  1. Step 1

    It gathers

    Each tool fills its own tab in one Google Sheet you own, by a connector or a monthly export. Each tab carries the date it was last updated.

  2. Step 2

    It checks

    A source older than you allow, or one that stops before the month ended, is flagged and left out. Payouts are checked against sales.

  3. Step 3

    It writes

    Totals, the change on the month before, and a few plain sentences written by fixed rules, not AI. The same numbers always give the same words.

  4. Step 4

    It reaches you

    A Google Doc from your template and a Report tab in the sheet, with the link emailed to you on the 2nd. Nobody else gets it.

Waits for your OK

  • Who sees it. The report goes to the one owner email in Settings. Sharing it further is your call.
  • What counts as stale. You set how old a source may be and how far payouts may drift from sales before it is flagged.
  • Fixes to the numbers. The report points at a gap. A person corrects the tool it came from.
Watched by Kustos

Konsul builds it. Kustos keeps it running and right.

Once it is live, Kustos checks it on a schedule and drafts a fix when something breaks. A person approves every change.

What could go wrong

A connection lapses and a number stops updating without anyone noticing.

Every source carries an as of date, and a stale one is flagged and left out. QuickBooks Online, for example, ends a connection after 100 days without use, and its token changes each time it is refreshed, so the newest one has to be saved.

Payouts and sales disagree.

Payouts plus processor fees are compared with sales. A gap over your tolerance is flagged in dollars. Cash sales never reach a payout, so the Sales tab should hold card and online sales, or the tolerance should be wider.

Data fees creep in.

QuickBooks began charging for API use in 2025. Its free Builder tier includes 500,000 metered CorePlus credits a month. Connector tools charge too: the Coupler.io Starter plan was listed at $32 a month. Prices change, so check before you pick one. A monthly export costs nothing.

A summary sentence gets read as advice.

The sentences say up, down or flat with the percent, and name the gap. They describe the month. They do not recommend anything.

Next step

Start with the process that costs you the most.

Rough numbers are fine. Describing it takes about three minutes.

Tell us what's breaking