What we’re building, and what stays with the manager
What Dynamic.ly does, what it doesn’t, and why the manager always decides.
Most restaurant software adds something: another dashboard, another login, another number to check before service. We’re building the opposite.
Dynamic.ly reads what a restaurant already has: supplier invoices, inventory, recipes and sales from the till. It puts them side by side and looks for what changed. When something matters, it suggests one clear action and shows the evidence behind it.
How it works
The areas we’re working on:
- Ingredient costs: spotting when a supplier price moves.
- Menu prices: checking which dishes that change touches.
- Stock: what’s on hand and what’s about to run short or go to waste.
- Invoices: reading them in, so nobody has to type them up.
- Staffing and orders: comparing plans with what actually happened.
What stays with the manager
This is the part we care about most. Dynamic.ly suggests, the manager decides. Every action can be approved, edited or rejected, and nothing changes in the restaurant without someone saying yes. The people running the room know things no invoice shows, like a regular’s birthday booking, a chef’s new special or a delivery that came in short.
Restaurants don’t have to switch systems either. Dynamic.ly is designed to work alongside the tools a restaurant already uses. It doesn’t replace the POS.
Where we are
We’re getting ready for a wider release and opening a small number of free pilots with independent restaurants in New York, London and Athens.
We’re also planning to connect Dynamic.ly with Happily, our happy hour app in New York, so restaurants can turn quiet hours into deals people nearby can find.
We’ll keep posting what we learn here, including what doesn’t work.
Want Dynamic.ly in your restaurant? Early access is open.
Join the waitlist