Do not delay a Y Combinator application to commission a polished website. YC's public FAQ encourages founders to apply at the idea stage. Our practical recommendation is to prioritize the application and accurate evidence of what you are building, then use a simple page when it helps people understand the product.
That does not establish whether a particular field in the current application form is required. Check the current YC application instructions and the form itself. A website, founder video and product demo have different jobs; one should not be presented as a substitute for another.
What YC's public guidance says, and what it does not
The published FAQ does not make a finished product a prerequisite for starting an application. That is different from claiming a landing page improves acceptance odds. This article offers website planning advice, not YC selection criteria or an endorsement.
If the deadline is near, complete the requested application materials first. Do not let a branding project replace work on the product, customer learning or a clear explanation of the company.
Keep the website, founder video and product demo separate
| Material | Its job | What to prepare |
|---|---|---|
| Website or landing page | A stable explanation people can revisit | Product category, audience, current status and an appropriate next step |
| Founder video | The application material described in YC's instructions | Follow the current official format rather than using a promotional film |
| Product demo | A concrete view of what the product currently does | A working workflow or a clearly labeled prototype with access instructions where needed |
YC's founder-video instructions specify one minute of the founders talking and direct product demos to a separate place in the application. Follow that guidance for the video; a polished website or product animation does not replace it.
When a simple website is useful
A landing page can help with customer interviews, outbound messages, early access, hiring or investor conversations. It gives those audiences one place to understand the offer and current stage. Build it for those practical needs, not an unsupported promise that it puts you ahead of other applicants.
- You are sharing the product with people outside your immediate network.
- You need an accurate explanation and one consistent contact or access route.
- You have a working product or prototype that can be shown honestly.
- You are collecting early interest and can explain what happens after signup.
The minimum useful startup landing page
Keep the page small. It should answer these questions without a live explanation from the founder:
- What is it? Name the product category and the task it supports.
- Who is it for? Identify the first user or buyer clearly.
- What exists today? Distinguish a live product, prototype, private beta and planned capability.
- Can I see it? Use a current screen, short workflow clip or labeled concept.
- What happens next? Offer the action that matches the stage: contact, early access, demo or trial.
Below the first section, add the workflow, identifiable team and a short explanation of common questions. Use customer names, numbers and quotes only when they are accurate and you have permission to publish them.
A worked example for a pre-launch product
This is an illustrative brief for interview-scheduling software, not a client case study:
| Page element | Example |
|---|---|
| Headline | Coordinate interview panels from one scheduling workspace |
| Audience | For recruiting coordinators organizing multi-person interviews |
| Product status | Private prototype: planned calendar connections are listed separately |
| Visual | A labeled prototype screen using sample candidate data |
| Next step | Request an early-access conversation, with the process explained beside the form |
The example makes the product understandable without pretending it is further along than it is. Once the live workflow changes, update the status and visuals together.
Common mistakes to avoid
- Using "AI-powered platform" as the whole explanation.
- Presenting concept screens or planned integrations as shipped features.
- Inventing users, traction or waitlist numbers to fill a proof section.
- Sending reviewers or prospects to broken links or inaccessible demos.
- Offering a trial when the only available action is a waitlist.
- Spending the application preparation period on an unnecessary full brand rollout.
What to check before sharing the link
Open the page and demo from a fresh browser session. Confirm that the product description matches the application, the visual status is labeled correctly, links work and any required access instructions are available through the appropriate application field. Test the page on mobile and submit its form once to verify the response. Do not expose confidential customer information in public screenshots.
Build the page for the company, not a funding shortcut
A clear page can remain useful whether the application succeeds or not. It can support the next customer conversation and give the team a consistent product explanation. Judge its value by those tasks instead of making unsupported claims about funding outcomes.
Use the stage-by-stage SaaS website guide to choose what to build now. If you already need the page for outreach or launch, review NexaFlow's SaaS website design and send the product stage, target audience and immediate launch goal. We can scope the website around that need; we do not act for YC or promise acceptance.
