There is a moment most freelancers remember. It is mid-afternoon, a client has sent a vague request, three browser tabs hold half-finished proposals, a pipeline is waiting for a decision about which runner to use, and you realise you have not yet done any actual engineering. Nothing dramatic has gone wrong. You have simply spent the day choosing: which client to answer first, which tool to reach for, how to phrase a quote, whether to say yes to a side request. By evening you are tired in a way that has little to do with hours worked.
That tiredness has a name that many solo DevOps freelancers learn the hard way: decision fatigue. Working alone means every decision lands on one person, and there is no colleague to say “we always do it this way”. The good news is that you can build that colleague yourself, in the form of a short set of standing choices. What follows is a sequence of seven moves, told through the kind of situations a freelancer meets in a normal week.
Step one: notice where your day leaks
Take one ordinary week and keep a small note beside your keyboard. Each time you pause to choose something that you have chosen before, make a tick. You are not judging yourself, only collecting evidence. Typical ticks include picking a repository layout for a new client, deciding which monitoring stack to propose, choosing how to word the first reply to an enquiry, and deciding when to stop for the day.
By Friday the ticks will cluster. For one freelancer I know of, nearly half the ticks were about the same three things: how to start a new project, how to answer a new enquiry and what to charge for small jobs. Those clusters are where a standing choice pays off first.
Step two: write a short service menu
Open-ended offers sound flexible, but they hand every prospective client a blank page and hand you a custom quote each time. A short menu is kinder to both sides. Think of two or three clearly described ways you usually help, such as a pipeline set-up engagement, a review of an existing deployment process and a small recurring support arrangement. Describe each plainly, including what falls outside it.
You still stay free to do unusual work when it feels right, but the menu becomes your default conversation. When someone asks “what do you do?”, you no longer improvise. When someone asks for a quote, you start from a known shape and adjust, instead of building from nothing. For more on the early practicalities of working this way, an introductory set of answers for people just starting out as DevOps freelancers is a friendly companion read.
Step three: fix your technical defaults
Now turn to the tools. Every freelancer has a drawer of favourites, and the temptation is to choose afresh each time. Instead, write down the defaults you will reach for unless a client’s environment dictates otherwise. A simple version might cover your preferred infrastructure-as-code approach, your standard continuous integration layout, your usual way of managing secrets handover and your documentation template.
The story of a freelancer I will call “the contractor” illustrates the benefit. Early on, the contractor treated every engagement as an excuse to try a new combination of tools. It was exciting for a while, and then a minor outage at a client’s site arrived on a day when the contractor could not remember how that particular setup had been wired. Afterwards the contractor wrote a one-page list of defaults and committed to it for new projects. Not every client wanted those defaults, but the ones who did got work that was faster to deliver and easier to hand back.
Step four: set a standard working rhythm
Freelancers often skip this because freedom over hours is a major attraction of the lifestyle. Yet a loose schedule produces constant micro-decisions about when to start, when to check messages and when to stop. A light structure removes many of them. Choose a small set of fixed windows: one for deep technical work, one for client messages, one for admin and invoicing. Keep them roughly the same each day.
You do not need to be rigid. If a client incident requires you to rearrange everything, you will. The rhythm simply gives you a default to return to afterwards. If you also hold a full-time job and freelance on the side, a fixed pattern matters even more, a subject explored in a piece on balancing freelance work with a day job.
Step five: make a short list of standing answers
Many freelance decisions are really repeated questions: Do I take this small request outside scope? Do I accept a call at short notice? Will I take on another client this month? Rather than answering from scratch while a client waits, write a few standing answers that fit your situation. They might read like this:
- Requests outside the agreed scope get a short written quote before any work starts.
- Calls are booked in the messaging window, not accepted on the spot.
- New engagements begin only when the current ones have a clear next step.
- Invoices go out on the same day each week.
These are your own rules, and you can change them whenever the situation calls for it. Their job is to save you from reopening the debate each time.
Step six: build a tiny routine for the people side of work
Even a one-person business has calendars to manage: your own days off, planned travel, the dates a client’s team is away. Think of how a small company manages the same thing. The website Inoroff describes a leave and attendance platform for smaller teams, with requests, manager approvals and work schedules held in one place. A freelancer does not need software for that, but the idea carries over neatly: decide in advance how you record time off and how clients learn about it, and the question stops nagging you.
Step seven: try it for a month and adjust
Run the new setup for a month before you judge it. In the first week it will feel odd, and you may feel boxed in. By the third week you may notice that your afternoons feel lighter and that proposals go out sooner. Keep a short note of what changed and what chafed.
At the end of the month, sit down for half an hour and edit the lists. Delete anything you never used, and add a line for the situations that caught you off guard. Resist the urge to expand the menu dramatically. The value comes from its brevity.
A few things that can go wrong
Over-engineering is the first trap. Some freelancers spend a week designing a perfect set of standards and a weekend producing documents nobody reads. Keep the lists to a page. A second trap is treating defaults as commandments: when a client has a good reason to deviate, deviate, and note the reason. A third is leaving out the exits. A freelancer who has no way to say “this client is a special case” will eventually abandon the whole system in frustration.
Finally, remember that limiting choices is not the same as limiting ambition. You can still learn new tools, try new kinds of work and grow. The difference is that you do it on purpose, on a day you set aside, rather than letting every new option compete for attention at once.
What a calmer week can look like
Picture the same freelancer from the opening, a few weeks after making these changes. A new enquiry arrives; the reply starts from a template and goes out within the messaging window. A new project begins with the standard layout, so the first commit happens within the hour. At midday there is a short, planned break, and at the end of the afternoon the invoicing window opens as it does every week. Nothing about the work has become easier in a technical sense, yet the day feels shaped rather than scattered, and the tiredness at the end of it comes from engineering, not from endless choosing.
That is the real promise of the approach. You are not squeezing more hours out of yourself. You are giving the hours you already have a calmer structure, so the good thinking arrives where clients need it. Start with one page, one week of ticks and one short menu, and let the rest follow.