See an exampleGet a pilot dashboard

Use cases

Dashboards for operations managers

Orders, refunds, and revenue from the export you already pull. Totals rows and blank amounts are left out, and listed.

Get a pilot dashboardSee the example
Paid orders per day, September412 orders
Data ends Sep 28

1 totals row and 4 blank amounts left out · Sample data

Operations reports break in small ways: a subtotal row counted twice, a blank amount read as zero, a date read as the wrong month. Each one is caught, left out, and written on the receipt.

The numbers should match the export. Every time.

Reports operations teams rebuild every week

Monthly orders reportRefund watchRevenue by monthFulfillment timesSupport backlogInventory turnsOn-time shippingReturns by reason

What changes with receipts

  • 5rows left out of 1,203
    Left out
    1 totals row, 4 blank amounts
    Fixed
    Dates read as day/month

    Exports with all their quirks

    Merged headers, subtotal rows, mixed date formats. We clean them, and the receipt lists every change.

  • 2.4%refund rate, September
    Counted
    10 of 412 orders
    Definition
    Refunded ÷ paid orders

    Refunds handled one way

    Paid revenue minus refunds, defined once, so the refund rate and the revenue always agree.

  • Sep 28last day with data
    Check
    2 days missing
    Effect
    Shown on every September number

    Partial months called out

    If September's data stops on the 28th, the number says so instead of looking like a slow month.

  • +8.2%paid revenue vs August
    August
    $11,530, 389 orders
    September
    $12,480, 412 orders

    Trends you can trace

    Each month in a trend keeps its own receipt, so a jump can be traced to the rows that caused it.

An example dashboard

Built the way your pilot would be. Click any number to see its receipt.

Sample data · not a real company
Orders report, SeptemberClick a number

Paid revenue by month ($k)

Receipt

Orders, September

Definition
Orders with a payment
Source
orders_q3.xlsx, 412 rows
Left out
1 totals row
Check
Data ends Sep 28
Orders, September
41210 refunded
Definition
Orders with a payment
Source
orders_q3.xlsx, 412 rows
Left out
1 totals row
Check
Data ends Sep 28
Get a pilot dashboard

How this example was built

Metrics we often propose for operations teams

You pick five to seven. Each one comes with a definition like these, written down before we build.

Paid revenue
Paid orders minus refunds.The number everyone means by revenue.
Orders
Orders with a payment.Volume without the noise of abandoned carts.
Average order
Paid revenue ÷ paid orders.Shows whether growth comes from more orders or bigger ones.
Refund rate
Refunded orders ÷ paid orders.An early sign of product or fulfillment trouble.
Time to ship
Median hours from payment to shipment.The customer's first experience.
On-time shipping
Orders shipped by the promised date ÷ orders shipped.Whether promises are kept.
Backlog
Orders paid but not shipped at the end of the day.Tomorrow's workload, today.
Repeat customers
Customers with more than one paid order in the period ÷ all customers.Loyalty in one number.

Questions

Something else? Ask us

Which systems can you read?

Anything you can export to a spreadsheet: Excel, Google Sheets, or CSV. The pilot covers one spreadsheet.

What if our export has totals and blank rows?

We leave them out and list each one on the receipt, so the total still matches what you'd calculate by hand.

Can I check a number myself?

Yes. Each receipt names the file, the rows used, and the rows left out.

Is our data safe with you?

Your spreadsheet is used only to build your dashboard and seen by one person. The AI only sees column names and your goal, never the rows. We delete our copy 30 days after the pilot.

What does it cost?

The pilot is $99 once, credited to your first month at launch. After launch, Solo is $29 a month and Team is $99 a month for up to 5 people.

Other teams