Your old files are worth real money.

AI labs are paying for records of how real work gets done. We find the buyer, handle the contract and walk you through all of it. Personal details are stripped before anything leaves your systems.

Email and chat
The back and forth behind a decision, an approval, a complaint, a fix.
Outlook, Gmail, Slack, Teams
Jobs and tickets
What the problem was, what your people did about it, whether it worked.
Your CRM, helpdesk or job system
Files and records
Quotes, reports, specs, drawings. The written output of the work itself.
Drive, SharePoint, your server

What are your records worth?

Nobody has ever quoted your business a price for this, so there is no going rate to look up. This works from replacement cost instead: what it would cost to pay people to produce the same records from scratch.

Move the inputs to match your business.

This changes how much a record is worth, not whether it counts. Healthcare and consumer finance are out of scope for now.

40

Everyone, full and part time, across all locations.

12

History counted for licensing stops at seven years, because buyers rarely want more than that.

Email and chat

Not where it is supposed to go. Where it really ends up.

Usually

Whether it worked, what it cost in the end, whether the customer came back. The single biggest driver of value.

Indicative one time license
$0 to $0

Work records produced a year0
Years of history in scope0
Records in the licensable set0
Ongoing supply, per year$0
Below our current minimum. At this size the legal and preparation work costs more than a license returns. Come back as you grow, or point us at a bigger business that should hear about this.
How this number is built
  • Each industry has an assumed number of substantive work records per person per year, and an assumed replacement cost per record. Both are averages, and both are estimates rather than quoted rates.
  • History counts for a maximum of seven years, because buyers rarely pay for more.
  • How the work is recorded scales the whole thing, because records nobody can reach are worth nothing.
  • Recorded outcomes are weighted heavily. A record of what was done is useful. A record of whether it worked is far more useful, and far rarer.
  • The license band sits at 12 to 30 percent of replacement cost.

Illustrative estimate in USD. Not an offer, not a valuation, and not a guarantee of a sale. What a dataset actually clears for depends on buyer demand, the state of your systems, and the rights you are able to grant.

Four businesses, four very different numbers.

Illustrative profiles, not completed sales. Each runs the same arithmetic as the estimator against a shape of business we expect to see.

Notice how much the recording habits move the number compared to headcount.

Professional services

28 person civil engineering firm, 14 years old

$48k to $119k
Records a year2,520
Years in scope7
Recorded inSoftware
Outcomes keptAlways
Why it scoresReports with a stated recommendation, and a project file showing whether the recommendation held. That pairing is the whole product.
Field service

60 person HVAC service company, 22 years old

$72k to $181k
Records a year10,800
Years in scope7
Recorded inSoftware
Outcomes keptAlways
Why it scoresSymptom, diagnosis, what was replaced, and whether the unit came back in ninety days. Verifiable without a human grading it.
Insurance

15 person commercial brokerage, 9 years old

$14k to $34k
Records a year2,250
Years in scope5
Recorded inMixed
Outcomes keptUsually
Why it scores lowerGood judgment, but half of it lives in spreadsheets and the other half in people's heads. Size is not the problem here.
Logistics

140 person freight forwarder, 30 years old

$163k to $408k
Records a year30,800
Years in scope7
Recorded inEmail
Outcomes keptUsually
Why it scoresEnormous volume, even with messy recording. The clearest case for supplying records going forward rather than selling the back catalogue once.

The public internet is spent. Your file server is not.

Everything published openly has already been scraped and trained on. What has not been touched is the record of how actual work gets done inside actual companies.

You generate that every working day, and then you file it.

Public data

Already scraped, already trained on

Every website, forum, manual and public document. All of it went into the last generation of models years ago.

Worth nothing. Everyone has it.
Your systems

Worth more than you think

The quote you nearly sent. Why you changed it. What the job actually cost when it was finished.

Has never been digitized by anyone outside your company.

The decision, and the reasoning behind it

Which option your people compared, what the situation actually was, and why they rejected the obvious answer. The final number is the easy part. The path to it is the asset.

Whether it turned out to be right

The job that came back. The quote that was wrong by thirty percent. The fix that held for three years. Almost nothing on the open internet has this attached, which is exactly why it is worth paying for.

What your people checked before committing

The supplier they called, the spec they looked up, the thing they went and physically measured. Models are bad at precisely this, and the people building them know it.

We license how you work. Not who your customers are.

Every business holds information about other people, under contracts, under privacy law, and under plain common sense. That constraint shaped the whole scope.

We built around it rather than asking you to find a way past it.

In scope

Your company's work, de-identified.

  • The problem as it was described to you
  • What your people decided, and the options they rejected
  • The internal back and forth that got to the answer
  • Generic job characteristics: scope, materials, conditions
  • How it turned out, and anything that had to be corrected
  • Your own internal guidance and written procedures

Never leaves your systems

Removed before anything is transmitted.

  • Customer and client names, addresses and contacts
  • Your pricing, margins and contract terms
  • Anything personal about your staff or anyone else
  • Your customer list, and the fact that any customer is yours
  • Passwords, keys, card and bank details
  • Anything under a confidentiality clause you name

What that looks like on an actual record

Constructed example, a service call. De-identification runs on your machine, before transmission, and your staff approve the output before it moves.

As it sits in your system
customer Delgado Property Group, 4412 Oak Ridge
contact Marisol Delgado, 956 555 0118
invoice $1,840 parts and labour
reported Rooftop unit short cycling, 40 ton, 11 years old
found Low charge, plus a failing contactor nobody had flagged
did Replaced contactor, leak searched, recharged. Advised full replacement within 2 seasons.
outcome No callback in 18 months. Customer replaced the unit the next spring.
As it leaves, once you approve it
customer removed
contact removed
invoice removed
reported Rooftop unit short cycling, 40 ton, 11 years old
found Low charge, plus a failing contactor nobody had flagged
did Replaced contactor, leak searched, recharged. Advised full replacement within 2 seasons.
outcome No callback in 18 months. Customer replaced the unit the next spring.

Where the work actually lives.

Rarely in one place. Part is in a proper system, part is in a note somebody typed at four in the afternoon, and part is in an attachment nobody has opened since.

Conversations

The threads where something got decided. Usually the only place the reasoning survives, and almost never where anyone thinks to look.

OutlookGmailSlack TeamsCall notes

Jobs, tickets and cases

The structured spine of the work. What came in, who handled it, what they did, and when it closed.

SalesforceHubSpotZendesk JiraServiceTitanProcore

What happened next

The part nobody else can supply. Callbacks, warranty claims, change orders, final invoices against the estimate. This is what turns a record into something a model can be scored against.

Final invoicesChange orders Warranty claimsRepeat jobs

Documents and drawings

Quotes, reports, specs, plans, photographs. Stripped of client, address and price before any of it moves.

SharePointGoogle Drive DropboxYour file server

How you tell people to do it

Internal procedures, checklists, training notes, the document that explains how your company handles the awkward cases. Short, and worth more per page than anything else on this list.

NotionConfluence SOPsHandbooks

We walk you through all four steps.

No records move during onboarding. We work from counts and screenshots until a buyer agreement is in place, and you pay nothing at any stage.

01

Qualify

Thirty minutes. Size, industry, and whether your records survived your last system change. Plenty of businesses are not a fit and we say so on the call.

02

Scope

Mutual NDA, then we map what you have and where. You set the exclusions: customers, departments, date ranges, anything under a confidentiality clause.

03

Extract

Our tooling runs inside your network, read only. De-identification happens before transmission. Your staff review a sample and sign off before anything moves.

04

License

We take it to buyers. You receive 30 percent of everything it earns, you keep ownership of the underlying records, and you can decline any individual buyer.

6 hours

Roughly what this costs your staff, in total. Most of it is the review sample in step three. Businesses on older systems, or holding records across several platforms, should expect more. We do the rest.

Before you decide.

The six things worth knowing before you spend half an hour on a call with us.

What it costs you

Nothing, at any stage. We are paid only out of what a license earns. If it never sells, you are out the staff time and nothing else.

What you keep

Ownership of every underlying record. The license is term limited and you keep operating exactly as you do now.

What never moves

Customer identities, personal data, pricing, and anything that could tie a record back to a named person. Stripped on your hardware.

Who reviews it

Your counsel, before you sign. We expect it and we budget time for it, and we send the agreement early so they have room to work.

What you can veto

Any buyer, any department, any customer, any date range. Exclusions are set in the agreement and can be widened later, not narrowed.

What is not promised

A sale. Buyer demand is real but concentrated and slow. A signed license is permission to try, not a cheque, and anyone telling you otherwise is selling something.

The questions owners actually ask.

Straight answers, including the ones that are not in our favour.

Am I selling my business, or my customer list?

Neither. You are licensing a de-identified copy of how your company works, for a fixed term. You keep the original records, you keep the business, and nothing about your operation changes.

Your customer list, their identities and your commercial terms are out of scope and never leave your systems.

What about my customers' personal information?

It is removed on your hardware, before anything is transmitted, and your staff approve a sample of the output before the first record moves. We would rather carry the cost of doing that locally than hold personal data at all.

Removing names is only the first step, and anyone who tells you it is the whole job is wrong. Context can identify people too, which is why the scope excludes addresses, pricing, and anything tied to a specific account.

Who is actually buying this?

Two groups. AI labs building models that have to handle real professional work, and the data vendors who supply them under existing contracts. Both are short on records of how expensive expert work actually gets done, because none of it is public.

You can decline any individual buyer. We name them before anything is transferred.

Our records are a mess and half of it is in email.

Normal, and not disqualifying. Email is often where the useful part lives, because it is where the reasoning happens. Pulling it into shape is our problem rather than yours.

What does hurt is not knowing how things turned out. If you cannot connect a job to whether it came back, the records are worth a fraction of what they otherwise would be.

Am I training my own replacement?

Honestly, a bit, and we are not going to pretend otherwise. Models are going to get better at this kind of work whether or not your company takes part, and the training data will come from somewhere.

The choice in front of you is not whether it happens. It is whether you are paid when it does. If that trade does not sit right with you, do not do it, and we will not try to talk you round.

What happens when the license ends?

The buyer's right to use the data for new training stops at the term end. A model already trained cannot be untrained, which is true of every data license in this market, and the agreement says so plainly rather than implying otherwise.

You keep your records throughout. You are licensing a copy, not selling the original.

Find out whether your records qualify.

Thirty minutes, no files, no preparation. We go through your size, your systems and what you actually keep, and tell you on the call whether it is worth either of our time.

We are not a fit for everyone. We work with US businesses of 20 or more people with at least three years of records, outside healthcare and consumer finance. If that is not you, say so on the form and we will not waste the half hour.

Required.
Enter a valid work email.
Required.
Required.
Required.
Required.
That did not send. Try again, or email the same details to support@joinvellum.com.

We reply within two business days or not at all. No mailing list, no follow up sequence.

Received.

If your size and record history clear the bar, you will get a time to pick from within two business days. If they do not, you will get a short note saying so rather than silence.