What is the value of the time you no longer need to work?
The question sounds theoretical. It got very concrete. Last Tuesday you delivered in two hours what used to take eight. Same deliverable, same client, same value to their business. Your invoice just shrank by three quarters.
The case repeats everywhere, and it has nothing to do with a miracle tool. It follows mechanically from something simple: when you sell hours and your speed goes up, your income goes down.
The day going faster cost you money
The math is blunt because it's exact. A solo billing $75 an hour who delivered in eight hours collected $600. The same work delivered in two hours, at the same rate, is worth $150.
The client receives exactly the same thing. Their sense of the value hasn't moved by a cent. The entire difference gets absorbed by you and nobody else.
The usual reflex is to pad the estimate, or to leave out the part where it took two hours. That works for a while, and it installs a permanent low-grade dread: you spend your days hoping the client doesn't ask for detail.
There's a less visible cost: what it does to the relationship. A client who watches you bill less for the same result often concludes the work was easier than you claimed. Your efficiency becomes an argument against your price, without you saying a word.
A pricing model that pushes you to hide your own efficiency is worth a close look.
Why hourly punishes efficiency
The hourly rate came from a world where time spent was a decent proxy for effort and result. That proxy is holding less and less.
The size of the gap is documented. An experiment by Shakked Noy and Whitney Zhang, published in Science in 2023, randomly assigned 453 college-educated professionals to occupation-specific writing tasks, with half given access to ChatGPT. Average time dropped 40%, and rated output quality rose 18%.
A 40% drop in time, with quality going up, describes exactly the situation that breaks hourly billing. The work is better and it's worth less money. No rate adjustment fixes that for long, because the problem lives in the unit of measure.
The math gets clear with numbers. A project that took you 20 hours now takes 10, thanks to your tooling and experience. At $75 an hour, you go from $1,500 to $750 for the same deliverable. With the 10 hours freed up, you can take a second project, and you land back at $1,500 for your 20 hours. Same income as before, two clients to coordinate instead of one, twice the back-and-forth. You worked harder to stay exactly where you were.
On a flat fee, that same project stays at $1,500 and now costs you 10 hours. The second project comes in at the same price, inside the same 20 hours. You finish at $3,000. That is the part that matters: your efficiency gain lands in your pocket rather than the client's, and you get to decide what to do with it, double the income or take the 10 hours back.
There's a second effect, more insidious. Hourly billing creates an interest in not improving. Every hour you save is an hour you don't bill, so your brain starts treating investment in tooling and method as pure expense. That's an untenable position in a trade where everyone is speeding up at once.
Selling an outcome instead of hours
Moving to value comes down to changing what the transaction is about, rather than naming a bigger number and hoping it lands. The client stops buying your presence and starts buying a specific end state.
You can see the difference in how the offer reads. "I'll work on your site at $75 an hour" describes a spend with no visible end. "Sales page rebuild, two rounds of revision, delivered in 12 days, $2,400" describes a purchase with a start, an end, and a known price.
The second version is more comfortable for the client, which people forget. A fixed price gives budget predictability that a running meter never will. Plenty of clients happily pay a bit more to avoid watching a counter.
It's also more demanding on you. You have to estimate well, define a clear scope, and hold it. That's the exact muscle that goes missing when a project quietly swells, which is why moving to value starts with better scoping rather than better selling.
Not every project converts equally well, and it would be dishonest to pretend otherwise. Fuzzy scope, ongoing support work, an emergency nobody can size yet: in those cases hourly often stays the most honest format, for you and for the client. Fixed pricing works when the expected result fits in one sentence. Start with those projects.
Your price level is a separate question from your pricing model. If the real issue is that you charge too little, treat it on its own, the way we did in why you're still undercharging. A bad hourly rate converted into a bad flat fee is still a bad price.
Moving to value without losing clients
The main fear never changes: announce a new model, watch clients leave. In practice the shift rarely happens all at once, and almost never across your whole client base at the same time.
One project is enough. The next one. You take what comes in, estimate it in hours for your own internal use, and present it to the client as a fixed price with the scope written down. Then you watch what happens.
Three things usually do. The client accepts without comment, which is the most common outcome. Or they ask how many hours that represents, and you answer that the price covers the result and the revisions included. Or they decline, and you learn something useful about that specific project.
Scope is what makes a fixed price livable. Write down what's included, what isn't, and how many rounds of revision are covered. Without that, a flat fee turns into unpaid hourly work, and that's the one genuinely expensive way to botch this transition.
It's worth naming what you trade away. Hourly is comfortable because it caps your downside: a project that drags gets paid for anyway. A fixed price moves that risk onto you. What you buy in exchange is the upside when things go fast, which hourly never gives you at all. The trade is worth making once your estimates are reasonably good, and the only way to find that out is on small projects first.
For existing clients, the conversation looks like a rate change: you prepare it, you give notice, and you anchor it in what the client gets. The same principles from raising your rates without losing clients apply to changing your model.
One blind spot to watch. Under a fixed price, non-billable time becomes invisible without becoming any smaller. The back-and-forth, the coordination, the email: all of it keeps existing, and it ends up either in your price or in your evenings. That's the subject of invisible admin, and it matters more once you leave hourly, not less.
One step this week
Take your last delivered project. Write down what the client actually got: the form that works, the page that converts, the process that runs without them. Put it in one sentence, from the client's point of view, without mentioning your work.
That sentence is your offer. It carries a price, and that price has nothing to do with how many hours you put in.
So put two numbers on that project. One the old way, your hours times your rate. One from the sentence you just wrote, asking what that outcome is worth to the client's business. If the two land close together, hourly was serving you fine there. If the second is much larger, you've found where your model leaks.
This is a shift that takes a few months, with experiments, blown estimates, and adjustments. It starts with one proposal written differently.
The modern solopreneur's playbook, one article at a time.
Pricing, workload, tools, the reality of working alone. When I publish a new one, you get it by email. No spam, no algorithm between us.
One email when an article goes live. Unsubscribe in one click. Privacy policy.