Latest / Freelance Careers with Fexingo: Independent Work, Consulting, and Self-Employment / How Freelancers Can Build a Client Price Escalator That Actually Sticks
Transcript
- Lucas: You know how every freelancer I talk to says the hardest part of their business is raising rates on existing clients? Luna: Oh yeah. It's the universal dread. You've built a good relationship, you're delivering value, and then you have to ask for more money. Lucas: Right. And the typical advice is 'just do it' or 'have the conversation.' But that's like telling someone to jump out of a plane without a parachute and saying 'trust the wind.' Luna: There's no structure to it. No framework. Lucas: Exactly. So today I want to talk about the client price escalator — a pre-agreed, structured mechanism for increasing rates over time. Not an inflation clause, not a 'we'll renegotiate next year.' I mean a specific, contractual or written understanding that your rate will go up by a certain amount at certain intervals, tied to something concrete. Luna: Okay, I love this. But I have to say — when I hear 'price escalator,' I think of those cell phone contracts that sneak up on you. How do you make it feel fair? Lucas: That's the key question. Let me give you a real example. I worked with a freelance UX designer — let's call her Sarah — who landed a contract with a Fortune 500 retail company. She was doing product design sprints for them, and the initial rate was $150 an hour. She knew that if she stayed at that rate for three years, she'd be leaving money on the table. Luna: Right, because her expertise grows, the market moves, and her costs go up. Lucas: So instead of a flat rate, she proposed a 15% annual escalator, starting after the first six months. But the genius move was how she framed it. She didn't say 'I need to protect myself against inflation.' She said 'I want to commit to this relationship long-term, and I want my compensation to reflect the increasing value I'll bring as I learn your systems, your customers, and your industry.' Luna: That reframes it completely. It's not about her — it's about the partnership. Lucas: Exactly. And she tied the escalator to specific deliverables and milestones. Year one, she'd lead two design sprints per quarter. Year two, that would go to three, with more complex projects. The escalator was linked to the increased scope. Luna: But what if the client says no? 'We can't commit to annual increases.' That's a common pushback. Lucas: Then you have a conversation. Sarah had a backup — a two-year contract with a fixed rate but a guaranteed minimum of hours. That gave her the security, and she could revisit rates at renewal. But the client actually said yes to the escalator because it was reasonable and well-justified. Luna: So what's the structure you recommend? Is there a standard model? Lucas: I think there are three types. The first is cost-plus escalator — tied to CPI or some inflation index. I don't love that one because it's defensive and small. The second is value-linked — tied to specific outcomes, like if you reduce their time to market by X%, your rate goes up. Luna: That one is harder to measure, but powerful if you can. Lucas: And the third is milestone-based — tied to tenure or project complexity. That's what Sarah used. You say 'after 12 months, my rate increases by 10% because I will have developed institutional knowledge that makes me more efficient and effective.' Luna: I like that. It's predictable for both sides. But what about when a client is really price-sensitive? Like a startup or a non-profit? Lucas: Then you adjust the magnitude. Maybe it's 5% instead of 15%. Or you do a two-year escalator freeze with a larger jump at renewal. The point is to get the conversation started. Even a small escalator trains the client that rates grow over time. Luna: That's a good point. It sets a norm. And if you never mention it, the norm is that your rate stays flat forever. Lucas: Right. And let's talk about timing. When do you introduce the escalator? Ideally, during the initial proposal, not after the relationship is established. It's much easier to include in the first contract than to amend later. Luna: But what if you're already working with a client and you want to add one? Is it too late? Lucas: Not if you handle it right. You can say 'I'd like to propose a framework for our ongoing work together that ensures I can continue to deliver at the highest level.' And then propose a six-month trial escalator. Or you can link it to a new project or expansion of scope. Luna: So it's never really too late — you just need a reason that feels organic. Lucas: Exactly. And one more thing — the psychological framing. People hate losing more than they love gaining. So instead of 'I'm raising my rate by 10%,' you say 'I'm offering you a 5% discount on my standard rate for the first year, with an escalator to full rate over time.' Luna: Oh, that's clever. You anchor them on a higher starting point. Lucas: Yeah. If your normal rate is $200, but you start at $180 with an escalator to $200 over two years, the client feels like they're getting a deal. And you're just getting to your actual rate. Luna: That's a total reframe. And it's transparent if you explain it. Lucas: Exactly. Now, I want to be honest — not every client is right for an escalator. If you're doing a one-off project or a very short engagement, it's not worth the complexity. And if the client is a small business with razor-thin margins, you might strain the relationship. You have to read the room. Luna: But for longer-term retainer relationships, it seems like a no-brainer. I've used a version of this with my consulting clients, and it's saved me a lot of awkward conversations. Lucas: And for those of you listening who are thinking about it — here's a simple script. 'Based on our work together, I'd like to propose a pricing structure that aligns with the growing value I bring. Starting in month seven, my rate will increase by 8% annually. This allows me to invest more in your project and ensures I can continue to prioritize your work.' Luna: That's direct, professional, and it frames it as a benefit to the client. I like it. Lucas: Now, I want to shift gears slightly. Because something else has come up in conversations with listeners recently — how we keep this show going. And it connects to pricing and value. Luna: How so? Lucas: Well, we don't run ads. That's a deliberate choice. The show is funded entirely by listeners who chip in a few bucks a month through buy me a coffee dot com slash fexingo. It's not a huge number, but it's enough to cover production costs and keep us independent. Luna: Yeah, I think that model works because it's voluntary and it's tied to the value people actually get. If we've helped you think through a career move or a pricing strategy, that's great. And if you want to support that, the option is there. Lucas: Exactly. It's like a price escalator for the show — listeners who find increasing value over time can contribute accordingly. No pressure, just an honest option. And it keeps the content focused on you, not on advertisers. Luna: Right. So back to escalators — I want to ask about one more scenario. What if a client agrees to an escalator but then tries to renegotiate when it's time to increase? Lucas: That happens. And that's why you need the agreement in writing. But also, you need to be prepared to have the conversation again. Remind them of the value delivered. Show them the results. And if they still push back, you have a choice — hold firm or offer a compromise. Maybe a smaller increase in exchange for a longer commitment. Luna: So it's not set in stone. It's a starting point for negotiation. Lucas: Exactly. The escalator is a tool, not a weapon. It's designed to make the conversation easier, not to force a confrontation. And if you approach it with that mindset, most clients will respect it. Luna: I think the bottom line is: don't leave your pricing to chance. Have a plan, have a structure, and communicate it early and often. Lucas: That's it. And next time you're drafting a contract, ask yourself: 'What would this relationship look like in three years? And how do I build that into my pricing today?' Because if you don't design it, you'll end up reacting to it. Luna: Good point. And if you want to see some sample escalator clauses, we'll link to a resource in the show notes. Lucas: Yes. Until next time, keep building those frameworks.