The Service You Price by Feel Every Single Time

You have priced this thing a dozen times. Every time, you open a blank proposal, stare at the screen for a moment, and type a number that feels about right.

You are not guessing randomly. You have experience. You have a sense of what the market will bear. But you are still not working from data. You are working from a feeling shaped by your most recent project, your mood, and how much you want the work.

That is not pricing. That is estimating by memory, and memory is unreliable.

Why One Service Always Stays Soft

Most freelancers track their hours across everything but only analyze the numbers for their main service type. If you are primarily a designer, you probably have a decent sense of what a branding project takes. You have done enough of them to feel the pattern.

But the secondary services, strategy calls, documentation, onboarding support, workshops, those get quoted from feel every time because you do not do them often enough to build intuition, and you rarely go back to check what they actually cost you.

The result is that your secondary services quietly drain margin. They are priced as if they are easy and fast because they feel peripheral. Your logs usually show something different.

What Happens When You Pull the Actual Numbers

Go back through your time tracker and find every project where you offered the service in question. Pull the logged hours. Compare them to what you charged.

Calculate the effective rate for each one. Not your invoice total. Your actual hourly return.

You will likely find one of two things. Either you are consistently underpricing it because you underestimate how long it takes. Or the range is so wide that you are pricing based on how the client feels rather than what the work requires.

Both are fixable once you can see them.

Building a Floor From Your Own History

Once you have your historical data, find the project where the work went smoothly, nothing unusual happened, and the client was straightforward. Look at the hours it took. That is your baseline.

Now look at the projects that ran long. What caused it? Revision cycles? Unclear briefs? Slow approvals? Those are risks, not exceptions, and your price should account for them.

If your baseline project took 8 hours and the tricky ones took 14, you are not pricing a service that takes 8 hours. You are pricing one that takes 8 to 14 hours depending on factors outside your control. Your price needs to reflect the realistic middle, not the best case.

The Difference Between a Quote and a Number

A quote has a rationale. You can explain it. You can defend it. If a client pushes back, you have something to stand on beyond I thought that felt right.

When you price from data, that rationale exists. You can say this type of project typically runs between 10 and 15 hours based on past work, and my rate is $X, so the range is $Y to $Z. That is a professional conversation. It builds confidence on both sides.

Pricing from feel puts you in a weak position the moment anyone asks a follow-up question.

The Review That Takes Twenty Minutes

Once a quarter, open your time tracker and pull hours for every service type you offered. Do the math on effective rates. Flag anything where the number is low or inconsistent.

Update your internal rate card. Adjust your templates.

Twenty minutes of looking at real data will do more for your pricing than any industry survey or what a peer tells you they charge. Your data is specific to your work, your clients, and your process. It is the most honest input you have.

Stop pricing that service by feel. The data you need is already in your logs.

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