Perhaps you don't need another developer at this time. I find that operating at n-1 developers forces a team to really consider what the most important feature

Perhaps you don't need another developer at this time. I find that operating at n-1 developers forces a team to really consider what the most important features are. As a developer, it's really easy for me to start thinking of really cool features, and if only I had another programmer or two on my team, I could do those features. But those are usually the superfluous features. Joel Spolsky makes the same point in one of his posts on Joel on Software, although he uses a schedule as the limiting factor instead of number of programmers. (Skip to item 13: http://www.joelonsoftware.com/articles/fog0000000245.html http://www.joelonsoftware.com/articles/fog0000000245.html). I'm saying this because based on the first sentence of your post, it sounds like these projects in the pipeline aren't mission-critical. Of course I could be wrong. You know your business better than I do.