47 resources from Y Combinator we point founders to, and the questions each answers.
🛠️ Tool
✓ Link checkedFreeIntermediate
Why we picked it
The primary source for the SAFE itself, plus YC's plain-English primer explaining post-money mechanics. Use the official document, not a random copy, and read the primer before you sign.
Why we picked it
The best free on-ramp for founders who feel 'too early' for a funded accelerator, it distils YC's thinking into a structured course and, critically, includes the largest co-founder matching platform anywhere. It builds the proof and the team you'll need before you ever apply for equity money.
Why we picked it
This is the canonical, primary source for how the world's most influential accelerator actually works, deadlines, batch structure, the interview, and what acceptance gets you. If you're seriously considering a top accelerator, read the mechanics straight from the source rather than a second-hand summary.
Why we picked it
A short, plain-spoken YC talk where Seibel says it outright: be in love with your problem and your customer, and treat the product as something that can change. He walks through grading a problem instead of grading an idea, and picking a handful of real early users to check whether your solution actually lands. It is the fastest way to reset from solution-first thinking without reading a whole book.
Why we picked it
If your market is a small number of high-value customers, you are running an enterprise sales motion whether you call it that or not, and this is a practical, honest walkthrough of it. Pete Koomen (who took Optimizely to $100M ARR) breaks the funnel into prospecting, outreach, qualification, pricing, closing, and implementation, and makes the case that founders should do their own selling first. A good starting point for operating a low-count, high-value market rather than a generic sales pep talk.
When each deal is large, founders should run their own early sales to learn the customer's problem deeply before hiring a team.
The enterprise funnel has distinct stages (prospecting through implementation), and each one needs different attention when you only need a handful of wins.
Closing ten large customers is a very different game from acquiring a thousand small ones, and the relationship work continues long after the first signature.
Why we picked it
When you have no budget and one weekend, the highest-signal research isn't a report, it's a handful of real conversations, and this YC talk is the clearest guide to doing them well. Gustaf Alstromer shows exactly what to ask so users hand you real problems instead of polite opinions. It reframes market research from something you buy into something a solo founder can just go do.
Why we picked it
Kevin Hale (YC partner, Wufoo co-founder) walks through how to package your idea so an investor believes it can grow fast, and a big part of that is telling the founder story so 'why you' lands instead of sounding like a boast. It is practical and script-level: how to open, what to lead with, and how to make your unfair edge legible in the first minute. Watch it once before you write a single pitch line.
A pitch is really a hypothesis about why this company can grow quickly, so your 'why you' has to feed directly into that growth story, not sit as a separate bio slide.
Investors weigh how well you can sell and tell the story, so evidence you understand your customer beats abstract claims about your background.
Lead with clarity: make the problem, your insight, and why you are the one to solve it understandable in a sentence or two.
Why we picked it
When an investor doubts the team, the fastest fix is often not arguing about the team, it is showing progress that makes the doubt look silly. Seibel is blunt about which proof points actually move a seed investor: what you have done since you started, how fast, and why that is impressive. It reframes the meeting from "convince me you are the right people" to "look at what these people already pulled off".
Why we picked it
Two YC partners who both started companies in their early twenties make the case that being young is a real advantage, not a gap to apologize for: few obligations, high energy, and permission to take the kind of risk that gets harder later. If you are worried that no work experience disqualifies you, this reframes your situation as the good starting point it can be. It is short, plain-spoken, and free.
Why we picked it
Two YC partners walk through tarpit ideas: the ideas that look obvious and exciting (often because a trend made them feel inevitable) but quietly trap founders for years. It is a grounded, concrete list of avoidable errors, with the trend-driven ones front and centre, and it names why these ideas keep tempting new founders. A useful gut-check before you commit months to something that just feels hot right now.
Why we picked it
This is the canonical early-stage talk on where a founder's time actually pays off, and it keeps pulling you back to building something people want rather than studying the market from the sidelines. Altman is blunt that the work is making a product so good people tell their friends, which is a useful counterweight when you feel the urge to keep researching competitors. Treat it as a starting point for calibrating how little upfront analysis you really need before you ship.
Why we picked it
When referrals are not available, you have to manufacture signal yourself, and this is the canonical piece on doing that through cold outreach on GitHub, LinkedIn, and Hacker News. Taggar is blunt that cold outreach is slow (plan for months) and only works when every message is genuinely personalized to what that person built. Read it as honest expectation-setting, not a promise of a quick hire.
Look at public work (GitHub contributions, shipped projects) to judge people you have never met, since that is real evidence a resume is not.
Cold outreach can work but is a grind: expect it to take months, and never send a generic message.
Reference the specific work that made you reach out. That single detail is what separates a reply from being ignored when you have no shared connection.
Why we picked it
Tyler Bosmeny built Clever's sales engine and this talk is the plainest case for why the founder, not a hire, has to make the ask for the first customers. He is direct about the close: pick the people who need you most and will move fast, do not quibble over small terms, and get to a yes. Watch it when you keep collecting praise but keep flinching from actually asking someone to pay.
Why we picked it
YC's answer to what you need before a seed round is not a revenue number, it is a rate: raise once your product is being adopted at an interestingly rapid rate, with 10 percent per week for several weeks cited as impressive. That reframes the whole question for an Indian founder sitting on modest absolute numbers: a small base growing fast beats a large-looking base that is flat. Use it as the counterweight to the Blume floor.
The readiness test is a growth rate, not a milestone: a product being adopted at an interestingly rapid rate, with 10 percent week over week for several weeks called impressive.
Raise when you have figured out the market and built something people are adopting fast, not before you have that signal and not after you have already stalled.
Minimize time in fundraising mode: a tight, fast-growth story lets you raise quickly and get back to building instead of dragging a weak deck around for months.
Why we picked it
This is the source document for the entire SAFE debate, written by YC's CFO who papered thousands of these. It walks the actual dilution math (why post-money SAFEs are cleaner than pre-money), what a priced round buys you that a SAFE does not (defined ownership, a board), and the trap of stacking SAFEs at low caps that you only reconcile at the Series A. Read this before you copy any template.
Why we picked it
This is the reference point for what a clean deal looks like, written by the people who have watched hundreds of Series A term sheets cross their founders' desks. It names the exact clauses that quietly cost you (liquidation preference above 1x, participating preferred, cumulative dividends that compound the hurdle every year, and board or protective-provision language that hands investors operating vetoes) and teaches you to read the terms an investor insists on as a signal about how they see the risk. It ships with a downloadable clean template you can hold your own term sheet up against.
1x non-participating is the standard; anything richer (participating, multiples, cumulative dividends) is a red flag you negotiate before the price
Board and protective provisions can hand investors control over budgets, hiring, and pivots even at a founder-friendly valuation, read those clauses as carefully as the economics
The terms an investor pushes for reveal how risky they think the deal is, so a 'dirty' term sheet is also a signal about the investor
Why we picked it
This is the actual math you are trading against, straight from the source: $125K for a fixed 7%, plus a $375K uncapped MFN SAFE that converts at your next round's lowest cap. Read it before you romanticize the check. On a $15M cap that SAFE alone is another 2.5%, so YC ends up owning roughly 10% of your company for $500K. Indian founders should also note the fine print: YC only invests into US, Canada, Cayman, or Singapore entities, so an Indian company must flip its parent offshore to take the deal.
Why we picked it
YC's own CFO walks through exactly how a SAFE, a note, and a priced round each land on your cap table, and she does the cap and discount math live on slides so you can see founder ownership move. This is the canonical source: YC invented the SAFE, so this is the instrument explained by the people who wrote it, not a law firm reselling the idea.
A SAFE is not debt: no interest, no maturity, so it never comes due as a repayment problem before your next round
A valuation cap and a discount are two different levers, and the investor converts on whichever gives them the lower price (more shares, more dilution for you)
Model the shadow cap table: SAFEs do not show up as issued shares until they convert, so your real post-Series-A ownership is lower than the number you carry in your head
Why we picked it
This is the canonical case for splitting close to equal, written by a YC group partner. It arms you with the exact four reasons to hand a skeptical cofounder (or your own ego): a great company takes 7 to 10 years, so who wrote the first line of code in month one is noise; more equity means more motivation; almost every startup dies, and a demotivated cofounder is how; and Seibel's blunt line that if you won't give your partner an equal share, you picked the wrong partner.
Why we picked it
This is the one term sheet to benchmark your own against. YC wrote out the fairest single-page term sheet they could from having reviewed hundreds of Series A deals, and every bracketed item is exactly the clause that gets negotiated. It calls out the specific traps by name: participating preferred, cumulative dividends, and a 2-2-1 board versus the founder-friendly 2-1. Download the Word doc, drop your investor's term sheet beside it, and every deviation is a question you now know to ask.
From
Y Combinatorby Jason Kwon and Aaron Harris20 min read + Word template
The bracketed items in the template (beyond company and lead investor names) are precisely the terms that are always or frequently negotiated, so they are your negotiation checklist
Board control matters more than valuation: aim for a 2-1 (two common, one investor) structure, not the investor-heavy 2-2-1 that can let a board fire the founders
Clean means 1x non-participating liquidation preference, broad-based weighted average anti-dilution, and no cumulative dividends; anything richer for the investor is a flag
Why we picked it
This is the discipline your title slide lives or dies by: Seibel's rule is to name the company and say what it does in the plainest possible words, then run the two-sentence test (email a smart friend, have them explain it back, revise until they get it with zero questions). His worked line, 'Socialcam is a mobile app that makes it easy to take videos and share them with friends and family,' is exactly the one-liner you drop under your company name.
Why we picked it
This is the canonical slide-by-slide template from the person who has read more pre-traction decks than almost anyone. Seibel's rule directly answers your question: put your single strongest thing right after the 'what you do' slide, so if you have no revenue but a great team or a sharp insight, that leads. He also insists you present any traction with real timeframes instead of a vague chart, which is exactly the honest signal a pre-traction founder should lean on.
A seed deck is 10 to 12 boring, legible slides: title, problem, solution, market, traction, team, ask. Lead with whatever is strongest.
With no revenue, your team slide and your non-obvious insight ('what do you know that everyone else doesn't') carry the deck, so move them early.
Show traction with dated timeframes and specific numbers, not a smoothed hockey stick, because investors are grading your thinking at this stage, not your metrics.
Why we picked it
Kevin Hale's rule for a non-designer is three words: legible, simple, obvious. He argues an investor should grasp a slide's point in seconds, so the fix is not prettier gradients but fewer words, bigger type, and one takeaway per slide. It reframes design as clarity, which is exactly the bar a founder with no design skill can actually hit.
Why we picked it
The cleanest India pivot story told by the founder himself: Meesho began as Fashnear, a hyperlocal fashion app, and became a reseller commerce giant only after the market showed them where the real pull was. Aatrey narrates the turn as a data-led decision, which is the exact tone you want when an Indian investor can look up your old cap table and previous product in five minutes.
On
Y Combinatorby Vidit Aatrey (Meesho co-founder and CEO)35 min
Meesho survived multiple pivots (Fashnear to store-onboarding to WhatsApp resellers); the founder frames each turn as following demand, a model for your own narrative
The pull came from watching small resellers actually use the product, proof that the sharper bet should be evidence you saw something others missed
Told plainly by the founder in a canonical YC session, so it doubles as a script for how to say the old thing did not work without flinching
Why we picked it
This is the canonical source on the highest-stakes 30 seconds in startups, from the people who coach hundreds of founders through it each batch. Its hard rule matters for your opening: say plainly what you do and why, immediately, because 'a common error is to avoid describing what you do until far into the presentation, and that is always a mistake.' It kills the pretty-but-vague opener before you write it.
Why we picked it
YC partner Tim Brady defines burn rate and runway plainly in a few minutes, which is the vocabulary you need to see why a profitable-looking product can still empty the bank. It separates gross burn (everything you spend) from net burn (spend minus what actually comes in), the split that explains the disconnect you are feeling. Short and founder-facing, so it is a fast reset before you re-open your model.
Net burn, not per-unit margin, is what drains the account: it is total monthly spend minus real cash coming in, and it can stay negative while each sale looks profitable.
Runway equals cash in the bank divided by net burn, so the fix-first lever is usually the fixed spend sitting in gross burn.
Watching burn and growth together tells you whether each dollar spent is buying enough progress, or just buying time.
Why we picked it
This is the essay to read first, from a YC partner who co-founded Justin.tv/Twitch and has done equal splits across his own startups. It makes the honest case that early contributions are a tiny sliver of a 7 to 10 year build, so an equal split plus vesting protects the friendship better than haggling over who did more in month one. It is the clearest short answer to 'how do we split this without a fight later.'
Default to an equal split: the value is almost all in the years ahead, not in who wrote the first line of code, and a lopsided early split kills motivation when you need it most.
The real protection against a later fight is a 4 year vesting schedule with a 1 year cliff, so anyone who walks in year one leaves with nothing and the equity stays with whoever actually builds the company.
Have the awkward conversation now, on paper, rather than discovering the disagreement two years in when there is real value on the table.
Why we picked it
This is YC's curated shelf of talks and essays filtered to market size, so you get partner-level guidance in one place instead of hunting across YouTube. It is a good next stop after the single Kevin Hale video when you want more angles from founders and group partners. Everything here is free and vetted by the people who fund thousands of startups.
Why we picked it
YC's counterpoint is worth hearing precisely because it pushes back on being stingy: if this person is a real co-founder doing years of work ahead of you, generosity buys motivation across a four-year vest and prevents resentment. Read it against your traction story to decide honestly whether this is a true co-founder (lean generous) or an early employee wearing the title (grant, not founder equity). It is also the canonical source on why a one-year cliff and four-year vesting are non-negotiable.
Why we picked it
YC is openly skeptical of a remote co-founder (they discount the plan if a linchpin is distant), which makes this the most honest place to pressure-test the idea before you commit. YC founders running fully-remote teams walk through the actual mechanics: the right check-in cadence, keeping culture alive across a gap, and why demonstrated communication is the thing investors watch for in a distributed team.
Why we picked it
This is the source of truth, not a blog's guess about it. YC says plainly that the batch is in-person in San Francisco with a 3-day retreat and weekly meetups, that the remote Covid experiment ended in 2022, and that once the 3 months are over you can go wherever you want. It also confirms YC connects accepted international founders with immigration attorneys and helps you incorporate, so you can price the relocation before you apply, not discover it after.
Why we picked it
This is the horse's-mouth map of how a batch actually runs, and it names the two levers you should grab in week one: your group partner (6 to 10 companies per section, group office hours every two weeks plus one-on-ones as often as you ask) and Bookface, where batchmates and alumni answer questions and make intros. Read it to know exactly whose office hours to book and why the founders in your section become your most useful network for years.
Why we picked it
YC partners who have watched thousands of founders unpack what the essay looks like in practice, with real examples from Airbnb, Stripe, DoorDash, and Algolia. You hear how far the best founders push manual work and, just as usefully, how they knew when it was time to stop. It turns the slogan into judgment you can apply to your own week.
Why we picked it
This is the resource that most directly backs the hard version of the answer. Caldwell draws on data from thousands of YC companies to argue that teams without a technical co-founder consistently underperform, and that no-code and outsourced development are being oversold. Read it when you are tempted to believe you can skip technical ownership entirely.
Why we picked it
Three YC partners debate the honest nuance behind ship-fast advice, so you get the cases where waiting is defensible and the far more common cases where it is just fear. It keeps you from using the rare exceptions as an excuse to stall. Useful once you have internalized launch-fast and want to pressure-test your own reasons for delay.
Why we picked it
Cheung's YC Startup School talk is the tightest primer on choosing a small set of numbers that show whether your startup is actually healthy. She pushes weekly goals and frequent feedback so you catch a stalled feature fast instead of months later. A grounded starting point before you touch any analytics tool.
Why we picked it
A living list of problem areas YC actively wants founders to tackle, useful as raw material and as a way to spot where the world is changing fast. Treat it as prompts to react to, not ideas to copy, since the strongest version still comes from a problem you connect with. Good for jolting yourself out of a blank page.
Why we picked it
This is YC's direct answer to your question, walking through how partners spot ideas that only became buildable once models got good. It pushes you toward specific painful jobs inside an industry rather than a general assistant, and warns against the ideas everyone can see. Watch it to calibrate what a strong AI-enabled idea looks like versus a demo.
Why we picked it
Four YC partners talk through what is actually working in AI companies they fund, including which ideas look like second chances because the technology finally caught up. It is candid about hype versus real traction, which helps you separate a durable opportunity from a demo that impresses in a tab. Good listen while you are still deciding whether a space is real.
Why we picked it
A YC partner's direct notes to women founders on self doubt, asking for what you need, and not shrinking the ambition. It speaks to the keep going half of your answer, the part bias tries to erode. Short, specific, and from inside one of the best known founder pipelines.
Why we picked it
YC's curated shelf of talks and essays filtered to women founders, spanning fundraising, self doubt, and building. It is a free, high signal library to work through rather than a single piece. Bookmark it and pull the specific talk you need before each milestone.
Why we picked it
The developer forum where a lot of new tools and shifts get discussed before they reach the mainstream tech press. Reading it daily, especially the comments and Show HN, puts you next to the obsessed builders your instinct should be tracking. Skim it as a standing habit, not a one time visit.
Why we picked it
Product Hunt's own founder, talking to YC about what separates launches that land from ones that don't. He's blunt that a clear tagline and clear imagery matter more than clever framing, and that you should test your pitch on someone who's never heard of your product before you post it.
Why we picked it
HN's own posting guidelines tell you plainly what a technical, skeptical audience wants from a launch post: no editorializing, no hype words, no asking for upvotes, just a clear and honest description of what you made. Reading this before a Show HN saves you from the most common way founders get torn apart in the comments, and it doubles as a good gut check for any launch copy at all.
Why we picked it
Two YC partners talk plainly about why founders who avoid rejection end up avoiding their customers altogether, and why the founders who do best treat a no as information instead of a verdict on their startup. It is a useful mindset reset if objections are making you avoid sales calls entirely. Short enough to watch between calls.
Why we picked it
A US buyer deciding whether to trust an unfamiliar Indian vendor reads your contract as closely as your product. YC's free, plain English SaaS sales agreement, used by thousands of startups since 2015, signals you understand how US enterprise procurement works and saves you a costly first legal bill. Use it as your default paper for a pilot or first contract.
Why we picked it
Written for founders who would rather be building product than selling, this is a grounded guide to identifying and prioritizing the leads worth your time, whether they come from outbound or somewhere warmer. It is a good complement to the more channel strategy focused resources here, since it focuses on what to actually do once you are in front of a lead.
