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
WASTE
SIGNALS
PROFILE

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

INDEPENDENT RESTAURANTS
FAST CASUAL TEAMS
CAFÉS
TAKEOUT & DELIVERY
SMALL MULTI-UNIT GROUPS
NO HARDWARE
BUILT FOR OPERATORS
WASTE VISIBILITY → ACTION
INDEPENDENT RESTAURANTS
FAST CASUAL TEAMS
CAFÉS
TAKEOUT & DELIVERY
SMALL MULTI-UNIT GROUPS
NO HARDWARE
BUILT FOR OPERATORS
WASTE VISIBILITY → ACTION

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.

The goal is not more charts. The goal is a cleaner read on money lost, repeated reasons, pressure shifts, and what to adjust next.

CORYN.CA / WASTE DASHBOARD
Last 7 Days
Last 30 Days
All Time

Money Lost

$428

Last 7 days

Units Wasted

63

Tracked units

Waste Logs

21

Recorded events

Top Loss Item

Chicken

Highest cost

Main Reason

Overprep

Recurring

Alerts

3

Action needed

Waste trend

Units Wasted

LAST 7 DAYS

Units Wasted

63

+8%
80604020Apr 01Apr 02Apr 03Apr 04Apr 05Apr 06Apr 07

Cost distribution

Top 3 share

Top 3

59%

Chicken Breast
28%
Salmon Fillet
18%
Rice Batch
13%

Top loss items

01

Chicken Breast

Top loss item

$146

02

Salmon Fillet

Top loss item

$91

03

Rice Batch

Top loss item

$68

What changed

PM shifts are now driving most of the variance.

Waste on top-selling days is drifting higher when demand peaks around bowls and proteins.

By shift

PM

By level

High

Main reason

Overprep

Per log

$20

Operator view

Clear signals at a glance.

Money lost
Top loss items
Reason patterns
Next prep action

What to do next

Lower PM protein prep

Thursday and Friday PM shifts are consistently showing the same pressure pattern.

What changed

Waste up 14%

Protein-heavy days are drifting upward faster than normal service variation.

Quick take

Less guesswork

CORYN is clarifying where margin is leaking before it becomes routine.

Adaptive recommendations

Waste data becomes an operating recommendation.

Not just reporting what happened, but clarifying what deserves a tighter prep decision next.

Where waste happens

PM shift.
High volume.
Protein-heavy mix.

Example prep items

Units wasted by prep item

PM SHIFT

Chicken Breast

18 units

Rice Batch

11 units

Salad Mix

8 units

Sauce Pan

6 units

By shift

PM

By business level

High

Top waste reason

Overprepared

Top-selling days

Thu / Fri

Product depth

More than a chart

WHAT TO DO NEXT

Lower PM chicken prep.

Protein-heavy evenings are creating the clearest cost concentration.

WHAT CHANGED

PM waste is climbing.

The pattern is holding across multiple top-selling days.

QUICK TAKE

Less guesswork.

Teams get a sharper sense of where margin is slipping.

ADAPTIVE RECOMMENDATIONS

Signals that turn into action.

Not just dashboards. Clear operational next moves.

Money Lost
Units Wasted
Waste Logs
Top Loss Item
Main Reason
Alerts
Waste Trend
Top Driver
Per Log
Top 3 Share
By Shift
By Business Level
OPERATOR VIEW
TIME RANGE SELECTOR
TOP KPI CARDS
WASTE TREND
TOP LOSS ITEMS
WHAT TO DO NEXT
WHAT CHANGED
ADAPTIVE RECOMMENDATIONS

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.