Team make-up
Back end in PHP, Python, Java or .NET, front end in React, Vue or Angular, mobile in Flutter or native code, plus QA and, if wanted, a business analyst or scrum master.
What makes up a dedicated team with us, and how you can tell whether it is working.
Back end in PHP, Python, Java or .NET, front end in React, Vue or Angular, mobile in Flutter or native code, plus QA and, if wanted, a business analyst or scrum master.
The first fortnight follows a concrete plan: access, an architecture tour, an introduction to the domain and small first tickets reviewed by your people.
The team adopts your sprints, definition of done and review rules. We only introduce new practices if you ask for them.
Time logged per ticket, shared retrospectives and a monthly report on throughput, open items and anything unusual.
Holidays and sick leave are covered; changes in the line-up are flagged early and accompanied by a handover so knowledge is not lost.
Managed devices with encrypted drives, access only with a second factor and only to what is needed. If you prefer, we work exclusively inside your virtual desktop environment.
Confidentiality undertakings for everyone involved and a contractual transfer of the rights of use in the code to your company.
For mainstream technologies, the gap between first call and first merged pull request is usually a matter of weeks.
Roles, seniority, technologies, expected duration and how the team slots into your organisation.
We propose profiles, you hold the interviews and decide.
Two weeks by the plan, then a joint review of whether pace and quality are right.
A monthly conversation about size and composition, with adjustments made within the agreed notice periods.
An external team does not replace product ownership. If nobody on your side grooms the backlog and clarifies requirements, even the best team will build the wrong thing. Check beforehand who takes that role. If nobody can, a project with a fixed deliverable is the better choice.
Our model is designed as a service: Apply organises and answers for its own specialists, and you set the functional goals. Where the line to worker placement under the Austrian Temporary Employment Act lies depends on how the arrangement works in practice. Have your legal adviser review both contract and day-to-day reality.
We recommend at least three months, since onboarding does not pay off otherwise. After that the agreed notice periods apply and the team can be scaled down step by step.
Short absences are covered by a stand-in. If someone leaves the team, we announce it, introduce a replacement and plan an overlapping handover. Wiki documentation keeps knowledge from resting with individuals.
By role, seniority and volume, invoiced monthly for hours actually worked. We prepare a concrete quote after the first conversation.
German or English, depending on the team and your preference. Code, commit messages and technical docs are normally in English, while talks with business users happen in German.
Which roles are you missing, on which stack and for how long? We will reply with suitable profiles and a quote.
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.