Support Retainer vs Hourly: Which Fits Your Software?

Choose hourly billing when your software rarely needs work and you want to pay only for what happens. Choose a retainer when downtime would hurt, when changes arrive every month, or when you need someone who already knows your system to answer fast. Most teams end up with a mix: a small fixed monthly fee for monitoring and availability, and hourly billing for anything beyond it.

This guide explains how each model works, what a Swiss business should expect to pay, where each one goes wrong, and which contract clauses decide whether you are treated fairly.

TL;DR

• Hourly billing means hours worked times a rate. It suits irregular, small or exploratory work, and gives you cost control but no guaranteed availability.
• A retainer is a fixed monthly fee for readiness, monitoring and a defined scope. It suits production systems where response time matters.
• The model matters less than the contract: scope, response and repair times, incident priorities and what happens to unused time.
• Many providers combine both: a monthly fee for availability, hourly billing for changes and improvements.
• Review the arrangement every few months against the monthly report and your real workload.

How the two models actually differ

With hourly billing, you pay for hours worked multiplied by the hourly rate. When nothing breaks and nothing changes, you pay nothing. When something breaks, you pay for the time it takes, whatever that is.

With a retainer, you pay a fixed monthly amount for availability, ongoing support or maintenance, as one Swiss invoicing guide for IT freelancers describes it. You are buying a relationship and a promise: someone is watching the system and will respond within an agreed time.

The difference is who carries the uncertainty. Hourly billing puts the risk of a large bill on you. A retainer puts the risk of an idle month on the provider, and you pay for that in the form of a base fee.

The hybrid is the common case

Pure versions of either model are rarer than the debate suggests. Swiss provider VSHN, for example, describes a monthly retainer covering documentation upkeep, regular reviews and readiness to support, while the effort for improvements, changes and problem management is billed hourly. That split is sensible: the fixed part pays for being ready, the variable part pays for work.

A managed software retainer can also be built the other way round. According to one guide on what a managed retainer should include, it may be a fixed fee or hourly billing against an agreed monthly estimate. So when someone says “retainer”, ask which of these they mean.

What a support retainer usually includes

A retainer is only worth its fee if the deliverables are concrete. A typical managed software retainer, as described by Infoloop, covers:

• Monitoring, in some cases around the clock
• Fixes with response-time targets
• Monthly improvements
• Scheduled security updates
• A monthly report

Other maintenance pricing overviews add regular dependency audits and priority response for critical issues. Treat these lists as a menu, not a standard. Every provider packages them differently, so compare what is written in the agreement, not what the sales page implies.

What is usually not included

New features, redesigns, large migrations and fixing problems caused by third parties’ changes often sit outside the fixed fee. That is not a trick; it is how the economics work. But it has to be written down. If “support” in your contract does not say whether small changes count, you will find out at the worst moment.

What it costs in Switzerland

Prices vary widely by seniority, specialization and system complexity, so treat any figure as a range to calibrate, not a quote.

Hourly rates. One Swiss benchmark page for freelancers puts web development at roughly CHF 80 to 200 per hour, with small agencies often around CHF 120 to 160 and larger agencies or specialist consultancies at CHF 160 and above. Senior specialists sit at the top of the range. These are market indications published by an invoicing-software vendor, not price lists, so ask for written rates.

Retainers. There is no Swiss standard. A monitoring-and-readiness retainer for a small production system is priced very differently from a retainer that includes a block of development hours. As a reference point from our own pricing, our Run & monitor plan costs 750 CHF per month. Larger or more demanding systems are scoped individually on our pricing page.

A worked comparison

To see where the lines cross, use an illustrative calculation (the numbers are invented for the example, not a quote). Suppose hourly work costs CHF 150 per hour and a retainer costs CHF 750 per month for monitoring plus fixes within a defined scope.

Situation	Hourly cost	Retainer cost	Better fit
Quiet month, 1 hour of work	CHF 150	CHF 750	Hourly
Normal month, 4 hours of work	CHF 600	CHF 750	Roughly even, retainer adds readiness
Busy month, 10 hours of work	CHF 1,500	CHF 750 plus any out-of-scope hours	Retainer
Incident at 2 a.m., no contract	Depends on who answers	Response time defined	Retainer

The break-even is about five hours a month. If your average over a year is clearly below that, hourly is cheaper on paper. If it is close or above, the retainer wins, and you get response guarantees on top.

The table hides one thing: the cost of waiting. With hourly billing and no agreement, you are in the queue behind the provider’s retainer clients. If an hour of downtime costs you more than the retainer’s monthly fee, the decision is already made.

When hourly billing is the better choice

Hourly billing fits when:

• The software is small and stable. A brochure website with a few updates a year does not need standing support.
• Work is unpredictable or one-off. A single integration fix, a performance audit or a short investigation is easier to buy by the hour.
• You want maximum cost control. You approve each piece of work and see exactly what it cost.
• You are testing a new provider. A few paid hours show you how they communicate before you commit monthly.

Its weakness is incentives. When the provider earns more the longer a task takes, you need to trust their estimates or cap them. Swiss public-sector IT terms address this directly: the Federal Administration’s general terms for IT work contracts (January 2024, in German) distinguish a fixed price from remuneration based on effort with an upper cost limit. You can borrow that idea in a private contract: hourly billing with a ceiling you must approve to exceed.

When a retainer is the better choice

A retainer fits when:

• The system makes money or serves customers. Online shops, booking platforms and customer portals cannot wait days for a fix.
• Dependencies age constantly. Frameworks, libraries and payment or shipping APIs change. Regular updates are cheaper than emergency upgrades.
• You have no in-house engineer. Someone must watch the system and tell you what matters.
• You want predictable budgeting. A fixed monthly line is easier to plan than a variable one.
• Knowledge continuity matters. The same people who built or know your system respond, which shortens every fix.

The weakness is paying for time you do not use, and the risk of vague scope. That leads to the contract.

What to check in the agreement

This is where most disputes start. Swiss public-sector terms are a useful checklist even for private deals. The WSL’s published general terms for IT work contracts and maintenance of individual software (status as at January 2024) point to the elements a maintenance contract should define:

1. Scope of maintenance and support. The federal terms say the type and scope of services must be specified.
2. Standby, reaction and repair times. The federal terms require contractually agreed availability, response and fault-resolution periods, with response time depending on incident priority.
3. Incident priorities. Define what counts as critical (shop down, payments failing) versus minor (a typo, a layout glitch).
4. Remuneration. Fixed fee, hourly, or hybrid, and how out-of-scope work is priced.
5. Source code and documentation rights. You should know who owns the code and whether you receive documentation, so you can leave without a rewrite.

Unused hours

If the retainer includes a block of hours, settle in advance whether unused hours roll over, expire or convert to something else. Maintenance pricing overviews flag vague scope and rollover disputes as common retainer problems. A clean answer in writing costs nothing now and avoids an argument later.

Reducing the hours you burn

A good share of support time goes to repetitive questions rather than real faults. If your users generate many routine enquiries, AI support agents can take the first line of those conversations, which leaves your retainer hours for technical work.

Notice and exit

Check the notice period, what a handover looks like if you leave, and whether the provider will document the system on exit. A provider confident in its work has no reason to hide these terms.

How to review whether your retainer still fits

Review every quarter at first, then twice a year. Use the monthly report as your evidence. It should show what was monitored, what was fixed and what was improved. Then ask three questions, in line with how maintenance pricing guides frame the review:

• Does the cost still match the complexity of the software?
• Does it match the actual workload?
• Is the response speed you pay for the speed you need?

If reports show the same few hours used every month and nothing else, consider a cheaper scope. If out-of-scope hours keep appearing, the base package is too small. If you never read the report, either the provider is not communicating or you are paying for something you do not need.

A simple decision rule

Count your last twelve months of software work.

1. Fewer than three small requests and no incidents: go hourly, with a named contact and written rates.
2. Regular requests or a system that must stay online: choose a retainer with a clear scope and response times.
3. Heavy development plus operations: use a retainer for monitoring and readiness, and bill change work hourly or as fixed-scope projects.
4. Unsure: start with a short retainer term and a review date.

The cheapest model is not the one with the lowest rate. It is the one where the scope matches the work and nobody is surprised by an invoice.

How we work with support

At Ampersand, ongoing support runs through plans rather than open-ended hourly work. Our Run & monitor plan costs 750 CHF per month, and bigger systems are scoped to what they need. The same senior engineers who build your software stay involved, so you are not explaining your system to someone new each time something breaks. You can see all plans and services on our pricing page, and examples of what we have built on our works page.

FAQ

Is a retainer cheaper than hourly billing?

Not automatically. A retainer is cheaper when you use more than the break-even number of hours each month, and more expensive in quiet months. What you gain is availability and faster response, which an hourly arrangement does not guarantee.

What happens to unused retainer hours?

It depends on the contract, and you should settle it before signing. Some providers let hours roll over for a limited period, some let them expire, and some use the fixed fee only for monitoring and readiness with no hours attached. Get the rule in writing.

Can I combine a retainer with hourly billing?

Yes, and it is common. A fixed monthly fee covers monitoring and readiness, and changes, improvements or larger problems are billed by the hour. Make sure the contract states exactly which tasks fall on which side.

What should a support agreement define at minimum?

The scope of maintenance and support, reaction and repair times, incident priorities, the remuneration model, and your rights to source code and documentation. Swiss federal IT terms treat these as core elements of a maintenance contract.

Sources

• Invoicing Software for IT Freelancers in Switzerland
• Freelance hourly rates Switzerland 2026
• Allgemeine Geschäftsbedingungen für Werkverträge im Informatikbereich und Pflege von Individualsoftware (Federal Administration, 2024)
• General terms and conditions for IT work contracts and maintenance of individual software packages (WSL)
• Custom Application Operations Support (VSHN)
• What a Managed Software Retainer Should Include (Infoloop)
• Software Maintenance Pricing Models Compared (2026)