Edit: just looked at your blog - my system mails checks and takes just a little of that back every month :-)
The immediate problem is not lack of money but lack of staff. Taking VC means turning up the heat on the lack of staff problem, and more money does not identify the right technical candidate, and in my mind at least, you really need a technical candidate who is partner grade and partner committed. Someone without the commitment can leave behind perfectly good code in an environment where those who remain were not close enough to its creation to quickly make sound modifications...imagining what a person without technical chops can leave behind in the code base is left as an exercise for the reader.
[Glad you enjoyed the blog.]
I recruited and retained several top level devs in my 10 years prior to going it alone. I'm not too worried about that bit. But thanks for making me think about what worked well in the process back then.
Anyway, I was in the parking lot about an hour ago and thought the right developer might come in already knowing angels, vc's or 3F's.
The last seven years is sunk cost and the only effect it can have on the future of the company besides providing a knowledge base is psychological drag. And bringing in a partner with large equity is exactly what taking VC is anyway..except that VC will make decisions based upon distribution of risk while a 5050 partner will have a similar concentration of risk to yours.
Overcoming the sunk cost mindset is tough. Just giving someone half a company you spent seven years building sounds crazy. But the seven years you spent getting to this point are irrelevant to VC decision-making. All that matters is going forward. Any different orientation on your part creates an impedence of expectations.
Good luck.