Before a six-figure data quote, make your archive countable
You have email, chat, tickets and documents. The next question is which systems, which dates and which records can actually be included in a company-data license.
A company archive can look valuable in an intake form and still be difficult to quote. “We have eight kinds of tools” says something about the business. It does not tell a buyer whether there are usable exports, whether the same years overlap, or whether customer data has been mixed with the company's own operations.
In a company-data buyer conversation, the recorded November 3 to 7 follow-ups asked for export formats, date ranges, sizes, tool names and a complete systems list before an offer. That is the owner decision this note addresses: what should you establish before turning a public six-figure benchmark into a spending plan?
Eight tool categories are not eight scoped exports
We reread one software-company intake and its earlier duplicate on November 14, treating them as one company. The fuller intake selects eight tool categories. It reports five years overall but gives longer periods for four individual categories. The structured systems list has not been saved.
One owner intake, checked November 14. Form completeness is not a data-quality score. 4 ÷ 8 = 50% of categories have an individual year answer.
| What the fuller intake establishes | Count or scope | What it does not establish |
|---|---|---|
| Selected tool categories | 8 | Eight named, accessible and deliverable systems |
| Categories with individual year counts | 4 of 8 | Exact start and end months, or an export covering those dates |
| Saved structured systems lists | 0 | That the company has no data or cannot export it |
| Overall history versus category answers | 5 years overall; 10 to 12 years for the four specified categories | A single reconciled licensing period |
Visible calculation: 4 ÷ 8 = 50% of selected categories have a category-level year answer. This is one owner's form completeness, not a market average, a data-quality score or an acceptance probability. The missing systems list describes this console record, not every document the owner might hold elsewhere.
The gap is resolvable. An overall five-year proposal might deliberately exclude older material. Or the overall answer might need correction. We cannot choose between those explanations from the form. The useful next action is to reconcile the intended period, rather than silently appraise every category at its longest stated history.
Why operational context is attracting attention
The October 23 CRM-Agent-Bench preprint evaluates agents on stateful business tasks using checks on actions, order, final state and protected state. Its 555 tasks span nine business domains. This is research evidence that business-agent evaluation can depend on how a process unfolds, not only the final answer. It is not a buyer request for these particular records. CRM-Agent-Bench.
Our practical inference is to preserve links and chronology when scoping an archive. A ticket with its resolution, relevant work history and associated documents may describe a process that an isolated screenshot does not. That does not authorize bundling every system or every customer's information. Scope and permissions still determine what belongs in the review.
The money: company-level benchmarks need company-level scope
Rightmark's Q4 Price Index lists operating companies with at least 30 staff and English records at $185,000 to $1M+ per company. Its detail for 30 to 99 staff gives $185,000 to $720,000, depending on years and region, with Medium confidence. This is a published program summary, not the quote for the intake above. Price Index, checked November 14.
| Reference or planning amount | Unit | How to use it |
|---|---|---|
| $185,000 to $720,000 | USD per qualifying company in the 30 to 99 staff reference band | Context for a scoped operating-company review, with years, region and terms still relevant |
| $10,000 to $100,000 | USD per shut-down startup archive, code and workspace | A different company situation; not a price to add to the operating-company band |
| $3,000 | Hypothetical 40 hours × $75 per hour | A preparation-cost illustration, not a measured charge or recommended budget |
The operating-company number is not a price per app. Eight selected categories do not produce eight times $185,000, and one company filing two forms does not become two licensable archives. A range also does not tell you how much exclusivity, de-identification or export support a proposed agreement will require.
For cost planning, imagine a hypothetical written gross quote of $200,000 for an agreed archive and $3,000 of preparation expense. The arithmetic leaves $197,000 before other costs, fees and taxes. Neither amount is a quote for the case in this note. If there is no written quote, the honest commercial status is “proceeds unknown,” not $197,000 expected income.
The key insight is that a scope sheet lets the owner and buyer price the same thing. It can expose a missing export or a rights issue before substantial work begins. We do not have evidence that completing it causes a specific price increase.
Build a systems list that answers the buyer's questions
Use one row per real system, rather than one row per broad category. This table is a suggested template, not a record of additional facts about the case.
| Field | Useful entry | Decision it supports |
|---|---|---|
| System and owner | Actual tool, account or entity, responsible administrator | Who can confirm scope and access |
| Period | Start and end month; gaps; retention limits | Which years are truly included |
| Volume | Measured records or bytes, with measurement date; label estimates | Whether preparation and transfer are feasible |
| Export | Available format, plan restrictions and export method | What can be delivered without promising an unavailable capability |
| Connections | IDs or links connecting tickets, documents and discussions | What context survives the export |
| Exclusions | Customer-held data, personal material and restricted records | What must stay outside the proposed package |
Do not upload raw employee or customer records to establish these facts. Start with the description and confirm the review process. If access is incomplete, label it. If one tool retains two years while another retains ten, show both instead of reporting ten years for the entire bundle.
The realistic first outcome is a clarified archive scope and a decision about the next review step. The final offer, if any, remains a separate commercial event.
Sources and limits
The analysis uses two versions of one owner intake, reread in the authenticated console on November 14, plus the recorded November 3 to 7 buyer follow-ups and public Rightmark pricing pages. We did not open an export, measure the archive or verify the owner's answers. No private model estimate or commercial offer is published here. Buyer and owner identities are withheld. The form example illustrates a scoping gap; it does not measure the prevalence of that gap across Rightmark's pipeline.
Company-owned operational archives with a clear systems list
Describe the email, chat, documents, work systems and other company records you can include, with dates, volumes, export options and exclusions.
The public Wanted page has no open purchase request at this check. See the operational-data scope. Private buyer discussions do not amount to an offer for your company.
Operating-company reference, 30 to 99 staff
$185,000 to $720,000
USD per qualifying company; Medium confidence published-program reference, dependent on years, region and scope.
This is not a per-tool price, the value of the example intake or assured net proceeds. Licensing terms, rights, preparation and due diligence remain part of the actual review.
Price Index, Q4 2026, checked November 14. Indicative estimate, not an offer. An incomplete intake does not establish qualification for the band.
Reconcile the systems before requesting a quote
Prepare one row per system with its name, dates, size, export method and exclusions. Note where the overall company answer differs from a tool-level answer.
If you need help defining what belongs in the archive, talk to Rightmark. Start with scope, not raw files.