The menu problem
Every business tool has menus. Menus have submenus. Submenus have tabs. You know the answer is somewhere in the system, but finding it takes longer than just asking someone. So you ask a colleague, or you open a spreadsheet, or you just guess. The tool has the data but you can't get to it fast enough for it to matter.
Workplace lets you type a question. "How many days off does Ana have left?" "When does Marko's contract expire?" "Who has the Dell monitor?" You get the answer immediately, in a sentence — not a dashboard, not a report, not a page you need to interpret.
This is not about making the software smarter. It is about removing the distance between having a question and getting the answer. The data was always there. The problem was always the twelve clicks it took to reach it.
Not a chatbot
This is not a chatbot with canned responses. Workplace reads the actual data — employee records, contracts, time off balances, asset registers, document metadata — and gives you a real answer based on real numbers. If Ana has 8 days left, it says 8. If her contract expires on March 15, it says March 15. No summaries, no approximations.
It works because all six modules share the same database. When you ask a question that spans modules — "Does anyone on Marko's team have a laptop warranty expiring this month?" — Workplace can cross-reference team directory, assets, and warranty dates in a single query. You would need three different screens to piece that together manually. Here it takes one sentence.
The answers come with sources. You see which record the answer was pulled from, so you can verify it or navigate to it directly if you need more detail. It is a lookup tool, not a black box.
What you can ask
Time off balances — yours, your team's, anyone you have permission to see. Contract dates, terms, renewal deadlines. Asset assignments and warranty status. Document locations and classification. Team structure and reporting lines. Upcoming expiries and deadlines across all modules.
Workplace answers from data it already has. There is no setup, no special configuration, no training phase. The questions are the interface. If the data exists in the system, you can ask about it in whatever phrasing comes naturally. "Who reports to Petra?" and "Show me Petra's direct reports" get the same answer.
You can also ask aggregate questions. "How many people are on holiday next week?" "What is the total value of assets assigned to the design team?" "How many contracts expire in Q2?" These are the kinds of questions that normally require exporting data to a spreadsheet. Here they require a sentence.
What it won't do
It won't make decisions for you. It won't approve a time off request just because you asked "Can Ana take Friday off?" — it will tell you her balance, show any team conflicts that week, and let you decide. The decision stays with you.
It won't speculate or predict. If the data is not in the system, it says so. It does not guess, it does not infer, it does not fill in gaps with assumptions. "I don't have that information" is a valid answer, and it is better than a confident wrong one.
It won't take actions without confirmation. Asking "Give Ana Friday off" does not approve the request — it prepares the approval for you to confirm. The difference matters. You stay in control of every change to the system.
Works in your language
Workplace understands questions in multiple languages. Ask in Croatian, German, English, Slovenian — same data, same answers. This matters for EU companies with multilingual teams, where the person asking the question in Zagreb and the person asking in Vienna should get the same answer without either switching languages.
The system does not translate your question into English behind the scenes and translate the answer back. It understands the question natively and responds in the language you used. Ask in Croatian, get the answer in Croatian. Switch to German mid-conversation, the answers follow.
Workplace.hr launches in July 2026. Join the waitlist to be among the first to use it.