Ask HN: Data questions for YC?
Hi Hacker News,
I'm Jared, I work at Y Combinator. We're going to be talking and writing about how we use data at YC, and I'd like to get the community's feedback on what would be most interesting. For example, some topics we're considering are:
- What data you should have before applying to YC
- How YC uses data to help evaluate applications
- What mistakes we've seen early stage startups make with data
We'll be hosting a talk on this and then writing a blog post to follow. What would you like to hear about?
30 comments
[ 3.0 ms ] story [ 79.2 ms ] thread2. What are some data points YC wish it has in evaluating startups? This would be a very interesting discussion topic. It can be something that the startup community work on together as we move forward... to make the industry/process more "scientific".
The more data point, the less we have to guess. That's what YC is trying to achieve right? Bring sanity to chaos of choosing and incubating startups. This idea of sharing data is a great start!
Ideally I'd also like to know a bit more, like the most common angles attempted (in general terms, not specific), although I can imagine how this might be disclosing people's ideas. Example: x% of attempts at idea A going after the high end failed, but y% of going after the low end survived and morphed or expanded to something else that has potential.
2) Which areas have the most statistically significant change in number of applications since the previous funding cycle. e.g. Developer Tools vs Developing Countries. Because it could point to upward and downward trends.
Ideally I'd also like to know about ideas in general too.
3) The top 3 questions on the YC application that startups answer most poorly.
4) The top 3 questions startups that are accepted and/or do well answer the best.
5) The biggest mistakes you see in applications and how they can be avoided (if they can.) Or the most common things missing.
6) The most convincing arguments you see in applications, and how they're made (e.g. by providing numbers and percentages, rather than saying "we're growing a lot".) Example: "if X is true, then Y" is more convincing than "I know Y will work", because you show that at least you're aware of X and are digging into it.
7) What most applications think will never work for a fairly well-defined idea, because it's such a good source of new ideas. But only if it's safe to assume the startup that applied won't pursue it, as to not run into confidentiality issues.
This can be information in the aggregate. e.g. show the top 2 things most applications think will never work, which could account for 80% of the applications, but don't show the outlier 20% which may be a good idea. In other words, provide corrective information, but don't provide what might be the answer.
8) If there's a positive or negative correlation between confidence in the idea and being selected or doing well. Ideally, I'd like to know if I'm writing my application in a way that suggests I have no idea what I'm talking about. But only if you believe providing this will help the startups and the application process.
9) Which parts of the application process that founders often think look like negatives turn out to actually be positives. So startups don't get discouraged.
10) To the extent each question on the application is scored and the score can be useful if it's communicated back to the startup, provide the score back to the startup.
Ideally, do this fast enough so the startup can rethink its answers. e.g. in cases where the startup had better info to supply but didn't, or if you believe it would help.
(1) and (10) are tricky because of confidentiality, the rest we can mostly do.
1) What kind of usage numbers "look good"?
2) What kind of ROI on adwords campaigns (or whatever) "look good"?
Or maybe it would be better to frame these as null-hypotheses: E.g. what makes an early adwords campaign look like the whole idea should be scrapped?
Does it scrape data from the application to display it on the side (like downloads, revenue, MAU, etc). Does it compare an application with a similar YC company (that either failed or succeeded) such that a partner can make a correlation.
I'm just shooting in the dark, and have no clue if it actually has anything to do with data.
[1] https://twitter.com/sama/status/715617188841795585
> Awesound - AdWords for podcasts
> Bulletin - Airbnb for Retail
> Müvr Labs - Fitbit for your knees
> Palaround - Tinder for private networks
> Sage - Uber for eldercare workers
> ...
https://blog.ycombinator.com/first-fellowship-virtual-demo-d...
- Didn't get into YC, e.g. funding, exits - Didn't get into YC the first time but got into YC on a subsequent attempt
I'd love to see this data.
For example, there was a sneaker startup in the most recent batch, which was the first one admitted to YC (AFAIK), but probably not the first to apply.
I'd be curious to see if you had data over the past few batches to demonstrate trends like this space growing.
A consultant or a developer acting as a part-time data scientist works?
- the amount of time founders spent on their project before applying
- correlation between age and university studies, previous work experience of founders at big companies
- what kind of tasks did they outsource
Formats, file types, databases, tools etc...
2) Is this biggest mistake usually that people don't fire fast?
3) We know the unicorn growth rate - but what is the median/average growth rate for a semi-successful YC company?
4) What makes a company part of the walking dead?
5) What are the primary channels a lot of YC companies use for user acquisition? How has that changed?
6) What are the primary reasons for rejection for YC companies? Does it differ by partner or uniformly the same?
7) We know that airlines are hard. It'd be great to see what specific categories of startups that YC has funded that are just more difficult to grow in or are easier to get traction in - e.g. consumer v. enterprise, analytics, gaming/media?
8) In fact, I'd love to see a review of PG's claims in general either backed by data or refuted by data. I suspect they're backed by data, but it'll likely give more insight into the key area that people find interesting. For example, are more people now finally choosing NOT to go to grad school?
How was data used to select the potential market?
How was data used to craft the customer interview questions?
How was results data from customer interviews used to make a decision to pivot or move forward?
I am aware that studies are often a case of GIGO and this is an inherently hard space to quantify. But I have taken classes in this area and read works that were research based, such as Getting to Yes, and I am always interested in any solid data that relates to what many people feel is a soft science at best, thus not worth taking seriously.
Thanks.