Latest / Solopreneur Sessions with Fexingo: One-Person Businesses, Freelancing, and Independent Work / How Solopreneurs Protect Their Time From Scope Creep
Transcript
- Lucas: There is a specific kind of exhaustion that only freelancers and solopreneurs really understand. It isn't the kind that comes from working long hours. It is the kind that comes from working on things that were never part of the original agreement. Luna: Yeah, the invisible overtime. The extra revisions that weren't billed. The 'quick favor' that takes three days. Lucas: Exactly. And we have talked about pricing before. But today I want to drill into the structural leak that kills profitability even when your hourly rate is high. It is scope creep. Not the vague idea of doing more work, but the specific contractual ambiguity that allows clients to assume inclusion. Luna: So this is less about saying no, and more about defining what yes actually means? Lucas: Precisely. Most solopreneurs write proposals that focus on outcomes rather than inputs. That sounds good. But if you do not define the inputs, the client defines them for you based on their expectations. And those expectations are usually infinite. Luna: I see this all the time with design clients who think branding includes every social media post for a year because they didn't specify a limit. Lucas: Right. So let us look at a concrete example. Imagine a marketing consultant hired to create a launch campaign. The contract says 'create and execute a four-week digital campaign.' Sounds clear, right? But execution can mean posting, community management, A/B testing ad copy, and writing weekly performance reports. Luna: And if none of that is itemized, the client assumes you will do all of it until they say stop. Lucas: Until they say stop or until you burn out. I worked with a graphic designer recently who quoted a flat fee for a logo suite. She did not specify the number of concepts or revision rounds. The client asked for twenty variations. She spent two weeks iterating on logos that were never going to be used. Luna: That is not just lost time. That is lost confidence. You start resenting the person paying you. Lucas: It is toxic. And the worst part is that she felt guilty charging extra because she thought she should have been clearer. But clarity is a service product too. You need to sell the boundary as much as you sell the creative work. Luna: Do you think most people avoid setting these boundaries because they fear losing the client? Lucas: Fear of losing the client is real. But fear of looking difficult is often bigger. Solopreneurs worry that if they put strict limits in the contract, they will seem rigid. They think flexibility is a selling point. Luna: But flexibility without structure is just chaos. Or unpaid labor. Lucas: It is unpaid labor disguised as generosity. Here is the thing about professional services. Your time is your inventory. If you give it away, you are giving away your ability to serve other clients. You cannot scale if you are constantly absorbing undefined scope. Luna: So how do you frame the boundary so it feels like protection for the project quality rather than just restriction? Lucas: You tie it to quality. You say, 'To ensure the highest quality output, we will focus on these three core deliverables within this timeline. Additional requests will be scoped separately to maintain that standard.' Luna: That shifts the narrative from 'I won't do it' to 'I want to do it well.' Lucas: Exactly. It makes the constraint a feature. Now, let me ask you something. When you look at your own workflow, where does the ambiguity usually hide? Luna: For me, it is always in the maintenance phase. Clients expect ongoing support after the main project is done, without a retainer agreement. Lucas: Maintenance is the silent killer. You build the system, hand it over, and then they email you every Tuesday asking why it broke. Without a defined support window, you become their free IT department. Luna: Yes. And it fragments your focus. You jump from deep work to troubleshooting all day. Lucas: So here is a practical framework. First, define the 'Done State.' What exactly happens on the last day? Is it a file delivery? A training session? A sign-off email? Write it down explicitly. Luna: Second, define the 'Change Process.' What happens if they want something new? Lucas: Third, define the 'Exclusions.' List three things you are definitely not doing. This forces you to think about what falls outside the scope before the client does. Luna: That third one is smart. Exclusions prevent assumption. If you don't list it, they assume it's included. Lucas: Let me pause here for a second to talk about how this show stays running. If these conversations have moved your work forward in some small way, consider supporting the network directly. It keeps the production ad-free and ensures we can keep digging into these operational details. You can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: It really helps us dedicate the time to research these specific frameworks instead of rushing through surface-level advice. Lucas: Thanks for listening. Now, back to the exclusions. Let us say you are a copywriter. An exclusion might be 'SEO keyword research' or 'social media scheduling.' Why is listing exclusions powerful? Luna: It sets a precedent. It shows you know your lane and respect theirs. Lucas: It does. And it invites collaboration. If they need SEO, they hire an SEO specialist. You refer them. That builds trust. You are not gatekeeping; you are curating the best outcome for them. Luna: That changes the dynamic completely. Instead of a transactional vendor, you become a strategic partner who knows when to say 'not my job, but I know who can help.' Lucas: Right. And that referral value is huge. But we need to go deeper into the contract language. Vague terms like 'reasonable effort' or 'industry standard' are traps. They mean different things to different people. Luna: What are better alternatives to those phrases? Lucas: Use numbers. Specify 'three rounds of revisions,' 'two forty-five minute strategy calls,' 'one hour of implementation support.' Quantify everything you can. If it cannot be quantified, define the criteria for acceptance. Luna: So instead of 'high-quality design,' you say 'design must meet brand guidelines and pass accessibility standards.' Lucas: Exactly. Criteria remove subjectivity. Subjectivity is where scope creep thrives. When the client says 'it doesn't feel right,' you need to be able to point to the criteria and say, 'We met the agreed criteria. If you want to change the direction, that is a new scope.' Luna: That requires a lot of confidence to enforce. Especially with difficult clients. Lucas: It does. But remember, a client who respects your boundaries is easier to work with than one who exploits them. Boundaries filter out bad fits. If a client gets angry about clear terms, they were likely going to be difficult anyway. Luna: So the boundary acts as a screening tool. Lucas: It is. And it protects your cash flow. Every hour spent on unscoped work is an hour not spent on billable work or business development. The cost of scope creep is not just lost time. It is lost opportunity. Luna: That is a hard metric to track though. How do you measure the opportunity cost? Lucas: You track your billable utilization rate. If you spend thirty percent of your week on non-billable fixes, your effective hourly rate drops significantly. You can calculate this easily. Take your monthly revenue and divide by total hours worked, including the unbillable ones. Luna: Oh wow. That usually looks terrible compared to the stated hourly rate. Lucas: It does. And seeing that number is often the wake-up call needed to tighten contracts. Once you see your effective rate drop, you start fighting for every hour. Luna: It makes the abstract problem of 'feeling busy' into a concrete financial problem. Lucas: Precisely. And solving it feels like profit protection. Which brings us to the final piece. Change orders. You need a simple process for handling mid-project additions. Luna: A one-page addendum? Lucas: Keep it simpler. A quick email summary works. 'Per our conversation, adding X will require Y additional hours and Z additional dollars. Please reply 'approved' to proceed.' Get the approval in writing before you start. No verbal approvals. Luna: Verbal approvals are ghosts. They vanish when it comes time to invoice. Lucas: They vanish. And then you have to chase payment for work you already did. Writing it down first removes the awkwardness later. You are just following the process you agreed to at the start. Luna: It normalizes the extra cost. It becomes just part of the business mechanics. Lucas: It does. And eventually, clients get used to it. They realize that paying for extra scope is fair and expected. It builds a healthier relationship based on transparency. Luna: Transparency over assumptions. That seems like the core shift. Lucas: It is. Assumptions are free, but they cost you dearly. Clarity costs nothing but time upfront, and it pays dividends in retention and margin. Luna: So the takeaway is to quantify the deliverables, exclude the noise, and charge for the deviations. Lucas: Quantify, exclude, and charge. Three steps to stop bleeding hours. It turns your service into a productized offering with clear edges. Luna: I am going to review my current contracts tonight. There are probably three places where I left the door open. Lucas: Do it. And next time a client asks for 'just one more thing,' check your exclusions first. See if you can smile and say, 'Let me send you a quick quote for that.' Luna: That might be the most valuable sentence you've said all week. Lucas: I hope so. Because protecting your time is the only way to protect your business.