Good advice guys!
CaRDiaK: it is a fun place to work. The whole small startup thing is fun, and we're working on unusual and interesting stuff. Your point about project management is spot on: we're trying some things but are having difficulty finding something that really works. I'll definitely take a look at that book, Code Complete is still a favorite of mine so I'm interested in what he has to say on this subject.
MasterPi: I guess the guy who is part manager/part designer/part developer owns all the project and does the sort of things you mention. However, he is also the guys who asked me to come up with a process that'll work better for us. :P
Michael Butler: I'll take a look at your suggestion too. I currently see it used on Amazon for $4 so that won't hurt.
Harlock123new: I like the idea that many simultaneous projects are unavoidable for now and as such we should plan for that. That should at least go some way towards more accurate time estimates...
TexasToast: there are no bigger companies than us in this field. We have a few competitors that compete on price but we are able to provide better applications and expertise. So far, anyway...
davewill: I'll mention the need to unit test core stuff. I like that idea. My biggest fear when it comes to unit testing is having to constantly rewrite the tests for our viewmodels because the requirements change sometimes on a weekly basis. I'm not sold on the code reviews myself, but we do have the situation where one guy may fall ill or go on holiday and then "his" project goes haywire and the other two have to spend a lot of time figuring out that guy's code. I guess I figured code reviews could help prevent that, as well as improve the quality of the code we all write when there's always someone else watching too, but I'm starting to feel like it would soon become a chore and either suck up time or fall by the wayside. There are no real communication issues, but things are so busy that everybody usually just dives in to their own project/area (there's a "web guy", a "XAML guy", a "multitouch guy", a "Unity3D guy", etc) and the others never see or hear about the code, either because it's not their field of expertise or because they already have so little time to spare for their own stuff.
spivonious: we looked into scrumm but didn't feel like it would fit: we can't meet (either in person or via skype) with our clients as often as scumm requires, for instance. We've picked up a few small things from a scrumm course, though: we're succesfully using a Definition of Done and have a daily standup with the entire company (five people who each have three minutes to get the rest up to speed on what they are doing), which helps.