CASE STUDIES
Simple solutions.
A tangible difference.
See how we approach implementation, from a business need to a working process.
EXAMPLE IMPLEMENTATION
Leave requests
without email chaos.
An application for recording annual leave, focused on what the team needs most often.
1 day
to build the core application
EXAMPLE WORKFLOW
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
Dates → approval → team update
THE NEED
Leave is in the calendar. The customer gets a reply.
“Hello. Your colleague Marta hasn’t replied to an urgent email for two days, and I can’t reach her by phone.”
“We’re very sorry. Marta is on leave until the end of the week. It looks as though she forgot to set an automatic reply.”
How the solution works.
01
A request in Teams
The employee completes the leave request in Teams.
02
Manager approval
The manager receives the approval request in Teams too.
03
Calendar and automatic replies
Once approved, the absence appears in the employee’s calendar and an automatic email reply is set.
04
A summary for HR
HR receives a monthly email summarising who was on leave and when.
The solution works on a phone, in a web browser and in the desktop application, 24/7.
Implemented in 1 day.
Implementation cost: PLN 200 excluding VAT.
WHAT YOU GET BACK
Less admin. More time.
15 min
On each request completed by hand and then re-entered into the HR system.
60 min
Reconstructing information from a lost paper leave request.
30 min
Arranging a meeting when absences are missing from the calendar.
And the customer knows straight away when to expect a reply, rather than being left waiting.
In total: around 0.5 hours per employee per month.
An estimate for this example. Actual savings depend on request volumes and the previous way of working.
Get your time back for what matters.
Let’s start with a conversation about your business. Free, with no obligation.