YC's Group Partners Discuss Doing Things That Don't Scale

for these learnings is good to do. And doing things that don't scale, I think the main goal is that. How much can I learn? In 2013, Paul Graham, the founder of Y Combinator, wrote an essay entitled,.

do things that don't scale. And this essay transformed the culture of Silicon Valley. PG said not to worry about the theoretical problems of scaling and fix the thing in front of you right now. Do everything you possibly can to get early customers and delight them, even if it meant doing things in a manual and one off way.

The essay created a playbook for startups who needed to get from zero to one, And many of them made it, and they're making it right now. So today, we'll hear from the YC Group partners about the best examples of companies that did unscalable things to get off the ground. Let's get started.

So I think to start with, to set this up, what I remember from being a founder in the early two thousands is that investors and people in general at big tech companies were obsessed with this word Scalability. Because the issue with the Internet and the issue with websites was that people created these early web servers, processors were pretty slow, the size of bandwidth is pretty slow.

And so if you wanted to build an Internet company, and if it only could serve 10,000 or a hundred thousand people, and the site crashed, it didn't scale.

And it's actually pretty hard to scale. It was a real problem. Yeah.

Meant, in addition to technically scaling, which in this case just means the servers can handle the load, it also meant business models had to scale. A scalable business model would mean a business model that does not top out at a small amount of money. It's a business model that could go all the way into making billions of dollars. I actually think Google is indirectly.

Responsible for responsible for basically warping the minds of a whole generation of founders and investors Yes. And creating the problem that Paul Graham had to solve Yeah. With his essay. Google became so famous for this, because they did so much content marketing, everybody wanted to emulate Google.

And so, everybody from day one wanted to do the same thing and to be thinking about how they were going to build something that was as scalable as Google. And you wouldn't be able to raise a dollar from investors if you do not have a scalable solution.

Period. Full stop. And again, I'm not saying this is wrong, but this created the elephant in the room when you were a founder during that era, and I would argue to a lesser extent, still to this day, was if you did not have good answers to how your product or solution or business model scaled, it was not considered a venture capital fundable company.

Paul Graham heard this problem because many Y Combinator companies were obsessed with this thinking of scalability Yeah. For all the reasons I just mentioned. And so he had to invert it and say, the opposite.

Ignore this. And he wrote this essay with this amazing title, Do Things That Don't Scale. Yep. And this essay, I would argue, it transformed the culture. Like, it actually transformed not overnight, but over the years that followed, it actually transformed Silicon Valley culture, and it became ingrained in the psyche of the current generation of I.

agree. Because what he realized was the biggest problem that most startups have is they can't get users and they're not making something people want, not that their architecture is not scalable enough. Think about how many startups build something,.

this beautiful thing that has like so much scalability.

And no one wants it. It's like if you build it, they will come. The field of dream it's the field of dream startup. Right? It's the it's this beautiful thing, and you hired a big team, and it's like you got all the servers set up, and you're ready to scale. You got a chief architect in place. Yeah. And, like, no one cares.

And and and everyone churns. It's game over. Yep. Right? And so this Do Things That Don't Scale And at the time, it was such a contrarian title. I would say it's analogous to Mark Zuckerberg's Move Fast and Break Things. Yes. Do Things That Don't Scale, it sounded at the time like somebody was crazy.

It was so contrarian. Especially coming from an investor. Yeah. Which is why it had a real impact.

And so that is the context. To me, the point of Paul Graham's essay, and that we talk about all the time in office hours, is worry about the thing that is your biggest problem at any one point of time and try to slay that dragon first before you worry about later dragons you have to slay. And for most startups, it's just getting zero to one. It's getting the first customer.

It's building the first product. And to just get from zero to one, you don't need to worry about scalability. So don't. And then if you're lucky enough that people want your product enough that you have the luxury of worrying about scalability, great. Okay. Then you should totally scale. Again, like, he's not saying never scale ever for any reason. That is not what the advice is.

Yeah. It's just worry about it.

At the right time. Yes. As Dalton and Jared pointed out, do things that don't scale really encouraged founders to focus less on the future problem of scaling and more on solving the hair on fire problems of their first customers.

It was about focusing on what really matters in the moment. Next, Hajj and Pete talk about the Airbnb founders and what they did to inspire Paul Graham's essay. So what do we mean, Hajj, when we say do things that don't scale? What are those actual things? I feel like a lot of the spirit behind, like, PG's essay here was to get startups to be urgent, feel urgency, and be like, hey.

Like, you don't have time to spend six months writing the perfect piece of software before you go and get a real customer. Yes. And I feel like what inspired him with this was the Airbnb guys. They'd been working on that idea for a while, had no users, and they needed to get the flywheel turning. And so one of the pieces of advice he gave them was, hey. Look.

Like, you need just, like, really high quality listings. Like, the most important part of a listing is a photo. And so if you can't get people to upload high quality photos, just go and take them yourself and, like, have this catalog of really great places to stay with, like, professional quality photos. And so the Airbnb guys would go out and do that.

And that was clearly something that did not scale. That's what got them that, like, flywheel turning early on. And if they had been like, oh, like, we can't do that because, like, that's never gonna scale, they would totally have missed out on that. Totally. Right? It's like so much of that work is actually just like it can feel beneath you in a way.

Like, if you if you come in particular, I think the archetype here is, like, you come from, like, a really well paid job at, like, Google Yes. Facebook. Yes. You're, like, used to having, like, reports and infrastructure, and people do all this stuff. And then you come into a startup and it's like, okay. Like, I've got to send the cold email. I've got to, like, cold call.

I've got to do all of this. Like, I've got to, like, manage all of the admin stuff. I've to get the company incorporated. Like, no one else is going to do it. Yes. And one thing I've just noticed again is the best founders, no matter how smart they are, like, they just, like, dive into that. I think you just gotta have that mindset of, like, nothing is beneath me.

The only thing I care about is, like, getting to product market fit, serving customers, getting users, and.

that will, like, send you in the right direction. As an early stage founder, no task is beneath you. No action is too small or manual if it is in service of your customers. That's an important piece of this philosophy.

Next, Nicolas and Brad talk about the unscalable things that Nico did at Algolia to get his first customers and how he used that practice to more deeply understand what his users needed. We, in our jobs, run across companies sometimes that are like terrific examples of doing things that don't scale. There's a company from the winter twenty two batch that I worked with called Fleek. Mhmm.

And they are a marketplace for secondhand clothing, connecting wholesalers, the people who just like get tons and tons of clothes coming in in boxes from all over the world and actual secondhand clothing shops. So it's like the back office stuff. How did how does the clothing in the secondhand clothing shops get there? Fleek is this marketplace that connects the two. There's more. What did they do?

So when they started out, it was just three guys with an idea. And they didn't have a website. They didn't have any clothes. They didn't have anything. And so they had to figure out how do we get a marketplace started between these two parties.

And so they would go to the wholesalers in London, these giant warehouses full of clothes, and they would say, give us this box and just pick a box of clothes and say, give us six hours. Just give us the box for free. We'll bring it back in six hours, and either you'll have all the clothes back or you'll have a bunch of money.

And so they would get these clothes, basically, and they would schlep to all these shops around London and come back with $6,000 for the store. And they would do that over and over and over again and go to these different wholesalers. And eventually, people knew them as these, like, useful people Mhmm. In the wholesale community who were helping, you know, match buyers and sellers.

So what did they learn from that? I mean, why did they do that? Well, they did it because they had to figure out who actually like, what sells Mhmm. What doesn't sell, when's the best time to bring clothing in there, how to price this stuff, how elastic is the demand for it.

And these are things that you need in a marketplace, but it's very, very hard to figure that out by building a a a marketplace web page and then emailing a bunch of people and asking them to transact in it. Yeah. And instead, they did this, like, mishmash in person carrying cartons of clothes around and selling them by hand to get all those lessons into their bones. How long did they do that?

They did that for about four months. That was a great way for them to get started. But eventually, they needed to transition and start introducing the buyers and sellers to each other through their website.

Because at the end of the day, they in order for them to, like, have a scalable business that can start making money with good margins, they need the buyers and sellers to be transporting the clothes themselves and using their own delivery fleet and employees to to actually make the connections. They can't just be the CEO and the founders of the company moving products back and forth.

I mean, a great, great story.

One one of the stories I remember that gave me a good impression was the story of Stripe. I know it's a pretty well known story when the Stripe founders would actually work with their customers, like implement their software, their API directly in the software of their customers. And and we actually did that with Algolia too. Mhmm.

I remember when we implemented Algolia in Product Hunt, you know, Ryan, the founder, that was before Product Hunt became huge. And he didn't have, like, any resource to implement search himself. And so we remembered the Strive story. We did it. Like, he gave us access to his GitHub.

The first version of Algolia of search on Product Hunt was us implementing it and pull request and him putting that on mind. He was probably thrilled for the help at the time. He loved it. Right. He loved it. He couldn't ever have done it otherwise. Yeah. And so for him, it was such a help.

And for us, I mean, of course, it paid back, like,.

thousand times. Do you feel like you learned anything from from setting customers up in that way? Yeah. Because that created connection. Because from that point,.

you have that contact, that connection with the customer that is so much stronger. You can ask them anything, and you have way more candid conversations with them than if they are your customers and always worried about what else you're going to ask them, like money or whatever.

That that's a great point. You have context that all of your later conversations and interactions with them kind of grows out of. You know why they're using it, what they wanna get out of it, and a, that helps you developing the product yourself, but it also helps them have a much better experience using the product. Anything you can do to optimize.

for these learnings Mhmm. Is good to do. And doing things that don't scale, I think the main goal is that, How much can I learn Mhmm? Today? Yeah. Not waiting to have developed anything. Maybe what I'm going to develop is going to be the wrong thing. Like, if I can do anything like manually, even going physically doing the job yourself Yeah.

Not the software, you are going to make sure that what you're building is actually providing value. Yeah. And better do that before building too much. Yeah. And and so said differently,.

really strong, like, founders that we run across are people that are operating in a way that optimizes for learning. Yes. Right? When we when we see people, oh, like, let's jump to self-service early on.

It's it's in some ways, you wonder, like, oh, they're they wanna hide behind their computers versus going out and talking to their customers and really grappling with their with their problems and their pain. Optimize that for learning is a good way of looking at it. As Brad pointed out, the best founders we work with at YC.

operate in ways that optimize for learning, and getting in the trenches with your customers is an incredible way to learn about their biggest pain points. Next, Serbia and Erin talk about how founder FaceTime with customers can give you a real advantage over your bigger, better funded competitors.

There's nothing like that founder face time in the early days. Right? And that's a great example of something that doesn't scale, but that's so important in recruiting customers, recruiting employees.

One of the best, sales founders that I worked with was Ryan from Vendor. And Vendor buys SaaS software, for, startups and and big companies, and he's really great at sales. And one of the things that I've heard him talk about and that I learned from him is that as a founder, you have to sell yourself, especially when you don't have a product. You have a product that's That's the only thing you own.

Exactly. It's, like, really janky. Yeah. Yeah. And so, you know, it's when you're reaching out to somebody, say, here's my cell phone. Contact me any hour of the night. Or, you know, reach out to me because I am, you know, basing the future success of my company on making you successful, and I'm gonna do whatever it takes to do that. I will stop at nothing to do that.

And, ultimately, when you're selling to somebody, especially as an early stage founder, what you're really selling is yourself. You have to get them to make a bet on you. And so really leaning into that is important because, especially, sometimes people are scared. Like, oh, I'm going up against this big, well funded competitor or a public company or whatever.

Like, what middle manager is gonna give out their personal cell phone number Yeah. Yeah. When trying to win a customer's biz like, nobody's going to. Right. Absolutely. Make people feel like you care about them and you're gonna stop at nothing and your personal career depends on making them successful,.

people are gonna wanna go with you every single time. Every single time. Yeah. Don't be afraid of taking that first step that doesn't scale so you could truly validate what it is you're working on. Anything is better than standing still. And sometimes making progress means doing things that don't scale. One of my favorite examples of a company that did unscalable.

things to get off the ground is Instacart. In his original essay, PG says, partnerships usually don't work. They don't work for startups in general, but they especially don't work as a way to get growth started. Startups can't rely on big partnerships with brands to get going, so they're forced to be more creative.

Here's the story of how Instacart launched without a single grocery store partnership.

Do you have any good examples of this? Maybe from your own companies or from other companies you work with? The best example that I love is from Instacart.

Mhmm. And so, you know, Instacart's a service that lets you I'm sure lots of people are familiar with it. You open your app and you can browse the inventory from a grocery store and make an order. And so a normal person starting this business might think, oh, we've got to, you know, we wanna support Trader Joe's and Whole Foods.

So let's go and, like, talk to, like, management of Trader Joe's and try and get a a some kind of, like, corporate partnership or something, get access to their data, and, like, it's gonna take a really, really long time. You we have to pay salaries and some lawyers and all this kind of stuff. It might take years.

And instead, what Instacart did was they took their YC money and went to Trader Joe's and just bought one of every item at Trader Joe's. And over a weekend, got access to a photography studio, took all the produce that they bought, took it to the studio, and took pictures of it all, wrote down the prices, and on Monday morning, put all of it online and said, we're Instacart.

You can order anything from Trader Joe's. Some founders might say, like, maybe this is not, like, perfectly legal. Trader Joe's might object. You'll get a cease and des even if it is legal. Does this matter? I think it matters that you're not doing anything illegal. Yeah.

I think it if Trader Joe's object to you running this thing, honestly, they'll probably only notice when you get to a certain scale, and then you have the negotiating leverage. You have all these customers who are already buying through Trader Joe's Mhmm. That actually, they don't wanna shut you down. Mhmm. And that's exactly how it played out with with Instacart. Mhmm.

They struck deals with these grocery stores eventually after they got to scale, and they'd use this kind of hacky janky solution to get to scale. Because it took a founder to highlight to them that this idea was actually a good idea. Otherwise, they would have never never come come up with it themselves. Yeah. Absolutely.

And if you'd have gone to Trader Joe's or Whole Foods with nothing and tried to present this idea, you'd have been laughed out of room probably. Yeah. At the very least, it would have taken you years to get that deal. Yeah. Okay. All of these examples ends up succeeding. But the cases where you do things that don't scale, and it turns out no one wants a thing, actually, that's good as well. Right?

Because you've just saved yourself months or potentially years of building something that actually no one wants. It's way bad better to know that upfront and to be able to, like, pivot your product slightly or choose a whole new idea completely. And by doing this stuff that doesn't scale, you've not, like, hard coded yourself into a corner.

Know, you haven't written so much software that it's hard to change. A lot of the processes are manual. You're doing it yourself. And so if you wanna try something different the next day Mhmm. It's really easy because there's no software to change. Mhmm.

And the bet that you're making ultimately is once you've figured out the right configuration of the service or the product or whatever it is, that you will then be able to use software, write an algorithm that will provide the same level of quality of service Mhmm. At scale. Yeah. But it might take you several years of investment to do that.

And so in the early days, without making that investment, you can give the appearance of that service or product already existing by basically faking it manually, by Yeah. Pulling the strings in the background, doing tons and tons of hard work yourself to deliver that incredible white glove experience to customers. Doing things that don't scale lets you experiment, fail fast, and try new things.

It lets you test your assumptions before you spend months building a product.

From an engineering perspective, doing unscalable things gives you freedom to move more quickly. The first version of your product doesn't need to have a ton of technical infrastructure. Next, Diana and Michael will talk about DoorDash and how they built the first version of their product in one day and did a lot of clever manual work to find out whether people wanted what they were building.

DoorDash as a product was built in one afternoon.

Whether you believe it or not, the tech stack was basically Google Drive to upload the menus Mhmm. HTML CSS for putting the menus. The phone was Tony's phone. Yep. And then find my friends to pretend to have real time dispatch.

So it would be one of the founders going to go pick up the order, and then the other founder, it was a team of four, would be watching in real time where with Find My Friend where the order was, and it would text the customer, hey, your order ETA is ten minutes, twenty minutes. And the orders were just taken on Google Form. Granted, the team was actually very technical.

It was a team of with Stanford engineers, Stanford MBAs. They totally could have done the fancy thing and build, like, a dynamic site with Google Mac real time tracking and everything. But the founders were very pragmatic. That was not the hardest thing to prove out. It was like, is this even a thing that people wanted? That was.

the start up point. Like, that's the path no big company would ever take. This is the advantage you have as a start up. Right? It's the thing you can do and no one else can do. To your point, too many founders kind of we have to unteach them what they learn at the big companies. And, like, you play the big company game, they will always beat you.

You always have to thinking about what would you have gotten fired for Yeah. At the big company. That should be your playbook at the startup. I think the second kind of misconception that's embedded inside of a lot of startups' founders' minds is there's a way to do this in an error free play. Like, if I'm working at Google, I have to be far more careful. Alright.

I need to create plans that are kind of error proof. Yeah. And that's why it takes Google forever to do anything. As a startup, your path is full of errors. Like, error errors are the feature. So, like, should you be so lucky to have a product that so many people wanna use that it crashes and then you figure out how scale, that is the correct thing. Right?

Like, the way I always try to describe this is, like, imagine a house that has a number of cracked pipes and you have no idea which pipes are cracked or not. The big company person would go and check every pipe one by one. And it would take two years. The startup person turns on all the water. Yeah. And wait. Where's water coming from? That pipe's cracked.

Let's go fix it. And turns out that, like, when you are dying because too many people are using your product, the motivation to fix those bugs goes through the roof and they get fixed rather quickly.

Actually, I don't think we've seen startups die because of that reason. Never. That's not that is actually a % solvable problem. And you're not gonna die from it because the incentives are so high Yeah. To fix it, and you're on the path to build a large company at that point. Yeah. But most of them don't even get to see that. And you gotta,.

like, run the pipe and run with the mess and embrace the chaos. Yep. Doing things that don't scale is the startup way. It's the advantage you have as a small company. But at what point should you stop doing unscalable things? When do you flip the switch? This is a really important one because people who get from zero to one often get stuck here. Harge and Pete discuss.

The other side of this advice though is, like, do things that don't scale is great advice, but at some point, you do need to scale. And I think that's where it's useful to have, like, good advisers and investors around you because they can tell you, like, hey. Look. No. No. No. Like, you're in do not do things that don't scale mode. Yes.

And, like, oh, actually, like, now you need to flick the switch. Now now this is working. Now you should scale. Yes. Yeah. I think that's a great point. And you can think of kind of those early.

doing things that don't scale as a quick way to answer an important question. And once you've answered that question, well, now you have license to invest. Yep. Right? Yep. Yep. Yep.

One of the forms that I've seen this question take with with founders that are building SaaS software is that there's this moment in the earliest stages where you can make money by selling consulting services to other companies. Yep. Right? And so we actually had this example at Optimizely where we were building software to help companies run AB tests.

But at the earliest stages, we got companies to pay us just to go in and manually build AB tests for them. Yep. Right? And so we're making money. Great. The first version of our product was actually something that we used to make ourselves more productive in delivering those consulting services.

And that's all great. Right? Because it helps you answer the question, is this something that anyone will pay for? Right? Yes. It turns out the answer is yes. The failure mode here though is getting addicted to that consulting revenue because, like, that's the thing that won't scale quite literally. Like, it won't scale and you won't be able to build a big business if you depend on humans' labor.

Right? It's a really interesting example of where you can't just fixate on just your revenue number, but it's because you can always get revenue to go up by taking on more consulting. Yes. But it's why you can get around it by just setting yourself really ambitious growth targets. And I feel like this is partly why we push the companies to have such big growth targets.

It's one way investors tell apart what's a consultancy or a small business from, like, a start up that could be Stripe or Airbnb one day is, like, can it grow 10 x? So you can't a consultancy business, like, 10 x in a year. You can grow, like, real software business. Totally. The advice to do things that don't scale might sound counterintuitive,.

but it is truly the best advantage startups have over their larger competitors. It helps you intimately learn about your customer and their problems. It ties those early users to you more tightly and gives you opportunities to delight them. And it makes it possible to experiment quickly and fail fast if things aren't working. Go read Paul Graham's essay right now. Link in the description below.

That's it for this episode of Office Hours. If you like this and wanna see more, please be sure to click like, subscribe, and the bell icon down below. We'll see you next time.