While we don't share a complete list of our publishers, the Pew Research Center recently released a methodological analysis of our platform that highlights a number of them.
I work over at Google Consumer Surveys and wanted to offer you a coupon to run a free test to gauge opinions on some different names once you have a few options you like.
Shoot me an e-mail and I'll be happy to send it your way.
Perhaps you're asking the wrong question. It often should be "How do I get ___ to be interested in reporting on me?" rather than "How do I get on?"
Think of it as a value equation: you want the reporters to help you get press and make people think you have something cool on hand; they want something cool to share with their readers.
So, one way to do it is - as most of the comments have suggested - use guerrilla tactics to get to the journalists/writers/topics that are often covered.
But, what if you created or generated something that is really unique and content-worthy? We did this recently with my product, and ended up with an unsolicited TC piece.
How'd it work? We showed-off the types of awesome things our product could do, and it caught the writer's interest.
So, I'd say find a way to show-off why what you're doing deserves coverage, and then take some steps to help get that in front of people (that's where Twitter, HN, etc. comes into play).
Also, quick note, but the traffic you probably expect from TC coverage may not be accurate.
It's a great point. To compare benchmarks, we'd have to consider...6 months in behavioral changes since the Pew survey; the likelihood that long tail users also use the main social properties; what we actually classify as a social network; medium effects on answer bias and more.
I couldn't agree more with your points about the importance of survey design. Our hope with GCS is to provide a real time, affordable, iterative mechanism for conducting this type of research.
The challenges faced when benchmarking against Pew and others, is, I believe, an indication of the value of continually collecting and updating data.
A year ago, I posted similar things on HN about collaborating with technical folks to bring my ideas to fruition and received a variety of responses. Some wanted to learn more and help, others not so much. So far, the ones below are cordial, but you'll get a slew of hackers telling you that you're "not trying hard enough if you don't learn to hack and do it yourself."
That article does the best job, I believe, in summing up what actionable steps you can be taking. You're not going to be a software engineer, and frankly, it's a bad use of the talents you have to try. But, there is an incredible amount of value in learning a little bit about code, being able to prototype - or at least mock-up - something, and most importantly, understanding what makes engineers tick. People are inspired by the idea of building great things - what you need to do is learn how to communicate your vision.
So, that's my advice; I'd recommend the article as a guide to get started. Now (warning) here's my editorial:
We "non-technical" folks have been overwhelmed by the rhetoric about how "if you can't hack, you can't add value." Give me a break. If it were all about coding, the 99% of failed start-ups would have succeeded. I see so many "projects" and "businesses" run by hackers who, typically out of pride, ignore the most basic "non-technical" principles that could have brought them success.
Yet, where WE fail as non-technical folks, is by behaving in EXACTLY THE SAME WAY, failing to appreciate the other half. Hackers are not code monkeys here to do our bidding and "turn our billion dollar idea into an app." The mutual lack of respect is the problem! Embrace that, and you'll find engineering PARTNERS you can create magic with.
Turns out, my ideas were solid too, since in the time since, one of them was launched by Google (where I work - I was uninvolved) and several others have been piling up on TechCrunch recently with funding. Why didn't I do them? I realized I was guilty of that lack of understanding of the other half. Since then, I've learned/am learning functional amounts of Python/JS/HTML/iOS and have developed an exponentially better understanding of how to collaborate with engineers. As a result, I believe I am infinitely more prepared to start a successful business.
the ad placements really take away from the experience you're creating. build a great product people come to use, then figure out how to incorporate advertising.
extra thought: you have the luxury of any monetization approach you'd like -- don't feel trapped by typical display units.
What issue were you having with the "take the tour" button?