Seller Guidance
How Much Is Company Data Worth To AI Buyers?
By Basic Trace | Published | Sources checked
A company's records do not have a reliable price based on employee count or storage size alone. The useful question is what a particular buyer would pay for a defined, deliverable package under agreed terms. Public payout ranges can help you decide whether to investigate, but they cannot establish what your archive is worth. This guide explains how to prepare for that review and compare proposals without turning an estimate into an assumed payment.
What Public Payout Ranges Actually Tell You
Mode advertises $100,000 to $5 million and calls its calculator illustrative. It says a fixed offer follows review of the systems, dates, history, record volume, quality, ownership and access terms. That is a buyer's advertised range, not a set of independently verified completed transactions. Checked November 8, 2026.
Treat the headline as a reason to investigate fit. It does not establish a minimum payment for an applicant, a typical seller outcome or a price for each employee. A firm outside the buyer's current requirements cannot use the bottom of the range as a floor for its archive.
Source: Mode: Advertised Range And Offer Review FAQ. Checked 2026-11-08.
Micro1 Also Prices Each Partnership Individually
Micro1's enterprise page advertises payments from $100,000 to over $3 million. Its FAQ identifies volume, workflow complexity, quality, domain expertise and uniqueness as compensation factors. These are published program statements, not an appraisal of your company. Checked November 8, 2026.
A closed company should confirm the applicable program before using an enterprise headline. An archive that stopped growing at closure is a different proposition from ongoing participation. Ask which records and future obligations the proposed amount covers, and request an explanation tied to that scope.
Source: Micro1: Enterprise Pricing, Compensation And Payment FAQ. Checked 2026-11-08.
Start With The Archive You Can Actually Offer
Our recommendation is to prepare a scope sheet before asking for a number. List each system, the dates retained, the format available and the person who can arrange authorized access. Separate an active workspace from an export on a hard drive and from an account nobody can currently open. Each requires a different delivery plan.
Then distinguish the records held from the proposed package. A shared drive might include your own operating procedures alongside customer documents, personal folders and material subject to restrictions. Describe unresolved exclusions candidly. Your advisers should assess permissions before records are offered or transferred.
Do not inflate volume by counting repeated backups as distinct operating history. Identify missing attachments, deleted channels and broken links. A buyer can assess a clearly described partial archive more sensibly than a large number that conceals gaps. None of these preparation steps guarantees interest or a particular price.
Explain The Work Behind The Files
A useful seller description explains how the records connect. For example, a support ticket might link a reported issue to an engineering discussion, a project task and a final resolution. If those connections survive in the archive, describe them. If only the final document remains, say that instead of implying a complete workflow.
Prepare a short narrative of the business: what the team did, which systems it used and how work moved between them. This is Basic Trace's preparation advice, not a buyer scoring formula. The purpose is to make the archive understandable without sending raw customer material during an introductory conversation.
Historical employee count and years in operation provide background. They do not prove how many records remain, whether the records are usable or whether the company can authorize a transaction. Avoid multiplying headcount by an invented dollar rate. Public program ranges do not support that calculation.
A Fictional Example: Two Archives From The Same Company
Consider a fictional software company that closed after six years with a peak team of 60. Its former administrator finds a shared drive, a chat export and a project tracker backup. These details are illustrative. This is not a Basic Trace client, a buyer-approved applicant or a reported transaction.
The first inventory says only that the company has a large archive. A closer review finds duplicate backups, missing chat attachments and customer folders that require separate assessment. The seller cannot yet say what could be delivered. Assigning a payout from headcount alone would hide the questions that still need answers.
The second inventory maps the retained dates and connects internal project documents to tracker records. It marks restricted folders for exclusion and identifies who can explain the systems. That preparation does not establish a higher price. It gives a buyer a clearer basis to decide whether to review the package and what further information to request.
If one buyer requests the historical copy and another also requests continuing work, those proposals cover different obligations. A closed company should identify what it can actually perform before comparing the headline amounts. A future commitment cannot be valued as though it were cash already payable.
Compare Written Offers On The Same Basis
Ask each interested buyer to describe the proposed package in writing. Compare the same systems, dates, exclusions and permissions. If the scope differs, record that difference next to the amount. A larger proposal may require broader rights or more delivery work; the amount alone will not show whether it suits the seller.
Our recommended comparison sheet has separate fields for the stated amount, conditions, payment milestones, delivery responsibilities and unresolved questions. Do not combine a fixed payment with potential future compensation into a single guaranteed total. Have your advisers review the agreement, including exclusivity and any limits affecting later licensing.
- Scope: which systems and periods are included, and which records are excluded?
- Rights: what uses, recipients, duration and exclusivity are proposed?
- Acceptance: what is checked, who decides and what happens if part is rejected?
- Payment: which event triggers invoicing and when is each amount due?
- Work: who exports, filters, repairs gaps and answers questions?
- Future obligations: are refreshes or additional participation required?
Payment Timing Belongs In The Comparison
Micro1's process section says payment is made within 30 days of acceptance. Its FAQ separately describes a review period of up to 30 days after transfer, followed by invoicing after approval and payment within 30 days of invoicing. Ask which sequence the agreement uses. Checked November 8, 2026.
In your comparison sheet, give transfer, review, acceptance, invoice and payment separate entries. Ask how a correction request affects the timetable. This prevents a phrase such as '30-day payment' from being mistaken for cash due immediately after the first conversation. The proposed contract needs to resolve the actual deadlines.
Source: Micro1: Enterprise Pricing, Compensation And Payment FAQ. Checked 2026-11-08.
Estimate The Seller Effort Before Committing
Even an archive that already exists may need preparation. Someone may have to locate an administrator, restore an old export, explain folder structures or coordinate professional review. Obtain estimates for that work where possible. Do not describe those costs as known until the responsible people have assessed them.
Use a simple planning worksheet: proposed payment, expected external preparation costs, adviser costs, internal time and unresolved conditions. Keep tax questions separate for your accountant. This worksheet is not a prediction of net proceeds, but it helps identify what must be clarified before the seller commits to a delivery process.
Avoid undertaking extensive restoration solely on the strength of a website calculator. First ask whether the buyer has enough information to express preliminary interest and what review would follow. Preserve existing records while evaluating the opportunity; a possible transaction should not become a reason to discard originals or bypass retention advice.
What To Prepare Before Requesting A Review
A concise, accurate preparation file is more useful than an unsupported valuation claim. Start with a system inventory and a summary of unresolved permissions. Ask the buyer what secure process it uses for any requested samples, and obtain appropriate approval before sharing them.
- Company profile: industry, location, operating dates, closure status and historical team size.
- Archive map: systems, retained periods, export formats, gaps and duplicates.
- Proposed scope: records for consideration and exclusions awaiting adviser review.
- Authority and access: who can authorize the proposed transaction and arrange delivery?
- Commercial questions: fixed amount, conditional amounts, review steps and deadlines.
Use An Estimate To Organize The Conversation
Basic Trace's estimate tool provides an indicative starting range, not an offer or an independent appraisal. Use it to organize the company profile you want to discuss. Only a buyer reviewing a defined package can decide whether to make an offer, and the written terms determine what the seller must deliver.
For a closed company, the immediate objective is a credible description of what remains and what can be considered. With that in hand, you can ask focused questions about fit, scope and review rather than negotiating against an advertised ceiling. Basic Trace is a sell-side broker; named buyer programs are market examples, not evidence of completed Basic Trace deals.
Discuss Your Company's Records
Start with what you own, what you can access and what you want to achieve.
Estimate your archive