HN user

dalton

2,632 karma

Partner at Y Combinator

Posts42
Comments125
View on HN
dalton.substack.com 6y ago

How YC will be funding the S20 batch

dalton
150pts43
dalton.substack.com 6y ago

The Three Questions: Culture Biosciences

dalton
14pts4
www.ediblegeography.com 8y ago

How to Clone Mineral Water (2012)

dalton
82pts13
techcrunch.com 8y ago

Polymail (YC S16) looks to unify business email tools into a single web app

dalton
47pts18
blog.ycombinator.com 10y ago

WorldCover (YC W16): Peer-To-Peer Funded Crop Insurance in the Developing World

dalton
11pts2
blog.ycombinator.com 10y ago

StealthWorker (YC W16) Is a Marketplace for Talented Cybersecurity Specialists

dalton
12pts0
netbeez.net 10y ago

Netbeez: Network monitoring with Raspberry Pi

dalton
49pts15
techcrunch.com 11y ago

BlueCrew (YC S15) Provides Workers for the On-Demand World

dalton
34pts11
daltoncaldwell.com 11y ago

Bitcoin adoption in 2015

dalton
88pts61
techcrunch.com 11y ago

Theorem (YC S14) aims to be the Priceline for fashion

dalton
35pts5
bitcoin.app.net 12y ago

Should App.net Accept Bitcoin?

dalton
84pts60
joyfulgrit.com 12y ago

Sales for nerds

dalton
1pts0
daltoncaldwell.com 12y ago

The tech industry: one or many?

dalton
33pts3
blog.app.net 12y ago

We are just getting started

dalton
72pts24
daltoncaldwell.com 13y ago

Where will Google Reader traffic go?

dalton
37pts32
blog.app.net 13y ago

App.net Passport for iOS is now available

dalton
3pts0
daltoncaldwell.com 14y ago

App.net project update #1

dalton
46pts24
daltoncaldwell.com 14y ago

What Twitter could have been

dalton
372pts122
daltoncaldwell.com 14y ago

Zen & the art of startup advice

dalton
22pts7
daltoncaldwell.com 14y ago

How Nokia got bamboozled by Hollywood

dalton
56pts22
daltoncaldwell.com 14y ago

Oh, the Places You'll Go

dalton
289pts54
daltoncaldwell.com 14y ago

The Edifice Complex, a silent killer

dalton
3pts2
ber.gd 14y ago

Observing traffic prioritization in Comcast’s network

dalton
104pts27
ber.gd 14y ago

Video streaming & net neutrality

dalton
111pts25
daltoncaldwell.com 14y ago

Two brilliant moves that helped create the Apple iOS powerhouse

dalton
100pts49
daltoncaldwell.com 14y ago

Why having an MBA is a negative hiring signal (for startups)

dalton
19pts16
daltoncaldwell.com 14y ago

The music industry vs AOL

dalton
20pts2
daltoncaldwell.tumblr.com 14y ago

Why Zombie Yahoo must be stopped

dalton
10pts0
daltoncaldwell.tumblr.com 14y ago

Startup Recruiting and the Stanford Prison Experiment

dalton
97pts18
blog.app.net 14y ago

Launching your mobile app at SXSW? Maybe we can help.

dalton
6pts0

I realize that this is likely to be less illuminating than you would hope, but the Retool founders were relentlessly focused on getting their first users, building quickly, and getting to profitability as if their lives depended on it. Witnessing them go from 0-10K MRR was to witness someone walking through walls.

To give a perspective on how much of an outlier this team is, my recollection is they got to ~1M ARR very quickly and with just the 2 cofounders and one employee. That is rare.

Congrats to Retool!

I worked with Retool when they were in the YC W17 batch. They were previously working on a p2p finance app for the UK, and I remember sitting in the conference room when they told me they were pivoting to Retool.

The Retool idea made immediate sense to me because at my prior startup we used django-admin to crank out internal pages and it was amazing. So it seemed clear to me that having something along those lines that was available in every programming environment would be useful, but it was harder for me to wrap my head around competing with free. This sort of reminds me of Algolia competing with Apache Solr - as it turns out can be a great business if you build a great product and really understand your customers. Also I did not appreciate the power of having a drag-and-drop interface, all of the integrations etc.

David and the whole Retool team have done a truly brilliant job executing since then, excellent work.

I don't have much to add to all of the other YC-related information out there - I think having a cofounder is generally a good thing, but not every company we fund does.

That's a fair point, and there are a number of situation dependent factors. I wrote this letter to myself because I know what I would do differently 12 years ago and I have the benefit of hindsight now. Obviously the crisis is different today, we didn't have a pandemic in 2008, there is definitely no one-size-fits-all advice, and every company needs to be figuring out the right thing to do right now. But keep in mind what ended up happening 12 years ago is that everyone lost their jobs. The letter is my thoughts about what could have prevented that outcome back then, at least partly.

For large dollar value contracts you usually have an account rep/point of contact you can get on the phone.

You can explain to your rep what you are dealing with, what your budget is, and make a concrete ask. I get the sense that the larger of a customer you are for someone, the more willing they are to work with you.

Hi, I am the author of this post. As I said at the top my intent was not initially to publish it widely, but here we are. If anyone has questions about what I wrote I'm happy to answer them here.

Hello HN, I am the author of this - it's part of a series of short posts about startups I that worked directly with at YC. This is the first one I have posted one to HN.

Let me know if you have any questions. Also I would love to hear if you are working on something ambitious like the Culture Biosciences founders are!

imagine we are talking about CPU clock rate - the rate at which founders are able to make progress - which means everything from how many customers they can talk to in a day, how fast they learn from running a test, how fast they can build a prototype, how quickly they internalize feedback from customers, etc.

Hey Dom, we worked together directly when you were in YC, and I deeply disagree with your assessment that having progress helps a startup succeed in YC.

The worst case scenario is a newly accepted YC startup with a little bit of traction... just enough traction that they aren't willing to change ideas/markets and not enough traction for them to actually know they have product market fit. It's the uncanny valley of product-market fit. These companies with a little bit of progress can spend months or years of their life chasing what they later realize was a mirage.

When a new YC company enters the batch with very little or no traction (and can move incredibly fast) they will longterm outperform companies accepted with small traction most of the time. Based on the hundreds of companies I have personally funded at YC, speed is the single most predictive variable of if a startup will succeed - not traction at time of accept.

Early Decision 8 years ago

Yes, you are off. Our apps submitted metric is growing.

The reason we started sending out emails to remind people of the deadlines is the sheer # of founders we talk to in person and over email that complain that they missed the application deadline and they didnt know when the date would be.

Questions about when the app deadline is, if you can submit late, when the deadline is for the following batch, etc is the #1 most common type of question in our support queue, and sending out reminders seemed like the best solution.

I'm the head of admissions at YC and I can assure you that a huge percentage of the companies that we interview and fund are at idea stage.

One explanation I have for why it my appear the startups we fund are "far along" at demo day is that the startups moved so quickly during the batch. For example, the startup Inokyo in the current batch recently put out a video of the autonomous store they built in Mountain View: https://techcrunch.com/2018/08/16/inokyo/ When we funded this startup 3 months ago it was for a different idea and so they quite literally started from scratch.

Startups moving fast should hopefully seem far along by demo day, irrespective of their starting point :)

I appreciate both of your sentiments, thank you.

I continue to be at least somewhat optimistic that non ad-supported models are worth trying. It seems like Patreon is doing really well and is perhaps something we can all learn from.

I think we are going to offer it under backer.app.net/project-name. It's something worth testing I think.

fwiw I have personally witnessed a significant percentage of consumers accusing a crowdfunding project of being a "scam" if it is hosted on their own domain rather than an impartial 3rd party like Kickstarter. I think that is one of the reasons consumers like Kickstarter vs self-hosted crowdfunding.

Additionally, in the Bitcoin use-case, if you have a page on your subdomain powered by Backer that accept Bitcoin, consumers will be confused and angrily say that you already accept Bitcoin because that page exists. That is also something we learned first-hand.

My instinct is that trying to run multiple Backers at the same time might make it harder for any one of them to succeed, and thus it might make sense to run them serially.

We are certainly open to trying things like this out, and sharing the best practices of what works best with the public.

App.net is a subscription service. We have a subscription state machine that works great with Stripe. We have systems to deal with upgrades, downgrades, proration, shifting to different plans. Additionally this requires us changing our accounting systems and wading into new tax complexities.

It's fascinating to me that people think that for any retailer to accept Bitcoin it's as easy as embedding a widget on their site. I have been comparing notes with other companies that are also considering adding Bitcoin support and these are the sorts of questions that come up.

There are lasting legal, technical and support operations that we are willing to take on long term if the market's big enough to support it. Otherwise, it's not worth the effort to implement those long term.