All articles
Development

Project Kontrol: Why We Develop Our Studio Tool

Vladimir Perovic Apr 25, 2026 2 min read 274 words

Updated:

An interior material decision affects quotations, purchasing, scheduling and construction. We develop our internal Project Kontrol tool to make those links visible and agreements retrievable. The key development task was understanding studio processes and deciding what genuinely needs recording.

Experience with other tools

We tried general tools, including Plane and Vikunja. They can be good choices, but our workflow called for closer links between phases, cost lines and client decisions. That explains a custom tool; it does not prove other systems incapable. Licensing, guest access and data location depend on product and contract. Self-hosting gives control but requires maintenance, backups and an accountable owner.

From task to completed work

Each task has a project, phase, deadline and responsible person. Notes and subtasks explain the next step. Planned, selected, contracted and paid amounts remain separate. A moved deadline requires review of dependent activities and agreement with crews; automatic recalculation does not confirm availability. Link quotations, drawings and records to the work they concern.

AI-assisted development and checks

AI tools help prepare code, tests and explanations. People developing and operating the system remain responsible for requirements, access and calculations. Check changes with demonstration data, then test access boundaries and failure recovery before adoption. Rapidly written code does not prove a correct business process.

The tool records the agreement

Project Kontrol is our studio’s working system. Client viewing depends on agreed access to a specific project. This article is not an offer of software licensing or a public demo account. Its value depends on regular recording and verification: completion requires checking the work, not simply moving a card.

Sources and next steps

← Back to journal
SEARCH
Select Language