Research artifact from SNHP's experiments — not a product. → snhp.dev

Owner sandbox

Run SNHP on your own menu.

Put in a couple of your drinks and your real numbers. Then watch two versions of the same day play out on the same customers: your static printed menu vs dynamic SNHP quotes — margin, walk-aways, savings and waste, side by side. The pricing here is the real SNHP offer-graph engine, running live in your browser.

A simulation of the mechanism — not a real shop's books, not a forecast.
1 · Your menu2–3 drinks + one topping · edit the names & numbers
DrinkMenu $Cost $
Topping (made in batches)Menu $Cost $
2 · Today's conditions
Foot traffic
Customers flexible on pickup time
35%
These are the customers who'll take a +30/+60-min slot for a better price — the room SNHP has to smooth your rush.
Runs one simulated day on the numbers above.
3 · Twin worlds — the same day, the same customersone simulated day
Static · your printed menuone price, all day
$0margin
walk-aways ↙
0
cups
0
walked away
0
toppings
$0
customer surplus
0
off-peak
$0
waste
SNHP · dynamic quotenegotiated before pay · never above menu
$0margin
walk-aways ↙
0
cups
0
walked away
0
toppings
$0
customer surplus
0
off-peak
$0
waste
What SNHP did that a printed menu can't
4 · On your menu, this day

—

✓Never above your menu ✓Discount-only (≥60% of menu) ✓Never below your margin on a full-price buyer
Honest note. This is a simulation of the mechanism, not a production forecast or a real shop's books. In this sim SNHP already knows what each customer would pay. Live, it has to discover that through the negotiation — so real discounts are more cautious and some quotes miss. That's the main reason real-world results are more conservative than this idealized model. A live deployment is also deliberately guarded — smaller discounts, tighter floors, and it earns trust before it earns margin. The caveats and the paired 30-day study live on the owner panel.
See the owner panel & caveats → More demos →

—