Nobody Pays You for the Code Anymore.

You are not paid for the code any more. You are paid for the claims you can keep true, and I learned that from my own pricing page.

Every Intelligence and Widget plan card said "2 months free." It said it for months. It was false on three of the four cards it appeared on.

A plans page is not a list of features. It is a list of claims, and every one has a truth value you are now responsible for.

Why did my line go false?

Two months free means a year costs exactly ten times a month. That is arithmetic, not a mood. Of the four annual prices on those cards, exactly one is ten times. The other three are 10.05, 10.09 and 10.05, because I set the annual amounts to land on round numbers and never derived them from the monthly.

I did not see it, because I never multiplied.

It was not a lie I decided to tell. Nobody chose a wrong number. The line arrived as an assumption, got printed, and then nothing in the world was arranged to check it again.

The real discounts are 16.67, 16.29, 15.91 and 16.29 percent. The obvious repair is "save about 16 percent." It reads well and it is nearly true.

It is still false for one of them. The note I left in the code says why: "about 16% would still overstate one card, which is the same mistake in a smaller font."

So the card says "Save 15% or more" now. Worse copy. Lower number. A floor instead of an average.

What makes a floor different from an average?

The floor is not immune. Add a fifth plan at ten percent off and the card is false again, because a worst case is only as good as the worst thing in it.

What changed is how it fails. A test asserts that every plan clears the floor, so that fifth plan breaks the build before it reaches the page. The claim cannot go quietly wrong, because something refuses to ship while it is wrong.

The average had no such tripwire. It was a description of one afternoon, and it would have gone quietly false the moment the catalog moved, with nothing anywhere arranged to notice.

That difference has nothing to do with honesty as a personality trait. One claim is checked by a machine on every commit. The other needed a person to remember.

Why are there so many more claims than there used to be?

Here is where the machine enters, and it is not where I expected.

Generation did not make claims less true. It made them cheaper to make. A feature that took a quarter now takes an evening, so it reaches the plans page in an evening. The moment it lands there it stops being a feature. It becomes a promise with your name on it.

Nothing got cheaper about keeping that promise. Verification did not get cheaper when generation did. So the ratio moved. More lines, the same capacity to check them, and the checking was never the part anyone budgeted for.

Some of those lines are also trivially copyable now, which is the argument everyone reaches for first. That is true of features whose entire cost was the building. It is not true of the ones whose cost sits outside the codebase. "Connects to twelve thousand banks" is a feature nobody copies this weekend, because its price is contracts.

Copying is the smaller problem. The bigger one is that you hold more claims than you can audit, and average is free means the market keeps handing you more of them.

Is a feature not also a promise?

Yes, and this is the strongest objection to everything above, so I will not reclassify it as off topic.

A feature you list is a feature you must keep. So every line is a commitment of some kind, and the tidy split between inventory and posture is softer than I would like.

What survives is the asymmetry. A feature line commits you to keeping something anyone can now build, so you carry the obligation without keeping the advantage. A guarantee line commits you to something that was never cheap and does not get cheaper. Answering for uptime. Publishing a methodology. Replying to support. Letting an outsider audit your data.

The other real objection is that customers buy working software, and a cheaper competitor with the same capability wins the deal. That is true. It is also the mechanism, not a counterargument. When capability stops being scarce it stops deciding deals, and something else does. The only question is whether you chose what.

What do I actually change?

Read your plans page one line at a time and ask one thing of each: what would tell me this went false?

If the answer is a person noticing, that line is already decaying. If the answer is a test, a monitor, or a number computed from a source, it will hold. Most lines have no answer at all, and those are the ones that will embarrass you, well before a competitor copies anything.

Then write the claims you can defend rather than the ones that read best. A floor beats an average. A published methodology beats a confident number. Everyone says AI-native and almost no one is, and the tell is which of those two a company reaches for when it has to get specific.

If nothing in your system would notice a line going false, you are not making a promise. You are making a guess in public.

Related reading:

• Average Is Free. Build Best-in-Class. why the floor moved and what survives above it
• Per-Seat Pricing Is on Borrowed Time. the model this argument eventually collides with
• Your Moat Is Now an Anchor. what happens to a defensible thing when defending it gets cheap
• Verification Is the New Literacy why proof, not production, became the constraint
• 84 Ways to Tell Me I'm Wrong. the machinery that decides what I am able to promise
• I Cannot Read My Own Codebase. I Ship to It Daily. what standing behind code you have not read requires