We hear this surprisingly often from social institutions: only after implementation do they discover how much ongoing help they need to buy from the software vendor. A small usability question, an unclear error message or a workflow adjustment quickly turns into another billable support hour.
The quote clearly listed the licence, implementation and data migration. What remained unclear was how often the team would later need to call the vendor or open a ticket. These are the support costs that are rarely calculated during software selection, yet can burden the operating budget for years.
The problem is not that a vendor offers good support. It becomes expensive when its software creates avoidable support needs and every question carries an additional charge.
Vendor support is rarely simply “included”
Many vendors advertise personal support. That sounds reassuring, but says little about the later cost. Depending on the contract, requests may be billed:
- according to actual time and an hourly rate
- in minimum units, such as 30 or 60 minutes per request
- through a monthly support plan or prepaid hour allowance
- with surcharges for short response times, prioritisation or out-of-hours help
- as paid consultancy once a request is not classified as a technical defect
- as separate customisation when fields, roles, templates or workflows must change
All of these models can be legitimate. The risk arises when it is not clear before signing what help is included and which everyday questions will trigger an invoice.
How poor UX turns into billable vendor support
An outdated or confusing interface is more than an inconvenience. It can become a lasting commercial risk for the customer. When common tasks are difficult to complete without help, the vendor's support desk becomes part of the normal workflow.
Unclear navigation creates recurring usability questions
Employees cannot find a function, miss a status or do not know where an entry was saved. The vendor explains the route by phone or remote access. The immediate question is answered, but the cause remains. The same billable request returns with the next team or after the next staff change.
Unclear workflows are billed as consultancy
Who approves a report? Why can a dossier not be closed? What must happen before billing? If the software does not clearly show status, responsibility and next step, the vendor must explain the workflow.
The distinction can be difficult: is the cause a knowledge gap in the institution, unsuitable configuration or a poorly designed process in the product? Without a clear agreement, even a question created by the software may be treated as paid consultancy.
Unhelpful error messages make the vendor indispensable
A message such as “Operation failed” gives the user nowhere to go. If neither the cause nor a useful next step is shown, only the vendor can explain what to do. Good messages cannot solve every technical issue, but they prevent simple corrections from automatically becoming support cases.
Only the vendor can make small changes
If every change to a dropdown, role, template or process stage requires a paid ticket, small organisational developments add up. Social institutions change services, responsibilities and reporting requirements. Their software should support ordinary adjustments without forcing them to buy external specialist hours for every detail.
Updates create new demand for explanations
New releases are essential for security and improvement. But when interfaces or workflows change without clear guidance, every update creates another wave of requests. Institutions should clarify how changes are communicated and whether help with vendor-created changes is billable.
A simple calculation for external support costs
An initial estimate can use this formula:
Vendor support hours per month × hourly rate + support plans, surcharges and minimum billing units
A deliberately simplified example: an institution buys an average of six vendor support hours per month. At CHF 220 per hour, that is CHF 1,320 per month or CHF 15,840 per year. Internal time spent describing the problem, coordinating appointments, testing and following up is not yet included.
Minimum billing units can increase the total further. If ten 15-minute questions are each billed at a one-hour minimum, the institution pays for ten hours rather than two and a half. This is not an industry benchmark, but it shows why the billing logic matters as much as the hourly rate.
Questions that should be answered before signing
Our software selection guide covers the wider evaluation. To understand future support costs, institutions should also obtain written answers to these questions:
- Which support services are included in the licence or base fee?
- Which requests count as defect resolution and which as paid consultancy?
- Who pays when an issue or change is caused by the vendor's update?
- Which hourly rates, minimum units and surcharges apply?
- Does billing begin as soon as a ticket is received and analysed?
- Which response and resolution times are agreed?
- Can costs above a defined amount require advance approval?
- Which settings can the institution manage itself?
- Are documentation, training materials and release notes current and included?
- Does the institution receive a transparent report of cases, causes and billed time?
Do not only ask for an explanation of the support process. Let different employees test typical tasks and deliberately difficult situations. The more explanation a demonstration requires, the more carefully you should estimate the paid support that may be needed later.
Fair support solves problems instead of selling the same explanation repeatedly
Competent vendor support has genuine value. New requirements, complex integrations, data migrations and unexpected technical incidents need experienced people. Good vendors explain when charges arise, document their work and help eliminate recurring causes.
A warning sign is when similar tickets are billed repeatedly without improvements to usability, documentation or configuration. If the same request occurs among several customers, the vendor should consider whether the product itself needs to become clearer.
The fair question is therefore not only “Why do your employees need so much help?” It is also “Why does this part of the product repeatedly require an explanation?”
Reducing support charges in an existing contract
- Review invoices and tickets together: classify the last six to twelve months by cause, duration and cost.
- Identify repetition: mark questions that recur or appear in several teams.
- Separate defects, usability issues and change requests: these categories should not automatically be billed in the same way.
- Discuss root causes with the vendor: for frequent cases, request improvements to UX, documentation or configuration rather than another individual explanation.
- Increase self-service: clarify which roles, templates and workflows your team can manage. Our page on customisation explains why this matters.
- Agree cost controls: define allowances, approval thresholds and transparent reporting.
- Compare total costs again: include realistic vendor support in renewals and future software decisions.
The real price of software appears during operation
A low licence fee can become expensive when the institution must buy vendor assistance for every ambiguity. Modern UX, understandable workflows, good documentation and sensible self-service are not convenience features. They directly affect how dependent an organisation remains on paid vendor support.
Lua aims to provide support where it creates real value, not to keep billing for avoidable usability problems. We would be happy to demonstrate this with one of your real workflows and show how a clear, adaptable solution reduces day-to-day support needs.
