Hi, I'm Viktor
Dance instructor on Sundays, application support on Mondays.
Twenty-two years of ballroom and Latin, six years of application development and user support. Both are crafts that only work through repetition and care.
Before the software existed
The idea.
I have been dancing since I was twelve. Standard, Latin, competitions, wedding lessons, trial classes, kids' dance. In recent years, increasingly behind the scenes too: course planning, member lists, billing, finding participants over WhatsApp and Excel.
In parallel, I have spent six years in application development and user support. From helpdesk tickets to Power Platform workflows, I have seen the full range. What both worlds share: understand what is really needed first, then build a solution that stays out of the way.
Dance schools are unusual businesses. They live on relationships, on recognition, on the brief conversation between classes. The software should protect that, not displace it. It should handle the admin and then become invisible.
Principles
Three principles that guide DanceDesk.
Practitioner first.
Every feature has to pass the test: would this actually help me on a Saturday morning with thirty sign-ups? Or does it only look nice in demos and annoy me in daily use?
GDPR and DACH-native.
Self-hosted in Germany. No US-cloud third party. SEPA, direct debits, dunning, privacy compliance, all aligned with the standard local schools are audited against.
Quiet in the background.
The valuable minutes in a dance school happen on the floor, not at the screen. DanceDesk takes the admin off the table and only speaks up when something genuinely needs attention.
Got a question?
Write to me directly. I reply myself, no helpdesk system in between.