overwhelmedfreelancer

Tag: Project Management

  • Why September Feels Like January for Freelancers

    September is the unofficial second New Year of freelance work – clients come back, projects restart, deadlines suddenly get closer, and the calm systems that worked during summer begin to fall apart.

    September has a strange energy when you work for yourself. Summer is ending, clients are coming back from holidays, projects that were casually postponed until “after August” suddenly become urgent again, and conversations that went quiet a few weeks ago restart as if no time has passed at all. A brief you received in June comes back with new comments. A client who disappeared for three weeks suddenly wants to move quickly. Another company starts planning Q4 and asks whether you have availability. None of these things are unusual on their own, but when they happen at the same time, September can feel surprisingly similar to January: a fresh start mixed with the uncomfortable realisation that there is already far too much to organise.

    That is why September often feels like a second New Year for freelancers. January comes with resolutions, new plans and the urge to finally become more organised. September creates almost exactly the same reaction, except this time you are rarely starting with a clean slate. There are unfinished projects from before the summer, old client conversations that suddenly become relevant again, invoices to follow up on, documents that need updating, new enquiries arriving at the same time and deadlines that felt distant in July but are now only a few weeks away. The instinct is often to reorganise everything: clean up the task manager, rebuild the Notion workspace, create a better calendar system or promise yourself that this time you will finally keep every project perfectly under control.

    The problem is that freelance work rarely arrives in a perfectly organised form. Clients do not usually return from holiday with a neat list of tasks ready to be copied into your project management system. Work comes in fragments. One request arrives by email. Feedback appears in a Google Doc. Someone mentions a deadline during a meeting. Another client sends you three WhatsApp messages and ends the conversation with “one more small thing”. A new file arrives without much explanation, while an important decision is hidden halfway through a Slack thread from two weeks ago. Before you can actually start designing, writing, coding, editing or consulting, you often have to reconstruct what the work is supposed to be in the first place.

    This is one of the most underestimated parts of freelance work. A surprising amount of time is spent not doing the work itself, but preparing yourself to do it. You look for the latest version of a file, reread an email to make sure you understood the request correctly, search a conversation for the date someone mentioned, check whether you already replied to something, and try to remember whether a new request belongs to the existing scope or should become a separate task. Every individual action seems insignificant, which is exactly why it is easy to ignore how much time they consume. Ten minutes looking for information here, five minutes checking an old thread there, another few minutes switching between tools — and suddenly a large part of the day has disappeared into work that nobody really thinks of as work.

    September makes this problem much more visible because the number of active projects and conversations tends to increase at the same time. During a slower August, an imperfect system might work perfectly well. You remember most things because there are only a few of them. You can keep a couple of deadlines in your head, check your inbox from time to time and rely on memory to tell you what should happen next. Once several clients become active again, that same approach starts to break. The information has not suddenly become more complicated, but there is simply more of it. More emails, more messages, more files, more decisions and more small requests competing for your attention.

    This is usually the moment when people start searching for a better productivity system. They install another task manager, download a new template, restructure their folders or create an ambitious colour-coded calendar. For a few days, it feels like everything is finally under control. Then another client sends an important request somewhere outside that system, and the cycle starts again. The problem is not necessarily that freelancers lack tools for managing tasks. There are already hundreds of tools for managing tasks. The bigger problem is that freelance work usually begins before something becomes a task at all.

    Most productivity advice starts with a very convenient assumption: you already know what you need to do. Write the task down. Give it a priority. Add a deadline. Put it into a project. Schedule time to complete it. That advice works once the task exists, but client communication often arrives one step earlier. A message like “Could we use the second version, update the pricing, change the headline and maybe prepare something for mobile before Thursday?” is not a task. It is several potential tasks hidden inside a sentence. Someone has to notice them, understand them, decide what they mean and translate the conversation into actual work before any productivity method can help.

    That translation layer becomes particularly exhausting when you are managing several clients simultaneously. You are constantly moving between communication and execution: reading, interpreting, remembering, organising, doing, checking and then going back to communication again. The result is not always obvious chaos. Sometimes everything still gets delivered on time. But the mental cost can be significant because your brain becomes the place where all those disconnected pieces have to come together. You are effectively acting as your own project manager while also trying to do the specialist work clients hired you for.

    A useful September reset, therefore, might not begin with a new productivity system at all. Instead, spend a week noticing where your work actually starts. Look at every new task that appears and ask where it came from. Was it an email? A WhatsApp message? A client call? A comment in a document? A Slack thread? A voice note? A meeting? A random message sent while you were already focused on something else? Once you start paying attention, you may realise that the problem is not your ability to prioritise. The problem is that your workload is being assembled continuously from many different places.

    And when work is fragmented, attention tends to become fragmented as well. Every time you leave what you are doing to find a message, check a deadline, locate an attachment or remind yourself what a client meant, there is a small cost. Individually, those interruptions feel harmless. Repeated dozens of times across a week, they can become one of the biggest sources of frustration in freelance work. The goal should not necessarily be to squeeze more tasks into every day. It might be to remove some of the unnecessary friction that happens before the real work can even begin.

    That is why September does not have to become another month of productivity resolutions. You probably do not need a completely new version of yourself, a stricter morning routine or another complicated system that you will abandon by October. You may simply need fewer things to remember, fewer places to check and fewer moments when you stop what you are doing because you are trying to reconstruct what someone asked for three days ago.

    Because a calm workload does not mean having nothing to do. It means knowing what needs your attention, where the information is and what should happen next. And as clients return, projects restart and the busiest part of the year begins, that might be a much more useful September goal than trying to become more productive.

  • The Client Who Asked for “One Tiny Change” and Accidentally Ordered a New Website

    How One “Tiny Change” Turned Into an Entirely New Project

    A friend of mine once told me a story that should probably be included in every freelancer onboarding course, somewhere between “always get a deposit” and “never trust a client who says this will only take five minutes.” He was designing a fairly simple website for a small company. Nothing especially complicated: a homepage, a few service pages, a contact form, some basic responsive work. The scope was clear, the deadline was reasonable, and the client seemed unusually easy to work with. The homepage was approved quickly, the general direction was accepted, and for a brief, beautiful moment there were no seventeen-person email chains discussing whether the button should be blue or slightly bluer, no founder’s cousin suddenly joining the project because they had “some UX experience,” and no mysterious stakeholder appearing two days before launch with a completely new vision.

    Everything was going suspiciously well.

    Then came the message: “Looks great. Just one tiny change.”

    Every freelancer reading this already knows that this sentence should have triggered some kind of emergency siren, but at the time my friend did what most of us have probably done more than once. The client wanted one additional section on the homepage. It really did seem small, so he added it without making a big deal out of it. The next morning another message arrived. Since they were already adding that section, could it maybe include a few testimonials? Sure, that made sense. And since the testimonials were there, perhaps each one could link to a separate case study so potential customers could see the work in more detail? That also sounded reasonable. And if they were creating case studies anyway, perhaps there should be a dedicated page where visitors could browse all of them?

    At this point, the tiny homepage change had developed its own navigation item, but the project was still growing.

    The client then realised that the case studies would be much more useful if visitors could filter them by industry. Once those industries existed, it suddenly seemed logical to reorganise the service pages around them too. And once the services had been reorganised, the original navigation no longer felt quite right. Maybe that needed another look. Perhaps the homepage messaging should also change slightly to reflect the new structure. And if the homepage copy was changing, perhaps the hero could be redesigned as well. None of these requests was outrageous on its own. In fact, most of them were perfectly sensible product decisions. That was exactly what made the situation so difficult to notice while it was happening.

    Two weeks later, my friend was sitting in front of a Figma file containing roughly twice as many screens as the project he had originally agreed to design. The most interesting part was that the client was still perfectly happy. There had been no argument, no uncomfortable negotiation, no evil client deliberately trying to squeeze free labour out of a freelancer. Nobody had ever said, “Could you redesign half of our website for free?” The project had simply expanded one perfectly reasonable request at a time, and because every request felt small in isolation, nobody had stopped to acknowledge that together they had become an entirely different piece of work.

    Eventually, my friend sent the client a message explaining that they had moved considerably beyond the original scope and that the additional work would need to be estimated separately. The client’s reply was simple: “Oh. I thought all of this was included.”

    And that was the real lesson.

    The problem wasn’t necessarily the client. It wasn’t even the fact that new requests had appeared. Projects change, people have new ideas, and good work often creates more ideas. The problem was that nobody had clearly marked the moment when the original project ended and additional work began. Every time my friend replied with “sure,” “no problem,” or “I’ll add it,” he was quietly changing the rules of the relationship without realising it. From the client’s perspective, everything was working exactly as expected: they asked for something, he agreed, and the work appeared. There was no obvious reason for them to assume that the fifth extra request was fundamentally different from the first one.

    In other words, he had accidentally trained the client to believe that new ideas were free.

    This is one of the stranger things about freelancing. Boundaries rarely disappear in one dramatic moment. There is usually no cinematic scene where a client announces that they intend to consume every remaining hour of your week. Instead, boundaries disappear five minutes at a time. A quick revision here. A small call there. One additional version. A tiny favour because the launch is tomorrow. “Can you also…” “While you’re in there…” “It should be quick.” None of these requests seems important enough to stop everything and start a formal negotiation, which is precisely why they can quietly turn a profitable project into something completely different.

    My friend eventually worked it out with the client. They agreed that the additional functionality should become a second phase, created a new estimate, and continued working together. There was no dramatic breakup and no angry invoice dispute. But after that project he permanently changed one sentence in his vocabulary. Whenever a client asked for something outside the agreed scope, instead of simply saying, “Sure,” he started saying, “Sure – I can add that. Let me check how it affects the scope and I’ll send you an estimate.”

    Almost the same level of friendliness. Completely different business.

    The Moral

    Clients do not always create scope creep. Sometimes freelancers create it by making additional work look invisible. If every new request immediately becomes another item on your private mental to-do list, the client has no way of knowing that the project is expanding. From their perspective, they are simply continuing the conversation. Your job is not to reject every new idea or turn every small request into an awkward commercial discussion. Your job is to make the consequences of those ideas visible before they quietly become another week of unpaid work.

    Because the most dangerous sentence in freelancing is rarely: “I’m not paying for this.”

    Much more often, it is:

    “Oh. I thought that was included.”

    And now I’m curious: what is the best, strangest, funniest, or most painfully familiar freelance story you’ve ever experienced? Maybe it was a “quick call” that consumed an afternoon, a tiny revision that became an entirely new project, a client who disappeared for three months and then returned with an urgent deadline, or something so absurd nobody would believe it unless they had worked freelance themselves.

    –

    Send me your stories. The best ones might become the next post here — anonymously, of course, unless you want the credit.