Run your restaurant
by conversation.

Dayfolio gives your POS, labor, inventory, and accounting a shared vocabulary so you and your agents can reason across all of it. Ask follow-ups, delegate the reports, and open each morning to a custom briefing at 6am.

See how it works
ClaudeCowork
Online

How did we do last week vs target?

ClaudeSonnet

Revenue beat target by 4.1% at $182k. Prime cost came in at 61.4%, 1.4 pts over the 60% target, mostly driven by Saturday dinner labor. Food cost was in line.

ClaudeSonnet
Revenue by day versus targetTarget $25kMon22.4Tue24.1Wed25.8Thu26.7Fri31.2Sat33.6Sun18.2Revenue ($k)

Revenue by day vs $25k target. Saturday outperformed at $33.6k.

Why was Saturday dinner labor so high?

ClaudeSonnet

Two dishwashers overlapped from 5 to 7pm, plus an extra line cook called in to cover projected volume that didn't materialize. Labor was 34% vs the 28% target.

ClaudeSonnet
Saturday labor percent by hourTarget 26 to 30%1113151737%34%1921Labor % · Sat · hour of day

Labor % by hour, Saturday. Spike sits at 17:00 and 18:00.

Draft the Monday op meeting agenda around this.

ClaudeSonnet

Here's a starter agenda for Monday, 30 min, kitchen + FOH leads:

  1. Saturday labor review. Walk through the 5 to 7pm overlap and agree on a staffing rule for forecasted dinner volume.
  2. Prime cost reset. Confirm the 60% target for next week and the levers we're pulling (dishwasher scheduling, on-call cook policy).
  3. Forecast discipline. When we call an extra cook, require a volume threshold and a named approver.
  4. Owner and due date on each item before we break.
The problem

Your systems don't talk.

POS, labor, recipes, accounting. Four silos, four logins, one spreadsheet every Sunday morning.

Five systems, five versions of the truth. I'm building the sixth one by hand every Monday.

Sales, labor, food cost, rent. Each in its own silo. The daily profit number, the one I actually care about, I stitch together myself.

Half my sales live in one place, half in another, and the numbers never quite agree.

How it fits together

A common language for your stack.

Your operational domain, in one ontology, exposed through one MCP connector. Dayfolio ingests every source system, normalizes the nouns and the verbs that tie them together, and delivers it back as briefings, chat, and agent skills.

  • Ingest. POS, labor, inventory, accounting · every dialect lands in the same schema.
  • Normalize. Location, daypart, shift, menu item · one ontology everyone reasons over.
  • Deliver. Briefings, chat, agent skills · the same data, three operator surfaces.
Connectors

We speak your stack's languages.

Don't see yours? Setup includes a custom connector.

What you get

A cowork agent, grounded in your whole restaurant.

Briefings are the base layer. On top you get a real conversation partner that understands sales, labor, inventory, and the GL.

How was last Saturday?
Saturday ran a little hot on labor. Sales landed at $8,412, 6% above last Saturday, but labor came in at 31.2%

Have a conversation with your restaurant

Ask follow-ups in plain English. Your cowork agent is grounded in the whole restaurant, no new app to log into.

Drafted by Claude
Monday Agenda
  • Review Saturday labor vs forecast
  • Call produce vendor re: variance
  • Finalize Q2 menu pricing

Delegate the reports

Ask Claude Cowork to draft the Monday agenda, the investor update, the end-of-month variance note.

1
Dayfolio6:02am
Yesterday at Folio BistroSales $8.4k, labor hot on Sat, one decision today

One briefing, waiting at 6am

Tuned to your KPIs, your thresholds, your operator voice. The base layer, automated.

Toast logo
7shifts logo
QuickBooks logo
Square logo
OpenTable logo
DoorDash logo
Dayfolio

Fits the stack you already run

Toast, Square, Lightspeed, QuickBooks, 7shifts, and more.

Pricing

One plan, one way out.

No seat math. No feature tiers. Setup is scoped work, not a sales gate.

Limited to 5 founding customersQ3 2026
Today
The old way

What most groups run instead, and what every Sunday morning costs.

  • ~8 hrsper week

    rebuilding the same Sunday spreadsheet

  • ~5 daysper ask

    lag on a CFO ad-hoc question like 'why was prime cost off?'

  • 6 to 10weeks

    to spin up a new dashboard through IT

With Dayfolio
$250/ location / month
annual commitment
from $7,500one-time setup, connector mix dependent
What you get
  • POS, accounting, labor, and inventory connectors
  • Report personalized to your KPI targets and operator voice
  • Custom agent skills for your Sunday checklist
  • Kickoff, integration, and hand-off in 2 weeks

20 minutes, real operator questions, your data, not a canned deck.

Readyforyourautomated6ambriefing?

20 minutes. Real operator questions. Your data, not a canned deck.

No credit card · Quick to answer · Set up in two weeks