How we work
No debate about methodology. Only what we have found to hold up since 2012.
Prices
We publish our prices because it saves time.
- Technical short check: [AMOUNT]
- AI potential analysis: [AMOUNT]
- Discovery sprint: [AMOUNT]
- Development day rate: [AMOUNT]
- Operations packages from: [AMOUNT] / month
We are not the cheapest supplier. We are the one whose system you can still develop further in eight years.
Six principles
- 1
We say no when no is the right answer.
If standard software fits your problem better, or another supplier does, or no software at all — we say so. A badly matched contract costs us more over time than it brings in.
- 2
Something you can touch every two weeks.
No status reports about progress. Working software you can try out yourself. It is the only measure of progress that does not lie.
- 3
A small team that stays.
The same people work on your system — not a senior in the pitch and juniors in the build. Our team is small. That is deliberate.
- 4
Running costs are part of every decision.
For every architecture decision we ask what it will cost in five years. That question sounds different once you have run your own product since 2012.
- 5
Your knowledge stays with you.
Documentation, repository access, the ability to hand over. We never build a dependency that rests on you not knowing how the system works.
- 6
A direct line.
You speak to the people who build the system. No account manager in between.
Contract models
| Model | When it fits | How it is billed |
|---|---|---|
| Fixed price | Clearly bounded scope: short check, analysis, discovery sprint | fixed amount, defined deliverables |
| Time and materials with a budget cap | Development where the requirements are still sharpening | day rate, agreed ceiling, running transparency |
| Monthly capacity | Ongoing operation and continuous development | fixed monthly budget, clearly defined response times |
Frequently asked questions
Do you also work remotely?
Yes, by default. For workshops, kick-offs and important milestones we come on site. Within Upper Austria that carries no travel charge; elsewhere in Austria we agree a flat rate in advance.
What happens if we want to end the collaboration?
You get the code, the documentation, the access credentials and a structured handover. That is not a special case, it is standard. We keep clients through quality, not through dependency.
How big is your team?
[NUMBER] people. Small enough that you know everyone. Large enough that nobody is irreplaceable.
Do you take over existing systems?
Yes. We start with the technical short check.
Do you work with public sector clients?
Yes. We know the requirements for accessibility, documentation and public procurement.
Where is our data held?
In EU data centres. On request in Austria, or in your own data centre.