How to Price Work You Have Never Done Before Using Data From Work You Have

Every freelancer eventually has to quote something they have never done before.

A new service type. A format you are adding to your offering. A client industry you have not worked in yet. And the instinct is to guess. To look at what others charge, pick something in the middle, and hope it holds.

That approach works until it does not. And when it does not, the failure shows up in your hours log, not in the original quote.

Why New-Service Quotes Go Wrong

The problem is not that you do not know the work. Usually you have done something adjacent. You understand the craft. You just have not done this exact configuration before.

The guess you make at the start does not account for the setup costs of learning a new workflow. It does not account for the extra revision rounds that come when you are not yet fluent in a client type. It does not account for the research that happens before you can even start.

These are real hours. They just do not show up in your mental model of the project when you are building the quote from scratch.

What Your Old Data Actually Has

If you have been logging time consistently, your old projects carry useful signals even when they are not identical to the new work.

Look at the ratio of setup time to delivery time on past projects. If you typically spend one hour on setup for every four hours of delivery, that ratio probably holds for new work of similar complexity.

Look at your revision patterns. How many revision rounds do your projects actually go through? What do they cost in hours? If you typically see 20 to 30 percent of project hours go to revisions, that is a number worth building into a new quote.

Look at your client communication overhead. How many hours per project week do you spend on emails, calls, and status updates? That cost does not change much based on service type.

How to Build the Quote From Your Logs

Pull your last three to five completed projects. Calculate each one this way: total logged hours broken into delivery, revision, setup, and communication.

Average the ratios across those projects. Now apply those ratios to your estimate of delivery hours for the new work.

If you think the delivery itself will take 20 hours, and your historical data shows revisions typically add 25 percent, you budget 25 hours for delivery plus revisions. Add your typical communication overhead. Add setup time for anything new you will need to learn or configure.

Now you have a starting point built from real data instead of optimism.

The Part You Still Have to Flag

Data from adjacent work gets you close. But new work has unknowns that old work did not.

Be honest with the client about this. You can say something like: this is a new format for me and I want to be accurate with you. Here is my estimate based on similar work, and here is where I have flagged extra buffer.

Most clients respect that more than a confident number that turns out wrong.

If the project runs over your estimate, your time log will show you exactly where. That is the data you feed back into the next quote for this type of work. After two or three projects, you will have real numbers and you can stop estimating entirely.

How Time-Trak Supports This

The value of Time-Trak for new service pricing is the historical data it builds over time. Every project you close with clean time logs is a reference point for the next quote.

When you go back to compare similar projects, the task categories matter. If you have been labeling your entries consistently, you can see delivery hours, revision hours, and communication hours broken out. That is the input your quote needs.

New work is always a guess at first. But it does not have to be a blind one.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots