Dosya başına mı, lisansla mı: kurumunuza hangi model uyar
Her iki model de aynı platformu satın alır; farklı olan maliyetin biçimidir. Beş maliyet kalemi, her modelin bunları nereye koyduğu, hangisinin ne zaman uyduğu ve kurumunuzun kesişme noktasının hangi tarafında olduğunu anlamanın yolu.
Bu içerik henüz çevrilmedi ve İngilizce gösteriliyor.
The shape of the cost
A licence is one fixed line, whatever the year brings. Per case follows the work. Neither is cheaper in the abstract — the caseload decides, and it is worth knowing which side of the crossing you are on before you choose.
The five lines
An arbitration or mediation centre that decides to institutionalise its casework needs a system, and then has to decide how to pay for it. The conventional answer is a licence priced against the institution, and for a centre with a steady, predictable volume of work it is the right answer. Many centres are not there yet: a centre can register nine cases in one year and forty in the next, and a fixed quote cannot see that coming.
That gap is what the per-case model closes, and it is why we price both ways. What follows is what an institution actually pays for under each, so the choice can be made on the numbers rather than on the pitch. Two of the five lines stay with the institution either way, and they are set out here as plainly as the three that move.
| Cost line | Licence or build | Per case |
|---|---|---|
| The system itself | Institutionfixed A licence, or a build. Priced against the institution rather than its caseload, and payable whether the year is busy or quiet. | Vendorfollows caseload Carried by the vendor and recovered per case, so the line follows the work. |
| Integration | Institutionfixed Connecting the system to the institution's identity, mail, payments and website. Scoped once, and worth scoping carefully. | Institutionfixed Still the institution's, and smaller — there is less to connect. Worth having in the quote either way. |
| Hosting and storage | Institutionfixed Servers, backups and storage that only grows. Provisioned for the busiest year and paid for in the quietest. | Vendorfollows caseload The vendor's, and sized to what is actually used. |
| Upkeep and security | Institutionfixed Patching, dependency upgrades, certificate renewals, penetration testing, and the security review your members will eventually ask for. The same work in a quiet year as in a busy one. | Vendorfollows caseload The vendor's, and spread across every institution on the platform — which is what makes it cheaper to buy than to staff. |
| Someone who owns it | Institutionfixed A person inside the institution who knows how the system works and is answerable when it does not. | Institutionfixed Still worth having, though a smaller job. A named internal owner is what makes any system succeed, bought or built. |
Under a per-case model, 3 of the 5 lines move to the vendor. The other 2 stay with the institution under either model, and they are worth planning for rather than discovering: they are the lines that are about the institution rather than about the software.
Where the two lines cross
Neither model is cheaper in the abstract; they are differently shaped. Below a certain annual caseload, paying per case costs less than carrying a fixed platform. Above it, the licence costs less. The crossing is a real number, and it is specific to one institution's volume and one vendor's unit price.
We have not printed a figure, because an honest one depends on your caseload, your retention obligations and your seat — and we would rather work it out with you than publish a number that fits nobody. The picture is about shape. The useful question is which side of the crossing you are on, and how long you expect to stay there.
Which model fits
The crossing settles most of it: below it, per case; above it, a licence. These are the situations where the answer is clear without doing the arithmetic first.
Per case fits when
- Your caseload varies from year to year, or you cannot forecast it yet.
- You are formalising a practice that has run on email and spreadsheets, and want the system in place before the volume arrives.
- There is no capital budget this cycle, and waiting for the next one would cost you a year.
- You expect to grow into a licence, and would rather the cost followed you there than led.
A licence fits when
- Your caseload is high and steady and sits above the crossing. Past that point a licence is the better deal, and we will tell you so.
- Your burden is a small number of very long, very heavy proceedings, where the case is not the natural unit of work.
- You run several registries or chambers on one platform, where the case count stops being a useful proxy for what the system is actually doing.
- You need one fixed, predictable line in the annual budget more than you need the cost to follow the caseload.
Where the record has to live is a separate question, and it is settled before pricing rather than by it. If your statute or your members require the file to stay in one jurisdiction, we deploy to meet that under either model.
What to ask, including of us
Five questions that make a quote comparable, whichever model it is for. They are worth putting to any vendor, and we would rather answer them before signature than after.
What exactly is a case?
When does the clock start — filing, registration, or constitution of the tribunal? What happens to a case withdrawn in week two, and to one that settles before a hearing?
Is there a minimum?
A per-case price with an annual floor is a licence in another shape. It may well be the right deal, but it should be compared as the licence it is.
How do we get the record out?
In what format, on what notice, and at what cost. Worth settling before signature, and worth having in the contract rather than in an email.
Where does the data sit, and who can reach it?
Name the jurisdiction and the operator, not the certification. A certificate describes a process; it does not tell you which country holds the file or which staff can open it.
What happens when we grow?
What the price becomes at three times the caseload, and what it takes to move onto a licence. A model you can start on should also be one you can leave.
Digital transformation should not have to wait for a large budget. Nor should the way you start it become the thing you outgrow.
Which is why we price both ways.