Nextpoint pricing: per-user, per-GB and per-document in one model

Nextpoint pricing: per-user, per-GB and per-document in one model

Nextpoint’s pricing page is framed around simple per-user software pricing while also referencing per-GB and per-document units. The page publishes no price figure and directs readers to contact the company.

That combination matters because a multi-unit quote can look straightforward on the page but remain ambiguous in a proposal. The central question is not simply how many units appear; it is which unit establishes the base price, which units operate as add-ons, and what activity causes each additional charge.

This page was checked in November 2026. It is not a review, and nothing was tested. Pricing pages and product documentation change, so current pricing and capability should be verified with Nextpoint before a budget, purchase order, or matter estimate is approved.

What Nextpoint’s published pricing page establishes#

Nextpoint uses the language of per-user software pricing as its lead framing. It also references per-GB and per-document units. That does not disclose a combined price or reveal how the units are weighted.

The page provides no figure to quote and no explanation of whether users, data volume, or documents form the foundation of a quote. Its stated path for obtaining pricing is a conversation with the company. As a result, any numerical estimate would go beyond what the published page establishes.

The practical value of the page is the presence of three familiar pricing dimensions: seats, data volume, and document count. Those dimensions allow a buyer to identify the structure that deserves scrutiny, but not the amount that Nextpoint would quote for a particular matter or organization.

Why leading with per-user changes the cost exposure#

A seat-based model links the primary software charge to the number of people with access rather than directly to the amount of data they must review. In conceptual terms, that decouples the base subscription expense from corpus size. It does not establish that every other variable is free or unchanged, particularly when the same page also references volume and document units.

For a small review team working with a large corpus, a per-user foundation may fit the matter profile better than a model whose principal driver is data volume. The number of users remains limited even if the amount of material is substantial. The question for procurement is whether per-GB or per-document charges would then apply to the same corpus and processing activity.

The opposite profile presents different exposure. A large team working with a relatively small collection may produce more seat expense under a user-led structure, while the volume-based components remain comparatively limited. A matter with many temporary reviewers can also make the timing and duration of seat charges more consequential than the static size of the team.

This is not a prediction about Nextpoint’s quote. It is a reason to distinguish between the published emphasis—per-user pricing—and the possible composition of the actual price. The page does not state the proportions, thresholds, exclusions, or add-on mechanics needed to calculate either profile.

Per-user, per-GB and per-document measure different pressure points#

Per-user pricing treats access and staffing as a cost driver. Per-GB pricing treats data volume as a cost driver. Per-document pricing treats document count as a cost driver. A quote that contains all three therefore combines measures of team participation, collection size, and document population.

Those measures can rise independently. A team may add reviewers without adding data. A collection may expand through a custodian production without changing the review population. Documents may be collected or processed without a corresponding increase in the number of users. Whether each event triggers a charge under Nextpoint’s model is not stated on the pricing page.

Per-GB and per-document units should not be treated as interchangeable merely because both are listed. One is tied to a unit of storage or transfer, while the other is tied to a unit of documents. A document’s size, the processing stage, and any volume thresholds can make the two dimensions behave differently, although no such mechanics should be assumed without written confirmation from the vendor.

The same caution applies to the phrase “one model.” A page can present several units while still requiring a proposal to determine whether they are components of a single package, optional services, or separately triggered charges. The published page does not resolve that structure.

Which unit actually drives the quote?#

The first item to clarify is the base. The quote should state which unit Nextpoint is using to establish the primary price: per user, per GB, per document, or some stated combination. Without that information, the total cannot be compared with another proposal that is organized around a different unit.

Ask what each listed unit prices. For a per-user component, identify whether the count includes administrators, reviewers, project managers, or other users. For a per-GB component, identify whether the volume is measured at ingestion, processing, hosting, or another point. For a per-document component, identify which population of documents is counted and at which stage.

These are inquiry points, not assumptions about Nextpoint’s billing system. The point is to turn a sales conversation into a quote whose calculation can be inspected. A list of unit names is not enough if the triggers and counted events remain undefined.

Make the add-on mechanics explicit#

Where multiple units appear together, the relevant question is not only which one is primary. It is which apply as add-ons and what causes them to apply. Per-GB or per-document charges might be included in the base arrangement, activated by particular services, or quoted separately; the pricing page does not say which.

A useful written response would identify any minimums, thresholds, included allowances, or service-specific charges associated with each unit. It should also show whether a charge is calculated once, accrues through the matter, or changes when the underlying data or staffing changes.

That level of detail also prevents double counting during internal comparisons. If one proposal includes hosting within the per-user price and another adds hosting as a separate line, comparing only the headline amounts would not be meaningful. The comparison needs the same cost categories on both sides.

What happens when the team changes mid-matter?#

Per-user pricing creates a direct question for matters with changing staffing. Additional reviewers may increase the user-based amount. The quote should address whether users are counted when provisioned, when first active, when they complete assigned work, or at another defined point.

The timing of an added seat can matter as much as its price. If a reviewer is added for a short period, the quote should make clear how the period is treated and whether an unused remainder remains billable. A matter that pauses review may also raise questions about when seat charges continue and whether the count resets.

Ask for an example calculation using three stages: the planned review team, a temporary expansion, and the post-review team. The purpose is not to substitute a hypothetical for a proposal. It is to expose how the quote responds to a common source of scope change before that change occurs.

What happens as the corpus changes?#

The per-GB and per-document references make data growth a second issue. The quote should state whether new productions, refreshed collections, or later-loaded material affect the measured volume or document count. It should also distinguish original collection from subsequent production activity.

A useful clarification is whether any per-GB or per-document amount is a one-time charge or a recurring charge tied to retained data. That difference affects how an extended matter is budgeted. The published pricing page provides no basis for choosing one treatment over another, so the treatment must appear in the proposal or written response.

Hosting after review is complete#

The question of what happens when review ends is separate from the review-platform charge. A matter may remain open after active review stops, or records may need to remain available for an appeal, audit, production, or retention obligation. The reader should ask which hosting or data-retention charges continue during that period and whether they are governed by the per-GB, per-document, per-user, or another arrangement.

Also ask when hosting ends, how long data remains available, and what deletion or return process applies. Those are pricing mechanics, not compliance conclusions. A practical team can then estimate a post-review period without assuming that the software charge and the hosting charge expire at the same time.

Any question about legal retention or the end of a duty to preserve is matter-specific and jurisdiction-dependent. This analysis does not provide legal advice and does not determine when data should be deleted or retained. The relevant issue here is only whether the commercial terms make those periods visible.

A matter-profile comparison#

This framework keeps the comparison tied to named dimensions. It does not assume that Nextpoint’s quote will fall into any particular structure, and it does not establish that one unit is more favorable than another.

Make competing proposals comparable#

Comparisons with other vendors should begin with the pricing unit each proposal actually uses, not the language on a marketing page. Nextpoint’s page references per-user, per-GB and per-document units. For context, the Logikcull pricing page references per-GB and per-month units, while the DISCO pricing page references a per-document unit. The Everlaw and Relativity pricing pages name no pricing unit.

Those pages were also checked in November 2026, publish no price figures, and route readers to a sales conversation. A meaningful proposal comparison therefore requires normalizing the same items: base subscription, included data or document allowances, additional users, processing or review charges, hosting after review, and any other recurring or contingent fees.

Comparing a per-user model with a per-document or volume-led proposal without that normalization risks comparing different cost categories. It also risks mistaking an undisclosed mix of units for a single, simple basis. The proposal—not the pricing-page framing—must supply the calculation.

Questions for the written quote#

1. Which unit establishes the base price?
2. Which other units are included, optional, or triggered automatically?
3. What event causes each per-user, per-GB, and per-document charge?
4. Which users, documents, and data volumes are included in the base arrangement?
5. How does the quote change when the team grows or shrinks mid-matter?
6. How are temporary users and periods of inactivity treated?
7. How are later productions and changes in corpus size treated?
8. Which hosting, retention, export, or deletion charges apply after active review?
9. Are any charges recurring, one-time, minimum-based, or subject to thresholds?
10. Can the vendor provide a calculation showing how each unit contributes to the quoted amount?

A proposal that answers those points can be evaluated against another proposal on consistent dimensions. A proposal that does not answer them remains difficult to compare, even when it lists several familiar pricing units.

The procurement takeaway#

Nextpoint’s published framing places per-user software pricing first while also referencing per-GB and per-document units. The published page provides no figure, so the amount and composition of a quote cannot be determined from it.

The central issue is the unit behind the base price and the triggers behind everything else. For a small team facing a large corpus, the user-led framing may appear to align with the matter profile. For a large team facing a smaller collection, user exposure may matter more. The mixed units make that distinction provisional until Nextpoint states the calculation in writing.

Current pricing and capability should be verified with the vendor because the page can change. The relevant next step is a written quote that identifies the base unit, each additional unit, every trigger, mid-matter adjustments, and post-review hosting.