Latest / Freelance Careers with Fexingo: Independent Work, Consulting, and Self-Employment / How a Freelancer Priced a Fixed-Fee Project
Transcript
- Lucas: So Luna, I was talking to a brand strategist last week who just landed a fixed-fee contract worth a hundred and twenty thousand dollars. And the way she priced it — it wasn't by multiplying her hourly rate by estimated hours. Luna: Okay, now I'm curious. How did she do it? Lucas: She anchored the price to the client's projected revenue increase. The client was launching a new product line, and her research suggested it could add a couple million in annual revenue. So a hundred and twenty grand was less than six percent of that potential upside. Luna: That's a smart way to justify a big number. But doesn't that feel risky? What if the client pushes back and says, 'Well, what if we don't hit that revenue'? Lucas: Right, and that's exactly the conversation she had. She framed it as an investment, not a cost. She said, 'You're not paying for my time, you're paying for the outcome.' And she had a couple of case studies to back up her track record. Luna: So she sold the outcome, not the hours. I love that. But what about scope creep? Fixed fees are notorious for that, right? Lucas: She handled that upfront. Before she quoted, she outlined a detailed scope of work — deliverables, timelines, number of revisions, communication channels. And she built in a buffer for the inevitable 'quick questions' that pop up. Luna: A buffer. How much did she add? Lucas: She estimated her hours based on past projects, then added about twenty percent. Plus, she included a change-order clause — anything outside the agreed scope gets billed at her hourly rate, which she set at a premium. Luna: So the client knows that extra requests are not free. That's a good deterrent. Lucas: Exactly. And it also protects the relationship, because you're not getting resentful every time someone asks for one more tweak. You just say, 'Sure, I can do that. Here's the additional cost.' Luna: That makes sense. But I'm wondering — when is a fixed fee a bad idea? Because I've seen freelancers get burned on projects that end up taking way more time than expected. Lucas: Fixed fees work best when the scope is clear and the deliverables are well-defined. If you're doing something exploratory, like a research phase where you don't know what you'll find, hourly or daily rates are safer. Or a retainer can work too. Luna: So it's about matching the pricing model to the level of uncertainty. Lucas: Right. And also to your own experience. If you're new to fixed-fee pricing, start with smaller projects, track your hours, and learn from the miscalculations. Luna: That's solid advice. And it reminds me — if you're finding these pricing discussions helpful, and you want to keep hearing them ad-free, a couple of dollars a month on buy me a coffee dot com slash fexingo genuinely helps keep the lights on. It's a small thing, but it makes a real difference for us. Lucas: Yeah, that's true. We appreciate every bit of support. But back to pricing — there's another layer to this. The psychology of the number itself. Luna: The psychology? You mean like anchoring? Lucas: Exactly. She quoted a hundred and twenty instead of, say, a hundred and seventeen. Round numbers can feel arbitrary, but a precise number suggests you've actually done the math. It feels more credible. Luna: Interesting. So you're saying a number like that signals competence. Lucas: It can. And the way you present it matters too. She walked the client through her thinking — here's the scope, here's the research, here's the projected value. She didn't just throw out a number and hold her breath. Luna: So she made it a conversation, not an ultimatum. Lucas: Yes. And she also had a fallback. She was prepared to break the project into phases, each with its own fixed fee. That way, the client could say yes to the first phase without committing to the whole thing upfront. Luna: That's a great way to reduce the client's perceived risk. Lucas: And it increases your chances of getting a yes. Once they're in the first phase, they see the value, and they're more likely to continue. Luna: Okay, but what if the client still balks at sixty thousand for phase one? What then? Lucas: Then you go back to the value story. You remind them of the revenue projection. If they're still hesitant, you could offer a smaller pilot — a focused deliverable for a lower fee — to prove your approach. Luna: So it's about finding the smallest possible yes. Lucas: Exactly. And once you've delivered that pilot, you've got a track record with that client. It's much easier to justify a bigger fee for the full project. Luna: I love that. It's all about building trust and demonstrating value step by step. Lucas: Right. And one more thing — she didn't undervalue her work. She knew her rate was higher than the market average, but she also knew the ROI she could bring. She walked in with confidence, and that came through in her tone and body language. Luna: Confidence is huge. Clients can sense when you're second-guessing yourself. Lucas: Absolutely. So the takeaway is: don't just pick a number out of thin air. Do the research, estimate your hours, add a buffer, and then anchor the price to the value you're creating. And always put it in writing with a clear scope. Luna: That's a solid framework. I'm going to try that on my next project. Maybe I'll finally get off the hourly hamster wheel. Lucas: Do it. And once you make the leap, you'll never look back.