Home Use cases Functions About Contact
Book a demo
Operational finance intelligence · Swiss hospitality

Stop guessing where your margin went.

snodo sits on top of the systems you already run and tells you, to the franc, where margin moved, why, and the one measure that fixes it. It stays in the background and flags a number only when it moves far enough to need a decision.

Autumn 2026 · 60-day pilot · we set up and maintain your recipes
This week · Week 28SAMPLE
32.1%Theoretical food cost · ▲ +3.6 pt vs baseline 28.5%
Cost of sales (wk)CHF 156'400
Net revenue (wk)CHF 518'000
Chicken +18%, beef +11% feeding through recipes
Group Exec Chef · due in 7 days · −CHF 3'850/mo
≈ CHF 12'400/mo recovery in play · +CHF 940/mo measured
One layer, four answers

For every deviation, the four questions no single system answers.

Your POS shows the what. Your accounting shows the result at month-end. snodo is the layer between them that shows the why, continuously, per outlet.

Where

The outlet, the product and the shift where the deviation appears.

Why

The cause, tested against the alternatives and documented.

How much

The effect in francs, not just a cell coloured red.

Which measure

The fix, with an owner, a deadline and a measured result.

What snodo solves

The problems every kitchen knows, and what to do about each one.

01
"Food cost is up, but why?"
Every margin deviation broken down by cause and in francs: purchase prices, recipe costs, sales mix, discounts, inventory differences.
02
Supplier prices creep up unnoticed
Price drift per item × your volume = cost per month, linked to the exact dishes it hits.
03
Duplicate or wrong invoices get paid
Automatic check on capture: duplicates, overbilling and calculation errors stopped before payment.
04
Recipe costs and portion drift stay invisible
Live recipe costing from your invoices; a portion that has drifted becomes visible before it eats the margin.
05
Good insights are never acted on
Every recommendation becomes a measure with an owner, a deadline and an effect that is actually measured.
06
Outlets get compared unfairly
Each outlet is measured against its own history.
How it works

No new system. We don't replace what you run.

01

Connect

snodo plugs in on top of the systems you already run, starting with your POS and invoices. Nothing is replaced, nothing changes in the outlet.

02

We build and maintain your recipes

The hardest part is that most kitchens have no costed recipes, and keeping them current is a chore nobody has time for. So we build them for you and design a simple upkeep workflow around your chef: confirm the set once, then update any recipe with a WhatsApp voice note or a photo. No spreadsheets, no data entry.

03

It watches, you act

snodo stays quiet until something runs away, then hands you the cause, the franc amount and the measure, with an owner and a deadline.

Built for Switzerland

Your data stays in Switzerland, and yours.

Hosted in Switzerland

Your data stays on Swiss infrastructure.

nFADP-compliant

Compliant with the revised Swiss data protection act (nFADP/nLPD).

Four languages

The whole platform runs in English, German, French and Italian.

Where this comes from

Fifty conversations with Swiss operators, one published findings note.

Before building snodo we spoke with around fifty people who run food and beverage in Switzerland, then published what we heard as an anonymised research note. It is where the product comes from, and it is public.

Read the note

See where your margin goes. Try it on your own numbers.

We set up the 60-day pilot, build your recipes and you keep the results. You continue only with your explicit yes, no automatic renewal, no long commitment.

How snodo is used

One layer over the systems you already run.

snodo is not another system to migrate to. It connects the systems you already run, reconciles them and explains where margin moved, so an owner, a chef or an accountant sees the same truth, in seconds instead of hours.

Who it's for

From a single restaurant to a multi-outlet group.

🏛️

Groups & multi-outlet

Consolidated buying power, every outlet on its own baseline, and a suggested transfer instead of a purchase when one outlet is short and another is long.

🏨

Hotels

F&B margin across restaurants, bars and banqueting held together on one page, without adding a controller to the payroll.

🍽️

Independent restaurants

The margin discipline of a group operation, without the back office. The recipes are prepared for you; the chef just confirms.

The 60-day pilot

From connection to a decision, in one season.

WEEK 0

Connect & prepare

We plug into your POS and invoices and prepare the recipes for the pilot outlet. Your chef confirms them in a single session, max. two hours.

WEEKS 1-8

It finds and quantifies

snodo watches quietly and surfaces only what moves money: a price creep, a duplicate invoice, a portion drift, a void pattern, each with the franc amount and the measure.

DAY 60

You decide

The Value ledger shows what snodo found against what it costs. You continue only with your explicit yes, no automatic renewal.

A week in the life

What "it speaks only when something runs away" looks like.

Monday morning · This week

The rooftop bar's void rate 4.8% vs a 1.2% house baseline, concentrated after 22:00. Estimated ≈ CHF 1'250/week at stake.

Theoretical food cost 28.5% → 32.1%. Cause isolated: chicken +18%, beef +11% feeding through the recipes.

Duplicate invoice TG-88412 (CHF 2'340) held before the Friday payment run.

By Friday · Action & Value

Each finding is now a measure with an owner and a deadline, the chicken renegotiation, the roster fix, the portion control.

+CHF 940/month already measured from an earlier portion fix, 17% above what was expected.

Nothing else needed you. Every outlet inside its own range stayed quiet.

Put it on your own numbers.

The screens above use sample data. In a 60-day pilot they fill with yours.

Functions

Every screen, and the problem it solves.

You don't take on every screen at once. You start with the one view that answers your most expensive question, and add the rest as you need them. Here is the full set, grouped by the problem each one solves.

Control
01

This week

The daily control page: only what needs attention.

A balance of the week at the top, explained deviations, recovery potential in francs, then the few points that need action, each with outlet, cause, franc amount, owner and confidence. Everything inside its own range stays quiet.

02

Investigations

The cause machine: from deviation to documented explanation.

Every deviation runs the same chain, trigger, evidence, hypothesis tests, financial effect, confidence, measure, result. You see not only that something happened, but why and with what certainty, down to the single invoice.

08

Action center

Every recommendation becomes an owned, dated measure.

Each measure gets an owner, a deadline and a status from new to measured. Expected and actually measured recovery sit side by side, so the loop closes, visibly, instead of insights getting lost.

09

Reports

The weekly picture on one page, delivered automatically.

Where the margin went, which prices moved, what to do and the open measures, one page management and outlets read in two minutes. Schedule it to arrive every Monday, or send it once without saving.

10

Value

Why snodo pays for itself: a ledger of found versus cost.

Measured (independently confirmed), avoided (money not spent), in progress and even not recovered, each item with its owner and source. Most software asks you to trust it pays off; this one keeps the receipt.

12

Budget

Month-end overrun, seen from day 12, not day 31.

Spend-to-date against budget, per department, with a month-end forecast the moment the pace tips over instead of when the accounts close. You see the overrun while there are still weeks to do something about it.

Analysis
03

Profit bridge

Every franc of margin change, explained and attributed.

The change in operating contribution versus last week, broken into its drivers, volume, menu mix, supplier prices, discounts, wages, voids. Each bar is an amount; the total matches the result by construction.

07

Menu profitability

Which dishes really earn, on the food margin.

Every dish placed by volume and margin, stars, workhorses, puzzles and dogs, with recipe costs that update from each invoice. When beef rises and a dish slips into the "dogs" corner, you see it at once.

13

Labour productivity

Where labour hours earn, and where they don't.

Revenue per labour hour, plan against actual, by outlet and by daypart. The afternoon that is quietly overstaffed or the shift that never pays for itself shows up as a franc figure and a roster you can adjust, without touching payroll data.

Deep dive
04

Suppliers

Not a purchasing report: what price moves cost you, and your leverage.

Which price moves are costing you money this month, in francs and linked to the dishes, plus missing volume discounts, the same item priced differently across outlets, and an anonymous benchmark against other Swiss operators.

05

Inventory

Theoretical inventory, without anyone counting.

Invoices in as goods received, recipe-based consumption as goods issued, a theoretical stock that matches the P&L. Enter a count and the difference is calculated at once. Below par, snodo drafts the order for you to approve.

06

Invoices

The check before you pay: order, delivery note, invoice.

Every invoice checked on three fronts, what you ordered, what arrived and what you're billed, with duplicates and overbilling stopped before payment. snodo verifies, then hands a clean figure to you or your fiduciary.

14

Revenue integrity

Voids, refunds and discounts, monitored, never accusatory.

Pour, covers and cash reconciled against the POS, with voids, refunds, discounts and unusual patterns surfaced as questions, not accusations. The revenue a till system loses sight of on its own becomes visible before it adds up.

15

Waste log

The one input a system can't infer, captured by voice.

Waste is the one thing the data can't reconstruct, so we make logging it take seconds: the chef sends a WhatsApp voice note of what is going out, snodo transcribes it, values it from your invoices and files it by outlet, reason and daypart. Over weeks the pattern shows whether it is over-prep, spoilage or portioning, and what it costs.

Assistant
11

Ask Snodo

Query your data in natural language.

Ask "Why did the margin fall last week?" or "What if beef rises another 10%?" and get a documented answer in francs within seconds, with a link straight to the right view. It works in English, German, French and Italian.

+

And the setup behind it

Outlets, recipes, suppliers, roles and permissions.

A full client setup layer: departments and people to assign measures to, per-outlet recipes and targets, supplier-code mapping, and role-based access, so the right person sees the right numbers.

Start with one module. Add the rest when you're ready.

Sample data now; your own numbers in the 60-day pilot. We build the recipes and you keep the results.

Contact

Try the pilot.

Tell us about your operation and we'll set up a 60-day pilot on your own numbers.

Pick a time
You're booked.

A calendar invitation is on its way to your inbox.

This opens a draft in your e-mail app — you still need to send it. No obligation; we reply within one working day of receiving it.

E-mail
contact@snodo.ch

Write to us directly and we'll take it from there.

Book a demo
20 minutes, screen-share

We walk you through the live system on sample data, then talk about your outlets.

Where we are
Based in Switzerland

Swiss-hosted, nFADP-compliant · snodo.ch

About snodo

Built from fifty conversations.

snodo did not start with a product. It began with months of listening to the people who run food and beverage in Switzerland, and with the findings we published from those conversations.

The research note

Fifty conversations with Swiss operators, published in full.

Between June and August 2026 we spoke with around fifty operators, owners of restaurant groups, hotel directors, F&B and purchasing managers, finance directors and caterers, on the record and without asking for their figures.

We wrote up what we heard as an anonymised findings note, “Where the margin goes.” Every observation in it appeared in more than one conversation, so it reflects the industry rather than a single opinion.

It is public. If you run a hospitality business in Switzerland, request the full note and we will send it to you directly.

Request the findings note
Who we are

A small team of hospitality and software people.

We build snodo close to the floor and the kitchen pass, not from a distance. It is led by our founders with a small team spanning hospitality operations and software.

Martina Camusso

Martina Camusso

Co-founder

Studied hospitality management in Switzerland and a master's in finance in Spain. Worked in F&B, operations and purchasing across Switzerland, Spain and the United States.

Arsenii Morozov

Arsenii Morozov

Co-founder

Studied hospitality management in Switzerland and started working young in his family's hotel and restaurant. He went on to rooms and F&B across Europe and the US.

Want to try it on your own numbers?

We are working with a small number of operations this autumn. The 60-day pilot runs on your own numbers, and you keep the results.