I tracked every hour I billed in 2026. Six months. 14 clients. 80 hours.
Here's what I learned about freelance pricing that nobody talks about.
The pricing model that quietly destroyed my margin
For my first 3 years freelancing, I quoted by the hour. $75/hour. Sometimes $100. It felt safe — "X hours at $Y rate = $Z." Predictable.
What it actually did:
- Made clients budget-protect against me ("only 5 hours this week")
- Created adversarial conversations when scope changed ("but I paid for X hours, not Y")
- Made me optimize for the wrong thing: speed of delivery, not quality of outcome
- Locked me into a rate I had to defend instead of a value I could grow
The last month I did hourly billing, my effective hourly rate (after revisions, scope creep, and unbilled client communication) was $58. I was billing $75 but keeping $58.
What I switched to
Six months ago, I switched every client to value-based fixed pricing. Here's how it works:
- Discovery call. 15-30 min. I ask 5 questions about the outcome they want.
- Scoping doc. I write a 1-page doc describing the deliverable, the success criteria, and the fixed price.
- Fixed price quote. Based on value to the client, not hours it takes me.
- Outcome-based delivery. I deliver when the success criteria are met, regardless of time.
The first quote I sent under this model was for a Python automation project. I quoted $3,500 fixed. The same work would have been 30 hours at $100 = $3,000. Same effective hourly ($116 vs $100), but the framing was completely different.
What changed for the client
The client stopped asking "how many hours did that take?" because hours were no longer in the conversation. They asked "is this done?" instead.
The conversation about scope changes became: "This is in scope" or "This is a change order at $X." No ambiguity. No adversarial hour-counting.
What changed for me
I delivered the $3,500 project in 14 hours. My effective hourly rate: $250.
I was more motivated to deliver fast — not because I was racing a clock, but because I wanted to prove the value was real. Counterintuitive: fixed pricing made me work harder for the client.
Then the client referred me to another project at $5,000 fixed, which I delivered in 18 hours ($278/hr effective). Then another at $7,500.
In 6 months, my average effective hourly rate went from $58 (hourly billing) to $235 (fixed value pricing). 4x.
How to make the switch
The switch isn't free. Three things have to happen first:
1. You have to know the value
If I quote $3,500 for a Python automation that saves the client 10 hours per month, the value to them is $250/month × 12 × 3 years = $9,000+. I'm pricing at ~40% of value. That's the frame.
If you don't know the value, you can't price this way. Start by asking clients: "What does success look like? What's the alternative?" Their answers tell you the value.
2. You have to scope well
Fixed pricing fails when the scope is ambiguous. If I quote $3,500 to "build a Python script," I will lose money. If I quote $3,500 to "build a Python script that ingests this CSV, validates against these rules, and produces this report in this format, with this error handling, by this date" — I can deliver.
The discovery call is where this happens. The scoping doc is where it gets recorded.
3. You have to be willing to lose some clients
Some clients want hourly billing because they want budget predictability. Some want hourly because they want to feel like they're getting their money's worth. Some want hourly because they don't trust you yet.
Those clients will go elsewhere when you switch. That's fine. The clients who value outcomes (and trust you to deliver) will stay — and they'll pay more, refer more, and fight scope less.
The math
In the first month of value-based pricing, I lost 2 clients who wanted hourly.
In the second month, I signed 3 new clients at 3x my previous effective rate.
In the third month, I referred-out 4 hourly-only clients and replaced them with 5 outcome-focused clients at higher rates.
After 6 months, total revenue was 3.6x the same period in hourly mode, with 40% fewer hours worked.
What this has to do with prompt packs
Most prompt packs on Gumroad sell for $5-15. Most freelance content sells for $9-19. Those are hobby prices. They're priced that way because the sellers don't know the value they're providing.
If your prompt pack saves a freelancer 5 hours per week, and that freelancer bills $100/hour, the value is $2,000/month. Charging $9 for the pack is leaving 99.5% of the value on the table.
The Field Kit 02 — 118 Cursor prompts I sell for $9? That saves Python freelancers maybe 30 min/day. At a $75/hour bill rate, that's $750/month of value. At $200/hour, $2,000/month.
I price it at $9 because the alternative is $0 for most freelancers (they don't buy things), and $9 gets me 99% of the marginal conversions. The $9 price is deliberately low to maximize conversion, not because the value is low.
If I were selling to senior engineers at $200k+/year, I'd price it at $99-199. Same product, different positioning.
The lesson: pricing isn't a number. Pricing is a positioning. Hourly billing is a low-status position. Value pricing is a high-status position. Pick the position you want, then quote from there.
I run a one-person Python freelance shop. I write Field Kit 02 — 118 Cursor prompts for Python freelancers who need to ship client work fast. Free 10-prompt sampler or the full kit.
Top comments (0)