Flat Price Is a Feature

I want to make an argument that sounds like it's about billing but is actually about how a tool treats you: for prosumer software, a flat price is a feature. Not a discount, not a promotion — a feature, the same way autosave or dark mode is a feature. It changes what the product feels like to use.

If you're a consultant, a fractional exec, or running an agency of one, you've felt the opposite of this feature. You've felt the meter running.

Two ways software has learned to charge you

Most of the tools competing for your money right now use one of two pricing models, and both were designed for someone who isn't you.

Per-seat. You pay per user, per month. This model was built for companies, and it makes perfect sense there — more employees, more value, more cost, everyone understands the deal. The trouble is what it does to features. Once a vendor charges by the head, they start gating capability by tier to push you up the ladder. The thing you actually need is one plan above the one you're on, always. Look at how the workspace tools do it: the AI features, the automations, the good stuff sits in "Business" or "Enterprise," priced for a team of thirty, and you — a team of one — get to pay the team-of-thirty entry fee to unlock a feature you'll use alone.

Metered credits. This is the newer one, and it's spreading fast because AI has a real per-use cost behind it. You pay a base fee and then you buy credits, or you get a monthly allotment and pay overage when you cross it. Every action spends a little. Sounds fair. In practice it does something poisonous: it makes you ration.

The real cost of a meter isn't the money

Here's the thing nobody puts in the pricing FAQ. When a tool charges by the action, it moves the accounting into your head.

You start doing math before you use your own software. "Is this task worth a credit?" "I've got twelve runs left this month, better save them." "Do I really need to ask, or can I muddle through myself?" You hesitate at the exact moment the tool is supposed to help you. The meter turns every feature into a small financial decision, and small financial decisions, dozens a day, are exhausting in a way that has nothing to do with the dollar amount.

For a solo operator this is especially corrosive, because you're already the one watching every dollar. You do not need your assistant tool adding a running tab to the pile of things you're tracking. The whole promise of the tool was to take work off your plate. A meter puts a new job on your plate: being the accountant for your own software usage.

And then there's the surprise-bill tax. Metered pricing means your cost is variable, which means some months it spikes, which means you get an invoice that's double what you planned for because you had a busy week. Busy weeks are when you're making money. Getting punished with a higher software bill for the weeks you worked hardest is exactly backwards.

Why flat pricing is honest, and how it stays that way

A tool should cost like a tool. You buy a wrench once; it doesn't charge you per bolt. You pay for your software once a month; it shouldn't charge you per thought.

Flat pricing says: here's the number, it's the same every month, use the product as hard as you want. The mental accounting disappears. You stop rationing. You use the tool the way you're supposed to — freely, without a calculator open in your head. That freedom is the feature. It's the difference between a tool you reach for by reflex and one you approach cautiously because it's on the clock.

Now, the fair objection: AI genuinely costs money to run, so how does flat pricing not just bankrupt the vendor or get quietly enshittified later? The answer is caps, and caps done in the open are the thing that keeps flat pricing honest.

The right way to do this is a generous flat allowance with clear, stated limits — something like a set number of AI queries a month and a handful of autonomous task runs a day. Numbers most people never come close to hitting, published plainly so you know exactly where the edges are. That's not a meter. A meter charges you continuously and surprises you at the end. A cap is a fence you can see: inside it, everything is free and flat and un-metered; you always know where it is; and you never get a variable bill. On the rare occasion you hit the fence, you wait for the reset or move up one clearly-priced tier — you don't get an invoice you didn't authorize.

The difference between a cap and a meter is the difference between "you can use this much, and here's exactly how much" and "use as much as you like and we'll tell you what it cost when the bill comes." One respects your ability to plan. The other profits from your inability to.

What to actually look for

If you're evaluating tools as a solo operator, price them like the small business you are, not like the enterprise the vendor wishes you were. A few questions worth asking:

• Is the feature I need gated behind a team tier? If the AI or automation lives in "Business," you're subsidizing a team plan to use it alone.
• Is my monthly cost fixed, or can it spike? If a busy month costs more, the tool profits from your best weeks.
• Are the limits published and generous, or vague and punitive? Clear caps are a fence. Vague credits are a trap.
• Do I hesitate before using it? If you catch yourself rationing, the pricing has already changed how you work — and not in your favor.

A flat price with honest caps isn't the cheap option or the generous option. It's the option that treats your software like a tool you own instead of a utility you're metered on. For people who are the whole company, that's not a line item. It's a feature — maybe the one that matters most.