A Potential Client Recently Asked How Much My Hourly Rate Is

The Question

Recently, a potential client asked me a direct question: how much does an hour of my work cost? I deflected: "I don't sell hours." He insisted that everyone has a hidden hourly rate. Later, I regretted not giving a more thoughtful answer. This article is that answer.

2008: The Beginning

When I started freelancing as an interface designer, I charged 1,000 rubles per hour. This was above market rate at the time, but clients accepted it because I had a portfolio of hundreds of prototypes and a solid reputation through referrals. The model was simple and it worked.

The Productivity Paradox

As I gained experience, I encountered a counterintuitive problem: I got faster. An online store that used to take 50 hours now took 10. A social network project shrank from 250 hours to 100. You'd think this was a good thing, but the economics were brutal.

"While spending the same resources on finding new clients, I ended up earning two to five times less." The cost of client acquisition stayed constant, but the revenue per client plummeted because each project required fewer billable hours.

Failed Solutions

I tried several approaches to fix this:

• Inflating hours in reports — I rejected this immediately. It caused moral discomfort and felt dishonest.
• Raising the hourly rate to 3,000 rubles — The market wouldn't accept it. Agencies were willing to pay 1,500 at most.

Neither approach was sustainable. The hourly model was fundamentally broken for experienced professionals.

The Shift to Per-Project Pricing

The key insight came from flipping the perspective. If an average designer spends 90 hours on an online store and charges 90,000 rubles, why not sell the same work as a fixed-price project for the same amount — but complete it in 20 hours? That works out to 4,500 rubles per hour, or even more.

"A fixed-price estimate looks more reliable and understandable in the client's eyes." The client doesn't worry about paying extra if hours exceed estimates. They know the total cost upfront. And the designer's efficiency becomes an advantage rather than a penalty.

The per-project model also enabled collecting deposits — a significant improvement over the post-payment norm of hourly billing.

2017-2025: The Quality Investment

Something changed around 2017. I started going deeper into my work — talking to developers, studying how my documentation affected the development process, understanding how my decisions played out downstream.

My functional specifications gradually expanded to include elements I'd previously overlooked:

• Data validation rules
• Error messages for every possible state
• Edge cases and implicit interaction scenarios

I started asking questions like: "What happens if the user reloads the tab in the middle of this flow?" and "What if the list contains more than 100,000 rows?"

The Startup Experience (2018)

Launching my own startup and watching the development process from the owner's side was revelatory. I saw firsthand how good project documentation saved months of developer time. "Project documentation saved us months of development work." The investment in thorough specifications paid for itself many times over in reduced rework and fewer misunderstandings.

The Time Paradox Reverses

Ironically, the same online store that once took 50 hours (then 10 hours as I got faster) now takes 20-30 hours — because I'm covering every edge case, every error state, every interaction detail that I used to skip. The work is slower but incomparably more thorough. Clients who've experienced both levels of documentation never want to go back.

The Real Hourly Rate

So what's the honest answer to the original question? "One hour of my work costs at least 10,000 rubles."

But you simply cannot quote that number. "You just can't name that price. Only fixed-price." Here's why:

A company can hire a full-time employee for 200,000-300,000 rubles per month. With payroll taxes, that becomes 300,000-450,000. That employee works 160 hours per month, which comes to about 2,800 rubles per hour.

A freelancer charging 10,000 rubles per hour who completes a month-long project for 400,000-500,000 rubles looks expensive by comparison — even though they may deliver faster and better results. The hourly framing makes the comparison unfavorable regardless of the actual value delivered.

The Retainer Model (Current Approach)

Over the past year, I've been increasingly moving toward a retainer-based model with monthly payments. The advantages are compelling:

• One-time context immersion: You learn the client's business once and maintain that knowledge over months, eliminating the ramp-up cost on every new project
• No client hunting: Between projects, there's no gap in income while searching for the next engagement
• Monthly rate of 150,000-250,000 rubles in the Russian market
• Tax efficiency: For sole proprietors on simplified taxation, the employer doesn't need to pay the additional 40% payroll taxes they'd pay for a full-time employee
• "This can actually work out cheaper than hiring a full-time employee" — a compelling pitch for clients

Comparing the Three Models

Hourly Rate

Advantages:

• Convenient at the start of your career while you're still learning
• Market-oriented pricing gives you a benchmark
• High stability once you build a pool of regular clients

Disadvantages:

• Temptation to inflate hours in reports
• The market won't accept a high rate from freelancers
• Post-payment model (bad for the freelancer's cash flow)
• Growing expertise reduces income

Per-Project Pricing

Advantages:

• Deposits are standard practice
• Opaque hourly rate allows earning above market
• Client doesn't fear cost overruns
• Easier to sell to clients

Disadvantages:

• Requires experience for accurate estimation
• Low stability between projects — feast or famine
• Client may not invite you back for subsequent phases

Retainer

Advantages:

• All the benefits of per-project pricing without its downsides
• No need to benchmark against market rates
• Extremely high stability — it feels like a salary
• Can serve multiple clients simultaneously

Disadvantages:

• Much harder to close the deal initially

Conclusion

I never gave that potential client a straight hourly rate because it's "too high for the market and it fluctuates." Over the course of my career, I've evolved from hourly pricing to per-project, and now to a retainer model. Each transition solved specific problems created by the previous approach. The real lesson is that pricing isn't just about numbers — it's about finding a model that aligns your incentives with your client's and rewards expertise rather than penalizing it.