DEEN Send an enquiry

For businesses that get by without departments

Twelve systems hold your venue together. One of them is you.

A spreadsheet, scraps of paper, the group chat, the book behind the bar, the envelope with the tips, the shoebox for the accountant. Kajüte keeps all of it in one place — one system for the whole business, run by people who also have guests to look after.

Send an enquiry In daily use at the Monkeys Kajüte since August 2026 →

roster_week32_final_v3.xlsx

hours list, from memory

reservation book, one handwriting

“did anyone read this?”

cash book, handwritten

receipts, in a shoebox

The difference

One business. One system. One version of the truth.

In a corporation each of these jobs has its own department, its own software and someone who does nothing else. In your venue two or three people do all of it on the side — and the same record-keeping duties, the same deadlines and the same responsibility still apply.

That is why Kajüte is not another tool for another building site, but the one place where everything comes together. Clocking a shift fills the time account, the tip split and the monthly record at once — without anyone typing it up again.

roster in a spreadsheet
hours on scraps of paper
cancellations in the group chat
reservation book on the bar
regulars kept in someone's head
holidays on a wall calendar
tips in an envelope
recipes in a binder
cash book in a ledger
receipts in a shoebox
payslips by email
training as a PDF

One login for everyone. Each person sees what concerns them — and you see all of it.

Wednesday, 11:20

The roster is out. Now someone calls in sick.

The file sits on twenty phones, and from this minute on every one of them shows something different. Whoever misses the change still turns up — or doesn't turn up at all.

Availability lives on notes in a drawer, swaps happen in the group chat, and you are the one typing all of it up.

Here is how it works instead

Everyone enters their own availability. Whoever forgets gets a reminder.
You drag the shifts into place, with everyone's requests right next to them.
Swaps get sorted out between the two of them — you only confirm what they agreed.
Holiday and sick leave hang on the same roster, not in a second calendar.
Anyone who wants it subscribes to their shifts in their own phone calendar — team and day notes included.

Last day of the month, 22:40

You are reconstructing hours nobody remembers exactly.

You have to keep records either way. The only question is whether the list is written while the work happens — or four weeks later at the kitchen table, from memory.

Every hour that lands wrong you either pay twice, or you owe it to someone.

Here is how it works instead

People clock in from the home screen of their phone. One tap, no login.
Breaks run with a countdown and come off the net time.
Five minutes after the shift ends it clocks out by itself. Anyone who stays longer presses a button.
Time balance, overtime, night premium and public holidays are counted as they happen, month after month.
At the end of the month everyone signs off their own hours. You release the month, and then it is closed.
The released month becomes a time record as a PDF, with a timestamp and a checksum.

Saturday, 19:00

The big party is written in a book behind the bar.

Anyone who isn't in the building knows nothing about it. Anyone who is has to decipher the handwriting. And the note “birthday, table 4, cake at 21:00” is gone the moment the room fills up.

The next day nobody knows why the party of six waited for nothing.

Here is how it works instead

Reservations sit where the roster sits.
Whatever holds for the day hangs on the day — not on the person who happens to know it.
Private functions block the day, together with the running order, music, food and payment.
The guest records remember who came how often and what they drink — deletable on request.
Anyone who prefers paper prints the day list for the bar.

Tuesday, somewhere in the group chat

The training has been sent. Nobody read it.

House rules, opening up, locking up, who descales the coffee machine: all of it sits somewhere in the chat, between holiday photos and the question of who is fetching ice.

And when something is left undone, it was never anyone — because nobody was ever responsible.

Here is how it works instead

Documents with a read receipt. You can see who still has them open.
Opening and closing as a checklist, step by step, even for the new one.
Tasks have a deadline and a name. Done means done.
The recipe book stands behind the bar: the build, the glass, and the quantities for twenty.
Tips are split by the hours actually clocked, not by feel.

Monday morning, no guests

And then comes the part the guest never sees.

The weekend's takings, the delivery note from the drinks supplier, the cleaning invoice, the hours for the payroll office. None of it is difficult. All of it takes time, and all of it comes back every month.

By the time it is gathered up, two mornings are gone — and the accountant still asks for the one receipt nobody can find.

Here is how it works instead

A cash book with a running balance. The daily takings work themselves out; you only enter the movement.
The export goes to the accountant as an Excel file — into their own template if that is what they want.
Receipts file themselves as they arrive, instead of waiting in a shoebox for the year-end.
Hours, overtime and night premiums go to the payroll office as a finished file.
The combined payslip PDF splits itself onto the right people. Everyone sees only their own page.

Runs alongside

The small things that otherwise land on you.

Payslips: Upload one combined PDF — everyone finds only their own page.
Documents: Contract, reference, certificate sit with the employee instead of in a folder.
End of month: Everyone signs off their hours, you release them. After that the month is closed.
Time record: The released month becomes a PDF, with a timestamp and a checksum.
Night premium: The qualifying hours are counted by the system, not by you at midnight.
Public holidays: The system knows the statutory holidays and counts them in by itself.
Yearly summary: What someone worked over the year, on one page instead of twelve.
Tips: The daily pot goes in, the split comes out — traceable for everyone.
Own calendar: Shifts land in the phone calendar, with the team and the day notes.
Guest records: Who came how often, with a note — and wiped without a trace on request.
Recipe book: The build, the glass and the batch for twenty — even for the new one on a Friday.
Notifications: A push to the phone when something actually happens. Otherwise quiet.
On the home screen: Runs as an app on any phone, with no app store involved.
New people: An invitation by link; they fill in the rest themselves.
Light switch: Whoever locks up clocks out everyone who forgot.
Several venues: Several venues run on the same system, cleanly separated from each other.

In service since August 2026

Built in a bar, not on a drawing board.

Kajüte grew up in the Monkeys in Salzburg, because the same building sites were lying around there. Every feature had to survive a Saturday night before it was allowed to stay.

What is in it today, the team there uses every day: rosters, clocking in, reservations, guest records, tasks, training material, the recipe book, tips and the cash book. Not one part of it is still waiting for its first real Friday.

What it costs

You pay per head, not per venue.

Five people cost five. Five hundred cost five hundred. No base fee that crushes a small team, and no tier where it suddenly starts to hurt.

And no building blocks: there is no version without the cash book, no reservation module to buy on top. Whoever has Kajüte has all of it — otherwise it would just be one more island.

We are at the beginning of this, so the price per head is not set in stone yet. Tell me how many people work for you, and we will agree on a number that fits your business.

Agree on a number

Your team Your invoice

5 5 × per head

22 22 × per head

500 500 × per head

Contact

Tell me what your Friday looks like.

Write a few lines about how many people work for you and where it hurts most. The answer comes from me, not from a sales team.

Daniel Laserer · Laserer GmbH · Salzburg