I'm getting bored with my current Linux administration job and am considering starting a solo consulting practice, initially as a way to supplement my income. I'd like to hear from people who have successfully gone independent. How did you find your first clients, package and price your services, and decide what to offer? What technical and business skills are essential at the beginning? Should an admin build experience in areas such as cloud, containers, infrastructure as code, automation, security, or DevOps before trying to sell consulting services? I currently have some cloud and scripting experience, including Ansible, and have been learning infrastructure as code and containerization independently, but I don't yet have professional experience with those tools.
5 Answers
A good differentiator is a skill combination that solves a problem ordinary administrators usually don’t handle. Examples include industrial or embedded Linux, security and compliance, high-performance troubleshooting, specialized networking, cloud cost reduction, or automating a repetitive operational process. Simply knowing how to manage services and terminate processes usually won’t justify a consulting rate. You need a clear answer to “what problem do you solve, and why should the client hire you instead of an employee or generalist contractor?”
If possible, start on the side and keep the day job until the business has traction. One consultant’s experience was that it took roughly a year and a half to become stable and several more years to catch up financially with salaried peers. That timeline varies, but it shows why a financial cushion and supportive personal situation matter. Also check the legal, tax, insurance, and contracting requirements where you live before accepting work. Consulting can be a good fit, but being excellent technically does not automatically mean being prepared to run a small business.
“Linux administration” by itself is probably too broad and too easy for clients to treat as a commodity. The stronger consulting opportunities are usually tied to a specific business problem: cloud migrations, automation, infrastructure as code, container platforms, CI/CD, security hardening, reliability, or troubleshooting unusual production issues. Ansible is a useful start, but you’ll be more competitive if you can demonstrate practical experience with tools such as Terraform, containers, and cloud platforms. The key is being able to explain the value and outcome, not just list technologies.
The technical work is only part of running a consultancy. A surprising amount of time goes into sales, proposals, meetings, contracts, invoicing, taxes, insurance, scheduling, and explaining technical decisions to clients. You also need a plan for what happens if you are sick or unavailable. Clients may be reluctant to depend on one person unless you offer a very specific expertise or have a backup arrangement. Health coverage and the loss of employer benefits can also make the transition much more expensive than expected.
The most realistic way to start is through people who already know your work: former coworkers, employers, vendors, and local businesses. Small projects and referrals can turn into a longer contract. Freelance marketplaces may help you get initial work, but they often push rates down and make you compete like a commodity. Before leaving your job, try to build enough recurring work that the consulting income is becoming reliable. A single large client can be useful, but having several smaller clients protects you if one disappears.
At the moment I don’t have any potential clients lined up, so building a network and finding a specific service to offer would need to come first.
The role has also expanded toward platform engineering, SRE, and cloud operations. Traditional Linux administration still exists, but many current opportunities expect automation, cloud, containers, and software-delivery experience alongside Linux.