Latest / Freelance Careers with Fexingo: Independent Work, Consulting, and Self-Employment / How a Freelance Consultant Raised Rates by Charging Per Outcome
Transcript
- Lucas: So I was catching up with a friend who runs a boutique marketing consultancy, and she mentioned she'd just signed a client for a fifteen thousand dollar engagement. That's not unusual, but what caught my ear is how she structured it. Luna: What do you mean, how she structured it? She didn't quote her usual monthly retainer? Lucas: No, she ditched the hourly and project rates entirely. She charged per outcome — a flat fee tied to hitting a specific revenue milestone for the client. And it wasn't a small bet; it was three times what she would have billed on her old retainer model. Luna: That's a bold move. But it also sounds risky — what if she doesn't hit the milestone? Does she eat the loss? Lucas: Right, and that's exactly the trade-off. And before we go deeper into that, I want to be straight with you for a second. A few listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's genuinely what keeps this show running without ads. It's not a big ask, just mentioning it because we're able to have these detailed conversations thanks to that support. Luna: Yeah, it's a small group of people and it makes a huge difference. And honestly, the fact that we can dive into a niche pricing model like this without worrying about sponsors is pretty nice. Lucas: Exactly. Okay, back to the outcome pricing. The key is that she didn't just take a leap of faith. She had a framework for when it makes sense and how to protect herself. And that's what we're going to unpack today. Luna: Good. Because I feel like most freelancers hear 'outcome-based pricing' and think it's either a magic bullet or a terrible idea. Where's the middle ground? Lucas: The middle ground is knowing when to use it and how to structure it. My friend's case is a perfect example. She'd been working with this client — a SaaS company — on a monthly retainer for about six months. She was doing their content marketing, and she knew their funnel inside and out. Luna: So she had a lot of context already. That's probably not something you'd try with a brand new client. Lucas: Exactly. She had data. In the prior quarter, her content work was generating about thirty thousand dollars in new pipeline each month. So when the client said they wanted to double pipeline, she saw an opportunity to tie her fee to that outcome. Luna: And she priced it at fifteen grand. So she was essentially saying, 'I'll get you to sixty thousand a month in pipeline, and if I do, you pay me fifteen.' That's a fraction of the value created. Lucas: Right. And she'd have made only five grand on the retainer. So she tripled her fee, but she also took on the risk that she might not hit the target and get paid less. In this case, she hit the milestone in eight weeks. Luna: So what was her exact structure? Was it all-or-nothing, or did she have partial milestones? Lucas: She had a base plus bonus. There was a base fee of five thousand to cover her baseline work, and then a ten thousand dollar bonus triggered when the pipeline hit the agreed number. So even if she fell short, she wasn't completely out of pocket. Luna: That's smart. It's a hedge. And it makes the client feel like they're sharing risk too. Lucas: Exactly. And she had clear guardrails. The milestone was defined as 'qualified opportunities created' — not just raw leads. They agreed on what counts as qualified, so there was no ambiguity. Luna: I love that. So many freelancers get burned because they don't define the outcome precisely. What else should someone consider before trying this? Lucas: First, you need a baseline. If you can't measure where the client is today, you can't prove the improvement. My friend had six months of data. If you're starting cold, maybe ask for a paid diagnostic period to gather that data. Luna: So that's the discovery workshop approach we talked about in an earlier episode, but applied to measurement. Lucas: Exactly. Second, you need to believe you can actually influence the outcome. If the client's sales team is the bottleneck, you can't guarantee pipeline. So scope it to what you control. My friend's contract explicitly stated that her fee was tied to marketing-generated pipeline, not total company revenue. Luna: That's a crucial boundary. Because if you tie your fee to the whole company's revenue, you're at the mercy of factors you can't touch — like pricing changes or a supply chain issue. Lucas: Precisely. And third, you need a time limit. She set a ninety-day window. If she hadn't hit it by then, the bonus expired and the client could decide whether to renegotiate. That creates urgency and prevents an open-ended promise. Luna: So the time limit protects both sides. The client knows they're not paying forever, and you know you're not on the hook indefinitely. Lucas: Right. And another thing that made this work is she had a strong relationship. She'd been working with this client for six months, so there was trust. I wouldn't recommend this as a first engagement with a brand new client. Luna: Makes sense. You need that trust to even propose a structure where you get paid more if you succeed, because some clients might see it as you gaming the system. Lucas: Exactly. And you need to be confident in your own ability to deliver. My friend had a track record with this client, and she knew her content strategy was working. If she'd been less certain, she probably wouldn't have taken the risk. Luna: So what about the downside? What if she'd missed the milestone? She'd have walked away with five grand instead of fifteen. That's a big cut. Lucas: Yeah, and she acknowledged that. But she had enough buffer in her other clients that she could absorb that risk. And she also learned a lot about her own performance. Even in a 'failure,' you get valuable data about what works and what doesn't. That's something you can use in future pitches. Luna: That's a good reframe. It's not just about money, it's about building your evidence base. But I imagine some freelancers hear this and think, 'There's no way I can track outcomes like that. I'm a designer, or a writer, or a web developer.' Can this work beyond marketing? Lucas: Absolutely. The principle is the same: find a measurable outcome that ties to your work. For a web developer, it could be a fee tied to a drop in page load time that leads to higher conversion. For a writer, maybe a whitepaper that generates a certain number of qualified leads. The key is to identify what your client cares about and what you can measurably influence. Luna: But there's a risk that the client feels like you're making money off their success in a way that feels gimmicky. How do you frame it as a professional proposal? Lucas: You frame it as alignment. You say, 'I'm so confident I can deliver this outcome that I'm willing to put a portion of my fee on the line. That way, we both win when I hit the target.' That demonstrates confidence, and it shows you're thinking like a partner, not a vendor. Luna: That's a compelling pitch. But I have to ask — what about the ethical side? Are you incentivized to cut corners or chase the metric at the expense of quality? Lucas: That's a real concern, and it's why defining the outcome precisely matters. If you define it as 'qualified opportunities,' you can't just stuff the funnel with junk. And you should also include a quality clause in your contract. My friend had a clause that said all work must meet industry standards and be approved by the client. So it wasn't just a number chase. Luna: So there's a governance layer. That's reassuring. And I guess on the flip side, the client could also try to game the system by moving the goalposts. How do you avoid that? Lucas: You write the definition of the outcome into the contract in as much detail as possible. In her case, they specified the CRM fields that would be used to track opportunities, the stages that counted as 'qualified,' and even the time zone for the deadline. That eliminates most ambiguity. Luna: Wow, that's detailed. It sounds like a lot of upfront work. Is it worth it for every engagement? Lucas: No, and that's the key takeaway. Outcome-based pricing is not for every project. It works best when the outcome is easily measurable, you have a strong performance history, and the client is sophisticated enough to appreciate the risk-sharing. For smaller or more ambiguous projects, stick with hourly or project rates. Luna: So it's a tool in your pricing toolkit, not a replacement for everything. Lucas: Exactly. And when you do use it, you can command a premium because you're absorbing risk. That's why my friend could triple her rate. She wasn't just selling hours; she was selling outcomes, and that's worth more. Luna: I love that. And I think a lot of freelancers would love to have that kind of confidence in their own work. Is there a way to build up to it? Lucas: Sure. Start by tracking your own metrics on every project. What impact did your work have? How much did you increase revenue or save time? Build that evidence base. Then, when you have a client who trusts you and a clear deliverable, propose a pilot: maybe fifty percent of your fee tied to an outcome. That's a low-stakes way to test the waters. Luna: That's a great stepping stone. And it gives you data to refine your approach before you go all in. Lucas: Yeah. And even if you never do a pure outcome-based fee, thinking in terms of outcomes can change how you talk about your pricing. You stop saying 'I charge a hundred dollars an hour' and start saying 'I can help you generate fifty thousand in pipeline for fifteen thousand.' That's a different conversation. Luna: That's a powerful shift. So maybe the real lesson is about mindset, not just the fee structure. Lucas: That's the takeaway. It's about positioning yourself as a partner who delivers results, not a vendor who sells time. And when you can do that, you can charge for the value you create, not the hours you put in. Luna: Well said. I'm going to start thinking about what outcomes I could tie my own work to. Thanks for the food for thought, Lucas. Lucas: Anytime. And if any listeners try this, I'd love to hear how it goes. Maybe we can do a follow-up episode with your stories.