overwhelmedfreelancer

Tag: Client Communication

  • 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.

  • What to Do When a Freelance Client Stops Responding

    Silence from a client is frustrating. The real problem is not knowing whether to wait, follow up, pause the work, or walk away.

    Every freelancer eventually gets one of those projects where communication suddenly slows down. A client who replied within an hour now needs three days. Someone who seemed enthusiastic about the project disappears right after receiving a proposal. A nearly finished project gets stuck because the client has not approved the latest version. You send an invoice and hear nothing. At first, you tell yourself they are probably busy. Then you start wondering whether you should message again. Then you worry that another follow-up will make you look pushy. Before long, one unanswered email is taking up far more mental space than it deserves.

    The difficult part is that silence does not give you enough information to make a clean decision. If a client says they want to pause the project, you can plan around that. If they say the work is no longer needed, you can close it. If they ask for another week, you can adjust the timeline. But when there is no reply, everything remains open. You are not working on the project, but you are not really free from it either. You keep a slot in your calendar just in case they suddenly return. You hesitate to take on something else because the project might restart tomorrow. You reopen your inbox more often than necessary because maybe there is finally an answer. The work stops, but the uncertainty does not.

    First: A Slow Reply Is Not Always Ghosting

    It helps to separate genuinely disappearing clients from normal delays. Freelancers often work closely with people who are dealing with internal approvals, travel, unexpected deadlines, budget discussions, sick leave, changing priorities, or simply too many meetings. A reply that takes three days instead of three hours does not automatically mean the client is avoiding you. What feels like an important project from your perspective may be one of twenty things competing for attention on theirs.

    This is especially true when your work depends on larger organisations. The person you are talking to may be completely happy with your work but unable to approve anything because they are waiting for their manager, finance team, legal department, or another stakeholder. You might receive no response because there is genuinely nothing useful they can tell you yet. That does not make the delay less inconvenient, but it changes how you should interpret it.

    The problem starts when communication goes outside the pattern you have already established and there is no explanation. If a client normally replies within a day and suddenly disappears for two weeks, that deserves attention. If your work is blocked, a deadline is approaching, or money is overdue, you cannot simply keep waiting forever. At some point, silence becomes something you need to manage rather than something you hope will resolve itself.

    Do Not Let One Unanswered Message Occupy Your Whole Day

    One of the worst parts of client silence is how much attention it can consume. You send a follow-up in the morning, then check your inbox twenty minutes later. Nothing. You check again after lunch. Still nothing. You start wondering whether the message sounded too direct. Maybe you should send something on Slack instead. Maybe the email went to spam. Maybe they are unhappy with the work. Maybe they hired someone else. None of these thoughts actually move the project forward, but they create the feeling that you should keep monitoring the situation.

    This is where a simple rule helps: once you have sent a clear follow-up, there is nothing else to do until the next follow-up date. Put the next action somewhere reliable and return to your other work. If you decide you will contact the client again on Thursday, checking the inbox seventeen times before Thursday does not improve the situation. It only lets one inactive project consume attention that should belong to active ones.

    Freelancers often think of time management in terms of hours, but attention is equally important. A project can use very little actual time while still creating a huge amount of mental overhead. The goal is to convert uncertainty into a clear next action so that you do not need to keep thinking about it.

    How Long Should You Wait Before Following Up?

    There is no universal number because the right timing depends on the situation. A client who has not replied to a casual question for twenty-four hours probably does not need another message yet. A client who needs to approve something before tomorrow’s launch probably does. The more important question is not simply “how long has it been?” but “what happens if I continue waiting?”

    If the project is not currently blocked, waiting two or three business days before a follow-up is usually reasonable. If you need an answer to continue working, it is completely appropriate to follow up sooner and explain that the project is waiting on their input. If a deadline is at risk, mention the impact clearly rather than sending a vague “just checking in.”

    For example, instead of writing, “Hi, just following up on this,” you can say, “Just checking in on the approval for the homepage. I’ll need confirmation by Wednesday to keep the current Friday delivery date. If I hear back later, we may need to move the timeline.”

    That message does something useful. It explains why the reply matters.

    Clients are much more likely to act when they understand the consequence of not responding.

    Your Follow-Up Should Make the Next Step Easy

    A weak follow-up simply reminds the client that you exist. A good follow-up makes it easy for them to move the project forward.

    If you write, “Any thoughts?”, the client still needs to reopen the project, remember what they were supposed to review, and decide what to say. If they are already busy, that creates more friction.

    Instead, remind them what you need.

    “Could you confirm whether you prefer option A or B?”

    “I’m waiting for the final copy before I can continue.”

    “Please approve the attached version or send your remaining comments.”

    “I need the billing details to issue the invoice.”

    The easier the next action is to understand, the easier it is to respond.

    This is particularly useful when a project contains a lot of context. After several days, the client may genuinely have forgotten where things stopped. A concise summary can save them the effort of reconstructing the whole conversation. You are not nagging them. You are helping them restart the process.

    What to Do When the Client Is Blocking the Project

    There is a point where waiting quietly stops being professional because the lack of response starts affecting the project.

    Imagine you planned to spend Monday and Tuesday finishing a website, but you cannot continue until the client approves the content. If they disappear for a week and then return expecting the original deadline, you may suddenly be forced to rearrange your entire schedule to accommodate a delay you did not create.

    This is why blocked projects need clear boundaries.

    Tell the client that the timeline depends on their response. If the required input does not arrive by a certain date, the delivery date moves accordingly. This should ideally be written into your agreement before the project starts, but you can still communicate it during the project.

    You might say:

    “I’m currently waiting for your feedback before I can move into the next stage. If I receive it by Thursday, we can keep the current timeline. After that, I’ll need to reschedule the remaining work based on availability.”

    This is not a threat. It is basic capacity management.

    Your calendar cannot remain permanently reserved for someone who is not participating in the project.

    Stop Holding Empty Space in Your Schedule Forever

    Freelancers often make a costly mistake when a client disappears: they keep mentally reserving time for the project.

    You think, “They’ll probably reply tomorrow, so I shouldn’t book anything else.”

    Tomorrow becomes next week.

    The project still has not restarted, but you have turned down or delayed other work because you were trying to protect space for a client who was not communicating.

    This is particularly dangerous if you rely on project-based income. A silent client can create a gap in your revenue simply because you treated uncertain work as confirmed work.

    A better approach is to establish a point at which the project loses its reserved place in your schedule. For example, if you are waiting for client materials for more than five business days, you can pause the project. When the client returns, you will schedule the remaining work into the next available slot.

    That creates a fair rule for both sides. The client can take the time they need, but their delay does not require you to stay indefinitely available.

    When to Pause a Freelance Project

    Pausing a project is different from ending it.

    Sometimes the client is not refusing to communicate forever. They are simply not ready to continue. A formal pause gives the situation a status instead of leaving it in limbo.

    You can send a short message explaining that because you have not received the required information, you are pausing the project for now. When they are ready to continue, they can contact you and you will confirm the next available date.

    This is often much better than repeatedly sending follow-ups for weeks.

    It also removes the emotional part of the situation. You are no longer waiting for them. The project has a clear status: paused.

    If they return tomorrow, great.

    If they return in two months, you can decide whether and when you are available.

    What If They Disappear Before the Project Starts?

    Ghosting before a project begins is usually easier to deal with, even if it feels disappointing. You send a proposal. The client sounds interested. You answer their questions. Then nothing happens.

    Do not treat an enthusiastic conversation as booked work until the agreement is signed and whatever deposit you require has been paid.

    This protects you from planning your workload around opportunities that are still uncertain.

    A potential client saying, “This looks great, we should definitely work together,” is not the same as a project starting. Freelancers often get into trouble because they emotionally convert leads into clients too early. They stop prospecting, hold calendar space, or assume the money is coming.

    Until there is a commitment, keep moving.

    You can send one or two follow-ups. If there is still no response, close the opportunity mentally and continue with your business. They may come back later. If they do, you can reopen the conversation.

    You do not need to keep every potential project permanently alive.

    What If the Client Disappears After You Send the Invoice?

    This is where client silence stops being merely annoying and becomes a financial issue.

    If the invoice is not yet due, there may be nothing to worry about. If the payment deadline has passed, treat it as an overdue invoice rather than a communication problem.

    Send a clear payment reminder. Include the invoice number, amount, original due date, and whatever payment details are necessary. Avoid apologetic language. You are not asking for a favour. You are following up on an agreed payment.

    If there is still no response, continue according to the process defined in your contract and local legal framework. That might include additional reminders, late-payment fees where applicable, suspending further work, or escalating collection.

    The important part is to separate the emotional feeling of being ignored from the operational fact that an invoice is overdue. Once money is owed, you should have a process rather than improvising every message based on how uncomfortable you feel.

    Deposits Exist for a Reason

    One of the easiest ways to reduce the financial risk of ghosting is to avoid doing large amounts of work before receiving payment.

    For project-based work, an upfront deposit can protect both sides. The client demonstrates commitment, and you reduce the risk of completing an entire project only to spend the next three months chasing payment.

    Depending on the type and size of the project, you might ask for 30%, 50%, or another agreed amount before starting, with additional payments tied to milestones.

    The exact structure matters less than the principle: do not let your entire compensation depend on someone remaining responsive until the very end of the project.

    Good payment terms cannot prevent someone from disappearing.

    They can make their disappearance considerably less damaging.

    Build Client Delays Into Your Agreements

    If ghosting or delayed feedback has happened more than once, your contract should probably address it.

    You can specify how long the client has to provide feedback, what happens when required materials are delayed, how long you reserve project availability, and when an inactive project is considered paused.

    For example, your terms might state that client delays longer than seven days may require the project to be rescheduled. You might also define what happens if a project remains inactive for thirty days.

    This may seem unnecessarily formal when everything is going well, but contracts are most useful when things stop going well.

    Clear terms also make difficult conversations easier because you are not inventing a boundary in the middle of the problem. You are applying a process that both sides already agreed to.

    Do Not Chase Forever

    There is a difference between professional follow-up and repeatedly trying to revive a relationship that is clearly inactive.

    One follow-up makes sense.

    A second can make sense.

    A final message can make sense.

    Sending “just checking in” every five days for three months usually does not.

    Eventually, you need to close the loop.

    A final message might say that because you have not heard back, you are closing or pausing the project for now. They are welcome to reach out when they are ready to continue, subject to your availability.

    This gives you closure without burning the relationship.

    It also stops the project from remaining permanently present in your mental list of things that are somehow still happening.

    Freelancers need a way to finish inactive work even when the client never explicitly says, “This project is finished.”

    Track Follow-Ups Instead of Remembering Them

    The operational problem behind client ghosting is surprisingly similar to many other freelance frustrations: the important action is often hidden inside communication.

    You send an email and need to remember to follow up in three days.

    You ask for approval and need to check whether it arrived.

    You send an invoice and need to know when it becomes overdue.

    You ask the client for files and the next step cannot happen until they respond.

    These are not normal tasks because you cannot complete them yet. They are open loops.

    If you manage several clients, trying to remember all of those loops manually becomes exhausting.

    A simple waiting or follow-up list can help enormously. Record what you are waiting for, who needs to respond, when you last contacted them, and when you should check again.

    Once it is captured, you do not need to keep the entire situation active in your head.

    This Is Where Freelance Work Becomes Surprisingly Messy

    The difficult part of freelancing is rarely just doing the thing you were hired to do.

    It is everything around the thing.

    The unanswered email.

    The approval that never arrived.

    The document someone needs to review.

    The invoice waiting for payment.

    The client who said they would send something tomorrow.

    The feedback buried inside a message from last Thursday.

    Every project generates dozens of these little dependencies, and most traditional task managers are much better at showing what you need to do than what you are waiting for someone else to do.

    That is exactly where projects start feeling harder to manage than they should.

    You find yourself checking conversations instead of working.

    You remember that someone owes you a response but cannot remember which thread it was in.

    You leave messages unread because they have become reminders.

    You create calendar events just so you do not forget to follow up.

    At some point, managing the communication around the project becomes a second project.

    The Problem Is Not Just That the Client Is Silent

    This is one of the problems we keep coming back to while thinking about Hyzo.

    A client sends something.

    It becomes work.

    You respond.

    Now the next step depends on them.

    That state should be visible.

    If a task is blocked because you are waiting for approval, you should not need to reread the original email to understand why nothing is happening. If you need to follow up on Thursday, that should not depend on you remembering a conversation from Monday. If a project contains several open client requests and dependencies, you should be able to see them without reconstructing the whole history of the project.

    Hyzo is being built around the idea that communication, files, tasks, and project context should not live as completely separate things. The work already exists inside those conversations. The system should help organise what needs to happen next, including the moments when the next move belongs to someone else.

    Because freelancers do not only need help managing tasks.

    They need help managing everything between those tasks.

    Silence Is Easier to Handle When You Have a Process

    Clients will sometimes reply late.

    Some will disappear temporarily.

    A few will disappear permanently.

    You cannot control that.

    What you can control is what happens on your side when communication stops.

    Know when you will follow up.

    Know when the deadline moves.

    Know when a project becomes paused.

    Know how long you reserve space in your schedule.

    Know what happens when an invoice becomes overdue.

    And most importantly, stop letting unresolved client communication live indefinitely in your head.

    A silent client should create a next action, not an endless question.

    Once you have a process, ghosting becomes less personal and much easier to manage.

    You send the message.

    You record the follow-up.

    You protect your schedule.

    And then you keep working.

  • 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.