I'll throw in my 2 cents as typical HN 'suit'. For background, I do have a technical co-founder and am working on something currently and we've been working together over a year and are on our second project.
First, I think the OP's response was perfectly acceptable. Its important as a technical co-founder to determine quickly what the "suit" can bring to the table although I do think he left out some valuable skills like marketing, user adoption, team building. He did include 'industry experience' which is critical. (edit: I also recall my co-founder then asking me situational questions like how I would market x app, who would use it, pricing, etc to see if I've thought through the process)
Second, one aspect that I see missing often is chemistry. Over the last few years I've attempted multiple projects with several different people and I can't stress how important chemistry is with your co-founder and/or team. I actually really enjoy hanging out with my co-founder and consider him a friend and we regularly hang out (with each other's families) and that kind of trust carries over to our work. Trust is something you can't quantify so for those in search of co-founders, don't just look at credentials but look at the person too.
My last thought is that although you're a 'suit' like I am, you need to make an effort. There is a general curve that says in the idea phase the majority of the workload is done by the technical co-founder. While true, I do my best to try and offset that. It gives me no joy to sit on my ass while my buddy is coding to 3am every night. How would it make you feel if you're busting your ass pitching, getting customers, and doing cust dev while they are at happy hour? So to respond to this I do my best. I've picked up basic design skills (PS/AI/FW), I've gotten his help to install ruby and learn basic HTML/CSS so I can make easy changes. I alternate every few days from doing something design centric, customer oriented (get feedback/lead gen), to thinking about our product direction.
So my take aways are: ask questions, figure out if you can work together, and make sure everyone is willing to put in the work to make it happen.