Our team will be out of office on Friday, May 1, 2026. We’ll be back and ready to assist you starting Monday, May 4th.

Should I Let an AI Company Train on My Business Data in Exchange for a Discount?

Contents

Meta just put two prices on the same coding tool, one of them roughly 92 percent cheaper if you let them learn from your work. This article answers the question that creates for every small business owner: is that trade worth taking, and how do you decide?

Suggested SEO meta title: Should You Let AI Train on Your Business Data? A Pricing Guide


Somebody Finally Printed the Price Tag

For three years we have all been guessing what our data is worth to an AI company.

Last week, one of them told us.

According to The Batch from DeepLearning.AI, Issue 366, published August 14, 2026, Meta shipped an agentic coding tool called Muse Code with two published prices for the exact same product. The standard tier costs $1.25 per million input tokens and $4.25 per million output tokens. The contributor tier costs $0.10 per million input and $0.20 per million output, and you qualify for it by letting Meta learn from your sessions.

That is roughly a 92 percent discount on input and roughly a 95 percent discount on output.

So here is the direct answer to the question in the headline. Yes, you can take the trade, and for some work you should. But only after you have sorted your data into what is yours to give and what is not, because much of what flows through your business belongs to your clients rather than to you. Discount pricing on someone else's confidential information is not a discount. It is a liability you bought at a markup.

Here is the thing that gets missed in every conversation about AI and privacy.

We keep framing this as a security question. It is not. It is a pricing question. A vendor just published an exchange rate on your working data, and once a price exists, "I did not think about it" stops being a defensible answer. You are either selling on purpose or giving it away by accident.

My whole argument: stop treating your business data as exhaust. Start treating it as inventory. Inventory gets counted, priced, and sold deliberately.


Key Takeaways

Key Takeaways

  • Meta's Muse Code published a roughly 92 percent input discount for users who let the company learn from their sessions, the clearest public price yet on working business data.
  • The supply of high quality human text is finite, which is why frontier labs now pay for it in cash and in discounts.
  • Not all of your data is yours to trade, and the fastest way to get burned is to sell access to information a client trusted you to hold.
  • Sorting your data into four buckets before you choose a plan tier turns an accidental giveaway into a deliberate business decision.
  • Provenance rules are arriving on a schedule, so the outputs you publish are about to carry machine readable labels whether you plan for it or not.

The Problem Is That Nobody Ever Sent You an Invoice

Data does not feel like an asset because nothing about it behaves like one.

It is not on your balance sheet. It does not sit in a warehouse. Nobody hands you a receipt when a transcript of your sales call becomes training material somewhere. The category is invisible until the moment it is expensive.

I run into this constantly with the entrepreneurs I coach. Somebody pastes a client contract into a free chatbot for a plain English summary. Somebody else uploads three years of customer records to build a segmentation model. Both are doing genuinely good work. Neither checked what tier they were on or what that tier permitted.

Candidly, I have been sloppy here myself.

Early on I ran client discovery calls through whatever transcription tool was cheapest that month, and I could not have told you where those recordings lived or how long they stayed there. Not because I am careless with other people's trust. Because the question never surfaced. There was no invoice, no warning, no moment where a screen asked me to decide anything.

I have signed paperwork I did not fully read before. That habit has cost me more than money in my life, and I am not eager to repeat the lesson in a new format.

The difficulty is real and I will not pretend otherwise. Reading terms of service is miserable work. The documents are long, written by lawyers for other lawyers, and they change without telling you. A solo consultant with eleven active clients does not have a compliance department. Telling that person to "just read the terms" is useless advice delivered from a comfortable chair.

There is a second problem underneath the first. Most people assume the answer is binary. Either the AI company steals everything or it steals nothing. That framing is why owners freeze, then either ban AI entirely and fall behind or use everything for everything and hope.

Both responses share a root cause. You cannot price something you have never inventoried.

That is the reframe. You do not need to become a privacy lawyer. You need to know what is in the warehouse.


What the Research Actually Shows

Five findings changed how I think about this, and none of them are speculation.

One. The supply of human writing is finite, and researchers have counted it. Epoch AI estimates the total effective stock of human generated public text at roughly 300 trillion tokens, with a wide confidence range, and projects exhaustion of that usable stock somewhere between 2026 and 2032 depending on how aggressively labs train. Plain language version: the free pile is running low. That is the entire economic reason a vendor offers you 92 percent off.

Two. The cash market for data is already large and already public. OpenAI's licensing deal with News Corp is reported at more than $250 million across five years. Reddit's arrangement with Google has been reported at about $60 million a year, and its OpenAI arrangement at roughly $70 million a year. Publishers with leverage get paid in dollars. Everybody else gets paid in discounts.

Three. Retention windows got longer, and most users never noticed. In August 2025, Anthropic updated its consumer terms so that chats and coding sessions on Free, Pro, and Max plans could be used for model training unless the user opts out, with retention extended from roughly 30 days to as long as five years. That is not a scandal. It is a disclosed policy change. It is also a reminder that the default setting on your account today may not be the one you agreed to two years ago.

Four. Real companies have already been burned by their own employees. Samsung banned generative AI tools on company devices in May 2023 after engineers pasted proprietary semiconductor source code and internal meeting content into ChatGPT across three separate incidents inside roughly 20 days, as reported by Bloomberg and Forbes. Nobody hacked Samsung. Helpful people trying to work faster typed the crown jewels into a text box. Around the same time, Zoom faced a public backlash over terms language covering AI training and then committed not to use customer content, including audio, video, and chat, to train its own or third party models. Pressure works, but only after somebody reads the document.

Five. Provenance is becoming law, not preference. Article 50 of the EU AI Act requires synthetic content to be marked in a machine readable format, with obligations applying from August 2, 2026 and a transition allowing systems already on the market until December 2, 2026. The C2PA provenance standard, now at version 2.3 with thousands of members and affiliates, is how most vendors will satisfy it. Anthropic began embedding watermarks in text and attaching signed provenance metadata to files under the EU AI Act Transparency Code, with additional detail published August 15, 2026. The same week, ByteDance signed a memorandum of understanding with the Motion Picture Association establishing a global IP protection framework for its Seedance and Seedream models across TikTok, CapCut, and Dreamina.

Put those together. Data going in has a price. Content coming out has a label. The era of ambiguity is closing from both directions.


The Four Bucket Method

Here is what changed for me. I stopped asking "is this tool safe" and started asking "what am I about to put into it."

Everything now goes into one of four buckets, and each bucket has a standing rule.

Bucket one: Public. Anything I have already published or would happily publish. Blog posts, webinar replays, the free posts in our Facebook community, my own marketing copy. I trade this without hesitation. If a lab wants to learn from writing that is already out in the world in exchange for a 92 percent discount, that is a good deal for me.

Bucket two: Perishable. Internal work with a short shelf life and no third party attached. Draft outlines, brainstorm lists, meeting agendas, first passes at a landing page. This is where the discount tier earns its keep, because the value of that material expires in about a week anyway.

Bucket three: Proprietary. My actual competitive material. Prompt libraries, curriculum, pricing logic, the frameworks I teach inside AI Insiders. This is mine to trade, which makes it a real decision rather than a rule. Mostly I decline, because I sell this material for a living.

Bucket four: Privileged. Anything belonging to somebody else. Client files, member questions, financial records, anything shared with me under an expectation of confidence. Not for sale at any price, because it was never mine to sell. Nobody in this bucket agreed to fund my software budget.

The operational move is simple. Two accounts, not one.

I run a discount tier account for buckets one and two, and a paid, training excluded account for buckets three and four. The buckets tell me which window to type into. That one separation removed almost every daily judgment call, which matters because judgment calls are exactly what fail under deadline pressure.

The supporting tools are not exotic. A plain spreadsheet with one row per tool, one column for training default, one for retention window, one for the date I last verified it. Claude Projects and ChatGPT Projects to keep client work separated. And an AI model doing the reading of terms documents I lack the patience for.

Reddit put this more bluntly than I would have. A top thread on r/artificial this week: "Most AI agents are sending your data somewhere you can't fully see into. Does that bother anyone else?" Fair question. It bothers me a lot less when I know exactly what I chose to send.


Seven Steps to Price Your Own Data This Week

1. Inventory your tools first. Open your bank statement and your app switcher and write down every AI tool the business touches, including free ones a team member signed up for personally. You cannot make decisions about a stack you have never listed.

2. Sort your work into the four buckets. List the ten things you most often put into an AI tool and label each one Public, Perishable, Proprietary, or Privileged. The labels do the deciding for you later, when you are tired and in a hurry.

3. Have AI read the terms you will never read. Download the terms and privacy pages for your top tools, then run this prompt.

[The Job]
Analyze the data and privacy terms of the AI tools my business uses and tell me exactly what each one is permitted to do with what I put in.
This is for: me, the owner of a [TYPE OF BUSINESS] with [NUMBER] employees.
It matters because: [I need to know which tools I can safely put client work into and which ones I cannot].

[The Background]
Here is what you need to know: the tools we use are [TOOL 1], [TOOL 2], [TOOL 3]. Our current plan tier for each is [PLAN TIER]. The most sensitive material we handle is [CLIENT RECORDS / PRICING / MEDICAL / LEGAL / FINANCIAL DATA]. I have attached the terms of service, privacy policy, and data processing pages for each tool.
Do not use: the vendor's marketing pages, blog posts, or press releases. Use only the documents I attached.

[The Deliverable]
Return: a table with one row per tool and these columns: trains on my inputs by default yes or no, can training be turned off, how long data is retained, where data is stored, and what happens to my data if I cancel.
Must include: a one sentence plain English verdict for each tool and a short list of anything I should stop putting into that tool today.
Optimize for: accuracy. If a document does not answer a column, write "not stated" rather than guessing.

[The Questions]
Ask me any questions you have.

4. Set your defaults on purpose. Go into the privacy or data controls page of every tool on your list, choose the setting deliberately, then screenshot it. Defaults change when terms change, and a dated screenshot is the only record you will have.

5. Split your accounts. One account on a discount or training enabled tier for Public and Perishable work. One on a training excluded tier for Proprietary and Privileged work. Name them clearly enough that a tired version of you at 9pm cannot mix them up.

6. Tell your clients what you do. Add two plain sentences to your contract or onboarding email naming which AI tools you use and how their information is handled. I have never had a client object. Several have thanked me.

7. Recheck on a calendar, not on a feeling. Book a recurring 30 minute block once a quarter to reverify every row in your spreadsheet. Terms change quietly. Your calendar is the only thing that will catch it.


Frequently Asked Questions

Is it ever a good idea to let an AI company train on my data?

Yes, for material you would publish anyway or that has no third party attached. Marketing copy, published content, and disposable drafts are reasonable to trade for a steep discount. The trade becomes a problem only when the material belongs to a client or represents the competitive knowledge you actually sell.

Does the paid version of an AI tool automatically mean my data is not used for training?

No. Paid tier and training excluded are two different settings, and they do not always travel together. Enterprise, team, and API tiers typically exclude training by default, while consumer paid plans often do not. Check the privacy controls page inside your specific account rather than assuming your subscription covers it.

How do I know if my AI vendor is training on my inputs right now?

Look in account settings under privacy, data controls, or improve the model. Vendors are required to disclose this, and most expose a toggle. If you cannot find a clear answer in the settings or the terms, treat that silence as a yes and move sensitive work to a different tool.

What does the EU AI Act mean for a small business in the United States?

Article 50 transparency obligations apply from August 2, 2026 and require AI generated content to be marked in a machine readable format. If you have any European clients or customers, that reaches you. Even if you do not, your vendors are building the marking in globally, so your outputs will carry provenance data regardless.

Can I actually charge someone for my business data?

Realistically, no, not as an individual small business. The cash licensing market is for parties with scale, like News Corp and Reddit. Your leverage shows up as discounts, better plan terms, and the right to say no. Treat those as the currency, because for a company your size they are.


You Have a Decision Now, Not an Accident

Go back to where we started, because the number matters less than what the number means.

Meta did not publish two prices for Muse Code out of generosity. They published two prices because somebody inside that company did the math on what a million tokens of real human problem solving is worth, and the answer was large enough to justify giving the product away at roughly a tenth of the price.

Read that again. Your work, the ordinary stuff you do on an ordinary Tuesday, is worth more than the software you use to do it.

For three years the AI conversation has treated small business owners as consumers at the end of a very long line. Be grateful for access, careful with prompts, quiet about terms. Nobody mentioned that the thing you generate all day is the scarcest input in the entire industry.

Now somebody posted the rate, and posting the rate changes the relationship. You are not just buying anymore. You are supplying. A supplier who knows the price of what they supply negotiates differently than one who does not.

So take the discount when it is your data to give. Refuse it flatly when it is not. Put your client files behind a wall that does not have a checkbox on it. Write the two sentences into your contract. Set the calendar reminder.

None of that requires you to be technical. It requires you to be deliberate, and deliberate has always been available to you.

Your data was never exhaust. It was inventory you forgot you owned.

Count it.


About the Author

Jonathan Mast is the founder of White Beard Strategies, where he teaches entrepreneurs, coaches, and small business owners how to use AI without a technical background. He runs a Facebook community of more than 500,000 members, leads the AI Insiders membership at $247 per month, and speaks regularly on practical AI adoption. He is also the guy who keeps two AI accounts in two browsers with two different colored themes, because good intentions do not survive a deadline.

About the Author