From Developer to Business: My Transition to Contracting and the Lessons Learned

Shifting from permanent employment to contracting was never part of a grand plan. It began with a conversation with a recruiter, and before I knew it, I was stepping into a new world—one that would challenge me in ways I hadn’t anticipated.

When you're employed, your focus is often technical: solving problems, delivering features, collaborating with a team. But as a contractor, that focus expands. Suddenly, you're not just a developer; you're a business. You're responsible for marketing yourself, managing finances, keeping records, negotiating contracts, and preparing for audits—all while staying technically sharp.

Initially, I found this shift daunting. Financial management became a particularly stressful area. While tools like FreeAgent helped, I constantly found myself behind on invoices, forgetting to keep receipts, and worrying about compliance. I also took on the burden of trying to run everything flawlessly, which was neither sustainable nor necessary. There are no expense claims or mileage logs in my world—not because I don't incur costs, but because I simply haven't built those habits. It's an area I know I need to improve.

But the biggest change was in mindset. Contracting forced me to recognise that I was no longer just a developer on someone else's payroll. I was representing my own company, SoftWeb. Every engagement, every deliverable, every meeting was now a reflection of my brand. It’s a powerful, sometimes intimidating, lens to work under.

What surprised me most, however, was how much I enjoyed the autonomy. The freedom to choose engagements, the ability to shape my own trajectory, the direct relationships with clients—these were things I hadn't truly appreciated until I had them. Of course, this independence comes with risk. When the market slows or a project ends unexpectedly, the impact is personal and immediate.

Over time, I've learned to balance that risk with proactive planning. I maintain a short-term buffer and keep a close eye on my obligations. I’ve embraced blogging and LinkedIn to build visibility. And I’ve become more thoughtful about the kinds of engagements I accept, weighing not just the rate, but the environment, expectations, and cultural fit.

This journey from developer to business has been far from easy. But it’s also been one of the most rewarding phases of my career. It’s forced growth, sparked reflection, and ultimately, made me a better engineer and leader. I’m not just writing code anymore. I’m building a legacy.