What a document management system actually costs

Try looking up what a document management system costs. In most cases you will not find a number. You will find a contact form. The price exists, but it arrives after a call, a demo and a tailored quote, which means two or three weeks later.

For a company of ten people that is not a formality. It is the difference between deciding in two minutes and opening a sales conversation just to learn whether something fits the budget at all. This article lists the items that actually make up the cost of a DMS, so you can do the maths even when no price list is published.

Why almost nobody publishes a price

In the traditional document market, a public price list is the exception. The established vendors, the ones selling to mid-sized and large organisations, almost all work from custom quotes. From their side the reasons make sense:

• the price depends on modules, integrations and seats, and the combinations are many;
• the project nearly always includes consulting days, which can only be estimated after seeing the company;
• a reseller network works on different margins, and a single public list would squeeze them;
• a published number can be compared, and a salesperson would rather explain the value first.

The practical consequence, though, lands on you. Without a reference point you cannot tell whether you are looking at twenty euros a month or a twenty thousand euro project, and you cannot compare two offers until you have requested both.

The line items behind the cost

A serious quote contains far more than the licence. These are the items to ask about, one at a time.

Licence or subscription. This is the number everyone looks at. It can be monthly, annual or perpetual. Be careful with a perpetual licence: it almost always comes with an annual maintenance fee, without which you receive neither updates nor support.

Number of users. This is where the real difference sits. Some vendors count named users, others concurrent sessions, others separate full users from read-only ones. Always ask how a colleague who logs in twice a month is counted. In some price lists they cost the same as someone working in the system all day.

Storage. A document archive grows and never shrinks. Check how much is included and what an additional gigabyte costs, because this is the item that quietly swells over the years.

Setup and configuration. Folder structure, permissions, document types, approval flows where needed. In the cloud this is often included or inexpensive. In an on-premise project it is a line measured in days.

Migrating what you already have. Bringing in twenty years of folders is not a copy and paste. Someone has to decide what goes in, how it is named and how it is classified. Ask whether it is included and for how many gigabytes.

Training. A few hours, but they belong in the budget, including the working time of the people attending.

Usage-based items. OCR, automatic data extraction, AI features: these are often billed by volume or by credits. Ask for the unit price and estimate your real monthly volume.

Infrastructure, if you host it yourself. Server, operating system, database, backups, certificates, and above all the hours of the person keeping it all running.

The three pricing models

Almost every offer follows one of these three shapes, and knowing which one you are facing helps predict how the cost will grow.

Per user. Linear and predictable while the team is small. At twenty or thirty people it becomes the dominant line, and it is the model that punishes anyone who wants to give everybody read access.

Per company. A flat fee with users included up to a threshold. Good for larger teams, less good when there are two of you. The risk is the tier jump: you move from one plan to the next in a single step, and the difference can run into hundreds.

By volume. Per document, per page or per gigabyte. It looks like the fairest model and is the hardest to forecast, because nobody knows how many pages next year will bring.

The three-year sum for ten people

A monthly fee tells you very little. The number that matters is what you will have spent by the end of the third year, with everything in it.

For a ten-person company in the cloud the sum is built like this: annual fee, plus users beyond the included threshold, plus any extra storage, plus usage-based items, plus the onboarding effort in year one. If the fee is published, you can do that calculation yourself in ten minutes.

For the same company hosting in-house, the sum has a different shape: a high figure in year one covering licence, installation and migration, then a lower annual maintenance charge, to which you must add what almost no quote writes down, namely the internal time for updates, verified backups, certificates and restore drills. Those are days, not minutes, and they should be valued at the real cost of the person doing them.

The practical rule: a comparison based only on year one favours the cloud, a comparison based only on the licence favours self-hosting. Only the full three years tell the truth.

”But there is a free option”

It is a fair question, and the honest answer is yes: there are excellent open source projects for storing documents, with no licence cost at all. You do not beat zero on price, and there is no point pretending otherwise.

What differs is what you buy alongside the software:

• who answers when it breaks. With open source that is you, or a consultant billed by the hour when it happens;
• security updates, which have to be tracked and applied, not merely downloaded;
• verified backups, meaning the ones somebody has actually tried to restore;
• accountability. If the archive becomes unrecoverable, with a vendor you have a contract and a counterparty. With a self-built installation you have a colleague who feels terrible;
• time. A well-kept installation asks for a few hours a month, every month, for years.

If your company has a technical person who genuinely has that time, open source is a reasonable choice and deserves respect. If that person does not exist, the cost has not disappeared. It has moved onto someone who should be doing something else.

Questions to ask before signing

Take these into the conversation. They are worth more than another demo:

1. How many users does the price include, and what does the tenth cost?
2. How much storage is included, and what does the next gigabyte cost?
3. Are setup, migration and training included? If not, how many days do you estimate?
4. Are OCR and AI features billed by usage? What does one unit cost?
5. Is the maintenance fee mandatory? What stops working if I do not renew it?
6. What price increases apply at renewal?
7. If I leave, how do I get my documents back, in what format, and at what cost?

The last one is the most important and the most frequently skipped. An archive you cannot take with you is an archive that has bought you.

Where we stand

Blina Space publishes its prices, deliberately. There are three plans: Starter at 15 euros a month with 2 users and 25 GB, Team at 29 euros with 4 users and 250 GB, Business at 59 euros with 8 users and 1 TB. Extra users are 6 euros each, the trial runs 15 days and asks for no card. Paying annually gives you two months free.

Included from the start is what elsewhere is sold as separate modules: OCR, search across the content rather than the file name, an AI assistant working on your own documents, chat and file transfer, a recycle bin with restore, an activity log, virus scanning on every file, a dedicated database per company and hosting in Germany.

For an on-premise installation the price depends on the number of seats and the level of support, so it stays on request. But the cloud subscription, which is what nearly every company writing to us actually needs, is published on the site, no phone call required.

That is not generosity. A decision worth 29 euros a month does not deserve three weeks of sales process, neither for you nor for us.