How to Price a New Service Using Data From Work You Already Did

Pricing a new service is one of the places freelancers make the most expensive mistakes. No history, no data, so you guess. The guess is usually too low because it does not account for what you do not know yet.

But most new services are not entirely new. They share components with work you have already done. And if you tracked your time on that work, you have more to go on than you think.

Break the New Service Into Components

A new service type almost always contains familiar parts. A new package might include a discovery phase, a creation phase, revisions, and delivery. You may not have delivered this exact package before, but you have probably done each of those phases in other contexts.

Go into your time tracker and pull historical data on similar components.

How long does your discovery process typically take? You have done discovery for other clients. Look at the hours. What is the range? What does a heavy discovery engagement look like versus a lean one?

How long do revision rounds take on comparable work? You have logged those too. Look at the category.

You are building a price from parts you have actual data on rather than trying to estimate the whole thing from nothing.

The Components People Always Underestimate

When you are new to a service type, you tend to underestimate the things that feel invisible. Client communication for that type of engagement. The learning curve on any tools or formats that are new to you. The re-orientation time when feedback is late or unclear.

Look at your past data and find the projects most similar in structure. What percentage of total project time was not core deliverable work? That percentage is a useful input. Apply it to your estimate for the new service and add it as a buffer.

If you do not have that data because you never tracked anything but core work, this is the moment to start. You need it for every future estimate.

Build a Prototype Estimate, Then Pressure-Test It

Put your component-based estimate together. Then ask yourself three questions.

What happens if the client's feedback is slow and I have to re-read this work twice to re-engage? Add time.

What happens if the scope turns out to be 20 percent larger than the brief suggested? It usually does. Add a buffer.

What happens if I am slower at this than I expect because it is genuinely new territory? Add time.

None of these are padding. They are realistic adjustments based on how projects actually behave.

Price the First One to Learn, Not Just to Win

The first time you deliver a new service, your primary output is not just the deliverable. It is the data.

Track everything on that first engagement. Create categories specific to this service type. Log every hour of every component, including the parts you did not quote explicitly.

When the project closes, run the numbers. What did it actually take? How does that compare to your estimate? Where were you closest and where were you furthest off?

That data is what you use to price the second engagement. And the second engagement's data refines the third.

Within three to four projects of the same type, you will have a real picture of what the service costs you to deliver. Your prices can reflect that reality.

What This Does to Your Confidence

Pricing from data changes how you talk about your rates. You are not hoping the number is right. You know roughly what this kind of work requires because you have tracked it.

When a client asks how you arrived at your price, you can say it is based on what similar engagements have required in practice. That is a much stronger position than saying you looked at what others charge or that it felt about right.

The data is already in your time tracker. The new service just needs you to use it.

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