Client reference
Banking
A financial group operating in the Czech Republic and abroad, from banking and insurance to investments. Internal IT now runs its requests in a helpdesk from SBID that was built in a single hackathon.
Problem
IT requests scattered across e-mails and spreadsheets
Solution
An internal IT helpdesk built in a single hackathon
1 hackathon
The delivery format, instead of a months-long project
Agentic build
The application was built through agentic development in Power Apps
5 areas
Tickets, epics, timesheets, delivery plan and notifications
1 app
Instead of requests scattered across e-mail
The financial group's internal IT received requests by e-mail, in person and over chat, and tracked progress in spreadsheets. SBID built the helpdesk as a hackathon, with the team at one table with the people who asked for it. The application was built through agentic development in Power Apps and runs as a Code App directly on Dataverse.
Problem: requests lost among e-mails
Requests for internal IT arrived by e-mail, over chat and in the corridor. Everyone kept their own spreadsheet of what was in progress, who was on it and when it would land. Something more important was missing too: how much work IT actually delivered and what it was worth. Without that, capacity and priorities are hard to defend.

Solution: a helpdesk in a single hackathon
Instead of a months-long project we ran a hackathon: developers at one table with the requesters, decisions on the spot, and what is agreed in the morning running in the application by the afternoon. AI agents built the app under SBID's guidance as a Power Apps Code App on Dataverse. It covers:
- Tickets with priority, phase, resolver and due date
- Epics and the breakdown of larger requests into child tickets
- Estimated and spent man-days including remaining capacity
- Timesheets and a delivery plan as a timeline
- Discussion, attachments and notifications only for the people a ticket concerns
- A link to Azure DevOps and an interface in Czech and English
Result: IT knows what is on its plate
- Requests have one home and no longer get lost in e-mail or chat
- A dashboard of open, done and overdue tickets greets the team every morning
- Estimated against spent man-days gives a basis for capacity planning
- Business benefit is recorded on the ticket, so priorities rest on numbers
- A working application in one day instead of a months-long project
What we used on this project



