See which cost changes needa decision before service.

Follow reviewed invoice costs into recipes, inventory context, and a decision your manager can inspect.

Pilot-stage product · Illustrative product data, not customer results.

One cost change can affect the next service.

See the evidence. Keep the decision.

Know what changed.Decide what happens next.

Dynamic.ly is a pilot-stage mobile product for restaurant operators. Follow reviewed invoice costs into recipes, inventory context, and a recommendation your manager can inspect.

Discuss a pilot See how it works

Illustrative product views using example data. Not customer records or results.

Dynamic.ly Home: a decision awaiting manager review, with its evidence attached.

One cost changed. The source stays attached.

A delivery arrives with paperwork. Dynamic.ly reads the source, holds it for review, and keeps it attached to the cost change that follows.

Reviewed salmon line: 1 lb at $18.40, inventory item and source page attached. Invoice approval remains required. — A reviewed line still requires invoice approval

The original source page stays available for review.

Invoice ready for approval. The reviewed salmon line and source page remain attached.

The changed fact

$17.10$18.40/LB

▲+7.6%Reviewed unit-cost change

Atlantic salmon, Ocean Fresh. The vendor line is matched to the ingredient record and the change is verified against its source before anything downstream moves.

Source: Ocean Fresh; Verified

Cost history preserves the previous and current salmon cost and its source.

02 · Source and change

A changed input changes the economics.

Salmon Bowl economics showing a $14.20 configured internal price floor and a menu price above that floor.

Example recipe cost

$6.72

Current menu price

$18.00

Configured price floor

$14.20

Internal · Not published

Reviewed values and defined rules recalculate recipe economics. Recipe cost, menu price, and the configured price floor stay distinct. Both example prices remain above the floor.

03 · Consequence

A recommendation you can inspect before you act.

The offer, the window, and the restaurant’s limits are visible before anyone decides. Nothing is published on its own.

Suggested offer: $15.50
Service window: 5–7 PM
Internal price floor: $14.20

Illustrative app example. Prepared for manager review; no offer published. Any projected impact remains an estimate.

Prepared review plan only · Nothing published

A proposed $15.50 offer for 5–7 PM, with a $14.20 floor and manager review required.

Suggested offer: $15.50 for 5–7 PM. Prepared for review, not published. — The proposed action and the reasons behind it. Manager review required.

Why-now detail connecting a salmon cost change, illustrative expiry context, and the configured price floor. — The proposed action and the reasons behind it. Manager review required.

04 · Recommendation

Manager control

Dynamic.ly prepares the evidence. The manager makes the call.

Approval is a human act with a name against it. What gets stored is the decision — who made it, when, and on which revision.

Manager decision recorded with revision and timestamp. No external change was made.

A decision recorded — not an outcome invented.

Actor: General Manager
Revision: 1
Recorded: Timestamped
External state: Locked

This is an internal record. No menu price was changed, no offer was published, and no provider was written to.

The record

Source checked. Recommendation prepared. Decision recorded.

01Source checked — the vendor line and its verified change.
02Recommendation prepared — with the floor it respects.
03Manager decision recorded — actor, revision, timestamp.

External changes: Stay separate
Manager review: Records a choice
Projections: Remain estimates
Provider changes: Not performed

Decision history links source review, cost change, recipe impact and the manager’s decision.

05 · Decision and record

Proof before promises.

Dynamic.ly has no confirmed customer outcome to publish today. A projection, a recorded decision, and a later measured outcome remain separate.

Review the evidence model →See how results are measured →

Built around the people running service.

Make a costly change easier to see, inspect, and act on deliberately. Keep the judgment with the people who know the restaurant.

Operators can discuss testing the workflow. Hospitality professionals, builders, designers, and researchers can bring practical questions and specific contributions.

See why we are building it →

Field Notes

Practical notes on restaurant cost, evidence, and operator judgment.

Bring a real cost question.

Start with one invoice and one dish to discuss fit. A measurable pilot needs a broader baseline and a manager who can review the records.