The Rush Job That Taught Me How I Actually Price Things

The message came in on a Wednesday afternoon. Client needed a full content package by Friday. Same rate as always, they said. Just faster.

I said yes.

I always said yes to this client. They were good people. They paid on time. Saying no felt strange.

What the Next 48 Hours Actually Looked Like

I moved everything. Pushed a deadline for another client. Skipped two personal things I had planned. Ate lunch at my desk both days. Worked until midnight on Thursday.

The project got done. Client was thrilled. Invoice went out for the same amount we always used.

I felt exhausted and vaguely resentful and I couldn't quite explain why.

So I looked at my time log.

The Hours Were Not the Same

A normal version of that project took me about nine hours across a week. Comfortable pace. Some thinking time built in. I'd arrive at the work ready.

The rush version took fourteen hours in two days. The actual work wasn't more. But the compression cost me. More mistakes to fix. More decision fatigue. More time staring at a document trying to think because my brain was already tired.

I charged for nine hours. That's what the fixed rate assumed.

The five-hour difference was just gone.

The Pricing Logic I Had Never Examined

I had set my project rate based on how long a project takes at a normal pace with normal conditions.

I had never once thought about what happens when the conditions change.

Rush jobs are a different product. They cost the client the same but they cost me significantly more. Not just in hours but in what they displace. When I compress that much work into two days, everything around it suffers.

I had no rush rate. I had never built one. I had never even thought about whether I needed one.

What the Log Made Obvious

After that project I started flagging rush work in my time tracker. Any project with a turnaround under 72 hours got tagged. I wanted to see what the real hour pattern looked like over time.

After about four months I had enough data to see it clearly. Rush projects ran 40 to 60 percent more hours than standard turnaround versions of the same work. Every time. Not because the work was harder but because compression is inefficient and my brain doesn't run well at full sprint for two days straight.

I had been pricing the sprint at the same rate as the jog. For years.

Building the Rush Rate

I added a 50 percent surcharge for anything under 72 hours. Wrote it into my client agreement. Sent a short note to active clients explaining the change.

One client pushed back mildly. Everyone else just accepted it. Some of them actually seemed to respect it more than the old arrangement, where I would just say yes to anything.

The next time that first client came to me with a 48-hour ask, I quoted the rush rate. They approved it in twenty minutes.

I made more on that project than I ever had on a comparable one. And I still worked two hard days. But at least the math made sense.

The Lesson Underneath the Lesson

You can't build accurate pricing from memory. Memory flattens everything. The easy weeks and the brutal ones average out in your head into something that feels normal.

The log doesn't average things out. It shows you what the rush job actually cost. What the slow client actually cost. What the revision-heavy project actually cost.

That's information. And it's worth more than the guess you've been quoting from.

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