veydex

Veydex helpers

Seven who keep looking while you are somewhere else.

The dayThe teamPurchasingThe numbersThe tillOccupancyMargin

Your business produces data all day — more than one person can hold in view on the side. The helpers are not another chatbot but seven roles, each with a clearly bounded remit.

Observe. Propose. And carry out only what you allow.

  • ToniThe day
  • MiraThe team
  • BenPurchasing
  • KarlaThe numbers
  • JoThe till
  • RosaOccupancy
  • NoraMargin

Each helper sees only the area it is responsible for.

The cast

Seven roles. Seven remits.

Not one generalist doing a little of everything. Each role has an area, knows its data — and stays out of where it has no business.

What matters today, on one page.

Overnight something accumulates in every area. Toni gathers it up and puts it in front of you in the morning as one view — instead of seven.

For example
“42 reservations today, two of them with an allergy note. The licence expires in 30 days.”

Toni · The day

Needs Hub

Where staffing and occupancy do not match.

Mira holds the rota against what the day is likely to bring. If the two do not match, she proposes a staffing. Entering it is yours.

For example
“Saturday from 6 pm you are one person short. Proposal: one extra evening shift.”

Mira · The team

Needs Shift planning

What is missing, before it is missing.

Ben keeps an eye on consumption and stock. He speaks up before a line runs out — not on the evening after.

For example
“Oat milk will probably last until Thursday. Proposal: add it to the next order.”

Ben · Purchasing

Needs Inventory

What shifted, and why it counts.

Numbers arrive quickly, explanations do not. Karla notices when something meaningful shifts — and tells you which change is worth an explanation.

For example
“Tuesday lunchtime has been noticeably weaker lately, mostly on drinks.”

Karla · The numbers

Needs Analytics

Where something falls out of the pattern.

Voids, discounts, abandoned sales: Jo knows what is normal at your till. If something falls out of line, it lands with you as a case — not with your team as a suspicion.

For example
“One shift had unusually many voids yesterday. Worth a look.”

Jo · The till

Needs Till

When it fills up — and when it does not.

Rosa tells you early how full it will get. So staffing and purchasing fit what is coming, in good time.

For example
“Friday evening will be busier than usual — most seats are already booked.”

Rosa · Occupancy

Needs Reservations

What sells, and what pays.

Those are two different lists. Nora separates the article that crosses the counter often from the one that leaves something behind.

For example
“The pasta sells most often. The bowl leaves the most behind.”

Nora · Margin

Needs Till & inventory

Each role sees only its own area.

A helper gets the data of its remit — and none besides. Jo sees the till, not the rota. Mira sees the rota, not the margin. That is not a setting somebody can forget, it is the cut of the role.

And you decide how far it may go.

Three levels

From “show me” to “get it done”.

You decide how far it goes.

Every role works at one of three levels. You set it per helper — and take it back whenever you want.

Level 1

Observe

The helper spots something and shows it to you. Nothing more.

Level 2

Propose

The helper spots something and proposes a concrete action. The decision stays with you.

Level 3

Execute

For selected roles and within your limits, Veydex carries out approved tasks itself. Your rules still apply.

A proposal takes shape

Two roles, one proposal — and an approval that stays with you.

Rosa
Mira
  1. 14:05Rosa notices: Saturday will be busier than planned.
  2. 14:05Mira turns it into a proposal: one more person from 6 pm.
  3. 14:06The proposal lands with you — not straight in the rota.
  4. You accept it or turn it down. If you object, it does not happen.
  5. Veydex takes into account how your team works with proposals — so over time they fit your business better.

A proposal is not an action. Your approval is.

Control

Automatic does not mean unchecked.

Every automated action follows clearly defined permissions and safety limits. For you, that means:

A helper acts only in the area it is responsible for.
It works only with the data its remit needs.
How far it may go, you set for each helper individually.
Only what you have explicitly approved is carried out.
Critical actions can require your confirmation on top.
Your limits apply at every level.
What a helper has done stays traceable in the history.
You can rein in or switch off any helper at any time.

That holds for every action a helper carries out.

And if you object, it does not.

Limits

A system that knows its limits.

Veydex never widens on its own what a helper may do.

Veydex takes into account how your team works with proposals, to fit its support more closely to your business.

More autonomy only comes with your consent — and you can take it back at any time.

The decision stays yours.

Getting started

Start with the one role that takes the most off you today.

  1. 01

    Pick the area a helper should watch

  2. 02

    Activate the role and set it to observe

  3. 03

    Read proposals, accept or refuse them

  4. 04

    Only then decide whether it may execute

The helpers live in the Hub — you switch them on there like any other module. They build on the areas you already run; without those areas they see nothing.

No helper starts at level three.