r/ycombinator • • Jan 23 '25

Trying to find a tech co-founder

Post image
5.9k Upvotes

r/ycombinator • • Oct 11 '24

Sam Altman on how to start a startup:

Post image
854 Upvotes

r/ycombinator • • Aug 17 '24 Heartwarming Heart of Silver

Got funding. Met on YC cofounder matching. Worst experience.

830 Upvotes

Came to share my experience on YC Cofounder Matching. It was a horrible experience, with massive learning. 

TLDR - there is a really good reason VC's want the founders to have a deep relationship with each other and I learned the hard way why. My cofounder was full of BS and I fell for it.

I'm a software engineer and after being in my big tech role for a few years, I was burning to build something that could solve other people's problems. I had been on the matching site for a while but hadn't come across any profiles I really liked and decided I was just going to quit my job and work on a side project I'd been building for the last few months. Shortly  before my last day at work, someone matched with me on the platform and they had an idea in a domain I was interested in, seemed smart and had all the accolades (Ivy League university, top consulting firm, etc). I decided to team up and work with her instead of on my own project. We agreed on a 50-50 split.

At first it was great; we quickly became friends but then I started to notice red flags.

First, she assumed that because she had a fancy Ivy League degree and consulting firm on her resume, VC's would fight to throw money at us, despite how obvious the post COVID environment was to raise money. I knew from the start no one was going to just hand over money because of our accolades but it took her a while to realize and accept it. 

Secondly, even though she was the "CEO", I found myself feeling more and more like an employee reporting to a boss instead of an equal partner. I explained to her a few times how I was feeling, being very careful to use subjective "I feel" phrases instead of objective accusations, but no matter how I phrased it, she would end up with hurt feelings, sometimes crying, and I would find myself feeling like I had done something wrong and end up being the one apologizing to her, further cementing my subordinate relationship to her. Looking back, I realize now that I was working with an extremely toxic person (consultants – surprise, surprise). I had always worked with engineers before and had never really had the misfortune to work with anyone toxic, and certainly not to that level of manipulation. So I wasn't even completely able to process what was happening at the time.

Thirdly, when we initially met she marketed herself to me as an expert on the subject matter because of extensive projects she had done at her consulting firm. I realized later she massively oversold herself and probably did some projects that gave her some domain knowledge but nothing deep and obviously nothing that was able to impress any VC that she was a domain expert.

We finally got into an accelerator (not YC), and then things really took a turn for the worse. Now we were working 12-14 hours a day together and we had a demo day deadline coming up, so the problems mentioned above increased by magnitudes due to the pressure to produce something with results we could present. 

The toxicity and emotional manipulation got worse and I felt more and more like an employee. She would fight with the accelerator managing director and our accelerator mentors/partners when they told her she was approaching or thinking about a problem in the wrong way. She would argue or cry about everything if it wasn't done her way. When I wanted to bounce ideas off each other, she'd take it personally if I found problems in her logic; she would storm away from me or throw tantrums. I found myself having to think extremely carefully how I would convey any thoughts or ideas I had to her in order to make sure her feelings weren't hurt, which significantly slowed progress.

The last big red flag I noticed was that she didn't seem to actually be doing anything. I was cold calling potential customers and getting rejected all day in an effort to understand our target customer and see what we could offer or build for them. She was working on the slides/deck for something that didn't exist since we kept iterating as we learned more about the problems in the domain. When she wasn't working on the slides or attending a presentation on how to make your slides, she was spending our VC money.

I got us a domain for $10 on Google Domains, but once we got our VC money she wanted to drop a few thousand on a domain name that sounded better. I tried my best to explain that our first 10 customers wouldn't care what our domain name was as long as we could help them, and that I didn't think it was a good use of our resources.

She wanted to spend another $1,000 on a designer to come up with a color palette for us. I tried again to explain that I didn't think this was a good use of our resources since we didn't even know what we were building yet. 

She didn't listen to me on either issue. 

I realized at this point she cared a lot more about being called "CEO", having some cool LinkedIn titles, being able to post "we're hiring!", and ordering people around instead of actually building a meaningful product that would help improve people's lives. 

There was one weekend I had to go back home to my family and that was an opportunity to see the last 7-8 months from a bird's eye view. The thought of continuing to ride it out with her for the next few years made me actually shudder and I realized one of the most important lessons in my life: 

You don't have to give up to let go (of something that isn't working).

These are also the lyrics in one of my favorite Deadmau5 songs.

I called the managing director and told them the situation. They were surprisingly supportive of my decision. I left two thirds of the way through the accelerator and immediately felt relief but I also felt like a failure. I had entrusted the worst person I possibly could have with my dream and now I felt crushed and broken. She was so toxic I’m pretty sure I got some sort of trauma from the experience as I developed severe insomnia for the next 6 months. I had to see three different psychiatrists, none of which helped. Meditation and tiny amounts of melatonin ultimately worked for me and today I'm almost fully recovered. 

Here are the lessons I learned:

It cannot be overstated how important it is to know who you are teaming up with. Random people are fine, but you need a trial period for about a year before making commitments. You need to know how people will behave when they are working 12-16 hour days with you and are under pressure. 

Team up with other technical people. This is really subjective, and I know some really, really smart, amazing people who aren't technical. But with technical people, there's a mindset of "either it works, or it doesn't work." You don’t want "it doesn't work but I went to this really awesome university, I had this really awesome job, I know these really awesome people so give me money.”

It's okay to let go of something that isn't working. If you can figure out quickly that something or someone isn't working for you (in any kind of relationship, honestly) then leave. Life is short, you don't owe them anything, and be grateful you figured it out in a few weeks or months instead of years. 

Don't leave the stability of your job unless there's a reason to. I had this weird idea that my job was holding me back from building my startup. You can always descope and build your MVP in a weekend to test your hypothesis. Leave your job when you start gaining traction and/or revenue and it makes sense to do so. You hear about the success stories of YC where founders went in with just an idea, iterated on it a few times and walked out with 5 million in funding. You don’t hear about the vast majority who failed. 

Today I have no regrets. It was a difficult 8 months, I learned a ton and everything worked out


r/ycombinator • • Apr 15 '26

Graduated from YC in 2023. Here's what the next 3 years actually looked like.

767 Upvotes

I don't post much but I've been lurking here since before we even applied, so I figured it was time to give something back.

My co-founder and I went through YC S23 (if you really want my company name, you can probably find it in the YC directory by process of elimination). We'd been friends since first year university and have been for a decade since. I came from data science, he came from fintech. Our application revolved around being an all-in-one fintech forward practice management platform.

Three years later, we are a full featured all-in-one AI EMR, live in 150+ clinics with a team of 15. I wouldn't have believed any of that during batch. I was sleeping 4 hours a night, eating garbage, and cold-emailing/calling clinic owners who wanted nothing to do with us.

Here's what the three years actually looked like:

Year 1 was survival. We pivoted hard from what we applied with. The product we pitched at demo day is not the product we sell today. What stayed constant was defining the customer and the problem space. If you're deeply embedded with your users, the right product reveals itself, but you have to let go of the version you fell in love with from the beginning.

Year 2 was chaos that felt like progress. Fighting for new customers and when we closed them demands came in faster than we could support them. Every week something was on fire. We learned that the nature of stress doesn't go away - it just changes shape. Early on, the stress is "nothing works." Later, it's "everything works but it's all held together with duct tape and people are depending on us." Neither is easier.

Year 3 was the first time it felt real. Not easy, real. Customers renewing without us begging. Features shipping because users asked for them, not because we guessed. A team small enough that everyone has full context and nobody needs a meeting to make a decision. We've consistently out-shipped companies with 50x our headcount and I think that's the single biggest advantage of staying small for as long as possible.

A few things I wish I'd internalized sooner:

The batch is a blip. The relationships are forever. I still text S23 founders almost every week. When you're going through something that nobody in your normal life can relate to, having people who just get it is worth more than anything in the curriculum.

Small teams move at a speed that bigger companies literally cannot. Protect that. Every unnecessary hire, every premature process, every "alignment meeting" chips away at the thing that makes you dangerous. We're 15 people and I want to stay small as long as we possibly can.

Gratitude is the thing I underestimated most. Building something from nothing with your best friends, backed by people who believed in you before the numbers made sense, serving customers who rely on your product every single day. That's an insane privilege. I wish I'd slowed down to appreciate it more in year one instead of just grinding through it.

If you're in batch right now or thinking about applying, just do it.

The worst outcome is a few months building something that doesn't work, surrounded by some of the sharpest people you'll ever meet. The expected outcome is way better than that.

Happy to answer questions from anyone who's early stage. This community gave me a lot, I'm glad to return the favour.


r/ycombinator • • Jul 22 '25 Diamonds are Forever

We went from YC W24 to 500+ customers and $32M Series A in 9 months - AMA

680 Upvotes

I'm Selin, co-founder of Delve. Nine months ago we were 2 founders in YC with an idea that compliance software was fundamentally broken for startups. Today we just closed our Series A with Insight Partners at a $300M valuation.

The problem we saw was simple but massive. Every startup trying to sell to enterprises hits the same wall. They need SOC 2 or ISO 27001 certification. The legacy providers tell them it'll take 4-6 months and cost them $50-100k all-in. We watched founders lose million-dollar deals because they couldn't get compliant fast enough.

My co-founders and I had all dealt with this personally at our previous companies. We spent months researching HIPAA and SOC2, spoke to consultants, and still barely made our customer deadlines. We knew there had to be a better way.

So we built Delve to be AI-native from day one. Not AI as a marketing gimmick, but actually using it to automate 90% of the compliance work. We can get companies SOC 2 compliant in 2-3 weeks. Not months. Weeks.

The response has been wild. We went from beta to 500+ paying customers before we even raised our Series A. Companies were switching from incumbents mid-implementation because they realized they could get certified 3x faster with us.

Some things that surprised me along the way:

The market is way bigger than we thought. It's not just startups. We have companies with 10,000+ employees coming to us because they're tired of spending months on compliance every year.

Building while selling is absolute chaos but it works. We were shipping features based on customer calls from that morning. One customer needed 21 CFR compliance so we put it together in 5 days.

The incumbent advantage is mostly perception. Our competitors are great companies, but they built their product pre-AI. It's like comparing Blockbuster to Netflix. Different eras, different capabilities.

Oh, and we’re insane growth hackers. We sent 10,000 custom donuts to founders across SF. We flew a plane over Saastr instead of buying a booth. We sponsored hotel keycards to be the last logo you see before you’re done. We send custom doormats to 100’s of companies. Those stunt got us incredible leads - and founders love to work with people on their wavelength, and people they can see are good, decent, hardworking and honest.

Happy to answer questions about:

  • Building AI products that actually work (not just ChatGPT wrappers)

  • Competing with heavily-funded incumbents

  • The YC experience and fundraising process

  • Unconventional marketing

  • How we’re selecting candidates

  • The reality of 100+ hour weeks when you're onto something big

AMA!


r/ycombinator • • Mar 13 '25

The biggest mistake I made was chasing VC money

563 Upvotes

When I started my first company, I spent all my time creating pitch decks and financial projections for investors. I thought this was what successful founders did. I spent hours researching fundraising strategies while my actual product idea sat untouched.

I got some interest from investors and even had some follow-on investment secured. But I ultimately decided not to go forward with it. I realized I was approaching things backwards.

The second time around, I completely changed my approach. I focused on building something useful first. I talk to users weekly and make improvements based on what they tell me. I'm solving actual problems instead of perfecting investor pitches.

This different mindset feels much better. Without pressure to grow at venture scale immediately, I can make decisions that help users most. Growing more slowly but sustainably works fine for me now.

It's simple: build something people want first, then worry about funding later.


r/ycombinator • • Jul 17 '24

Why is no one going after the Bloomberg terminal?

559 Upvotes

I'm sitting in bloomberg terminal now and it's like I've time travelled back to 1998 (maybe even earlier).

How is it that, especially since the ai hype, no one has succeeded in taking them on?


r/ycombinator • • Oct 14 '25

Got crushed by a CTO yesterday on my SaaS and it changed my perspective [got the actual transcript snippets]

525 Upvotes

I'm pre-revenue. Met a company yesterday and wanted to demo my Fintech SaaS to them. In my mind, they were the PERFECT fit.

On paper:

  1. They need to deliver fast.

    1. My product solves that.

  2. They lack engineering.

    1. My product solves that.

  3. They lack product experience.

    1. My product solves that

  4. They aren't cash poor, but nobody wants to spend ££££

    1. I was happy to pilot with them and keep costs low.

You get the picture right? Perfect fit. Perfect match.

I spent weeks researching this company. I met the CEO for dinner and explained what it is I've built and he showed enthusiasm and wanted to progress to the technical meeting. I expected that it would be received well given the CEO wanted the gtm and wanted the solution to save on hiring and engineering time.

I enter the meeting and the CEO had to rush off as he had a family emergency. He invited the CTO and their Head of Banking Product into the meeting instead. So I begin demoing. There's a few technical hiccups. Their internet goes down in the office so I lose the head of product for a bit. I can't record the meeting as per the CEO's request because Google Meets said 'not allowed to record'.

Despite all that, I'm full of energy, enthusiastic and I persevere. That did not phase me. I begin by talking through exactly what my SaaS is all about. Specifically mentioning the three offerings that I know they need. The CEO had previously told me they were struggling on those points. So, I begin to demo and I show the most important, most beneficial solution I know they need. About 5 minutes in, the CTO interrupts:

[Actual transcript from the voice recorder I used in lieu of google meets]

CTO: "Let me stop you here right now. If internal programmers cannot manage this themselves, or cannot manage internal small engine which can handle the 3-4 providers, I don't think they are good enough to stay in the company. So, yeah, I'm really unsure that this will be interesting for us. I don't care how it is built or how nice features you have because we will not give our information out. We will not tell you anything about our information. And that's 1st thing, and 2nd thing, We are building right now, something from scratch, and our engine will do that. It's an issue that why should a transaction go to the 3rd party where the 3rd party will decide the behaviour, the behaviour are your own, and then your execute."

Me: "I absolutely understand that. In fact, I agree with you. Companies that just want something really simple will benefit less from this. I'm offering a solution that is very simple but can be really sophisticated, highly adjustable and a service that offers significant adaptability. I'm not pitching against a few simple if statements, I'm pitching against months of routing bugs, mistakes and loss in profits because of failures and stuck transactions. I've worked in fintech for years and so far I don't think any company I've come across have nailed this because it's a whole project and product in its own right. What I have here is the outcome of lots of seeing it wrong to get it right. You also mentioned PII. If I can just show you the payload that is expected, you'll note that no PII is passed in"

---- bit of demoing again and some mild back and forth ----

CTO: "You are just nice, friendly guy. We saw like 2nd time, you know? And, and, uh, whatever, but also it's very hard, uh, to outsource that things, you know? It's like, uh, please, because even there is no PII, there are like, amounts, volumes, uh, there are, it's a commercial information, right? Look at check marble, they are open source. You should open source. Also, what happens if you quit or you close business tomorrow"

Me: "I completely understand that. I do think that it's really hard to avoid working with any third-parties without some information exchange. As for open source and self-hosting, it is something I am certainly looking into, but I believe the fasted gtm for companies is to use my product as a SaaS. If it is cool with you, maybe we can have a quick look at check marble together?"

--- CTO asks me to share screen so I pulled up check marble on screen share to get an idea of what they do and it literally said they SaaS everything pretty much except for a basic self-hosting level. CTO realised he was wrong to use them as an example, but I didn't call him out on it ---

Me: "are you going to be working with any banking providers in this upcoming deliverable you have?"

CTO: "I cannot tell you that. Why are you asking me that?"

--- getting a bit more tense from the CTO. Bear in mind I know they are as the CEO told me that beforehand ---

Me: "Well you expressed some really important points. I think that BaaS providers are going to retain a lot of your data and so are cloud providers. I wanted to get an idea on how you might manage that so I could perhaps see if there's a better way to ship my service to you"

CTO: "No, I cannot tell you that."

--- at this point, I figure this is no longer a sales pitch. CTO made his mind up ---

Me: "Thanks. I understand. I'm hesitant to demo anything else because I don't want to waste your time and I respect your philosophy. William, do you have any feedback for me on this that I might be able to take note of? I understand you've worked for many major companies and would really love to know if you feel like those companies would benefit from this or do you feel like they would not or yeah?"

Head of Banking Product: "I think they would. Um, so okay, so an example, so when I was at [REDACTED] bank, we didn't have a smart system at all. It was everything was done manually. So we would allocate the ibans to the client through, you know, I think we had 7 partners. Part of my role was to sit down with the sales team and understand the client and root them down the right path is to which appetite would kind of, you know, would suit the payment type that they were trying to do. Right. Um, and it took, it took, it took a long time, so we've, you know, they were trying to build something, but they've been trying to build one for, And while I was there, what, a year or two? They probably been doing it for 3 years and still haven't got anything live. I don't know why. Um, I'm probably too many, like you mentioned at the start, there's too many moving external factors that they had.

Um, But yeah, they're definitely trying to do it. And I'm sure, you know, I kind of along the same lines as Jeff, where they would want to keep it in-house because the main part of this is the build, isn't it? That's what people would want. Yeah. And I'm not technical at all, but it makes sense that they would want to own the technology rather than rather than, um, purchase it on like a subscription basis.

You know, there's fintechs and regulated companies that are popping up all over the place. There's definitely a market for it. People that are trying to get there very quickly rather than kind of take the time to develop it themselves. Yep. There's definitely people that they'll be interested in sure. Yeah, but it's like really interesting for it's really important."

---- I asked a few questions about it and he re-affirmed my product-market fit ----

We closed and ended the meeting shortly after. Straight after the meeting the Head of Banking Product added me on LinkedIn and told me he definitely believes in the product and knows there is a market for it. We agreed to keep in touch.

So, I had a train-wreck of a meeting in my mind. I kept professional, kept enthusiastic and didn't show I felt like trash. As soon as the meeting closed I felt sick. I'm not a sensitive person at all in general, but being my first demo for this business, it wasn't great. A friend argued that I demoed to the wrong company. But I know I didn't, they were paper perfect fit. The truth is there is a lot more to being paper-perfect.

I went for a walk, echo-chambered with AI about how my idea was great and the CTO was wrong. Then it hit me. I just ignored an entire lesson because my need for self-preservation of spirit, mind and ego got in the way.

I remember standing in the park and just thinking deeply once I'd realised. So I sat down on the park bench and really thought heavily about it. Whether I am right or wrong, or the CTO was right or wrong, is irrelevant. The customer is always right. They are the ones with the cash and nothing else matters in that moment. Even if the CTO is wrong and inconsistent, it does not matter.

I messaged the CEO and congratulated them on their pathway to their deliverable in Q1 and he replied in kind thanking me.

To me, this is the start of something great. I've faced rejection before, not quite like this, but if you're willing to be resilient and honest with yourself there is data to be extracted in this. What this is not for me is the CTO was old-school, close-minded, etc. This is: The CTO did not like my product and how I presented it. He did not like the deployment model. I need to improve pitching and consider product delivery if others share the same feedback.

Wondering if anyone else had similar experiences and what they did with it or if anyone has any feedback on my situation?


r/ycombinator • • Jul 20 '24

Feeling very powerful as a technical founder with Claude Sonnet 3.5

520 Upvotes

It's mindblowing how quick I can move now with sonnet 3.5, and I'm not even saying LLMs in general because this is the first one of them that I actually feel this comfortable with. Like, I'm pretty sure I could implement copies of the technical parts of most popular apps in the app store > 10x as fast as I could before LLMs. I still need to make architectural and infrastructure decisions, but stuff like programming the functionality of a UI component is literally 10x faster right now and this results in such fast iteration speed.

My workflow right now for a feature is basically:

  1. think hard about the feature, and probably discuss it with claude

  2. write basic spec for the feature (this is just a few sentences and bulletpoints most often), also iterate with claude here

  3. be sure to provide claude with all relevant context, and ask for the implementation (the code)

One thing that I think is very important is that you do need to have a very good grasp of the architecture of your application, both the big picture but also more code-specific stuff like your design patterns with how you handle data fetching etc. If you don't have experience here (which you get by being a good programmer) and you just use claude, I think the codebase will most often become too messy and complex resulting in it being hard to make changes later. This is the trap I've fell into before and what I think programmers that are still resistant to using LLMs for more than autocomplete do. When it happens, you'll inevitably get the feeling that you should have just programmed it yourself from the beginning. But this doesn't happen if you consistently guide Claude to behave as you want AND you keep up with the actual code you are pasting. I think keeping up with the code given by Claude is so important that I sometimes have sessions where I just read the already implemented code so I get the same feel for it as I would if I had written it "by hand".

I think what I'm writing here is particularly true for startups, and it's less true for big companies. For the company I work at, while LLMs are still helpful they aren't nearly as helpful as when building new products. I think this is mainly because I can't get the same overview of the architecture and it's therefore difficult to provide the LLM with all the relevant context.

All in all, I'm just very happy with this because it allows me to focus on more difficult parts of the application. Developing the actual views along with their functionality is basically a solved problem now if you use LLMs correctly.

What is everyone's experience here? Anyone else on a power trip recently after developing stuff with Claude?


r/ycombinator • • May 20 '25

How do YC startups create such amazing launch Videos?

513 Upvotes

Very Curious are these launch videos created by advertising companies or they use software for that?

This is the one I loved the video creativity is amazing and the product is also ‘very valuable.

PS : I have No affiliation with them whatsoever.

YC X25 - minerva intelligence


r/ycombinator • • Oct 28 '25

From 7 YC applications to $24M funding & 41K GitHub stars in 12 months - AMA

507 Upvotes

Hi, I'm Taranjeet, co-founder of Mem0.

One year ago, my co-founder Deshraj and I were in YC S24. Today we have 41K GitHub stars and $24M in funding. Over the past few months, I've been reflecting on this journey from 7 YC applications to finally getting into raising our Series A. I wanted to share what actually mattered and what I learned along the way.

Discovering the Problem

Before Mem0, we built Embedchain: a simple RAG framework for developers. We'd build applications on top of it to improve the framework.

In December 2023, one of those experiments was an AI chatbot of Sadhguru (a famous Indian yogi). It went viral in India, but the most common feedback was: "This is cool, but it doesn't remember anything about my meditative journey."

That's when it clicked. We realized this was the problem with every AI chatbot and AI agent. Coding agents forget the patterns you rejected yesterday. Support bots make users repeat their entire history. Personal AI assistants don't remember any preferences from one conversation to the next. They seem "smarter," but every session starts from scratch.

This happens because LLMs are stateless. They have complete amnesia between sessions.

We immediately started prototyping memory solutions. A few months later in February 2024, OpenAI announced memory in ChatGPT. We'd already been building this, but their announcement validated that the market would care about this problem.

It also triggered the question we'd hear constantly for the next year when raising our Series A: "Won't OpenAI or Google just build this?"

When we raised our Series A, we addressed this objection upfront. Our take was that Big Tech launching memory is good for us. It validates the market and brings market education. But developers won't use Big Tech memory for one critical reason: vendor lock-in.

Today's agentic applications use different models for different tasks, constantly switching as new capabilities emerge. The last thing developers want is their memory, the accumulated understanding of their users locked to a single provider. We wanted to stay neutral and build a memory layer that works across every model, every framework, every platform. That's the infrastructure we're building.

Applying to YC

I applied to YC 7 times with different ideas, but I kept getting rejected. The last three applications were variations in the same problem space. I gave 3 interviews. This helped me understand that the application and interviews are not just about having the best idea and traction. They’re also about clarity of thought and conviction. 

Early on, I wrote applications like pitches, trying to convince YC to invest. But for the later ones,  I had more conviction in what I was building, so I wrote it like a conversation with a friend and explained things as clearly and simply as I could.

I also understood the importance of the application. The application is a forcing function that helps you distill:

  • What is the problem and who is the user?

  • How big is the market? A lot of users want this, or a few users want it badly.

  • Are you the best team to solve it? This comes across through how well you explain the problem and your traction.

There is content on the internet describing YC interviews as rapid fire. From my experience across 3 interviews, I felt the partners are genuinely trying to understand the problem, the user, and the team. If you don't give them a high-level overview upfront, their questions may feel like rapid fire because they're trying to piece together the context themselves.

During our 3rd interview, I opened the call by giving them a framework: one line on the product, what problem we're solving, why it matters, who it matters for, our traction, why we're the best team, and how big this could be if we solve it. This makes the rest of the conversation much easier.

Lessons from YC & Funding

We got into YC and raised our Seed round before YC even started. Conventional advice is to wait until demo day, but we had clear traction and a clear story, so we did a 2-week sprint and closed the round.

This timing turned out to be critical. By our demo day, two competitors had each raised $10M+. If we'd waited, we would have spent demo day answering "why you vs. them?" instead of telling our own story. We raised in the quiet period before the space got validated and crowded.

But then we overcorrected. After raising, we spent 2 months perfecting the memory algorithm without shipping anything visible to users. We thought we were being diligent. We were actually being conventional in the worst way - waiting until things were "perfect."

At the YC retreat, our group partner’s first words were: "Why haven’t you launched yet? You were doing great before YC." Within 36 hours, we launched. We rebranded to Mem0, refocused, and doubled down on shipping.

Shipping fast is common advice at YC, but sometimes when you’re heads-down trying to build the best product, you lose sight of simply getting it out there. Shipping quickly helped us understand our customers’ memory needs much faster, which in turn helped us improve our product and grow.

That's the journey so far. From 7 YC applications to shipping in 36 hours to raising our Series A. A lot of it came down to knowing when to follow advice and when to trust our own gut.

Big Takeaways

  • YC advice is valuable, but context matters. Sometimes following advice blindly can slow you down.

  • The YC application is a forcing function. It makes you clarify your problem, users, traction, and market.

  • The interviews are conversations, not rapid-fire grilling. Give context upfront.

  • Timing matters in fundraising. Being early can help you own the narrative.

  • Shipping beats perfection, especially when you have traction.

Happy to answer questions about:

  • The 7x YC application journey and what finally worked

  • Building and scaling open source (Embedchain: 8K stars, Mem0: 41K stars)

  • The YC experience and knowing when to follow vs. ignore advice

  • How the "Big Tech will build this" narrative helped us

  • Why memory is deceptively complex to build

AMA!


r/ycombinator • • Apr 03 '24

I studied how Retool (YC W17) went from zero to a $3.2 billion company in 5 years.

477 Upvotes

Founded in 2017, Retool is a low-code tool that helps companies ship internal software fast. In 2023, Retool hit $93.5M in annual revenue, serving 500,000+ customers like Doordash, Mercedez-Benz, NBC etc. It last raised $45 million in its Series C2 round at a $3.2B valuation in 2022 and is backed by Sequoia, and founders of Github, Gusto, PagerDuty, Plaid, Segment, Stripe, and Y Combinator.

Founding Story

David Hsu founded Retool 6 months after graduating from Oxford University in the UK with a degree in philosophy & computer science. Back in his Uni days, he had started Cashew - a Venmo for the UK market and faced firsthand the problem of building & scaling internal tools for KYC, fraud management etc. He realized that every engineer had to build an admin dashboard but hated doing it. This became the inspiration for David to start Retool.

The problem:

The idea behind Retool is that there could be a much higher level way of building internal tools. Instead of writing JSX, developers could have a drag and drop interface where the user could create standard components like tables, buttons etc and make it do things, like connect to an API endpoint. This way, developers could get to 60-70% of the way super fast and then customize the remaining 30% by actually writing code.

MVP & early traction:

Retool got into YC in the summer of 2017. Their mantra was simple - stay default alive. In order to not burn money, they just didn't spend any money so they didn't even hire anybody, and did everything themselves.

Since Retool was a product that was similar to FileMaker, Microsoft Access, David tried to find similar customers and convince them to try Retool. (FileMaker is a cross-platform relational database application, MS Access is a database management system). This seemed like a very plausible path to finding product-market fit.

Hsu “infiltrated” several LinkedIn groups for FileMaker developers and did extensive outreach. He sent out a few hundred cold emails, received three replies back and got one person on a call. That developer pretty much said that Retool is a horrible idea and wouldn’t ever consider using anything other than FileMaker.

He also experimented with language-market fit. At the start, he positioned Retool as an “Excel sheet with higher-order primitives.” (David even posted on HackerNews with this headline). Nobody knew what that meant. So the team continued iterating on the messaging.

One day, Hsu sent a cold outbound email to a startup called Rappi, positioning Retool as a platform that helps companies build internal tools faster.

Within 15 minutes, Rappi’s CTO replied asking to get on a call - that was the first sign that the messaging & positioning was hitting the right person.

Based on subsequent conversations, he zeroed in on his ICP- software engineers who are building internal front ends with React, Vue, Angular etc. Hsu also discovered that Retool was very useful for a CTO or a VPE of a fast-growing operationally-heavy company, such as a delivery company or a fintech company.

Hsu didn't pivot the product but instead pivoted the market. His research revealed that the market for Retool was significantly larger than originally anticipated. They discovered that 50% or 60% of all the software in the world is actually internal facing.

Hsu sent outbound emails, got demos booked. A lot of people said no while some said yes. Some of the people that said yes weren't ready for them. And so Hsu would go build all the features required to actually get them to use Retool. And he did that over and over again.

One of their first customers was an app that allowed drivers to work shifts with both Uber and Lyft at the same time. This startup needed a lot of internal tools to manage the billing process and be compatible with both ride-sharing apps.

But the company didn’t have its own backend servers and therefore relied on public APIs for integration — something that Retool didn’t yet expose. So their first customer couldn’t actually use the product. Hsu stayed up all night to build it.

Their approach to pricing was pretty simple as well. For the customers David would just quote progressively higher prices (like $2k a month) and see what they would say. If they said no, David dropped pricing a bit back down. This approach worked great because the customer felt like they got a great deal, David got a customer and also discovered that $2K was probably too high for this particular customer. He rinsed and repeated this process over and over again. And he made sure to never quote pricing via email because they might go away and David could not have any idea what the reaction was.

By just doing this, Retool made $500K in revenue in the first 9 months. For the next 9 months, they streamlined their outbound processes.

They scoured Crunchbase pro to identify 10,000 companies that fit the description of the companies they wanted to introduce Retool to. They filtered companies that had raised money in the past 6 months. They used Upwork to hire freelancers to gather verified contact details for these 4 people at the 10,000 companies: (a) Head of Engineering (b) VP of Engineering ((c) CTO and (d) Head of Ops.

David used PersistIQ, a sales automation tool in order to reach out to the 40,000. After A/B testing the email copy & messaging, they finally found the subject line and messaging that worked and hit their inboxes.

At a conversion rate of 8%, 2400 people said they were interested to learn more and they became early adopters. They even signed an enterprise customer pilot worth $1.5M right before YC Demo day. At this stage, they hadn't made a single hire outside the founding team yet.

But growth was linear since it was all outbound. Now they shifted their focus on getting exponential growth.

Public launch

On August 9th, 2018, after a year of growing Retool through sales & cold emails, David posted about Retool on Hacker News once again, kickstarting their inbound lead gen engine. At this stage, they had 40 customers and had $2 million ARR.

Hsu knew that developers had very high standards so he wanted to make sure that when Retool was public, the developers would be able to use a product that was functional & bug-free.

Since the launch, they discovered that 15-20 companies were signing up for Retool every day.

The goal was to optimize onboarding inbound signups. They wanted to delight every early customer—in spite of having a new product that had lots of bugs. The goal was to build a product that generates a lot of word of mouth.

To optimize for customer success, they built 3 tools to ensure they could intervene at any step:

  • Big fish swimming: This was real-time notification alerting the entire company on Slack whenever a large account was using Retool

  • Big fish errors - These were Slack alerts when users experienced failures or issues.

  • Shared channels - These were shared channels with the developers to debug errors together.

Via this, Retool was always spying on their users.Whenever anyone was using the product, the team was immediately notified. They would immediately go and watch exactly what the users were doing.

When issues came up, they immediately called the customer up and said hey, we saw that this error came through, we'd love to help you out. This really helped them build customer confidence - Retool stepped in before the customer could identify the problem and solved it instantly.

Scaling up via PLG & product marketing

In 2022, Retool raised $45 million in their Series C2 round at a $3.2 billion valuation from Sequoia. At this stage, they realized the market for internal tools was huge. Their focus was on triggering user awareness aka how do they get more developers aware of Retool.

This was a challenging problem because developers know how to build digital tools. They're not googling how to build simple stuff related to building internal tools. So it's hard to capture them when users are in the intent phase.

So they invested in brand marketing & content marketing, writing high-quality content around Retool. They also optimized for Google search intent. For example, users would search for the best firebase front end and Retool would show up in the search results.

During this time, Retool also shifted its pricing to a freemium model triggering its PLG efforts.

The goal was to make Retool as open and accessible as possible, and optimize for usage rather than revenue. The idea was to attract a big pool of users who are using Retool’s products regularly (North Star metric: # of active customers) who would eventually become paying customers 3-5 years later.

They tested different experiment iterations like giving a certain number of app building blocks for free versus allowing a certain number of users for free. Retool tested these experiments in Canada and India and monitored the data. They set up a feedback loop with customers of the free plans in order to determine if they were seeing enough value in the free product.

All of this research led Retool to launch a modified third version. The new free plan includes a more generous set of features, an unlimited number of applications, and unlimited collaboration – but a cap of up to 5 users for free. This allowed Retool to show the true value–and full capabilities–of the product, not just a sampling.

Sales-led growth

Retool's earlier outbound sales system became a lot more sophisticated. Account execs work primarily within five sales channels: (a) Inbound leads that come directly to the sales team (b) Outbound leads that come from account execs or business development reps ((c) Conversions from the self-service motion (d) Expansion of existing customers (e) Self-Serve Conversion + Expansion. The entire sales team is optimized around a single metric - Net Dollar Retention (NDR).

80% of Retool’s customers come from their self-serve business. In 2021, 20% of the revenue that Retool’s AEs booked came from self-serve conversions.

Once businesses are using enough seats in Retool, they’re move off of a monthly plan, reach out or their AE and start the conversation around a volume discount on an annual contract.

Inbound leads come to AEs via demo requests. Often these are people who need enterprise features — advanced integrations, security, etc. — and who wants to go and talk to a sales person.

Outbound leads typically come from AEs reaching out to VPs of engineering, directors of engineering, internal tools teams, data engineering teams who will benefit from Retool. The icp is zoned in after years of iteration both on the messaging side as well as the market side.

The deployed engineering team is a technical post-sale team that works with customers on building their applications. Deployed engineering at Retool is active in shared Slack channels, and does paired programming sessions with customers.

Customer Success Managers focus on technical and business relations with customers. This includes everything from onboarding and launching new use-cases to helping them overcome technical challenges.

Community-led growth:

Retool officially launched their Retool community to the public in May 2021 until and has been growing since. Retool’s discourse forum is the hangout place for developers to get tactical help. Devs can ask for suggestions, get fixes, request feature updates, and show what they have been working on.

They also have an exclusive Slack group for Retool power users who have been part of the community for a while & have made significant contributions. These power users get early access to beta features, get to show their best work, and collaborate with the best developers on the channel.‍

To get into the slack group, users need to be skilled and contribute. To enable this, Retool gives users the resources to learn how to build, deploy and manage software at scale using retool. They have also launched Retool University that includes the A-to-Z of working and building with Retool.

They have built a library of templates to get people to the aha moment and increase user adoption. This helps with viral growth loops similar to how sending webflow and typeform did it.

They have also set up the Retool Documentation for devs. Retool also has built up a marketplace called The Retool Developer Network. It connects companies with qualified developers to build impactful internal tools.

They also offer free Retool credits (upto $200k) to startups. They’ve partnered with HubSpot, Segment, DigitalOcean, and Brex to offer discounts for their software as well when they use it with Retool.

9 key takeaways from Retool:

  1. Be default alive

  2. Outbound sales led motion at the start is perfect

  3. You cant do PLG before you have PMF

  4. Language market fit is as important as PMF

  5. Stay lean as much as you can

  6. Price high and negotiate at the middle

  7. Optimize for customer support and retention at the start

  8. Cant go wrong with content / brand marketing

  9. Community led growth creates a moat

You can read the full essay (with some cool pictures & graphs) here


r/ycombinator • • Jun 18 '25

Most startup advice is like someone giving you their winning lottery ticket numbers

460 Upvotes

I remember reading countless books and watching videos (YC and others) on how to build a successful startup. But I've realized it's like someone giving you their winning lottery ticket numbers: what worked for them is probably not applicable to you (plus fooled by randomness/luck).

After working on my startup for 3 years, I strongly believe it comes down to a very simple formula:

  • Build a good technological foundation

  • learn what matters to customers

  • and just iterate as quickly as you can, every single day

That's it, you can just get started.


r/ycombinator • • Feb 10 '25

How We Got Into YC on Our First Try

454 Upvotes

TL;DR - Quick Tips:

  • Apply late in the batch - partners are eager to fill remaining slots

  • Keep application answers precise and to-the-point

  • Have a working demo, even if basic

  • Talk to real users before the interview

  • Strong technical background + showing founder determination (we quit our jobs and lived with mom while shipping 7 products) helps

  • Being a family founding team can be a plus if you can show prior collaboration

Our Background

My husband and I were doing the SF FAANG life - I was at Google, he was at Apple. But corporate life was slowly killing our souls. We started building side projects on weekends, and our first Discord bot (while not a huge success) gave us that founder high. The energy from shipping something quickly was addictive.

We made the leap - quit our jobs, moved in with my mom, and went full indie dev mode. Over seven months, we shipped seven different products. Some actually started making money. When we hit on a bigger idea that needed funding, YC was our only choice.

The Application Process - What Actually Worked

1. Late Application = Fast Track

Applying late in the batch turned out to be a huge advantage. Partners are actively trying to fill their remaining slots, which means faster decisions. Our timeline was crazy fast:

  • Started application on Friday

  • Submitted Sunday

  • Interview invite Monday/Tuesday

  • Interview Thursday

  • Acceptance call that night

2. Precise, No-Fluff Application

We spent an entire weekend crafting our application. The key was being ruthlessly concise - answer exactly what they ask, nothing more. It was painful cutting down our responses, but clarity beats completeness.

3. Working Prototype Matters

My CTO (husband) cranked out a basic but functional prototype over the weekend. Our demo video was just 1-2 minutes showing core functionality. No bells and whistles, just proof we could execute.

4. User Research is Critical

After getting the interview invite, we went into overdrive on user research. I spent 48 hours calling every product manager I knew, gathering real stories about the problem we were solving. This paid off huge in the interview - when they asked for more details, I had actual user anecdotes ready.

5. Strong Technical Foundation + Founder Determination

Having two ex-FAANG engineers definitely helped our application. But what really stood out was that we'd already taken the leap - quit our jobs, moved home, and were shipping products consistently. Actions speak louder than words.

6. Family Team Dynamic

My husband and sister are my co-founders, which is a red flag for some investors (a few said it to my face). But we spun it as a strength - we'd already proven we could work together, and co-founder breakup risk was minimal compared to new co-founder teams.

The Interview Experience

The actual interview was so short. Here's what we learned:

  • They showed up 15 min late (don't panic if this happens)

  • Questions were straightforward

  • It felt like they'd mostly decided and were just checking for red flags

  • That famous "email = reject, call = accept" thing? 100% true in our case

Final Thoughts

The whole process was intense but moved incredibly fast. If you're thinking of applying, my biggest advice is to focus on showing you can ship quickly and have thought about your user thoroughly.

Obligatory note: This is just our experience. Every team I met had a different background / experience.


r/ycombinator • • Aug 26 '24 Take My Silver

How do founders lose everything

Post image
433 Upvotes

See image


r/ycombinator • • Nov 12 '24

YC 2024 Request for startups

Post image
429 Upvotes

Thoughts?

Our startup doesn’t fit, but I’m not too worried…we already have an accelerator interview from somewhere else and applied to 10.


r/ycombinator • • Jan 27 '26

I joined YC twice as a founder and here's what changed in 10 years

427 Upvotes

Hey there,

I'm Quang, the co-founder of Vybe (YC X25). Previously, I was also the cofounder of Birdly (YC W16). I'm reflecting on how YC has evolved in 10 years, what remains the same and what changed.

What remains the same:

  1. The core principles remain the same: Talk to users, code, and grow a steady percent every week (5-10%)

  2. Weekly dinners to get inspired: "They've been in your shoes, look at where they are now". The structure is always the same: it's about 10-12 weeks. Every week you have a dinner with a prominent speaker, for example the founder of Airbnb, or the founder of Stripe, or the founder of Cursor. In our current batch,

  3. Group office hours with peers: "Everyone is struggling with the same things, don't worry": A group of 8 to 10 startups meeting for 1h30-2h every other week where you discuss your struggles, get advice from others, set up goals for the next two weeks, and create accountability partners. It reminds you that everyone is struggling, so don't worry too much about it.

  4. Individual office hours: "Let's deep dive on what's the #1 thing that prevents you from growing faster": This is a meeting with your group partner, who funded you, believes in you, and has the most context on you. Every week can be a different topic, but same question: What is the one thing that prevents you from growing faster?

  5. Demo day is still the anchor date to create urgency: "We'll be meeting with 1,000+ investors in a few weeks, if you want to get in, get in now": that creates a sense of urgency to close customers and meet investors.

What changed:

  1. San Francisco is way more vibrant than Mountain View :)

  2. Growth Expectations are way higher now. There is more budget for AI tools. It used to be that 12% growth week over week was top batch, now it's the average of the batch!

  3. But also, YC has way more reach among potential customers, so any tweet or LinkedIn post to announce your launch will bring you at least 50 to a few hundred sign-ups that all could become customers.

  4. YC has way more reach among investors, so the number of inbounds we get is probably 10-20x higher than 10 years ago. Of course, it is a different company, and I'm a different person and there are more investors. But I also heard from batch mates that don't have my pedigree that they also received a lot of inbound just becaue they're from YC

  5. A corollary is that YC really really emphasizes that you don't meet investors before you're ready, and the more you wait the stronger your startup will be. They actually recommend not talking to investors before ~10 days before the demo day.

  6. For top startups of the batch (top 25%), there is way less emphasis on Demo Day prep, but rather on the ~10 days before demo day to meet investors. For top quartile startups, they will have raised before demo day.


r/ycombinator • • Jan 22 '25

Launched. Making $1000/day so far.

419 Upvotes

Title.

We launched 5 days ago and we've already made ~$5000 from a handful of customers. The problem space is back office operations in healthcare, where there's a lot of room for disruption. We have an advisor who has had two successful exits in healthcare and just reapplied to YC.

I say all of this to ask, what's next? Do we keep focusing on growth and spam pitch decks? Experienced founders, what would you do?

Thanks!


r/ycombinator • • Apr 29 '24

Discord vs. Slack is such a good example of why most people should do B2B.

419 Upvotes

Discord is the better product technically, feature-wise, and pricing-wise, yet Slack sold for twice Discord's current valuation simply because its identity is enterprise, had a small set of enterprise-oriented features, and was charging more aggressively as a result of that.

Shit is crazy.


r/ycombinator • • Jun 17 '26 Popcorn

If you ever feel like giving up, just sleep

415 Upvotes

I’ve noticed a pattern

Sometimes I’ll be working on something and suddenly everything feels impossible

The product isn’t good enough, the market is too competitive, the problems are too big and blah blah. It feels like nothing is going to work out

And the weird thing is that in those moments, it all feels objectively true. Not emotional, Not temporary. but true, then I sleep. And when I wake up, the facts haven’t changed

The bugs are still there, the challenges are still there, the uncertainty is still there

But somehow the conclusion changes, instead of “this is impossible or I cant do it,” it becomes “this is difficult, but I can do it”. And those are two very different things

I’ve learned not to trust my brain when it’s exhausted

If I feel like shutting down a project, quitting, pivoting, or throwing months of work away, I have one rule,

Sleep first.. Most of the time, though, I wake up and realize I wasn’t seeing reality, I was seeing reality through exhaustion

How many times have you almost quit something that looked completely different after a good night’s sleep?


r/ycombinator • • Mar 01 '25

How Stripe grew to billions using founder led sales

410 Upvotes

Patrick and John Collison were going up against PayPal in the payment processing space. Instead of doing what most founders do and hiring a sales team they took matters into their own hands.

They created something people now call the "Collison installation" which was brilliantly simple:

  • They'd ask for your laptop when you showed interest

  • Set up Stripe right in front of you

  • Let you see how easy the API was to use compared to PayPal

  • Show you could integrate payments in minutes not days

This hands on approach worked because Patrick really understood developers. He knew they wanted to build with a product not just hear about it. By letting them experience the API immediately they could see the value for themselves.

Their word of mouth exploded. Developers who tried Stripe would tell other developers how much better it was than the alternatives. The product basically sold itself after those initial demos because the experience was worth talking about.

The Collison brothers even went straight to PayPal founders Peter Thiel and Elon Musk in 2011. They boldly told them internet payments were "totally broken" and pitched their solution. That gutsy move got Peter Thiel to lead a $2 million investment.

The benefits they got from selling themselves were huge:

  • They could approve feature requests on the spot

  • They learned exactly what developers hated about existing options

  • Their product roadmap was built on actual user feedback

  • They created a sales playbook based on real conversations

Stripe is now worth billions but it all started with two founders who weren't afraid to demo their own product. It shows that no matter how technical your product is nothing replaces the founder showing up and doing sales themselves.


r/ycombinator • • Jul 30 '24

Rejected from YC S24: closing now ~2m$ VC-led pre-seed :)

393 Upvotes

Just a cool feedback.

Repeat entrepreneur, was rejected a few weeks ago from the S24 batch (top 10% but solo). But concept was too big to go home, so I went all in anyways (self-funded).

Met then in June from an angel some VCs, lots of rejections, found a co-founder, did hours of call (tons) and we eventually landed a term sheet with a cool fund !

Now closing a ~2m$ pre-seed, launching in September our product, team hiring started. We also have additional investors we met ready for the seed after we’ll get a bit of metrics.

Note : the YC rejection was the easy part 🤡

Never give up


r/ycombinator • • Jan 28 '25

How do we know everything Deepseek is claiming about the training cost is true?

388 Upvotes

Have we forgotten history how propaganda is the greatest invention of all times


r/ycombinator • • Aug 05 '25 Heartwarming

How we got into YC S25 with just an Idea

378 Upvotes

Hey r/ycombinator!

I know the Fall YC application date just closed, hope everyone isn't feeling to nervous around here. I wanted to share how myself and my brother got into this current batch (S25) with just an idea and no product.

For reference I am the cofounder of Lilac: https://github.com/getlilac/lilac

We just launched publicly this morning!

When we applied to YC we had nothing more than the idea. Our application was pretty short, the video was just us two talking about the AI industry, yet we landed an interview.

The Application:
We got the interview most likely due to us being very straightforward and to the point. YC tends to not like any fluff -- they want you to state who you are, why you are fit to build what you want to build, and how much money it could make. That's it. They truly care less about what your product is and more about why you are going to be a driven founder. If you come across as a smart person who will stop at nothing to build a successful company you are likely to get into the interview stage.

The Interview:
If you get into the interview, congrats! You are considered one of the top applications this cycle. I want to stress that the interview is less daunting than most of you think. The partner you meet with chose you for a reason -- they partly want to verify the idea and your understanding of it, but they almost care more about your passion as a founder. In their eyes YOU are the product. Sell yourself. The questions will be fast for the first few minutes, but once they feel like your understanding of the idea is "vetted" the conversation will relax more. That's when you need to sell yourself.

The Batch:
When you get the acceptance call, celebrate! And then immediately get to work. The batches are shorter than they used to be and you need to maximize your time. Your batch doesn't start the day you arrive in SF -- it starts the day you get the call. Setup office hours immediately, start building for your launch, get out quick. We had to make a pivot two weeks in which delayed our launch until now, mid-batch. If I could do it over again I would have quit my last job a lot sooner and worked harder pre-batch so we could have gotten our launch out of the way week 1.

I hope this can help some of you in the coming weeks -- feel free to DM me any questions!