Fixing is good
Aside from the IR35 implications, being called back to deal with stuff is good for smoothing out cashflow.
No rational client wants an seriously unhappy contractor messing with source code or important system configs, so it is better for all that this is done in a friendly way. (yes I know not all clients are rational).
A bit of bug fixing can often be turned into maintenance contracts, you coming in every few months to kick or patch something, this increases your protection against IR35 since you're clearly doing work for multiple clients.
When I quit my last job as a CIO I left the contractors doing kicking and patching on a N days per year basis. That was in 2005, they've each had about a year's work that they slotted into gaps and it is the gaps between contracts that decide whether contracting is better or worse paid than permiehood.
Aside from the IR35 implications, being called back to deal with stuff is good for smoothing out cashflow.
No rational client wants an seriously unhappy contractor messing with source code or important system configs, so it is better for all that this is done in a friendly way. (yes I know not all clients are rational).
A bit of bug fixing can often be turned into maintenance contracts, you coming in every few months to kick or patch something, this increases your protection against IR35 since you're clearly doing work for multiple clients.
When I quit my last job as a CIO I left the contractors doing kicking and patching on a N days per year basis. That was in 2005, they've each had about a year's work that they slotted into gaps and it is the gaps between contracts that decide whether contracting is better or worse paid than permiehood.
Comment