SOFTWARE AGENCY vs IT SERVICE PROVIDER
Both are external IT firms you pay monthly, and German-speaking buyers search for both as a Dienstleister, so they land in the same shortlist constantly. They sell different things. One is measured on whether existing systems stay up. The other is measured on whether something that did not exist now ships. This page separates them so you brief the right category.
Book a thirty-minute callVerdictIf the deliverable is software that did not exist before, hire a software agency on a Werkvertrag. If the deliverable is keeping existing systems running, hire an IT service provider on a service contract with an SLA. Most companies need both, from two different vendors.
Compared on the dimensions that actually differ. Both categories contain excellent firms and weak ones; this is about which category fits which brief.
Delivery: software that did not exist before, working in production
What you are buyingAvailability: existing systems, networks and devices kept running
Werkvertrag, an obligation of result, or a monthly retainer
Natural contract typeDienstvertrag or framework agreement, an obligation of effort plus an SLA
The product shipped and did what the business needed
How success is measuredUptime, response times and tickets resolved inside the SLA
Both founders, senior by construction, the people who scoped it
Who is on your projectA named account team plus a shared support pool, sized to the seat count
You do. It transfers, with no lock-in
Who owns the code and IPUsually not applicable: the work is operations, not authored software
Neither. No vendor certifications, no round-the-clock support desk
Certifications and 24/7 deskTypically both: vendor certifications for what they resell, plus contractual out-of-hours cover
Fixed-scope build, or weekly billing that is cancellable any week
Typical commercial modelMonthly fee per seat or per device, on a multi-year term
Anything to do with running IT: we decline it and say so
Where the other one is betterAnything that requires product judgement and a new codebase
The two categories share a shelf in the buyer’s mind and almost nothing else. Read any procurement shortlist in the DACH region and you will find a Systemhaus sitting next to a product studio, because both answered a brief that said “we need software people”. The word Dienstleister covers both in German, which is exactly why the shortlist forms.
Start from the deliverable, because everything else follows from it. An IT service provider is paid to make sure things that already exist keep working: the network, the laptops, the file server, the cloud tenancy, the identity provider, the backups. Success is measured in uptime and response time. A software agency, also searched for as a software service provider or Softwaredienstleister, is paid to make something that does not exist yet work in production. Success is measured in whether the thing shipped, and whether it did what the business needed.
That difference propagates straight into the contract. Managed IT naturally sits on a Dienstvertrag or a framework agreement: an obligation of effort, with an availability promise bolted on. Custom software delivery naturally sits on a Werkvertrag: an obligation of result. Once you notice that, comparing day rates across the two stops making sense, because you are not buying the same kind of promise. A cheaper hourly rate attached to an effort obligation is not cheaper than a higher rate attached to a result obligation.
It also propagates into who is in the room. Operations organisations are staffed and rewarded for stability: predictable process, low change rate, clear escalation paths. Product organisations are staffed and rewarded for judgement under uncertainty: deciding what not to build, changing direction when evidence arrives. Both are legitimate engineering cultures. Neither converts easily into the other, which is why a vendor that genuinely does both usually runs them as two separate businesses with two separate hiring bars.
So when a firm from either category offers the other as a service line, the question is not whether they are honest. It is who staffs it. Ask how many people work on that line, whether they are the same people who handle the core business, and what they shipped most recently. The answer is usually informative and easy to get.
The healthy end state for most companies past a certain size is both, from two different vendors, with a clear handover boundary written down before the build starts. We have worked in exactly that arrangement: on the IKB engagement our work sat inside the utility’s own build, on infrastructure, devices and codecs, with a complete handover after year one. We were never the operator of the surrounding systems and never claimed to be.
Where does that leave Wavect? On one side of the line, deliberately. We build and hand over custom software. We do not run IT operations: no helpdesk, no workstation or network management, no 24/7 on-site desk, no operational SLA. If your actual problem is that nobody is keeping the lights on, we are the wrong call and an IT service provider is the right one. If your actual problem is that something needs to exist and reach production, that is our work, and the code transfers to you.
Most companies eventually need both. If your brief is really an operations brief, we will tell you that on the first call instead of quoting for it.
Tell us what you are building. We will tell you straight which route fits, no pitch.
Book a thirty-minute call