Estimate monthly demand
The estimate counts new input characters. Results already in the cache are not counted again.
The calculator starts with the provider's billing unit
Many AI language services bill based on input character count. This usually includes letters, numbers, punctuation marks, and spaces, though specific rules may vary. Some providers also bill for generated output or for each target language individually. Therefore, use the unit specified in the actual quote. Calculating based on word count is unhelpful if the final billing is based on characters.
Also, note exactly what the price covers. Automated translation, rewriting in "Plain Language" (Einfache Sprache), and a verified version in "Easy-to-Read Language" (Leichte Sprache) are distinct services. Technical usage is just one cost component. Professional review, linguistic editing, publication, and target-audience testing may be offered as add-ons, handled internally, or included in the package.
The calculator therefore operates using three categories: usage-based fees, recurring fixed expenses, and one-time costs. Usage-based costs primarily depend on the volume of characters processed. Recurring costs include items such as base fees, support, and monthly reviews. One-time costs cover setup, terminology work, training, or technical integration. This categorization makes it possible to compare quotes with different pricing structures.
Monthly input character counts can be derived from actual content
First, tally all content the service receives during a typical month. This includes not only body text but also headings, buttons, form messages, tables, metadata, and repeated revision cycles. If the same source text is processed in three languages and the provider charges for each run, the character count is tallied three times. Test requests and discarded drafts should also be included if they incur costs.
Usage data from the past three to six months provides the most reliable basis. If such data is unavailable, select typical content from each key category, count the characters, and multiply by the expected monthly volume. For example: 40 service pages averaging 18,000 characters each and 120 short messages of 3,000 characters each result in a total of 1,080,000 input characters. Add a visible buffer for revisions.
Distinguish between ongoing requirements and a one-off backlog. Processing 200 legacy pages should not be quietly folded into a typical month’s workload but rather handled as a separate implementation phase. When volumes are uncertain, work with low, probable, and high estimates. This ensures the calculator displays not just a seemingly precise figure, but the potential costs associated with realistic fluctuations.
The type of linguistic service determines the work required for each piece of content
Translation transfers content into another language. Revision into "Plain Language" improves accessibility for a broad audience. A version in "Easy Language" targets people with greater comprehension needs and follows agreed-upon professional standards. These tasks cannot be evaluated solely based on word count, as the effort involved in selection, explanation, formatting, and review varies significantly.
The scope of a language service assignment can also vary. Some clients provide clear, approved source texts from the start. Others require technical clarification first because certain paragraphs are contradictory or incomplete. This work goes beyond mere language processing; it necessitates queries and decisions by the responsible party. The cleaner the source text, the more reliably the time and cost required for the subsequent version can be estimated.
Clarify whether only the text is being supplied or the finished layout as well. For Easy Language, quality may encompass images, page layout, and an accessible publication format. Web translations may require handling links, metadata, and input fields. A quote for a raw file is not directly comparable to the price of a fully implemented and verified web page.
Complexity and potential consequences influence the effort required for review.
An event notice containing a date and location can usually be processed faster than an explanation of eligibility criteria. Technical terms, exceptions, figures, and negative statements require special attention. Poorly structured source material also increases the workload. A flat rate can balance out such differences, but buyers should understand the types of content it covers and when additional clarification incurs extra charges.
Errors in meaning can have serious consequences regarding health, safety, legal rights, deadlines, or finances. While this does not automatically make a text unsuitable for linguistic adaptation, it does increase the need for expert review. Often, a designated person at the client organization must confirm that conditions and exceptions have been accurately conveyed. This internal time investment is part of the total cost, even if it does not appear on the service provider’s invoice.
Categorize content not just by topic, but by actual complexity. A brief confirmation of a medical appointment might be straightforward, whereas a general information page could involve numerous complex decisions. A sample taken from each key content type reveals the realistic scope of queries and corrections needed. This provides a more reliable basis for assumptions than simply assuming that every page in a given section costs roughly the same amount.
People in various roles ensure the reliability of the final version.
Several roles may be involved in creating a publication-ready language version. Translators write in the target language, editors ensure clarity, and subject matter experts verify the accuracy of the content. For Easy Language content, a review involving people from the intended target audience may also be necessary. A service proposal should clearly indicate which of these services are included and which resources the client is expected to provide.
A "four-eyes" review does not automatically imply four complete rounds of editing. A second review might focus specifically on language, subject matter, or final formatting. Therefore, ask about the purpose of each specific review step. If a provider simply mentions "quality assurance" in general terms, it remains unclear whether someone compared the output against the source text or merely checked the spelling. Varying levels of review depth often explain significant price differences.
Internal work also incurs costs. Subject-matter departments answer questions, while editorial teams provide source materials and publish results. This time investment is easily overlooked because it does not appear as an external expense. Nevertheless, it should be made visible for the sake of a fair cost estimate. A service that costs slightly more-but effectively bundles queries and delivers content ready for publication-may ultimately be more economical than a cheap draft requiring extensive internal rework.
Fixed and recurring costs get their own fields.
First, enter all monthly recurring amounts. These include the service’s base fee, support packages, additional user accounts, technical monitoring, and regularly purchased language review services. Internal work can also be listed here if it occurs on a similar scale every month. Keep external invoices and internal time expenditure separate so that it remains clear later which expense would actually change under a different contract.
Alongside these are one-off costs. Typical items include setup, terminology lists, training, data protection and security audits, and CMS integration. Technical integration makes sense only if it genuinely simplifies the planned workflow. Also, factor in the time required for testing and adjustments by your own IT team. Otherwise, a low usage fee might appear attractive, even though the initial setup requires a substantial fixed investment.
Do not spread one-off costs unnoticed across an arbitrary term. For the annual analysis, they are fully allocated to the first year. When comparing offers spanning three years, you can also calculate a specific three-year total. This keeps two key figures visible: the initial funding required and the projected cost of normal operations thereafter.
Included volume, excess usage, and peak months affect the price
Many packages include a specific character allowance. Subtract this volume from the input character count for the given month, but never below zero; only the remaining excess usage is billed additionally. Unused volume may only be carried over to the next month if the contract expressly permits it. Otherwise, an annual average figure is misleading, as a quiet month does not automatically offset an expensive peak month.
Adopt the exact rule for excess usage. Some providers bill per started block of 100,000 characters, while others bill on a pro-rata basis per million characters. With block billing, the remainder is rounded up to the next full block. Also, check price tiers, minimum charges, and potential limits. These details can lead to significantly different invoices for the same character count.
Base your calculations on at least one normal month and one peak month. An annual report, a campaign, or the initial processing of an existing dataset can multiply usage in the short term. Specify the character count and the number of affected months for each scenario. Rush surcharges, additional verification, or temporary user accounts are also allocated to the peak month if they actually occur then.
A simple formula yields monthly and annual costs
For pro-rata billing, the rule is: excess usage equals the monthly character count minus the included volume, with a minimum of zero. Multiply the excess usage by the price per character, or divide it by the included one million characters and apply the price per million. Monthly costs comprise the base fee, charges for excess usage, and any recurring additional costs. In the case of block-based billing, usage is rounded up to the nearest full block before the calculation is performed.
An example makes the calculation verifiable. The service costs 650 euros per month and includes an allowance of one million characters. Each additional million characters costs a pro-rated 120 euros. Monthly fees of 900 euros for review and 180 euros for support are added to this. With a volume of 1.8 million characters, the excess usage amounts to 800,000 characters, resulting in a cost of 96 euros. A standard month therefore costs 1,826 euros.
In two peak months, the volume reaches three million characters each. The excess usage amounts to two million characters, costing 240 euros. Each peak month thus costs 1,970 euros. Ten standard months total 18,260 euros, while two peak months total 3,940 euros. Including the one-time setup fee of 2,400 euros, the total cost for the first year comes to 24,600 euros. This calculation can be repeated for any offer using the same volume figures.
Internal rework can significantly alter what initially appears to be a low price.
During a trial run, observe how long it takes your organization to reach the publication stage. This includes gathering sources, answering questions, comparing text, explaining corrections, and entering content. These minutes add up quickly across many pages. Use a realistic internal time value to compare offers with varying levels of "delivery readiness." While this figure need not be added to the external invoice, it should be taken into account during the decision-making process.
Watch out for recurring errors. If technical terms, links, or formatting issues require manual correction every time, this represents more than just a one-time learning curve. Estimate the frequency of these issues and the average time required to correct them. A provider who permanently reduces such errors after receiving feedback changes the costs over the course of the engagement. A sample should therefore comprise more than just a single perfect text.
Delays also have practical consequences. An outdated language version can generate support inquiries or may need to be temporarily removed. While this impact cannot always be meaningfully quantified in euros, it is part of the cost analysis. The cheapest processing option offers no advantage if content consistently arrives late, forcing internal teams to create substitute text or handle additional inquiries.
Three scenarios keep the cost calculation honest and up-to-date
Calculate low, probable, and high-volume scenarios. Focus on varying the monthly character count, peak months, and the review work required. Fixed contract costs remain constant unless a scenario triggers a different pricing tier. This reveals the usage level at which a larger package becomes more cost-effective and shows how sensitive the annual total is to volume fluctuations.
After a few months, compare your estimates with actual billing. Check whether character counts matched expectations, how often peaks occurred, and where additional rework was required. Update your assumptions based on this data. A calculation is useful if it improves decision-making and explains cost variances early on; it does not need to predict the future with euro-perfect accuracy.
The true cost of an AI language service comprises usage, fixed fees, expert review, publication, and maintenance. When quotes are calculated based on identical character counts, peak volumes, and quality standards, the differences become transparent. The organization can then make informed decisions about which tasks to outsource, which to handle in-house, and which package reliably covers both standard operations and predictable peak loads.