2 ms·
I've had a one-person technical consultancy for about a decade (with a year off in the middle, for a university research appointment, and an early stint helping
by neilv 8y ago
I've had a one-person technical consultancy for about a decade (with a year off in the middle, for a university research appointment, and an early stint helping out another niche expert firm). I'm looking forward to moving back to an employment/startup role, in which I can spend most of my time building good technical systems, rather than spending half my time on small business administration overhead for what's essentially only an individual contributor role (sales, compliances, accounting, learning enough about IRA/401(k) to create a plan, etc.).
Like in any line of work, there are way too many little bits of acquired wisdom to rattle off-the-cuff in an HN comment, so just a couple that first come to mind...
I've ended up always billing hourly, tracked in 15-minute increments. The hourly rate sounds high, but when I looked at the value I provided to a client over a year, and compared to a TCO of an employee who could've provided comparable value, it seemed that the client got a really good deal. Maybe too good; when it's remote work, I err on the side of avoiding slippery slopes about hours (e.g., clock doesn't start until I'm fully awake and exercised and typing on the computer on the problem; don't bill anything for a morning walk when I spent most of the time thinking about the problem). On-site, I'd bill all time, except for things like lunch and other significant breaks (e.g., non-work-related watercooler conversation beyond exchanging pleasantries).
One thing that comes to mind at the moment is that, if you initially find a client due to expertise in some niche (e.g., you're known in a language or open source community for a particular piece of stack that client uses), that might turn out to be only a small part of the expertise that you apply. For my favorite client, I was immediately applying other background I didn't expect, and I ended up becoming the go-to person on many topics, including things I learned on-demand. (I already believed in hiring people who could quickly pick up whatever flavor-of-the-month bit of stack was needed at any time, but this experience reinforced my opinion that this could also apply to more limited consulting arrangements. With consulting, you probably need an expertise in something foot in the door, though.)
Most things I think to mention here only apply to a minority of consultants, or are widely applicable to many kind of development roles.
Regarding multi-person consultancies... I'm glad that I didn't start hiring additional consultants or forming a partnership, because I'd foresee spending even more time on business administration, plus have the stress of other people's livelihoods dependent on my relatively neophyte business skills. I'm much more confident in my engineering skills. (Of course there are a few organizational/leadership things I'd like to try, as I think many of us would based on our experience in the engineering trenches, but am willing to give that up if someone else will make all the money and bureaucratic stuff just happen, so that I can focus on engineering things.) But if you want to move to the business side, that can work.