This question has been asked plenty of times before. Look up variations of "business/idea guy needs hacker." But you should at least hack a bit with Ruby on Rails so at the least you won't piss off your technical co-founder. If you have deep domain knowledge, significant contacts, and a problem that is worth solving, then getting a hacker co-founder should be pretty straight forward.
It is my personal belief that the team composition depends on the type of opportunity and where the core competitive advantage will come from. If you are a lawyer, and you want to make a paperless solution for legal firms, you better believe you'll need a technology wiz. However, if the technology component is honestly only a small part of the overall problem, then you can perhaps look to getting an employee or contract out the tech work.