Why Your Slowest Project Is the Best Place to Start When Pricing a New Service

The Instinct Works Against You

When you sit down to price a new service, you almost always reach for your best example. The project that went smoothly. The client who was clear. The scope that held. The one you could point to and say, yes, that is what good looks like.

That is the wrong one to price from.

Your best project is an outlier. Everything aligned. You were experienced with the work type, the client communicated well, the scope was tight. That is not the average project. That is the ceiling.

You need to price from somewhere much less comfortable.

What Your Slowest Project Actually Contains

Pull up your time logs for a project that took significantly longer than you expected. The one that felt like it would never end. The one where the hours kept stacking up past what you quoted.

Look at where the time went. Not the big chunks of core deliverable work. The other stuff.

Extra revision rounds that came from unclear initial direction. Calls to realign after the client changed something. Time spent re-reading old emails to remember where things stood. Internal rework because a handoff between phases was incomplete. Client response delays that broke your momentum and cost you re-entry time every time you picked it back up.

All of that is data. And it is data you will encounter again on the next project of this type.

The Mistake With Optimistic Estimates

Most pricing mistakes come from estimating the work itself accurately but ignoring the surrounding time.

You know how long it takes you to write a strong deliverable when you are in flow, you have clear direction, and nothing interrupts you. So you quote from that number. Then the real project arrives with all its friction and you eat the difference.

Your slowest project shows you the friction. It shows you the buffer you actually need, not the buffer you wish you needed.

Building the Price from Bad Data First

Here is a simple way to use this.

Take the total hours from your worst project of this type. That is your ceiling estimate. Not what you quote, but the upper boundary of what this work can actually cost you.

Then take your total hours from your cleanest, smoothest project of the same type. That is your floor.

Your real estimate for a new project lives somewhere in the middle, weighted toward the slower end depending on how much you know about the client and the scope. If the new client is clear and communicative and the scope is locked, you can move toward the floor. If any of those factors are uncertain, you move toward the ceiling.

This stops you from pricing from fantasy.

What Time Tracking Makes Possible Here

None of this works if you do not have the hours broken down in any useful way.

If your logs just say a project took forty hours with no detail, you cannot see where the forty hours went. You cannot identify the friction categories. You cannot spot that twelve of those hours were revision rounds that would not exist with a better brief.

Detailed time tracking, split by task type, gives you the raw material to do this analysis. You can see that your core deliverable work is predictable. The surrounding friction is what varies. And that is the part you need to build into the price.

Do This Before Your Next Quote

Before you price your next new service, open two projects. Your cleanest and your worst. Compare total hours and where they diverged. Then look at your new service and ask yourself which version is more likely.

That answer is your starting point. Not the version where everything goes right. The honest version, built from the time you actually tracked.

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