Find a co-founder who likes your ideas and trusts you'll get up to speed on whatever bits of the equation he/she doesn't want to handle. In a startup past the very earliest "get-to-prototype" stages there's a roughly even split between the sucky non-tech stuff and the actual development...you could take the non-tech stuff and leave the hacking to your co-founder. I'm quite technical and have developed a lot of software in the past ten years, but I found an even better developer and took on the sucky stuff while leaving him to handle most of the development. It's working very well (though I often find myself wanting to get back to real "work" when I'm doing the boring accounting/marketing/taxes/funding/support/etc. stuff--I have to remind myself that if we reach our goals I'll be able to hack anytime I want, in between rides on my robotic dinosaur, of course).
There're two possible questions in the title, and I'm not sure which one you mean. Are you asking how a non-hacker can start a tech startup, specifically one focusing on the web? Or are you asking how a non-hacker can start any startup, be it biotech, finance, auto-body, housepainting, or some other industry entirely?
For the first question, you really either need to be a hacker yourself or convince a top-notch hacker to work for you. You can't expect to start a successful tech startup if you don't have good tech. I listed some ways that entrepreneurs repel potential tech cofounders here - http://news.ycombinator.com/comments?id=13000 - and also suggest some things you might bring to the table that might convince a techie to work with you.
If you're just looking to start any startup and don't care about the field, the rule is always "Concentrate on your strengths." Basically, you want to go into business being more passionate about the particular project you're working on than anyone else on earth (or in your location, if you have geographic barriers to entry). That's what'll convince customers to buy from you rather than a competitor.
The other option, as others have suggested, is to learn to code yourself. I doubt that you'd be able to do a good job of coding something up yourself without anyone with formal computer science training backing you up, but learning never hurts. If you know that starting a tech business is something you want to do someday, I'd say you should start learning how to code now. Personally, whenever a non-hacker tells me about something they want to start, I can't really see what value they're bringing to the table. Most ideas aren't that original (and don't necessarily have to be to be successful), so if they can't actually make the product, what good does working under them do for me? Business-types are definitely useful, but not until there's at least some sort of prototype.
I've never actually done a startup myself, so this is really just my personal intuition of the way things should work.
Build a chain of trust to someone with technical knowledge, and use them to assess possible technical people.
Some suggestions for finding a co-founder can be found reading, Students guide to Startups. [1]
Reference
[0] Warren Harding was 29th President of the United States and had the distinction of being pushed forward because he had the perceived traits of a leader and turned out not to be so good. I picked this up reading the Malcom Gladwell book 'Blink', 0-7139-9844-X.
[1] pg, 'A students guide to startups'
the solution to my problem is simple
a) im learning how to code from the ground up xhtml, css, php, mysql and then prob move on to ruby (this will take many months if not longer)
b) im looking for a technical cofounder, problem is, they all have the 9-5 mentality.
I majored in Politics as well, maybe i need some Joe Kraus magic!
When the greatest motivation to work on a project is the insane coolness of the project itself, things are different. Then, the money is just a bonus.
Can you figure out something about your idea that hackers will find cool?
If you want a technical startup, you need a technical cofounder. "I'll just outsource the development" will doom you to failure. I know this because I am an employee of a startup that thought that way, and learned the hard way that execution matters; and spending umpty-million dollars in the first year on outsourced projects that you wind up needing to pay umpty-thousand-dollars in the first year of operation to replace -- well, let's just say that, even with venture capitalists involved, burn rate matters, and money you spend stupidly still counts as an expense.
or
b. Learn to find good hackers (this not easy), then: 1. Pay them lots of money, or - 2. Learn from Steve Jobs and be a walking RDF.