Latest / Freelance Careers with Fexingo: Independent Work, Consulting, and Self-Employment / Why Freelancers Lose Money On Bad Contracts
Transcript
- Lucas: The biggest lie we tell ourselves as independent professionals is that the hard part is getting the client. The easy part is doing the work. But if you have been in this game long enough, you know the work is actually the easiest part. The hardest part is surviving the gap between what you promised and what they expect, usually defined by a contract written by someone who didn't read it. Luna: Right, and I see this constantly with my consulting clients. They bring me a template from the internet, sign it without thinking, and then realize six weeks later that they own the intellectual property to every draft, even the bad ones. Lucas: Exactly. And it isn't always malicious on the client's side. Often, it is just laziness. They use a generic form, copy-paste a few lines, and hope for the best. But for us, that hope is a liability. Let's talk about the specific trap I call the 'Infinite Loop Clause.' It is that one sentence in a service agreement that says the deliverables must be satisfactory or approved by the client before final payment. Luna: That phrase alone has ruined more profit margins than any bad pricing strategy I have seen. It turns a fixed project into an open-ended consultation. Lucas: It does. Because 'satisfactory' is subjective. If I am a graphic designer and I send you a logo, and you say it doesn't quite capture the essence of your brand vision, do I have to redesign it? Do I have to redesign it five times? The contract doesn't say. So now I am working for free, hoping that eventually, I will hit the bullseye you had in your head all along. That is not a business model. That is a hobby. Luna: And the worst part is, once you start that loop, you feel guilty stopping. You think, 'I'm the professional, I should make them happy.' But happiness is not a contractual obligation unless it is defined. Lucas: Precisely. And this brings us to today's core topic: the difference between Scope of Work and Deliverables. Most freelancers conflate these two. They think if they list the tasks, they are protected. But listing tasks is not enough. You need measurable acceptance criteria. Without them, you are leaving your income stream entirely up to the mood of the person paying you. Luna: So, instead of saying 'design three logos,' we should say 'three distinct concepts based on the provided brief, with two rounds of minor tweaks included.' Lucas: Yes, and notice the word 'minor.' That is critical. Because once you remove that qualifier, the client can ask for a complete rebrand after round two. I want to share a specific example from last quarter involving a software consultant named David. He took a project to build a simple dashboard for a logistics company. The contract said he would deliver a functional dashboard. It did not specify the number of data sources or the user interface complexity. Luna: Oh no. Let me guess. They added four new data sources halfway through the project? Lucas: They added six. And they expected it to be done within the original timeline. David tried to negotiate, but the contract was silent on change orders. He ended up working eighty-hour weeks for three months to finish a job that should have taken four weeks. He made less than minimum wage. And when he finally finished, they paid him late because the dashboard didn't integrate with their legacy system, which wasn't mentioned in the initial scope. Luna: That is heartbreaking. And completely preventable. It sounds like the issue wasn't really David's skill, it was his documentation. Lucas: It was documentation. Or rather, the lack of it. Now, before we go deeper into the mechanics of fixing this, I want to pause for a second. We produce this show daily, covering careers, finance, and business strategy, entirely independently. There are no corporate sponsors dictating our topics or our tone. The only thing keeping these episodes ad-free and consistent is our listeners. If you find value in this kind of deep dive into your career mechanics, consider supporting us directly. Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It costs nothing extra for you, but it helps us keep the lights on and the research sharp. Luna: Yeah, we appreciate it. It really does make a difference in the quality of the work we put out there. Lucas: Thanks. Now, back to David's disaster. The lesson here is that ambiguity is expensive. In legal terms, we look for 'mutual assent.' Both parties must agree to exactly what is being exchanged. If the exchange is vague, the assent is void. You need to write your contracts so clearly that a third party could look at them and know exactly what was delivered and what was not. Luna: So, how do we translate that into practical advice for our listeners who are probably using Word documents right now? What are the specific phrases they need to delete? Lucas: Okay, let's get tactical. Here are the three most dangerous phrases I see in freelance contracts, and how to fix them. First, the 'Satisfaction Guaranteed' clause. Delete it. Replace it with 'Acceptance Criteria.' Define what success looks like. Is it a file format? A load time? A visual mockup? Make it binary. Either it meets the criteria, or it doesn't. Luna: That makes it much easier to argue. If it meets the criteria, they have to pay. No emotional negotiation required. Lucas: Exactly. Second dangerous phrase: 'Unlimited Revisions.' Never, ever write that. Even if you want to be generous, limit it. Say 'Two rounds of revisions included. Additional revisions billed at one hundred dollars per hour.' This sets a boundary. It tells the client, 'I am happy to help you refine this, but my time has value.' It also filters out difficult clients early on. Luna: I love that. It turns a potential conflict into a straightforward transaction. It removes the guilt. Lucas: It does. And the third one, which is the killer for many consultants, is 'Ownership Upon Completion.' This sounds good to you because you want to get paid. But it means you own the work until the check clears. If they don't pay, you still own the IP, but they have your work. If they do pay, you transfer ownership. The problem is, what happens during the transfer? What if they claim they never received the final files? Or what if they dispute the invoice while holding the assets? Luna: Right, so they hold leverage over you. They can drag out the payment process indefinitely because they have the goods. Lucas: Exactly. The fix is to tie IP transfer to payment receipt. Write 'Intellectual property rights transfer to Client upon full and final payment.' Simple. Clear. Unambiguous. Now, let's talk about Scope of Work vs. Deliverables again. Many people write a scope that is too narrow, which leads to scope creep. They say 'I will write five blog posts.' Then the client says, 'Great, but can you also do the SEO optimization, the image editing, and the social media captions?' Suddenly, you are doing ten jobs for the price of five. Luna: Because you didn't explicitly exclude those things. You left the door open. Lucas: You left the door wide open. The solution is to define what is NOT included. In the same document where you list your deliverables, add a section called 'Exclusions.' List everything you are not doing. No SEO. No image editing. No social media management. No travel expenses. This forces the client to either accept your boundaries or pay extra for the extras. It puts the decision back in their court. Luna: That is such a simple psychological shift. Instead of asking 'what else do you want?', you are saying 'here is what I am offering, and here is what is outside that package.' Lucas: Precisely. And it saves you hours of email tag. Because every time they ask for something outside the scope, you can point to the exclusion list and say, 'We can certainly do that. It will be an additional two thousand dollars and take three days. Shall I proceed?' Boom. Decision made. Luna: I wish I had known that five years ago. I spent so many weekends answering emails from clients who wanted 'just one small thing' that turned into a week's work. Lucas: Me too. But the good news is, clients respect boundaries. Paradoxically, having clear boundaries makes them trust you more. It shows you are professional. It shows you understand your own business. When you are vague, they assume you are disorganized. When you are precise, they assume you are competent. Luna: That is a great reframing. Competence looks like structure, not flexibility. Lucas: Exactly. Flexibility is nice, but structure is profitable. Now, there is one more layer to this. The payment schedule. Too many freelancers wait until the end of the project to invoice. This gives the client maximum leverage. If they are unhappy with anything, they withhold the entire payment. The better approach is milestone billing. Break the project into phases. Fifty percent upfront to start. Twenty-five percent at the midpoint. Twenty-five percent upon completion. Luna: This protects cash flow, obviously, but it also gives you exit ramps. If the client ghosts you after the first milestone, you have already been paid for the work you did. Lucas: It is a safety net. And it reduces the friction of the final handoff. If they owe you money at the end, you can pause delivery of the final assets. You hold the key until the lock is turned. It sounds aggressive, but it is standard business practice. You wouldn't give away a house before the mortgage is paid. Don't give away your work before the invoice is settled. Luna: I think the resistance comes from fear. We are afraid that if we ask for money upfront, they will walk away. But the reality is, serious clients expect it. Amateurs worry about it. Lucas: Spot on. And if a client walks away because you asked for a deposit, they were probably going to be a nightmare anyway. They were testing your boundaries before the work even started. Letting them go is a win. Luna: So, to summarize for our listeners: define acceptance criteria, limit revisions, list exclusions, and bill by milestones. That is the framework for a bulletproof freelance contract. Lucas: That is the framework. And remember, your contract is not a barrier to the relationship. It is the foundation of it. It clarifies expectations, protects your income, and allows you to focus on the creative work rather than the administrative panic. As we move through October fourth, twenty twenty-six, the market is rewarding precision. Clients are looking for partners who can manage risk, not just execute tasks. Your contract is your first product. Make sure it is as polished as your deliverables. Luna: I think that is a powerful way to look at it. The contract is part of the service. Lucas: It absolutely is. So, the question for you this week is not just 'can I do this job?' but 'can I define this job well enough to protect myself while doing it?' Take an hour this weekend, pull up your last contract, and hunt for those three dangerous phrases. Rewrite them. See how it feels. I bet you will sleep better. Luna: Try it. You might be surprised by how much clarity brings to your whole business.