Latest / Freelance Careers with Fexingo: Independent Work, Consulting, and Self-Employment / How a Freelancer Raised Rates by Refusing Rush Work
Transcript
- Lucas: A few years ago I was talking to a freelance UX designer based in Portland. She charged $120 an hour, which is decent but not top of market. She'd been at that rate for two years and couldn't seem to push past it. Every time she tried to raise it to $130 or $140, clients would push back hard. Luna: Classic rate ceiling. What changed? Lucas: She didn't raise her base rate at all. Instead, she added a clause to her standard contract that said, quote, 'Standard lead time is three weeks. Projects required in fewer than three weeks will incur a 50 percent rush fee on the total project cost.' That's it. No mention of raising the hourly rate. Just a lead time and a premium for rushing. Luna: And that worked? Clients actually paid the 50 percent? Lucas: Most did. Some pushed back. A couple walked. But here's the key: her average effective rate — what she actually earned per hour across all projects — went from $120 to about $144 within six months. Because roughly a third of her projects came in as rush orders. Luna: So she effectively got a 20 percent rate increase without ever saying 'I'm raising my rates.' That's clever. Lucas: Exactly. And it's a tactic that works because it's tied to something the client values: speed. They're not paying more for the same work — they're paying more for faster delivery. That's a much easier sell than 'I think I'm worth more now.' Luna: Before we dive deeper into how she implemented it, I want to mention something. Lucas and I record this show because we genuinely believe that better pricing tactics can make freelance careers more sustainable. And we keep it ad-free — no sponsors, no mid-roll interruptions. If you find episodes like this helpful, you can support that choice at buy me a coffee dot com slash fexingo. It's a low-key way to keep the show exactly what it is. Lucas: Yeah, and it honestly makes a difference. A lot of listeners use it, and that lets us spend time on these specific cases rather than chasing sponsorship deals. So if you've gotten value from the show, that link is buy me a coffee dot com slash fexingo. Now — back to the lead time clause. The UX designer I mentioned, she told me she got the idea from a friend who was a photographer. Photographers have charged rush fees for decades. You want photos edited in 24 hours? That's a premium. So she just adapted it for UX. Luna: Makes sense. What did the clause actually look like in her contract? Lucas: She showed me. It was a single paragraph in her scope of work section. It said: 'Standard project timeline is three weeks from signed agreement and deposit. Any project requiring delivery in fewer than three weeks will be charged a rush fee of 50 percent of the total project fee. Rush availability is subject to current workload and may not be available at all times.' Short, clear, no legalese. Luna: I love the 'may not be available' part. It gives her an out if she's already swamped. Lucas: Right. And it also signals that rushing is a favor, not a right. That's important psychologically. When a client asks for a rush, they're asking for a concession. The fee acknowledges that. Luna: Did she lose any clients over it? Lucas: She lost two in the first three months. One was a startup that needed a prototype in a week and didn't want to pay the premium. She let them walk. The other was an existing client who felt the clause was 'unfair' because they'd never needed a rush before. She offered to grandfather their current project, but after that, the clause would apply. They declined and moved on. Luna: So she lost two clients but her effective rate went up 20 percent. Is that a trade-off most freelancers would accept? Lucas: Depends on utilization. If you're at 80 percent booked, losing two clients might mean you have room to take on higher-paying rush work from others. But if you're at 50 percent, losing any client hurts. The key is to test it at a time when you have some buffer, so you're not desperate for every project. Luna: What about the clients who accepted the rush fee? Did they ever complain later? Lucas: A few grumbled. But she handled it by framing the fee as a trade-off. She'd say, 'I normally have three weeks for this, but if you need it in one, I'll have to reprioritize other work. The rush fee compensates for that disruption.' Most clients accepted that. Some even said it made them plan better. Luna: So the clause actually changed client behavior? Lucas: Yes. She noticed that within six months, the number of rush requests dropped slightly, because clients started planning ahead to avoid the fee. That's actually good for her — it smooths out her workflow. But the rush requests that did come in were from clients who really needed speed and were willing to pay for it. So her income went up and her stress went down. Luna: That's a double win. What about the clients who never needed a rush? Did they ever ask for a discount because they were giving her longer lead times? Lucas: A couple did. One said, 'Since I always give you four weeks, shouldn't I get a discount?' She thought about it and decided not to offer one. Her reasoning was that the standard rate already assumes a reasonable timeline. She wasn't charging extra for slow — she was charging extra for fast. That distinction matters. Luna: I think that's a smart boundary. If you start discounting for slow, you're just lowering your base rate again. Lucas: Exactly. And she also realized that the rush fee gave her a negotiation lever. If a client pushed back on the rush fee, she could offer to start the project earlier if they signed the contract sooner. That way, she still got the project on her timeline, without the fee. It turned into a scheduling tool. Luna: So the rush fee isn't just about money — it's about controlling your time. Lucas: That's the deeper point. Freelancers often feel like they have to say yes to every client request, especially on timing. A rush fee gives you permission to say yes — but at a price that makes it worth your while. Without it, you're just working faster for the same money, which is a recipe for burnout. Luna: Are there any industries where this wouldn't work? I'm thinking of, say, freelance writers, where turnaround times are already short. Lucas: It works best where the standard timeline is clearly measurable. For a writer, your standard might be one week for a 1,000-word article. If a client wants it in 24 hours, you charge a rush fee. The principle is the same. But if your standard is already 24 hours, there's no room. So you need to define a standard that's reasonable for you. Luna: What about freelancers who work in retainer relationships? Does a rush fee apply there? Lucas: It can, but it's trickier. Some freelancers include a certain number of rush projects per month in the retainer. Anything above that triggers a fee. Others just set a clear response time — like 48 hours for emails, 5 business days for deliverables. If a client wants something faster, it's an add-on. Luna: I've also seen freelancers use a 'rush fee' as a way to test whether a client values speed enough to pay for it. If a client balks at the fee, they might not actually need it that fast — they're just being impatient. Lucas: That's a really good point. The rush fee acts as a truth serum. If a client says 'I need this by Friday' but won't pay the premium, then maybe they don't actually need it by Friday. It forces them to prioritize honestly. Luna: So what's the one concrete step a freelancer should take after hearing this episode? Lucas: Pick one project type, define your standard lead time for that type, and add a rush fee clause to your next contract. Don't change your base rate. Just add the clause. Then track what happens over the next three months. How many rush requests come in? How many pay the fee? What's your effective rate at the end of the quarter? That data will tell you if it's working. Luna: And if you're nervous about losing clients, you can test it on new clients only, or add it with a 30-day notice for existing ones. Lucas: Exactly. The Portland designer started with new clients only. Once she saw it worked, she added it to her existing contracts at renewal. Within a year, all her clients were under the new terms. Luna: I think the real lesson here is that rate increases don't have to be blunt instruments. You can raise your effective income without ever saying 'I'm raising my rates.' You just have to tie the increase to something the client values. Lucas: And that's what makes this tactic so elegant. It's not about demanding more for the same thing. It's about offering a premium service — speed — at a premium price. The client gets what they want, you get paid fairly, and everyone's happy. Luna: Alright, I'm going to look at my own contract today and see where I can add a lead time clause. Lucas: Do it. And let us know how it goes. We'd love to hear from listeners who try this. Maybe we'll do a follow-up episode with your stories.