Everlaw pricing: what is published, what is not, and what moves the number

Everlaw does not publish pricing. Its pricing page routes readers to a scheduled meeting and names no pricing unit. That is normal for the category: none of Everlaw, Relativity, Logikcull, DISCO or Nextpoint publishes a price figure on its pricing page, and every one routes to a sales conversation.

The absence of a published figure does not make an Everlaw quote unpredictable. It means the quote must be built from a matter-specific set of inputs. The variables include data volume after processing expansion, the length of hosting, the number of users who need access, the modules included and the amount of professional services required.

Those variables do not all behave the same way over the life of a matter. Some create recurring monthly charges; others are one-time charges or can recur when the matter changes. Understanding the difference is more useful than searching for a headline figure that does not exist.

What determines an Everlaw quote#

The first question is what data will actually enter the platform. The relevant figure is not necessarily the amount of data collected from a custodian or the size of a production set. It is the processed volume after expansion. Depending on the source and processing settings, that can be materially larger than the apparent size of the original material.

A quote built around an early estimate may therefore understate the billing basis if the processed volume changes later. The sales discussion should identify whether the quote uses processed data, source data, a tiered schedule or another measure. For Everlaw specifically, the pricing page names no pricing unit, so the unit must be established in writing rather than inferred from a general product page.

Data volume also affects the shape of the quote. A small, fixed volume may fall within a stated allowance or a base commitment, while additional volume may carry a separate rate. The page does not publish the allowance, the rate or the unit, so neither can be evaluated without a quote.

The second question is how long the information must remain available. Hosting has a time dimension. Review may begin while a matter is active, but the platform may need to retain the data after the review period, during appeals, regulatory inquiries, audits or internal investigations. A quote that covers the first month is not comparable with one that covers a defined period of retention.

The third question is how many people need access and what they need to do. User counts can matter where access is priced per named user, seat or role, although Everlaw’s pricing page does not state whether or how it applies that approach. The relevant distinction is between people who need to review documents and people who need limited administrative, production or permissions access.

The fourth question is which modules are included. The same underlying data can support discovery, early case assessment, legal holds, depositions, internal investigations and other workflows. Those are separate scopes of work, and a quote for discovery alone should not be treated as a quote for all of them.

The fifth question is how much professional services work the matter requires. Configuration, migration, field analysis, review assistance, production support and workflow design can require different amounts of labor. Professional services should be separated from recurring platform and hosting charges so that the recurring portion remains visible after the initial project work is complete.

Which costs compound and which do not#

Monthly charges deserve particular attention because they accumulate through the matter. Hosting is the clearest example. If the data remains on the platform for twelve months, a monthly hosting component is paid twelve times, even if no additional documents are collected after the first month. Extended retention, additional users and recurring services can compound in the same general way.

Data-based charges can also recur as the processed dataset changes. A custodian collection, a production or an expanded set of files may increase the amount of data subject to platform charges. If the quote includes an allowance, ask what happens when the matter exceeds it and whether the excess rate is applied once or in stages.

One-time charges have a different role. Initial data loading, some configuration work and certain implementation services may be one-time costs, but they should not be confused with a complete budget. A one-time charge may recur if the scope changes or if the work must be repeated for a later phase of the matter.

The distinction matters when comparing an inexpensive-looking quote with a contract that is not. Compare the first invoice and the recurring monthly run rate separately. Then model the total cost over the expected review and retention period, including any thresholds or volume changes that are contractually possible.

That exercise does not reveal a universal formula. It reveals where the quote is exposed. A matter with stable data and a short retention period has a different profile from one involving repeated collections, expanded custodians, lengthy appeals or several legal holds.

What Everlaw’s pricing page does publish#

Everlaw’s pricing page presents use cases including eDiscovery, early case assessment, legal holds, depositions, data privacy, internal investigations, and FOIA and public records. The page also names AI features including coding suggestions, a writing assistant, a review assistant, predictive coding, and clustering.

These details do not establish pricing, but they do identify the product scope that a buyer may be considering. The page says the platform connects to external AI tools so that AI outputs are grounded in the evidence held in the platform. That statement may matter in a security, privilege or defensibility review, but the pricing page does not provide the pricing treatment for those connections or AI features.

Module scope is the hidden variable in many eDiscovery quotes. A platform priced for discovery alone may not be priced for holds, depositions, privacy work and internal investigations. A quote that includes only a review workflow may exclude a function the organization expects to use later. A quote that includes several workflows may also include administrative requirements, training or support that are not apparent from the product menu.

The practical approach is to map each required workflow to a named module or service in the quote. For each one, ask whether it is included, limited, separately licensed or delivered as professional services. “Platform access” is not a sufficiently precise description for a multi-workflow matter.

The AI features listed on the page create a second list for the sales discussion. Ask which named features are included in the proposed configuration, whether there are usage limits, and what related services are separate. Keep the answers tied to the quote and to the matter’s actual workflow. Do not assume that a feature named on a pricing page is automatically included in every proposal.

Questions to take into the sales conversation#

Begin with the unit. Ask what one unit represents and how it is measured. If the proposal is based on processed data, request the expected processed volume rather than only the source-data estimate. The unit should also appear consistently in the quote, order form and applicable pricing schedule.

Then ask what happens to the price when volume doubles mid-matter. A complete answer should address whether the original allowance remains available, whether a new tier applies, whether previously processed data is reprocessed and charged again, and when the change would take effect. Written examples are more useful than a general assurance that the vendor can accommodate growth.

Ask what hosting costs after review ends. Identify the date or event that ends the paid review period, the charges for data retained afterward, and whether retention can be extended for an agreed period. Also ask whether export or deletion occurs automatically, whether a service is required to remove the data, and whether any minimum term continues after the active work ends.

Ask what is billable but not included in the quoted amount. The answer should cover implementation, ingestion, data preparation, field development, training, project management, support, special exports, reporting, production support and any services needed to implement the selected modules. A price for the platform does not answer these questions by itself.

Ask what export costs on exit. Include the format, the volume, the support resources, the time required and the destination of the exported data. Also ask what access remains while the matter closes and how long the vendor will retain or make available the material. Exit terms are easier to evaluate before a dispute develops over them than after the team needs the data.

Several further questions can keep the quote commercially legible. Ask whether the quote is an estimate or a fixed commitment. Ask which fees are recurring, which are one-time and which are contingent. Ask whether discounts or allowances depend on the term, payment structure or scope, without assuming that any particular commercial arrangement is available.

Request a complete schedule rather than relying on a summary presented during a meeting. The schedule should define the pricing unit, included modules, allowances, overages, services, support, hosting, retention, renewal and exit. If a term is not included, it should be identified as open rather than treated as zero cost.

Making two quotes comparable#

A quote can only be compared with another quote after both describe the same work. Give both vendors the same data profile, including the expected processed volume, number of custodians, file types and anticipated collection timing. Use the same matter phases, review period and retention period. Identify the same modules, user roles, service levels and export requirements.

Then insist that both vendors express the proposal in the same unit. The comparison cannot rely on a generic per-GB figure from one proposal and a per-document figure from another unless the proposal documents the conversion and applies it to the same dataset. A per-user description does not become comparable with a storage or processing measure merely by placing the two side by side.

That point applies beyond Everlaw. Logikcull references per-GB and per-month units and offers a free trial. DISCO references a per-document unit. Nextpoint references per-GB, per-document and per-user units. Relativity names no pricing unit on its pricing page. Those units describe how a proposal is structured; they do not by themselves establish which proposal costs less for the same matter.

Use a common scenario. For example, specify a processed data volume, a defined number of users and a twelve-month period during which the data must remain available. Apply the same module set to both proposals. Compare the recurring monthly charge, the one-time services and the cost of the agreed overage separately.

Run at least one variation in which the processed volume increases. Repeat the comparison for a longer retention period or a larger set of user roles. This is not a forecast of what a matter will require. It is a way to see whether a proposal remains predictable under changed conditions and whether its pricing unit interacts with the data in ways the summary does not make apparent.

Keep module definitions consistent as well. A named feature does not create functional equivalence unless both vendors describe the same workflow. Ask each vendor to identify where the specified work occurs, what staff operate it, what output it produces and what additional charges or services apply. That is more reliable than comparing feature labels.

When a proposal uses allowances, compare them at the same volume and show the next increment above each allowance. When a proposal uses monthly hosting, compare the same retention window. When a proposal includes professional services, separate labor from platform charges so that the recurring cost is not hidden inside a blended figure.

What to verify before relying on a proposal#

Everlaw’s pricing information was checked in November 2026. At that time, the pricing page published no price figures and named no pricing unit, and its call to action was to schedule a meeting. The page’s use-case and AI-feature descriptions can help structure a requirements list, but they do not establish what any proposal will charge.

Verify current pricing and capability with Everlaw because pricing pages, packaging and product names change. Ask for the current quote, pricing schedule, module definitions and service assumptions in writing. Do not carry an old figure, unit or product name forward without confirming it.

This page is not a review, and nothing was tested. It describes what was published on the identified pricing page and the quote variables that a professional buyer can check with each vendor.