A fictional case study

Meet Pecan & Salt — and Maria's morning.

Pecan & Salt is a multi-location Austin restaurant. Maria runs it with her brother Carlos. She's been in the kitchen at 7am for fifteen years. This is what changes when Daily Ops Copilot fits into her morning.

01 — The operator

Maria runs three Austin locations.

South Lamar is the flagship. East Cesar Chavez is busiest for catering. Cedar Park is the new one — and the one she can't visit during the week. Her brother Carlos runs the South Lamar kitchen. Jasmine runs East. Tony is in Cedar Park.

Maria knows her business. What she needs isn't more software. It's a way to see all three locations on her phone before service starts, with the things she actually has to act on already at the top.

Concept
Pecan-smoked Texas BBQ with Tex-Mex influences. Brisket, migas tacos, chipotle queso.
Locations
South Lamar · East Cesar Chavez · Cedar Park
Owner
Maria Reyes — second-generation operator, runs ops with her brother Carlos.
Where she struggles
Too many tools, none of them talking to each other. Cedar Park drifts. Catering calls during dinner rush go to voicemail. Vendor prices creep up unnoticed.
02 — The stack

She already pays for the right tools.

Maria has been adding tools for years. Each one solves part of the problem and creates a new island. The data she needs is all here — it just doesn't talk to her or to itself.

Toast
POS · all 3 locations
7shifts
Scheduling · staff app
MarketMan
Inventory · low usage
QuickBooks Online
Books · Carlos's wife
Mailchimp
Customer email list
Google + Yelp
Reviews · responded by hand
Toast Tables / Phone
Voicemails next morning
Vendor inboxes
Strube Ranch, Sysco, others
03 — Where CoreEngine fits

An operating layer between the tools and the team.

CoreEngine doesn't replace anything. It sits on top — reading from the tools Maria already runs, synthesizing what matters, and delivering it to the people who need it in the form they'll actually use.

Tier 1 — The operators
Maria · Carlos · Jasmine · Tony
Phones · SMS · Email · WhatsApp
Tier 2 — CoreEngine
Daily Ops Copilot
Synthesis · alert routing · adoption telemetry · cross-tool sync
Tier 3 — Existing tools (already paid for)
Toast 7shifts MarketMan QuickBooks Mailchimp Google + Yelp Phone / Twilio Vendor email

Every box at the bottom is a tool Maria already pays for. Daily Ops Copilot is the middle layer — small, focused, replaceable. We don't try to own her data. We make her data useful.

04 — Maria's morning

One screen, with coffee.

Maria's phone buzzes before she's out of the kitchen prep area. The briefing is short on purpose. The things needing her attention are at the top. The work that's already handled is at the bottom — so she knows the system is doing its job without her.

Daily Briefing Tue · 7:00am
Pecan & Salt — across all locationsYesterday: strong Sunday — patio weather drove dine-in. Top sellers: brisket plate, migas tacos, pulled pork sandwich. Today's forecastWeather: warm and sunny — patio bump expected. Local: ACL Live show tonight — South Lamar runs late. Catering: one confirmed (Apple offsite, picks up midday at East Lamar). ⚠ Needs your attention1. CEDAR PARK: flat for the second weekend in a row. Tony texted "slow." Suggest a quick call today. [Call Tony] 2. STRUBE RANCH: brisket invoice posted overnight at a higher rate. Pattern is escalating. [See variance] 3. SOUTH LAMAR: schedule trending into overtime if not redistributed. [See schedule] This week's lift• Catering inquiries captured by missed-call recovery. • Migas tacos: best week ever — push on social? ✓ Handled overnight• Sysco invoice — extracted, matched, no variance, posted to QuickBooks. • Reviews collected and responded automatically (one flagged for your reply). • Pre-shift checklists complete at all locations by mid-morning.— CoreEngine · reply STOP to pause · reply HELP for the dashboard
05 — When something needs attention

An alert is a flow, not a notification.

Take the Strube Ranch vendor variance. By the time Maria reads about it in the briefing, the Copilot has already done five things in the background. She doesn't see the work — she sees the decision.

SIGNAL
Vendor invoice arrives in the inbox.
Strube Ranch sends an invoice to orders@pecanandsalt.com. Carlos doesn't see it for two days normally. The Copilot sees it within minutes.
EXTRACT
Pull the line items, match the vendor.
Brisket per-pound, total weight, total cost. Match Strube Ranch's history in MarketMan. Identify what changed.
COMPARE
Check against the last several invoices.
Detect the price-per-pound has been creeping up — three weeks of small bumps, and now a larger one. Pattern recognized.
DECIDE
Surface only when it matters.
A one-time bump might not surface. A pattern does. The Copilot decides this is one of the three things Maria sees today — and drafts the action options.
DELIVER
One line in her briefing. One tap to act.
"STRUBE RANCH: brisket invoice posted overnight at a higher rate. Pattern is escalating. [See variance]" — leading to a screen with three options: call vendor (script attached), substitute alternate supplier, or accept and move on.
LEARN
Whatever Maria chooses, the Copilot remembers.
If she dismisses three brisket alerts in a row, the threshold gets recalibrated. If she calls the vendor, the outcome gets logged. Each decision tunes the next briefing.
06 — What gets handled overnight

The work Maria didn't have to do.

The point of the briefing isn't to give Maria more to read. It's to make sure she only reads what she has to. Most things the Copilot handles never appear in the briefing at all — only a single line confirming they happened.

Sysco invoice processed. Extracted, matched against MarketMan, no variance flagged, posted to QuickBooks for Carlos's wife to review.
Reviews responded. Positive Yelp and Google reviews collected, drafted responses queued, simple acknowledgments auto-sent. One mixed review flagged for Maria's personal reply.
Pre-shift checklists complete. Each location's opening checklist sent to the GM, completion tracked. Tony at Cedar Park was the last to mark complete.
Catering inquiries captured. Last night's missed dinner-rush calls intercepted by the AI receptionist. Quotes drafted. Queued for Jasmine to call back this morning.
Reorder triggered. Pinto beans below par at Cedar Park — vendor reorder request drafted, waiting for Tony's tap-to-approve.
End-of-day summary archived. Last night's per-location wrap saved for Maria and Carlos's monthly review.
07 — How we get here

From first call to running operation.

We don't show up with a finished product to plug in. We start by understanding the operator. Then we build only what's missing.

Phase 0
Discovery
One week. Onsite for one shift per location. Tool audit. Operator interview. Written scope for what comes next.
Phase 1
Pilot
One location goes live. The Daily Briefing, the most important alerts, the first integrations. Adoption is measured weekly.
Phase 2
Operations Layer
All locations on the Copilot. Per-GM views. Cross-tool orchestration. The retainer kicks in. The system runs.

Phased. Fixed-fee per phase. Stop at any gate. We'd rather you walk early than be locked in.

Your operation

If your morning looks anything like Maria's, we should talk.

The data you need has been sitting in your tools for years. Daily Ops Copilot is the layer that meets your operators where they actually are.