EDMS Pricing: Calculate Implementation and Ownership Costs

An EDMS budget needs three numbers: the supplier payment, the internal effort required to operate the system, and the combined cost over your decision period. A subscription quote alone answers only the first question, and only if its inclusions are clear.

For pharma and biotech teams, there is no useful universal price without defining the document workflow, license mix, migration and implementation responsibilities. Below is a copyable worksheet and two completed examples. All example costs are illustrative USD assumptions, not supplier quotes, market averages or an Assyro price list.

The model covers electronic document management: controlled documents, their metadata, approval workflows and ongoing administration. It does not assume the purchase includes a full quality management system, an electronic trial master file or an eCTD publisher. Keep those boundaries explicit when comparing proposals.

Copy this EDMS cost worksheet

Start with a 36-month decision period, measured from the subscription start date. Use one currency throughout. Enter annual recurring charges separately from one-time work. Record the quote version and expiration date so a colleague can reconstruct the budget later.

Use four statuses for every line: quoted, assumed, included elsewhere, or unknown. An included line needs the reference to its parent charge. An unknown mandatory cost makes the total incomplete; it is never a zero.

Copy the table into your procurement document or spreadsheet. Add columns for amount, status, evidence, owner and year. No download or registration is required to use it.

For example, a training line might read: “USD 0 additional supplier charge; included elsewhere; subscription statement of work section 4; QA lead; year one.” Staff attendance still belongs in internal launch effort. These are different costs, so counting both is appropriate.

What published pricing actually tells you

Public pricing can establish a starting point and a charging model. It cannot establish your complete budget unless the published scope matches the purchase.

As checked on October 6, 2026, SimplerQMS lists its Starter plan from USD 17,500 annually for up to 15 users. Its pricing page describes a recurring annual per-user model with different license types and included implementation, validation services, migration and training. This is an eQMS offering with document control, not a stand-alone EDMS market average. Ask which user types and service scope apply to your proposal; do not divide the minimum by 15 and treat the result as a universal seat rate. SimplerQMS pricing and licenses.

Qualio takes a different approach: its pricing page requests a tailored quote, states that an implementation fee applies to all plans, and distinguishes edit users from basic users. Foundation lists five edit users and unlimited basic users; additional edit users carry a fee. Those distinctions affect a document-control budget, but the page does not supply a complete dollar quote for your workload. Qualio plans and pricing.

These examples explain why “20 users” is an insufficient request for pricing. Twenty people who only read documents may have a different licensing consequence from twenty authors or approvers. Neither supplier's stated service inclusions remove the need to identify your own staff responsibilities.

For a broader purchase including CAPA, complaints or supplier quality, use the QMS software cost guide alongside this worksheet. Compare equivalent scope before comparing totals.

Calculate supplier spend and total resource cost separately

Use these formulas for each year:

Annual supplier spend = subscription + separately charged recurring services + one-time supplier work falling in that year.

Annual internal cost = launch hours in that year × loaded hourly cost + operating hours in that year × loaded hourly cost.

Where roles have different rates, calculate each role separately and add the results. A loaded hourly cost is your finance-approved measure of employee time, including whichever employment costs your organization allocates. It is not automatically a new cash payment.

Annual total resource cost = supplier spend + internal cost.

Three-year TCO = year-one total + year-two total + year-three total.

Include each transition or exit charge in the supplier spend or internal cost for the year it occurs, exactly once. For example, adding a USD 5,000 supplier exit charge in year three to the USD 125,320 scenario below produces USD 130,320 total TCO. Do not add that charge again after summing the annual totals.

TCO here means total cost of ownership within the stated scope and period. It is an undiscounted planning total, not a net-present-value calculation or an accounting classification. Exclude recoverable taxes consistently; add nonrecoverable taxes and currency conversion where they apply. The examples below exclude all taxes, financing and foreign-exchange effects.

Track payment timing separately. A three-year prepaid contract can create a large first-year cash requirement even when your comparison allocates subscription cost across three years. Conversely, an employee's allocated time increases resource cost without increasing that year's payroll. Finance should see both views.

Example 1: A small biotech establishing controlled documents

This fictional planning scenario has ten internal users, two external reviewers, 2,000 existing documents and one approval workflow family. The assumed subscription covers all twelve users, standard hosting, support and the selected document workflow. There is no new custom integration or legacy-system subscription overlap. This is not a description of a named vendor's offer.

The team budgets supplier configuration and migration separately. Internal launch work includes inventory cleanup, requirements decisions, acceptance review, procedure updates and training attendance. Recurring staff time covers administration and routine review activities. The hours are planning assumptions, not a benchmark for how long these tasks should take.

The first-year supplier spend is USD 37,000: USD 24,000 plus USD 13,000 in one-time services. Internal effort adds USD 23,040. With unchanged scope and rates, three-year supplier spend is USD 85,000 and internal resource cost is USD 40,320, producing USD 125,320 three-year TCO.

This budget assumes the subscription and operating allocation run for twelve months in year one, including the implementation period. Do not also add a full twelve-month administration allowance outside this table. If administration starts later, model the actual months and preserve any launch effort that still occurs.

The decision is now more useful than “Can we afford USD 24,000?” The team must find USD 37,000 for supplier payments and make 256 staff hours available in the first year. If those people cannot provide the time, the plan needs a different schedule or a priced services alternative.

Example 2: A multi-site sponsor replacing an established repository

This second fictional planning scenario has 60 internal users, 25 external participants, 40,000 documents, three sites and two required integrations. The assumed subscription includes the stated user population and standard hosting. Annual connector maintenance and enhanced support are separate. Historical versions and metadata must be assessed before the migration statement of work is accepted.

The example assumes the old repository can be retired without additional subscription overlap and that no exit fee falls inside the three-year horizon. Those are explicit scenario choices. A real replacement project must price continued access or export services if they are required.

First-year supplier spend is USD 119,600. Internal launch and operating effort contribute USD 70,800. Across three unchanged years, supplier spend totals USD 234,800 and internal resource cost totals USD 128,400, producing USD 363,200 three-year TCO.

The two examples should not be read as a market price range. They have different workloads, assumed supplier fees and staff requirements. Their purpose is to show where a purchasing decision changes: the larger example depends heavily on the migration boundary and integrations, while the smaller example needs a realistic allocation of scarce internal staff time.

Stress-test the assumption most likely to change

Start with an assumption you can investigate, rather than adding an unexplained percentage to every line.

Migration sensitivity: in the second example, suppose discovery shows that the migration requires USD 44,000 in supplier work instead of USD 22,000, plus 100 additional internal hours at USD 100/hour. The combined increase is USD 32,000. Year-one resource cost becomes USD 222,400, and three-year TCO becomes USD 395,200. Recurring annual cost remains USD 86,400 because this scenario changes only launch work.

That gives procurement a specific next action: inspect a representative export and obtain a bounded migration estimate before approving the project. A document count alone cannot describe missing metadata, duplicate versions or inaccessible historical material.

Renewal sensitivity: return to the first example and assume a 5% annual subscription increase, compounded at each renewal. Subscription cost becomes USD 25,200 in year two and USD 26,460 in year three. Hold internal rates and hours constant to isolate this change. Three-year TCO rises from USD 125,320 to USD 128,980, an increase of USD 3,660. This is an assumed scenario, not a claim about any vendor's renewal policy.

Ask for a second quote scenario when adding users crosses a license band. Do not extrapolate a linear seat price if the contract uses minimum commitments, role-specific licenses or site tiers. For growth during the term, record the addition date and the actual proration rule.

Resolve scope gaps before presenting the budget

The largest budgeting mistakes often begin as an ambiguous responsibility. Use the following questions to turn an attractive headline price into a reviewable proposal.

1. Who can perform each action? List authors, reviewers, approvers, administrators and outside collaborators. Ask the vendor to map each action to an included license, rather than accepting “unlimited users” without role definitions.
2. What does migration include? Specify source systems, document and version counts, metadata fields, historical evidence, exception handling, reconciliation and acceptance. Name who cleans the source and resolves failed records.
3. What assurance work is delivered? Identify documents, test evidence, configuration coverage and customer responsibilities. A supplied package should have a clear acceptance boundary; do not assign a zero to your own review effort without examining the work.
4. Which environments and interfaces are priced? Confirm production and any required test environment, identity integration, connectors, API access and maintenance. Distinguish a connector license from the work of implementing the interface.
5. What changes the renewal bill? Record escalation, notice periods, minimums, additional users, storage growth and the procedure for reducing licenses. Retain the written answer with the quote.
6. What happens at exit? Ask for export formats, history and metadata scope, assistance fees, continued read access and deletion arrangements. If an exit price is unknown, report it as an excluded uncertainty rather than declaring lifetime cost complete.

Keep document-system costs separate from downstream publishing. If the project also buys submission assembly or publishing services, add a distinct work package using the eCTD software cost guide. A connector between the systems is not evidence that both licenses are included.

Check the worksheet before sharing it

A blank is not a price. If configuration is mandatory but the fee is unknown, report “known subtotal plus unpriced configuration.” An optional feature can be excluded if the document says the chosen workflow does not require it. A genuinely included service can carry zero incremental supplier cost, with its parent contract line referenced.

Apply that rule to example 1: remove the assumed USD 4,000 migration fee because the supplier has not scoped historical versions. The known first-year supplier subtotal is now USD 33,000, and the known three-year resource subtotal is USD 121,320. Neither is the final cost: show each as subtotal plus unpriced migration. Assign the data owner to provide a representative export and procurement to obtain the fee. Restore a complete total only after the scope and amount are accepted. Replacing the missing fee with zero would incorrectly turn a less complete estimate into a cheaper proposal.

Reject negative hours, negative license counts and unexplained negative costs. Show a confirmed discount as a separate adjustment to the appropriate supplier charge. Do not apply it to internal labor. Use whole people for license counts and the agreement's billing rules for partial periods.

Reconcile the worksheet in both directions: every quoted fee should appear once in the model, and every mandatory workflow should have a cost or a documented inclusion. Then ask an operational owner to confirm the hours and a finance owner to confirm rates, taxes and payment timing.

The result should state: decision period; currency; workload; first-year supplier spend; recurring supplier spend; internal hours; total resource cost; exclusions; and unresolved inputs. That compact record is useful to a human reviewer or an AI assistant helping compare proposals, because the assumptions travel with the numbers.

If you are considering Assyro for a regulatory-document workflow, bring that completed record to a discussion with the Assyro team. Ask for the exact current scope, inclusions and responsibilities against your requirements. A written, scoped proposal is the next input to the model - not a substitute for completing it.