Balancing Code and Company: The Hidden Costs of Being a Technical Contractor
When people think about contracting, they often focus on the freedom. Choose your clients. Set your rates. Work when and where you want....
When people think about contracting, they often focus on the freedom. Choose your clients. Set your rates. Work when and where you want. But behind that appealing exterior lies a constant tension: balancing the demands of being a hands-on developer with the responsibilities of running a business.
For me, this duality has been one of the hardest parts of the transition to contracting. I still love code. I'm happiest when solving complex architectural problems or refining systems for performance and maintainability. But those moments are regularly interrupted by realities like: Have I raised last month's invoices? Where did I put that receipt? Have I accounted properly for VAT? What if I get audited?
I use FreeAgent to manage my accounts, and it's a solid piece of software. But even the best tools can't replace consistent habits—and that's where I struggle. I'm often chasing paperwork in arrears, trying to piece together expenses, or worrying about whether I've tracked mileage I never claimed.
It's not just finances, either. Representing a business means you're also in charge of marketing, client relationships, risk management, and strategy. Every email carries weight. Every interaction becomes part of your brand. There's no employer to shield you from a client's frustration, and no payroll department to correct a late payment. You are the business.
That can be empowering—but it's also exhausting.
Sometimes, I find myself wishing for the simplicity of a salaried role. One where I could focus purely on the technical, without the overhead of entrepreneurship. But then I remember why I chose this path. Because when it works, it's immensely rewarding. I get to build, lead, and shape the kind of projects I care about. I can advocate for better standards and see the impact of my work directly.
The key is finding ways to protect your developer self from being drowned out by your business self. For me, that means clearer boundaries between working on projects and working on SoftWeb. It means carving out time for reflection, learning, and creativity—not just chasing deliverables or reconciling bank feeds.
Being a technical contractor isn't just about writing code. It's about holding the tension between craft and commerce. And if you can get that balance right, the rewards go far beyond the day rate.