The pilot

Bring the invoices.
Build the baseline.

A pilot starts with your restaurant’s source records and separates estimates from confirmed outcomes. It does not begin with a promised result.

Fit

A useful pilot has source access and a responsible reviewer.

  • Owner or chef operator with direct invoice access
  • One starting location
  • Perishable inventory or meaningful weak windows
  • A manager willing to review source drafts

Data needed

Enough evidence to establish what normal looked like before an intervention.

  • 4–8 weeks of supplier invoices
  • Current menu and prices
  • Core recipes, even if rough
  • A read-only Square connection when appropriate

Source: Dynamic.ly Backend · Sandbox

Square connection

Connected
LocationDowntown
MappingReviewed
ScopeMerchant profile read

Imported Square locations

Imported location

100 Demo Avenue, Demo City, NY 10001

Mapped

Provider authority

OAuth and credentials remain on Dynamic.ly Backend

Backend-owned

Write capability

Catalog, order, inventory, and payment write access is not enabled

Disabled
Sync locationsDisconnect

Square connection

Read-first, backend-owned, and explicit about what is disabled.

Dynamic.ly Backend owns OAuth and source evidence. The iPhone does not receive a Square token, and this pilot surface does not imply catalog, order, inventory, payment, or menu writeback.

Aegean Table · Example fixture

Pilot baseline setup

4 of 6 complete
4 of 6 complete

Square connected

Read boundary reviewed

Complete

First invoices imported

Example intake available

Complete

Core recipes mapped

Salmon Bowl included

Complete

Target margin set

Minimum floor $14.20

Complete

Slow windows

Tuesday · 5–7 PM

Needs review

Alcohol and compliance

Automation blocked

Needs review
Review 2 missing items

Baseline setup

Operating limits are reviewed before recommendations are useful.

The example setup records source readiness, a margin floor, a quantity cap, and a slow window. Missing or blocked items stay visible.

Pilot process

Four accountable stages.

  1. 01

    Source intake

    Load recent invoices and confirm the first drafts.

  2. 02

    Baseline

    Review ingredients, recipes, operating limits, and slow windows.

  3. 03

    Manager decisions

    Inspect recommendations and decide what, if anything, should happen.

  4. 04

    Measurement

    Compare the intervention window with the agreed restaurant baseline.

Measurement

Baseline, intervention, window, exclusions, and evidence state.

Every published number must name how it was measured. Estimated waste risk, projected recovery, and session activity never become customer results merely because a manager approved an action.

Session receipts and projections

What changed in the example loop

Evidence separated
Approved1Mock-confirmed
Recovery$420Estimated
Waste avoided$96Estimated
Margin lift18 bpsEstimated

Confirmed activity

One recommendation approved in this example session

Session receipt

Estimated outcomes

Approval does not convert projections into measured results

Not measured

AI summary

Draft explanation based on known structured values

Needs review
Review Audit & Sync

Request access

Tell us what margin problem you are trying to understand.

A person reads every request. No drip campaign and no false success message if delivery is unavailable.

By submitting, you agree to be contacted about the pilot. Your details are used for nothing else, never sold, and deleted on request. See our Privacy policy.