DashForge
← All work

Small-batch bakery

Sales, waste and tomorrow's bake sheet for a small bakery

Proof is for a small bakery's owner at 5am, piecing yesterday together from the till, a production spreadsheet and a notebook by the ovens.

Try the live demo See the screens

CloudPremade

/today
Proof on a desktop: The morning brief
Proof on a phone: The morning brief
About Proof

Proof is for a small bakery's owner at 5am, piecing yesterday together from the till, a production spreadsheet and a notebook by the ovens. The item that sells out looks like the best earner until someone takes off the cost of butter and time. Proof reads the till export and the production sheet overnight, and by morning it shows what each item earns, what went in the bin and a suggested bake sheet for tomorrow. In the demo bakery, Hearth & Hollow, the head baker signs off the bake sheet and never sees a single cost.

New data entry
None

reads the files the bakery already has

Earnings
Per item

after ingredients and labour

Morning figures
Overnight

plus Import now for the owner

What it does

What does Proof do?

  • Nothing to type in

    Sales and production come from files the bakery already has. Staff enter nothing new.

    /margins
    Proof: Earnings against sales

  • Nightly imports

    The till export and the production sheet are read every night, and the owner can run an import any time.

    /bake
    Proof: Tomorrow's bake sheet

  • Earnings per item

    Each item's price minus its ingredients and hands-on time, ranked beside how many sold.

    /waste
    Proof: Closing counts
The problem

What problem does it solve?

Yesterday's figures are split between the till, a production spreadsheet and a notebook by the ovens. The croissant sells out every morning, so it looks like the star until someone subtracts the butter and the lamination time. Tomorrow's quantities come from memory, and the bin at closing shows how that went.

How the demo handles it

Proof imports the till export and the production sheet every night and joins them, so nobody types anything new. It ranks every item by what it earns after ingredients and hands-on time, and counts what was baked and not sold. Tomorrow's quantities come from the last six of the same weekday, rounded to full trays, for the head baker to adjust and sign.

  • Waste with a photo

    At closing, the count of what went in the bin is logged with a photo of it.

  • A suggested bake sheet

    Tomorrow's quantities start from the last six of the same weekday, rounded to full trays, ready to adjust and sign.

  • Two logins

    The owner sees costs and margins. The head baker sees the bake sheet and waste, with no costs at all.

Try it yourself
/margins
Proof: Earnings against sales, on a desktop
Proof: Earnings against sales, on a phone
/waste
Proof: Closing counts, on a desktop
Proof: Closing counts, on a phone
Design choices

Why is it built this way?

  • It only reads

    Proof reads exports from the till and the production sheet and never writes back to them, so it can't break either one.

  • Earnings beside sales

    In the demo data the croissant sells more than anything else and ranks third on earnings, because butter and lamination time take most of its price.

  • Ready before opening

    The import runs overnight, so yesterday's figures are waiting on the morning screen when the ovens go on.

Screens

What does it look like on a computer and a phone?

Today's bake sheet, yesterday's takings and waste, the items that sold out, and the waste streak and bake sheet accuracy against their bests.

/today
Proof: The morning brief, on a desktop
Proof: The morning brief, on a phone

What is it built with?

Common, well-documented tools, so any developer you hire later can pick it up and keep working on it. Hover over or tap any of them to see what it does.

Who uses it

Who would use Proof, and when?

  • Opens the suggested bake sheet at the bench, changes what they know better, and signs it.

    The head baker, planning tomorrowScenario

  • Moves the price or the cost of butter and watches where the item lands among the rest.

    The owner, pricing an itemScenario

  • Photographs the bin and counts what's in it, item by item, before switching off the lights.

    Whoever closesScenario

FAQ

What do people ask about Proof?

  1. 01Can I try Proof before talking to anyone?

    Yes. The demo is a working app with sample data. Ask for access and we'll email you a sign-in link. Nothing you change there affects anyone.

  2. 02Is it cloud or local?

    Cloud. Your team signs in from anywhere, on a phone, a laptop or the shop computer.

  3. 03Is it premade, adapted or custom?

    Premade. It works as it is, and we set it up with your name, your people and your data.

  4. 04What does it run on?

    Next.js 16, TypeScript, Supabase, PostgreSQL, Row-level security, Scheduled imports, Private file storage, Mobile-first UI.

  5. 05What problem is it solving?

    Yesterday's figures are split between the till, a production spreadsheet and a notebook by the ovens. The croissant sells out every morning, so it looks like the star until someone subtracts the butter and the lamination time. Tomorrow's quantities come from memory, and the bin at closing shows how that went.

Want to try Proof?

It's a working app with sample data. Ask for access and we'll email you a sign-in link, usually within a business day.

Request the demo