Freelance DevOps work pays for results, not for hours spent looking busy. Yet most independents fill their weeks with things nobody pays for: unpaid discovery calls, endless proposal rewrites, forums, group chats and learning plans that never end. This FAQ answers the questions freelancers ask most about turning down work and noise. The short version is that a written list of what you refuse is cheap, and it protects the billable hours that keep the business alive.
What does it mean to have a “not doing” list as a freelancer?
It is a page, kept where you can see it, that names the jobs, requests and inputs you decline. It covers three areas: client work you will not take, admin and communication habits you will not keep, and learning or reading you will not pursue this season. No tool needed. A text file works.
Why does a freelancer need one more than an employee?
Because nobody else is filtering for you. An employee has a manager who, at least in theory, decides priorities. A freelancer is the sales team, the delivery team and the accounts department at once, and every inbound message looks like income. Without a rule set, you will reply to everything and finish less.
Which client requests should I refuse?
The common ones:
- Free “quick audits” that are really unpaid consulting.
- Projects with no clear contact who can approve work.
- Jobs where the stated goal is vague and the budget is fixed anyway.
- Requests to be on call around the clock at part-time rates.
- Work in a stack you have no wish to maintain, even if it pays well once.
You do not need to justify each refusal in detail. A short, polite message is enough: “Not a fit for me right now. Good luck with it.” Anything longer invites negotiation.
How do I say no without losing the relationship?
Keep it brief, kind and specific about what you do instead. Offering a referral to someone who is a better fit often leaves a stronger impression than a reluctant yes would. Clients remember a freelancer who was honest about limits, and they come back when the next suitable job appears. If you are new and worried about turning anything away, the beginner’s answers in a starter set of questions and answers for people entering freelance DevOps cover the confidence side of the problem.
What about meetings and calls?
Set a rule on duration and purpose. Many freelancers will not take a call without a short written agenda, and will not attend recurring meetings unless the client pays for the time. Some decline “sync” calls that could be a paragraph in a ticket. Decide your stance once and apply it uniformly; ad hoc exceptions are how weeks vanish.
Should I ignore messages from other freelancers and communities?
Mostly yes, with a caveat. Communities can bring work, advice and warnings about bad clients. They can also swallow whole afternoons in debates about tools. Choose one or two places that give you something concrete, mute the rest, and check them on a schedule. A practical way to think about that value is covered in the discussion on building a dependable network of peers and mentors as an independent. The point is a small, useful circle, not a large noisy one.
Is it okay to skip the latest tools and certifications?
Yes. Clients rarely pay extra for a badge in a product you do not use on their account. The sensible approach is to learn a tool when a signed or probable project needs it. Until then, “I do not do that” is a perfectly professional answer, and it lets you present a narrower, more credible offer.
Be aware, though, that some topics keep resurfacing in client briefs. If three different clients ask about the same thing in a quarter, that is evidence, and the skip item can move to your learning list.
What if I am freelancing while holding a full-time job?
The need for boundaries doubles. Your list should include working hours you will not touch, clients in your employer’s space whom you will not approach, and any task that might create a conflict. If this is your situation, the guidance on running a side practice responsibly next to a day job is worth reading in full. Put your own employer’s rules at the top of the page, because they set the limits everything else must respect.
How many items should the list have?
Between five and ten. Shorter lists get forgotten; longer ones become to-do lists in disguise. Write each item as a plain sentence starting with “I will not”. Example: “I will not start work before a written scope and a deposit.” Clear wording means you can apply a rule in seconds when a tempting message arrives.
Does this apply outside of work?
Yes, in a small way. Freelancers constantly buy laptops, monitors, headsets and software, and review reading can eat hours. Review blogs such as True Review Now, where buyers of gadgets, software and local services go to read opinions are handy, but decide first which features and opinions are irrelevant to your needs and skim past them.
How often should I review the list?
Monthly is enough. Look at what you declined, what you regretted declining, and what you accepted but wish you had refused. Adjust the page, keep it honest, and keep the exceptions few. A good test of the list is the invoice total at month end: if you protected billable time, income follows.
What is the first step today?
Open a blank file and write three lines: one client type you will refuse, one meeting habit you will drop, one input you will mute. Put the file somewhere you will see daily. That is the whole setup. Everything after that is just saying the sentences out loud when it counts.
