Five minutes before service
The manager adds today's focus. Staff get a short lesson and readiness check on their phone. The manager sees who is ready before guests arrive.
Training without a restaurant? Create learner profile.
Read tonight's focus and what must be escalated to kitchen or manager.
Three short questions with explanations if something needs repeating.
See who has read the briefing, who is missing the check, and what needs follow-up.
Choose your path
Most restaurants should start with the beta workspace. Personal learners can create a training profile and use the learning tree without being attached to a restaurant yet.
For owners, managers, and admins who want to invite staff and test Restaurant Training in operations.
For people who want to build restaurant skills, take readiness checks, and keep personal progress.
Before service
Restaurant Training is built for the minutes when a manager needs to get today's changes, allergy notes, and service focus to the team without another long message thread.
Specials, sold-out items, and new descriptions need to reach everyone before service starts.
Staff need to know what they can say and when the manager or kitchen must be involved.
Onboarding is easier when the first days have short, concrete steps.
It is hard to see who has read, understood, and is ready for tonight's focus.
Friday 16:30
Start with what you already have: menu, allergen notes, wine notes, simple guidelines, or today's specials. The beta should make that material useful before the next service.
Specials, sold-out items, large parties, and allergy notes are collected in one briefing.
The phone shows what they need to know, how to say it to guests, and when to ask.
Three to five questions check whether tonight's most important points are understood.
Follow up with two staff members or one weak spot before service starts.
Beta flows
Instead of starting with a heavy setup, you can test the situations where Restaurant Training should make a visible difference in daily operations.
Inside the beta
The product should not feel like another document archive. It should make today's changes visible, give each staff member one clear action, and show the manager where follow-up is needed.
Menu, specials, and service focus are collected in one short mobile view.
Explanations after mistakes turn follow-up into training, not control.
The manager knows exactly what to repeat in the briefing.
Operational use
The beta should show whether Restaurant Training helps in daily operations: before service, during onboarding, and when something important changes.
Role-based ramp plans, short lessons, and readiness checks make the first week clearer.
The manager posts today's focus, expected guests, specials, and sold-out items.
Staff are trained to know the boundary and ask a manager or kitchen when safety is affected.
Menu items, pairings, and guest language can become short explanations before service.
When a dish, routine, or allergy note changes, staff can acknowledge that they have read it.
Danish and English can work in the same team, while German is handled carefully with clear safety boundaries.
Training should stay close to operations: short, concrete, and easy to follow up on.
That is why the beta is built around phones, briefings, acknowledgements, and manager overview.Coming soon
These items are not sold as included beta features. They show the direction if the core flow works in real restaurants.
0 DKK
Free while beta is open. Feedback is expected.
14 days
For restaurants that want to test after commercial launch.
499 DKK/mo.
Ex. VAT. For one restaurant using training regularly.
999 DKK/mo.
Ex. VAT. More capacity for larger teams.
From 10,000 DKK
Ex. VAT + monthly plan. For teams that want help from the start.
| Plan | Users | AI answers | Quiz generation | Documents and storage |
|---|---|---|---|---|
| Beta | 30 total | Not included in free beta | Not included in free beta | 5 documents / 25 MB |
| Trial | 30 total | Limited trial usage | Limited trial usage | Light test setup |
| Starter | 50 total | 500 per month | 10 per month | 20 documents / 250 MB |
| Team | 100 total | 1500 per month | 25 per month | 50 documents / 1 GB |
| Personalized Setup | Based on selected plan | Based on selected plan | Based on selected plan | Based on selected plan + setup help |
All paid prices are ex. VAT. Beta requires no payment. Paid plans start after beta and commercial setup are ready.
Safety
Restaurant Training can help turn menus and guidelines into training, but it is still an internal tool. For allergens and safety, staff should escalate, not guess.
FAQ
Short answers to the things a restaurant usually needs to know before creating a free beta.
Yes. The beta requires no payment to start. Paid plans come later, after beta and commercial setup.
No. Menu upload is useful, but not required to create a workspace and invite a small team.
Menus, allergen notes, simple service guidelines, specials, wine notes, and routines. Dummy data can be used as a fallback.
No. It is an internal training tool for staff and managers, not a guest-facing chatbot.
No. For allergens and safety, staff must follow your procedures and escalate to a manager or kitchen.
Yes. The staff experience is mobile-first, so training can happen before or around service.
Danish and English are primary. German is supported with the same careful safety boundaries, not as certified compliance training.
If the product fits your operation, you can continue on a paid plan after launch. Otherwise you can stop without payment.
The beta is designed to start light. You can create a workspace, invite staff, and choose starter material afterwards.
Yes. Training can work for front-of-house, kitchen, and other roles as long as the content matches their responsibilities.
Your material is used for your restaurant training. Deeper integrations must be built with clear agreements, access control, and GDPR care.
Create a workspace, invite a small team, and test short lessons, readiness checks, and manager overview before paid plans launch.
Secondary path
The best path is creating a free beta. If you want to clarify something first, you can send a short beta request.
We agree a small beta test and choose material such as menus, allergen notes, simple guidelines, or dummy data if the beta fits your restaurant.
