Analytics & Insights

The numbers your operators actually read.

Daily revenue, channel mix, day-part heatmap, branch comparison — built for the morning coffee, not the board deck. Every number drills down to the receipt that made it.

The question

"What sold last Tuesday at 7pm?" — that question.

Most dashboards look impressive. Most dashboards don't get opened twice. The ones that do answer the question an operator actually has at 8am Monday with a coffee in hand.

We built this page around those questions.

  • What did we do yesterday? Total, by channel, by branch.
  • What sold last Tuesday at 7pm — and was that a fluke or a pattern?
  • Which marketplace pulled its weight last week and which one cost more than it earned?
  • Is the new server better or just luckier with the section?
  • Did the lunch combo cannibalise the à la carte or grow the ticket?
  • Where exactly is that 12,400 in Friday revenue coming from — show me the receipts.

Every question lands on a screen with one chart, one number, and a button that drills down to the receipts that made it.

Two views

Live for the shift. Cohort for the week.

Two views of the same data, on the same screen.

Live

Today's revenue ticking up. Open tickets on the floor. Average prep time on KDS, right now. Which station is behind. Which channel just spiked. The screen the manager keeps open between covers.

Cohort

Last 7 days vs. the 7 before. This month vs. last. Tuesday this week vs. Tuesday last week. The same numbers the manager looked at five minutes ago, but framed for the question "what's changing?"

You switch with one click. No second tool. No data warehouse.

The four lenses

Four lenses. Same catalog. Same receipts.

Revenue by channel

Dine-in vs. takeaway vs. each marketplace. Side-by-side, with marketplace fees pulled out so the number on the screen is what landed in the bank — not the gross before commission.

Item by channel

Which items sell where. The combo that lives on Wolt. The breakfast SKU that's branch-only. The burger that does 60% of Uber Eats volume.

Branch comparison

Two branches, four, twelve — same chart, ranked. Filter by day, day-part, channel, item. Drill into the branch that's lagging.

Day-part heatmap

Seven days across, the day broken into 30-minute slots down. Tangerine where you're hot, cream where you're cold. The staffing decision is on this screen.

Plus the smaller four that operators ask for the moment they see the big four:

  • Repeat customer share — what percentage of last week was somebody who came back.
  • Average ticket — by channel, by day-part, by branch.
  • Top performers — top items, top servers, top channels, this period vs. last.
  • Period comparisons — yesterday, last week, last month, last year. Same screen, scoped differently.
Drill down

Every number is a stack of receipts. Click it.

Reports that don't drill down get distrusted. We've sat with enough operators who've stopped opening their old dashboard because the totals didn't match what they remembered from the floor.

So every number on this page is clickable.

The Friday revenue total opens the list of every ticket that made it. The "Uber Eats +18%" stat opens the orders that drove it. The day-part heatmap cell at Tuesday 7pm opens the 41 tickets that landed in that 30-minute slot.

You can keep drilling — channel → item → branch → server → ticket → receipt — until you're looking at the line items the customer signed for.

Take it with you

Export to CSV or Excel. Your numbers, your laptop.

Operators don't trust software that locks the data inside it. Neither do we.

Every screen exports. CSV for the accountant, Excel for the partner who wants to model it, PDF for the franchisor's monthly report. The exports carry the same drill-down hierarchy the screen does — receipts included, not stripped.

No "premium reports" tier. No "advanced analytics" upgrade. The export button is on every screen on every plan.

By design

No engagement score. No black-box "insight of the day".

We made a deliberate choice here. The page doesn't show you an algorithm's guess about why Tuesday was slow. It shows you Tuesday — every receipt, every channel, every server — and lets you read it.

Insights, on this page, mean clarity: the right number, in the right shape, fast enough to act on before service.

If you want to ask a question of your data in plain English — "why did Tuesday lunch drop?" — that lives on the AI Advisor page, grounded in the same numbers you're looking at here. Not on this screen. This screen is the operator's view.

Bring last Friday

Bring last Friday. We'll show you what it actually did.

20 minutes with our team. Pull up your operation — channel mix, day-part, branches — and we'll show you the screen we'd open with our morning coffee. Live human, your language, under two hours when it breaks. Live in seven days when you sign. Reports are included — no module fees.