10 min read ·
How to Use YC’s Platform Without Rushing the Most Important Decision
Create a specific profile, approach several plausible candidates, and test the strongest relationship through a bounded project.

YC Co-Founder Matching is a free introduction service for people seeking potential startup co-founders. Start on the official YC page, create a profile through Startup School, and review suggested candidates. Treat any match as an introduction—not proof of compatibility. Several candid conversations and a defined work trial will tell you far more than profile similarity.
YC Co-Founder Matching: official access and quick answers
Use the official YC Co-Founder Matching page. Its sign-up and sign-in buttons route through Startup School, where participants create and access their matching profiles.
| Question | Short answer |
|---|---|
| Where do I join? | Through YC’s official page and Startup School |
| What does it cost? | YC describes the service as free |
| Does YC take equity? | No equity or other commitment is required merely to use it |
| Do I need an idea? | No; you may join with or without one |
| Must I be ready now? | No; you may explore potential future partnerships |
| Is my profile public? | No; YC says it is visible only to approved participants |
The audience is broader than founders already building a specific company. You can join while developing an idea, seeking someone with complementary interests, or meeting prospective collaborators before you are ready to commit.
YC says profiles are not public on the internet and are visible only to other approved Co-Founder Matching participants. However, the public page does not explain its approval criteria, detailed data controls, or whether and how identities and credentials are verified. Evaluate candidates independently and disclose sensitive information gradually.
How the matching process works
The basic workflow is straightforward:
- Create a profile. Describe your background, interests, skills, current plans, and what you want in a co-founder.
- State your preferences. These help determine which candidate profiles you see.
- Review suggested candidates. Look beyond titles and credentials to assess what each person wants to build and how they expect to work.
- Send an invitation. Explain why you see a potential fit rather than relying on a generic introduction.
- Connect after acceptance. A match occurs when the other participant accepts the connection.
YC’s July 2021 launch announcement said recommendations drew on information such as interests, location, and skills. Other launch-era materials described preferences involving location or timezone, time commitment, skills, and division of responsibilities. These remain useful discussion topics, but the historical descriptions do not confirm that every field or filter remains available today.
A match has a narrow meaning: an accepted connection.
Use the recommendation system for candidate discovery. It can expose you to people outside your network, but the available evidence does not establish that its suggestions reliably predict compatibility.
What the platform’s numbers do—and do not—show
YC’s landing page reports more than 100,000 matches, without providing a measurement date or methodology. Because a match is an accepted connection, this figure cannot be read as more than 100,000 companies or lasting founding teams.
The same page reports undated active-profile counts of 3,200 in San Francisco, 3,000 in New York City, 2,900 in London, 1,900 in Bangalore, 1,400 in Los Angeles, and 1,200 in Toronto. These self-published figures may indicate geographic breadth, but they do not show how recently participants were active, whether they fit a particular search, or how likely they are to respond.
YC highlights Whalesync, AccessOwl, Pledge Health, and clearspace as companies whose founders met through the platform. These selected examples show that an online connection can progress to company formation and YC funding; they do not establish a typical result.
No disclosed denominator supports estimating:
- The percentage of matches that lead to work trials
- The percentage that become companies
- Founder-retention rates after formation
- The likelihood that a platform-originated team enters YC
- The probability that a participant finds a suitable co-founder
Read connection volume as evidence of reach, not as a success rate.
Build a profile that gives candidates something concrete to assess
A useful profile should help another founder decide whether an initial conversation is worth having. Include:
- Relevant work, technical, operating, or research experience
- Industries, customer groups, or technical areas you understand
- What you have already built, tested, or learned
- Your location and timezone constraints
- Your expected commitment and likely timeline
- Responsibilities you want to own
- Responsibilities you want to share or have a partner lead
- The problems and company trajectories that interest you
If you do not have an idea, do not present yourself as a blank slate. Describe the problems, technologies, workflows, or markets you understand. Explain the kinds of people you want to explore with and what an initial project could involve. “Open to anything” gives candidates little basis for evaluating fit.
A nontechnical founder seeking a technical partner should demonstrate more than ownership of an idea. Useful signals include domain expertise, credible customer access, completed customer conversations, early validation, a clear understanding of the workflow, and progress made without waiting for an engineer. Present the opportunity as a shared company-building role, not as unpaid implementation work.
A technical founder assessing an idea- or domain-focused candidate can ask:
- Do they understand the customer problem firsthand?
- Can they reach prospective users and obtain candid feedback?
- Have they executed difficult projects before?
- Can they explain why the problem matters now?
- Do they communicate precisely while acknowledging uncertainty?
- Have they produced evidence beyond enthusiasm for the market?
These are prompts for better judgment, not a proven formula for receiving replies or forming a successful team. Specificity helps identify plausible fit; it cannot replace working together.
Use a compatibility scorecard before discussing a partnership
YC guidance emphasizes repeated conversations, relationship quality, mutual respect, and ability rather than a mechanically complementary division of skills. This scorecard converts those considerations into observable questions. It is a decision aid, not a compatibility test validated or endorsed by YC.
| Criterion | Observable question | What to notice |
|---|---|---|
| Mutual respect | Do both people take the other’s expertise and concerns seriously? | Curiosity without deference or contempt |
| Integrity and trust | Are claims candid and consistent, including when the answer is uncomfortable? | Openness about gaps, incentives, and mistakes |
| Commitment level | Do availability, runway, and timelines align? | Specific commitments rather than vague ambition |
| Communication | Can each person explain decisions and raise problems early? | Clarity, responsiveness, and listening |
| Execution ability | Are agreed tasks completed on time and to an appropriate standard? | Follow-through under ordinary constraints |
| Working style | Can both people agree on workable levels of speed, structure, and documentation? | Whether differences can be managed explicitly |
| Relevant insight | Does each person contribute knowledge that changes decisions? | Depth rather than impressive labels |
| Idea flexibility | Can both revise or abandon assumptions when evidence changes? | Attachment to the problem rather than one solution |
| Disagreement | Can conflict be discussed without avoidance or personal attacks? | Ability to disagree, decide, and continue |
Do not decide after one introductory call. Hold several conversations in different formats: an open-ended background discussion, a working session on a real problem, and a direct conversation about commitment, values, money, risk, decision-making, and expectations.
Verify consequential claims where appropriate. This might involve reviewing work samples, checking public professional history, speaking with references with the candidate’s knowledge, or asking the person to demonstrate relevant technical or commercial reasoning. Platform approval should not substitute for diligence.
A perfect skills split cannot rescue a relationship without trust. Conversely, two capable and adaptable people may cover gaps through learning and hiring. Prioritize whether you respect the candidate, can rely on their judgment, and can resolve tension without damaging the relationship.
Run a time-boxed co-founder work trial
A work trial turns abstract compatibility into observable behavior. Make it substantial enough to create real decisions and tradeoffs, but narrow enough to avoid an indefinite unpaid quasi-partnership.
1. Choose one bounded problem
Select a customer or product question that can produce a meaningful result—for example, interviewing a defined customer segment, testing demand for a workflow, building a constrained prototype, or evaluating one technical risk.
2. Set fixed dates
Agree on a start date, end date, and retrospective. Duration should reflect the participants’ availability and the problem, not a universal number of days.
3. Assign responsibilities
Record what each person owns, including research, outreach, implementation, design, documentation, and coordination where relevant. Identify decisions requiring joint approval.
4. Define deliverables
Examples include completed customer interviews, a documented synthesis, a working prototype for one use case, an architecture recommendation, or a tested landing page. Avoid vague outcomes such as “make progress.”
5. Establish a cadence
Choose a communication channel, meeting schedule, response expectations, and method for documenting decisions. Include at least one substantive working session rather than relying only on status updates.
6. Agree on success criteria
Decide what you want to learn about both the problem and the partnership. Product success and relationship success are separate: an unsuccessful experiment can still reveal a strong working dynamic.
At kickoff, discuss weekly availability, expected pace, decision rights, communication preferences, confidentiality, and how either person can end the trial. During the project, observe execution, responsiveness, reasoning quality, comfort with ambiguity, willingness to change direction, and behavior during disagreement.
Close with a retrospective:
- What worked well, and what created friction?
- Which commitments were or were not met?
- How did each person respond to new evidence?
- Would both people run another trial?
- Are both ready to discuss a partnership?
- Which major questions remain unresolved?
A third-party-hosted copy of a document presented as a YC-authored guide describes Kiwi Biosciences as a selected example in which prospective founders used a structured questionnaire and a month-long trial before continuing together. That illustrates the value of an explicit process, not that one month is right for every team.
Document expectations around confidentiality, existing intellectual property, jointly created work, and future use. Obtain appropriate legal advice before relying on or commercializing shared work.
Use YC matching alongside higher-trust channels
YC Co-Founder Matching should expand your search rather than replace every other route. Personal and professional networks may offer years of observable behavior, shared context, and trusted references. Online matching offers a different advantage: access to people who might never appear in your immediate circle.
YC’s 2021 launch announcement and discussion said founders should still search existing networks where suitable candidates are available, while presenting the platform as an option for people without those connections. YC also says it funds solo founders, so there is no reason to accept a weak partnership merely to satisfy a perceived application requirement.
Run several channels in parallel:
- Ask former colleagues, classmates, researchers, operators, and investors for thoughtful referrals.
- Participate in founder communities relevant to your technical field or customer market.
- Attend events that allow substantive working conversations.
- Use YC’s platform to reach beyond your current network.
- Consider YC’s advertised in-person matching meetups in San Francisco and New York City.
- Apply the same diligence standards regardless of where an introduction originates.
A warm introduction provides context, not guaranteed compatibility. An online introduction starts with less shared history, but it can develop into a strong relationship through candid conversations and demonstrated work.
Frequently asked questions
Does using YC Co-Founder Matching improve my chances of getting into Y Combinator?
There is no published basis for concluding that using the service improves the probability of admission. YC has highlighted selected companies that met through the platform and later entered its program, but those examples do not establish an admissions preference or success rate. Do not add a co-founder solely to influence an application.
Does YC verify every participant’s identity, employment history, or technical ability?
YC says profiles are limited to approved participants, but its public product materials do not establish that it verifies every identity, employment claim, credential, or technical skill. Treat profile information as an introduction, verify consequential claims independently, and limit sensitive disclosures until trust has been earned.
Do I need a co-founder to apply to YC?
No. YC says it funds solo founders. A strong co-founder may add judgment and capacity, but a rushed partnership can be worse than remaining solo. Continue searching if the right person has not emerged.
Use YC Co-Founder Matching to widen the top of your search funnel, not to bypass diligence. Create a specific profile, approach several plausible candidates, and test the strongest relationship through a bounded project. Commit only after both people have seen how the other communicates, executes, changes their mind, and handles disagreement.