The problem in one sentence
Together we phrase what should change and attach a number to it, for instance “open repair requests older than ten days”. That figure is later used to judge whether the project paid off.
What happens between the first conversation and live operation. Each piece is built so you can follow it and, if need be, hand it to another team.
Together we phrase what should change and attach a number to it, for instance “open repair requests older than ten days”. That figure is later used to judge whether the project paid off.
Who may see and change what: office staff, tenants, contractors, owners' representatives. Settling this early avoids squeezing access rules into a finished application afterwards.
An honest comparison with packaged products, sector solutions and add-ons for software you already run. If standard is good enough, you skip the bespoke build, and we will say so.
Figma designs of the key journeys that future users tap through on phone and PC. Misunderstandings cost minutes at this point rather than weeks.
A web application on Laravel and Vue with PostgreSQL, a clean API and automated tests. Established technology you will still find developers for five years from now.
If the application issues invoices or receipts, we cover the mandatory details, the seven-year retention under the Austrian Federal Fiscal Code and, if you wish, an export for BMD or RZL.
Hosting with Exoscale, Anexia or Hetzner, monitoring, daily backups and a maintenance agreement for security patches and small tweaks.
Four stages, each ending in a clear result. How long the later ones take is settled after the first, and then in writing.
Video interviews, a success metric, the role model, the market check and an effort estimate. The document works with any other supplier too.
Clickable designs, two or three feedback rounds with real users, then an agreed feature set.
Only what solves the core issue, used for real by a small group, with a demo every other week.
Further features ranked by value, training over video and the move into routine operation.
Name one person who owns the product. Not IT, and not the managing director “on the side”, but someone who knows the workflows, can spare two or three hours a week and makes calls the same day. Projects without that role are not coded any worse, but decisions come late or never, and that costs more than any line of code.
The repository sits in your GitHub or GitLab organisation from the outset. Rights of use in the code are set out in the contract, which provides for their transfer to you. We work there as invited contributors. If you end the relationship, you simply revoke our access.
Yes. Every stage stands on its own. Many firms work with the first release for a few months and then decide, based on real use, what is still missing. Often that list turns out shorter than expected.
The problem statement comes with its own quote in advance. For the build we quote each stage once its scope is clear. The basis is our rate of €110 per hour plus VAT, which also applies to later additions.
The product owner two to three hours a week; future users a few hours for prototype feedback and for trying the first release. More is rarely needed, and less tends not to work.
Schemes such as KMU.DIGITAL, aws programmes and grants from individual federal states support digitalisation. Whether yours qualifies is for the funding body or your adviser to confirm. We provide a description, timeline and cost breakdown but do not file applications.
Which problem should the software solve, and who deals with it today? We will come back with a quote for the problem statement.
Your enquiry has arrived
Our reply reaches you within one working day. Outages that leave your staff unable to work are dealt with first.
We could not find that town. Try another spelling, or choose whichever provincial capital lies closest; as everything is handled remotely, you get the same service in all nine Austrian states.