the team
Behind illumiqon are Thomas Schmidt and the specialists he brings in for a project. Thomas founded illumiqon in Klosterneuburg near Vienna in October 2025. He leads every project himself.
thomas schmidt, founder
Thomas is illumiqon's founder and managing director. He designs your software's architecture and writes code for it, on the backend and the frontend.
He started out making games in 2012 and has built business software in Java since 2014.
At the University of Vienna, Thomas taught computer science students Java. In 2020 and 2021, he led a development team and brought new members up to speed. If your company has an IT team, he does the same for them on your software.
Thomas has built customer portals used by millions of people a month, and tools for internal teams, in the automotive industry, in insurance and in energy supply.
Thomas on LinkedInwho builds with us
illumiqon is small. When a project needs more hands or specialist knowledge, Thomas brings in experts in development, architecture, frontend or operations from his network. They work in his team, and he still leads your project.
why illumiqon exists
Thomas has been building software since 2012. In that time, he's seen the same things go wrong in software projects again and again. So he founded illumiqon.
off target
Openness
Teams build what the ticket says, and nobody asks whether it helps the company or its customers. We put ourselves in the shoes of the people who use the software. In a workshop, we look at how they work today, and later they try out the latest version.
nobody owns the whole
Responsibility
Several vendors share a project, each answers for its own part, and the gaps are left with you. We answer for the whole project, from the first idea to day-to-day operation.
the knowledge walks out
Down to earth
When the vendor leaves the project, the knowledge leaves with them. We document our work and build with technology many developers know, and the code belongs to you.
seen too late
Openness
Teams build for months before anyone sees something that runs. With us, you get a link to the latest version from day one.
every change a change request
Openness
A fixed price for the whole project needs a finished specification, and every change becomes a change request. We only agree a fixed price for the starter project. After that, we work against a budget we agree together.
tied to the vendor
Responsibility
The vendor builds alone, and your IT team never really gets to know the software. After that, you need the vendor for every change. With us, your team builds alongside us and can carry on by itself afterwards.
quality under pressure
Craft
When time gets tight, tests get dropped, releases are done by hand, and something breaks in production. We automate tests, dependency updates and the checks before every release from the start. Coding agents are part of that, with clear guardrails.
chasing trends
Down to earth
Teams pick whatever is in fashion, and later nobody can be found to maintain it. We build with established technology that others can maintain too.
lights on
The name has three parts: “illuminate”, because we shed light on your idea, “IQ” for intelligence, and “on” as in switched on.