Founder's Edition
WASTE INTELLIGENCE FOR RESTAURANTS

Waste less.
Prep sharper.
Protect margin.

CORYN turns everyday waste logs into a clearer operating read: what happened, what keeps repeating, and what to tighten before the next shift.

CAPTURE WHAT HAPPENED

SEE REPEATED DRIVERS

TIGHTEN NEXT PREP

Waste log

Item, amount, reason

Context

Shift and business level

Review

Top losses and trends

9:41
◖◗◖86%

WASTE VISIBILITY

Weekly loss trend

SAMPLE

Money lost

$428

Logs

21

Per log

$20

Avoidable loss

$428

7 DAYS

Highest loss item

CHICKEN BREAST

Recommended action

LOWER PM PREP

PERFORMANCE SIGNAL

Quick take

Driver

Protein

Shift

PM

Action

Reduce prep

HOME
LOG
REPORTS
ACTIONS
INVENTORY
ITEMS
SETTINGS

WHY PHONE-FIRST

Faster. Tighter.
More operator-native.

Log the item, amount, and reason from a phone while the shift is still moving. Add deeper context later when the rush is over.

PERFORMANCE SIGNAL

Repeated waste patterns become
easier to see sooner.

Driver

Protein

Shift

PM

Action

Reduce prep

Alerts

3

Top 3 share

59%

By shift

PM

RESTAURANT REALITY

The product has to survive the shift.

Waste is noticed while prep is moving, orders are landing, and the team is already thinking about the next task. CORYN is designed around that reality: capture quickly, add context only when it helps, and review the pattern before the next prep decision.

LIVE SERVICE MOMENT

BUILT AROUND THE PRESSURE OF SERVICE

Waste happens in motion,
not after the fact.

CORYN is built for the moment waste is noticed, not just the office review after service. Capture the signal while the context is still fresh.

Moment

Real kitchen pressure

Capture

Fast item + reason logging

Handoff

Clearer next prep

Restaurant operator working through service

Operator view

Built for the person running the shift.

Phone-first logging keeps the workflow close to the kitchen instead of buried on a back-office laptop.

What gets captured

During service

Item, amount, reason

Fast enough to log while the context is still fresh.

After the rush

Shift, business level, notes

Only add context that explains the loss pattern.

Before next prep

Repeated drivers

Review what should be held, reduced, or watched.

Prep detail in restaurant kitchen
Prep detail

Prep pressure appears before the numbers do

The first useful signal is often simple: what was overprepped, when it happened, and whether it keeps repeating.

Food texture in restaurant setting
Cost signal

Food waste is still food cost

Every tray, batch, and portion has margin attached to it. CORYN keeps that cost visible.

THE OPERATING LOOP

From waste event to better prep.

Start with the fastest possible waste log, add only the context that helps explain the loss, then turn repeated patterns into a clear prep adjustment.

01
CAPTURE

Capture the waste event

Record what was wasted, how much, and why it happened without slowing down service.

Voice or quick tap

built for real-time logging

CHICKEN
2 TRAYS
PM SHIFT
OVERPREPARED
02
CONTEXT

Add operating context

Add lightweight shift details like business level, guests served, top sellers, or conditions when they help. The waste log comes first; deeper context can wait until the rush slows.

Guests served

186

Shift

PM

Top seller

Chicken Bowl

Conditions

Rush + rain

03
ACTION

Get the next move

Surface the biggest loss drivers and the clearest prep adjustment for the next shift.

Recommendation

Lower PM prep

Evening protein output is drifting above demand on heavy service days.

74%

ROI CHECK

Can the tool pay for itself?

A restaurant owner should not have to decode a spreadsheet to understand value. The clearest ROI story starts with one visible waste number, sizes the annual exposure, then compares a modest improvement against the plan cost.

Important guardrail

This is not a savings guarantee. It is a plain break-even lens using the sample dashboard number so operators can judge whether tighter waste visibility is worth the spend.

Operator receipt

$428

weekly waste loss visible in the sample dashboard.

The buyer question

If CORYN helps reduce even a small share of repeated waste, how much room is left after the software cost?

Step

01

Start with a visible weekly leak

sample dashboard waste

$428

This is the kind of number an operator can actually act on: waste that happened, with enough context to explain it.

Step

02

Size the problem over a year

$428 x 52 weeks

$22,256

This is not a forecast. It is a simple way to show how small weekly losses become real annual margin pressure.

Step

03

Test a modest improvement target

$22,256 x 10%

$2,226

A 10% reduction is intentionally conservative. It gives the buyer a clear break-even conversation without overstating savings.

Core plan cost

$1,788

$149 per month, annualized for the comparison.

Room after software

$438

Based on the 10% improvement test, not a promised result.

Practical takeaway

The sale is margin clarity, not a miracle claim.

PRODUCT READ

A waste dashboard built
for action, not noise.

Even on the homepage, an operator should be able to see what was wasted, what it cost, why it repeated, and what to tighten before the next shift.

COMMAND CENTER

Overview

What happened, what it cost, and where to look first.

Waste TypeAllPrep WasteService Waste
Date RangeLast 7 DaysLast 30 DaysAll TimeRefresh

ALL WASTE

$438

152 waste logs

Estimated food cost lost

BEFORE SERVICE

$412

prep, spoilage, closing

94% of loss

DURING SERVICE

$25.78

4 remake / return logs

6% of loss

UNKNOWN COST

1

waste log needs cost

Fix these for cleaner dollars

COST COVERAGE

99%

151 of 152 logs

Known or estimated cost

THIS WEEK AT A GLANCE

What happened

NUMBERS

WASTE COST

$438

152 logs | $2.88/log

ITEMS

BIGGEST LEAK

Chicken Karaage

$61.82 | 19 logs

REASONS

WHY IT HAPPENED

Overprepared

81 logs | $179

WEEKLY LOSS TREND

Cost of waste over time

vs previous period
$52$45$30$15$0May 5May 7May 15May 16May 17May 19May 22May 23May 24May 26

DAILY MOVEMENT

Up +383.3%

Compared to the previous logged day.

PERIOD MOVEMENT

Prep waste still drives 94% of loss.

Most dollars are still leaking before service.

OPERATOR READ

Where to review before the next rush

May 6-27

PRESSURE DAY

May 15 · $51.58

2 logs on the highest-loss day.

VERIFY FIRST

Chicken Karaage

$61.82 across 19 logs.

WINDOW TO CHECK

PM prep

$312 in 127 logs.

FRESH SIGNALS

What changed

Quick notes on what moved since the last read.

5

NOTES

SIGNALS

Loss Pressure

Needs Review

$437.50 recorded in this range.

INVENTORY

Chicken Karaage

Cost Missing

Add the latest receipt, purchase qty, or item cost so this read stays accurate.

CHARTS

Up +383.3%

Recent Movement

May 26 vs the previous logged day.

RECENT

Green Onion

Last Log

10 portion · Damaged · $1.20

INVENTORY CHECK

Chicken Karaage

Action

37 wasted with no received amount.

NEXT MOVE

Take action on the top opportunities to reduce waste.

Open action plan

Recent Waste Logs

View all logs
G

Green Onion

Known Cost

10 portion · Damaged · May 27 · 3:30 PM

$1.20

B

Burger Mix Brisket Blend

Estimated Cost

5 order · Leftover · May 20 · 12:41 PM

$19.70

C

Corn

Known Cost

25 portion · Spoilage · May 19 · 5:18 PM

$4.30

C

Cream Cheese

Known Cost

10 portion · Damaged · May 18 · 4:18 PM

$3.90

WHERE MONEY IS LEAKING

Loss by item
1

Chicken Karaage

19 logs, 39 units

$61.82

2

Chashu Pork Belly

3 logs, 30 units

$57.60

3

Fresh Salmon

11 logs, 21 units

$48.17

4

Tonkatsu Pork Cutlet

11 logs, 15 units

$45.67

5

Braised Pork

1 log, 24 units

$43.68

WHY CORYN

A sharper product because it refuses to be broad.

Most restaurant platforms grow outward until waste becomes one more tab. CORYN is built in the opposite direction: start with the loss, understand the operating context, then turn that signal into a tighter prep decision.

The honest moat

A bigger platform can add a waste screen.

The harder part is getting a busy kitchen to use it consistently and translating those logs into next-day prep language. That is where CORYN stays focused.

01Capture

The waste event comes first

CORYN starts with what was wasted, how much, when it happened, and why. That keeps the system tied to the actual kitchen moment.

02Context

Only the details that explain the loss

Shift, business level, top sellers, guests served, and notes give the waste log enough context without turning the workflow into admin work.

03Action

The output reads like prep direction

The recommendation layer points operators toward the next adjustment instead of leaving them to interpret another dashboard.

Product thesis

Waste is not a reporting category. It is an operating loop.

The system is strongest when every screen connects back to one question: what needs to change before the next shift?

Signal 01

Waste event

Signal 02

Shift context

Signal 03

Prep decision

01Field note

Broader systems start with back-office workflows.

CORYN starts with the wasted item, the service moment, and the prep decision that follows.

02Field note

Dashboards often explain the past too late.

CORYN keeps the next shift visible: what repeated, why it mattered, and what to tighten.

03Field note

Generic reporting is easy to copy.

The defensible layer is operator adoption: phone-first capture, kitchen language, and prep-specific recommendations.

CORYN

Waste visibility built for
better restaurant decisions.

Reduce avoidable food waste. Tighten prep output. Run a calmer, sharper kitchen.