24th - 25th October '26 · San Francisco

VibeCon SF 2026: Official Rules

Venue WiFiNetwork: Y CombinatorPassword: makesomething

01

Theme

Build for Main Street. Small businesses deserve better software. Build it this weekend.

Why now: many small businesses in healthcare, logistics, construction, finance and property still run on decades-old software, spreadsheets and phone calls. AI makes it possible to build something better in a weekend.

Who you're building for: a small business in one of six industries: healthcare, logistics, construction, finance, property or education. Think a dental office, a local courier, a roofing crew, an insurance agency, a landlord or a tutoring center. These are businesses that run on old software and don't have engineers to fix it.

What a strong project has: It starts with a fresh idea, a real problem solved in a new way, because a generic CRM or chatbot with a track label won't stand out. Pick the one job the business does every day and make it work live on Emergent from start to finish. Prove the problem costs money by showing what the old way costs in hours, dollars or lost customers, backed by real numbers and sources. Make it obvious why an owner would want it on Monday morning, and know your path to customers: who pays, what it saves them, and how you'd land your first 100.

02

Track Industry Focus

Healthcare & clinics

Who it's for

Independent dental, PT and therapy practices, home-care agencies

Example build

Referral inbox that reads faxed referrals and books the patient

Logistics & transport

Who it's for

Local couriers, small fleets, movers, freight brokers

Example build

Dispatch board that books loads and texts drivers

Construction & field services

Who it's for

Contractors, roofers, plumbers, HVAC and electrical shops, landscapers

Example build

Estimator that turns job-site photos into a quote the customer signs

Finance & insurance

Who it's for

Insurance agencies, bookkeeping and tax firms, mortgage brokers

Example build

Client portal that chases missing tax documents

Property & rental

Who it's for

Small landlords, property managers, short-term rental hosts

Example build

Maintenance requests that triage the issue and dispatch a vendor

Education & training

Who it's for

Tutoring centers, driving schools, studios, trade schools

Example build

Front desk that fills cancelled lessons by text

Example builds show the level we expect. Copying one will score low on originality.

03

Teams

Team size
Solo or a team of up to 4. Everyone on the team must be registered and at the event.
Team leader
Every team names one team leader. The leader creates the team's Emergent project, invites teammates and submits the final entry.
One of each
One team, one track, one Emergent project, one submission. You can be on one team only.
Finding a team
Bring a team or find one at the event.
Credits
Sign up for Emergent before the event with the email you used to apply on YC. Every builder gets 2,000 Emergent credits on that account, loaded before the event so you can start building at kickoff. Each team builds in one project owned by the team lead, so only the lead's credits are spent. Every team, solo or four people, works with the same 2,000. A 1,000-credit refill is available at the credit desk and goes on the team lead's account.

04

Rules

  1. 01

    Fresh build. All code is written after kickoff on Saturday. The theme and tracks are announced in advance, so come with ideas, research, data, customer conversations and sketches, but no code.

  2. 02

    Built and shipped on Emergent. Your product is built with Emergent in your team's Emergent project and is live at a public Emergent URL. No pasting in code from outside Emergent.

  3. 03

    Show your research. Back up the problem with research and data: industry numbers, owner interviews, time or money lost today. Cite your sources in your submission.

  4. 04

    Protect real people's data. Use synthetic or sample data for health, financial, student and tenant records. Payments in test mode only.

  5. 05

    Submit on time. Your team leader submits the form, including your demo video, by 12:00 PM Sunday. The build freezes at noon. Late entries are not judged.

  6. 06

    Video round, then live final. Pod judges score your demo video and can open your live app. If you make the Top 10, you demo live on the main stage from your deployed Emergent URL, with your video as the backup.

  7. 07

    You own it. You keep full ownership of what you build. By taking part, you agree to be photographed and filmed at the event, and we can feature your project and demo video in event recaps.

  8. 08

    Respect the venue. No alcohol, smoking or vaping. Wear your badge and wristband at all times. Builders use the ground and first floors only. If you leave after midnight, you can't come back until 6:00 AM. Attendees must be 15 or older; ages 15 to 17 need a signed parental consent form.

  9. 09

    Play fair. Help each other and clean up after yourself. Breaking a rule can remove your team from judging.

  10. 10

    Final say. Organizers' decisions are final. These rules may be updated before the event; the version at vibecon.com/rules is the official one.

What you can use

Allowed

  • Emergent (required for your product)
  • Claude and other AI tools for research, planning and copy
  • The Claude API and other APIs inside your app, with your own or sponsor keys
  • Design assets, UI kits and icons

Not allowed

  • Building your app in another coding agent or app builder and importing it, or pasting in code from outside Emergent
  • Code or logic written before kickoff
  • Real patient, client, student or tenant records

05

How to submit

Deadline
12:00 PM Sunday, Oct 25. Hard deadline; the build freezes at noon.
Who submits
The team leader, once per team, through the submission form at vibecon.com/rules.
What you submit
Team name and track; team leader and member emails (the ones on your Emergent accounts); live Emergent URL and a test login if needed; Emergent job ID; demo video link; your customer and how they handle the problem today, in one sentence; what you built in two sentences; your research and data, with sources.
Demo video (required)
Pod judges score this video. 2 minutes max; judges stop at 2:00. A screen recording of your live app with voiceover; faces on camera are welcome; no slides beyond a title card. Upload to Google Drive and set sharing so anyone with the link can view.
What the video covers
Open with the customer, how they handle the problem today and your strongest data point. Spend most of the video on the core workflow working live, start to finish. Close with why this wins. Tips: skip team intros, do a practice run, and open your link in a private browser window to make sure judges can watch it.

Video submission form

Deadline: 12:00 PM Sunday, Oct 25

The team leader submits the form once per team by 12:00 PM Sunday with:

  • —Name: the team leader's full name
  • —Team name: as registered at the event
  • —Contact: the team leader's email (the one on your Emergent account)
  • —Phone: a number we can reach during judging
  • —Video link: Google Drive link, shared so anyone with the link can view

06

Judging

Pod round (video review) · Sunday 1:00 to 3:00 PM

Pods
Your submission goes to one of 3 judging pods of 3 to 4 judges each.
What judges review
Your 2-minute demo video, your live Emergent URL and your research. You don't present in this round: no live pitch and no Q&A.
To advance
Your app must be live on Emergent, built during the event, fit your track and follow the data rules. Teams that don't meet these get feedback but can't advance.
Top 10
The top 3 from each pod plus the next-highest score overall make the Top 10, announced at 3:30 PM.

Final round (live on stage) · Sunday 5:00 to 6:30 PM

The Top 10 give a 5-minute live demo plus 2 minutes of questions on the main stage. Pod scores don't carry over. The final panel uses the same criteria to pick the winner, runner-up and third place.

Judging criteria (both rounds)

Judges score each criterion from 1 to 10, weighted to a total out of 100.

Execution & UI/UX

25%

What judges look for

The core workflow works live, end to end, with data that persists. A non-technical owner could use it without help.

A 10 looks like

Works live without a hitch, handles a mistake, feels finished

A 1 looks like

Slides, mockups or a flow that breaks

Originality & innovation

20%

What judges look for

A fresh idea or a new approach to an old problem, not a copy of an existing product.

A 10 looks like

Judges haven't seen this before and want to use it

A 1 looks like

A generic CRM, chatbot or clone with a track label

Problem research & data

20%

What judges look for

Research and data that prove the problem is real and costly, and an app built around what the research found.

A 10 looks like

Clear numbers with sources, owner interviews, features that answer the findings

A 1 looks like

No evidence the problem exists

Value, market & pitch

20%

What judges look for

Who pays, how much it saves or earns them, how you reach the first 100 customers, and a clear pitch.

A 10 looks like

A specific customer, real demand, and a story that lands

A 1 looks like

No clear buyer or plan beyond the demo

Use of Emergent

15%

What judges look for

Built and deployed fully on Emergent, using its features to ship more in the time.

A 10 looks like

Ambitious scope shipped end to end on Emergent

A 1 looks like

Emergent used only to host something built elsewhere

07

Awards

Winner

$10,000 and a direct interview for an upcoming YC batch

Runner-up

$5,000

Third place

$3,000

08

Key times

Before the event
Sign up for Emergent with the email you used to apply on YC
Sat 8:00 to 9:30 AM
Registration, check-in and breakfast
Sat 9:30 to 10:30 AM
Kickoff (theme, SMB tracks, rules, how to submit, judging) and welcome notes from Emergent and our Hero Sponsor
Sat 10:30 AM to 1:00 PM
Build Sprint #1, find your team, or go solo, start building
Sat 1:00 to 2:00 PM
Lunch
Sat 2:00 to 2:30 PM
Fireside chat with YC and Emergent leadership
Sat 2:30 to 6:00 PM
Build Sprint #2
Sat 6:00 to 7:00 PM
Dinner
Sat 7:00 PM to Sun 7:30 AM
Build Sprint #3; from 9:00 PM it continues as the optional overnight build
Sun 8:00 AM to 9:00 AM
Breakfast
Sun 9:00 AM to 12:00 PM
Final build block
Sun 12:00 PM
Submission deadline and build freeze
Sun 12:00 to 1:00 PM
Lunch
Sun 1:00 to 3:00 PM
Pod round: judges review your demo video (no Q&A)
Sun 3:30 PM
Top 10 announced
Sun 3:30 to 5:00 PM
Top 10 prep
Sun 4:00 to 5:00 PM
Dinner
Sun 5:00 to 6:10 PM
Final demos on the main stage: 5-minute demo plus 2-minute Q&A
Sun 6:10 to 6:30 PM
Winners announced, group photo and wrap-up

Questions? Find the Emergent team at the registration desk.