Six engagement types, matched to your starting position: a blank page and a need; a live product and too few developers; a patchwork of applications that do not exchange data; or a legacy system that should be relocated while it still runs.
The pain point is obvious, the specification does not exist. We move through discovery, prototype, implementation and launch in stages that you release individually, with Austrian invoicing rules factored in from the outset.
Apps on iOS and Android for service engineers on the road, sales reps or end customers, able to cope without signal and to use the camera and GPS. Listed in the app stores under your own developer accounts and maintained after release.
Solutions resting on PostgreSQL, Laravel, Django and Keycloak, free of seat-based licensing and of any lone vendor dictating renewals. Each delivery comes with an SBOM and a licence compliance check.
Engineers, QA specialists and business analysts who plug into your Git workflow and stand-ups from afar. Intended for product firms and software houses whose vacancies have stayed open far too long.
BMD, RZL, SAP Business One or Business Central synchronised with CRM, warehouse management, payroll and Microsoft 365. Electronic invoices as ebInterface files or via PEPPOL, with ZUGFeRD for buyers in Germany.
Legacy Access tools and out-of-support SQL Server instances brought onto supported versions, onto PostgreSQL or into an Austrian or EU data centre. Complete history, two practice runs and a tested fallback plan.
The right model depends on how much of your project is already pinned down. Agreeing a fixed sum for work nobody has specified is the most reliable way to end up in a dispute.
Who may use the code belongs in the agreement. Before work starts, we set out in writing which rights of use you receive in everything produced for you. At the close of every stage we hand over the current repository, the documentation and setup instructions, so a different vendor or your in-house developers could continue at any time. Third-party open source libraries retain their own licences and appear in a separate inventory. Ask a lawyer to review how far the transfer of rights reaches before signing.
A fresh increment lands in a staging environment every fortnight, reachable with personal logins for your staff. Should the result stray from your expectations, it becomes visible within fourteen days instead of on handover day.
A brief video meeting to grasp the problem and test whether bespoke code is needed in the first place. If an existing product would do, we say so before we hang up.
Talks with the staff who do the job every day, a written requirements document, a map of interfaces and screens you can click through. Invoiced on its own and owned by you, regardless of what you decide next.
Fourteen days of work, a demo, your approval. Between sprints the backlog can be reordered freely without amending the contract, provided the total effort stays constant.
Deployment, user training over video and hands-on support during the opening weeks. Following that, a maintenance agreement with defined reaction times is available.
Quite often a package suffices, and we prefer to flag that early. When your processes fit Odoo, Business Central, a sector-specific solution or a common CRM, setting that up is cheaper than writing software. Bespoke development pays when your methods give you a market advantage, or when tailoring a product has become pricier than a new build. Discovery puts the two sums next to each other.
After discovery. Any number offered before we understand the workflow would be guesswork. Discovery is sold at a fixed fee and yields written requirements, a timetable and an itemised budget. From that point we continue with fixed fees per stage, hourly at €110 plus VAT if priorities keep changing, or with a dedicated team on a separate quotation.
We can. First comes a code review lasting one or two weeks, looking at quality, test coverage, stale dependencies and documentation. The resulting report separates code worth keeping from code worth replacing. In such handovers the real gap tends to be access rather than code: server passwords, repository permissions, domain logins. Secure those beforehand, and get legal advice on which rights to the software you actually hold.
All of it. The repository is transferred after each stage rather than only at the finish line, along with deployment scripts, architecture notes and a register of third-party components. Hosting, app store and external service accounts carry your company’s name from the start, so none of your access hinges on us.
Several Austrian schemes back digitalisation in small and medium-sized firms, KMU.DIGITAL, aws programmes and regional schemes of the federal states among them. Eligibility is decided by the funding body alone, and deadlines frequently fall before work may begin. Apply is not a listed consultancy for these schemes, though we gladly prepare a tidy project outline and cost breakdown to accompany your application.
There is no need for technical paperwork. Tell us which task swallows the most time and what ought to change. We will suggest a working model and the scope of an initial discovery phase.
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.