A day rate feels fair.
You know what a day of your time is worth.
The client knows what they're paying for.
Simple.
The problem is what it signals.
When you price by the day, you're telling the client that the value of the work is tied to how long it takes you.
Which means if you get faster (better software, better pipeline, more experience ) you earn less per project.
That's the wrong direction.
The client doesn't care how many hours you spent on the lighting.
They care what the final result does for them.
A product render that sells 3x more units is worth the same whether it took you 2 days or 8.
Day rates also create a ceiling.
There are only so many days in a month.
And once you're fully booked, the only way to earn more is to raise the day rate - which feels uncomfortable every single time.
Project-based pricing removes that ceiling.
It ties your fee to the outcome, not the clock.
And it means your growing skills work in your favour instead of against you.
– Moritz
Tiny tactical tip:
Look at your last three projects. For each one, ask: "What did this deliverable actually enable for the client?" Write one sentence per project. If you can name the business outcome, you have the start of a value-based pricing conversation for next time.