Paste this. Leave the blanks blank.

Company name

Yoocal

Company URL

Product: https://yoocal-2026.pages.dev/new-home-1
This packet: https://yoocal-idea.pages.dev
Catalog origin: https://www.yoocal.com

Describe what your company does in 50 characters or less.

Local calendar for resort and lake towns.

What is your company going to make?

A town desk for what is actually on. A person picks Park City, Heber Valley, Midway, Jackson Hole, Elkhart Lake, or Green Lake. They search, filter by day and time and feeling, and see Tonight plus the month. They mark Interested or Going, name an itinerary, share it, and add it to a calendar. A host submits a listing for free after review, or orders Featured at $0.99 a day or Partner Sponsor at $9.99 a day. Guest prices stay the organizer’s prices.

Under that desk: a daily catalog gathered from public calendars, a map of the same nights, eleven feeling desks from music to nightlife, accounts, and a phone app started against the same catalog. Forty-three more towns are in a registry and held until the first towns show a repeat habit.

Where do you live now, and where would the company be based after YC?

Blank The product runs on America/Denver time and the beachhead is the Wasatch, Jackson Hole, and two Wisconsin lakes. Where the founders live, and where the company would sit after the batch, is not in the product repo. Fill it.

Explain your decision regarding location.

The first desks have to be near the towns, because a wrong listing and a host relationship are local. The software is already deployed and the catalog already publishes daily, so the company can be based wherever the founders will actually work, as long as someone can keep Park City honest through a season.

Who writes code, or does other technical work on your product? Was any of it done by a non-founder?

The 2026 product is the frontend, accounts, maps, and this pitch, in the yoocal-2026 repo. The daily listing engine that publishes the catalog is a separate repo and the live site at yoocal.com. The 16 September 2026 meeting notes name four people: Patrick Van Horn, Nabeel Muneer, Asad Muneer, and Omer Muneer Qazi.

What the repos support: Patrick Van Horn’s project is the listing engine. Omer Muneer Qazi’s project is the 2026 product. Nabeel Muneer is in the meeting notes around an agent view of scouting. Asad Muneer is in the meeting notes. Titles, equity, who is a founder, and who wrote which subsystem beyond that are Blank.

Are you looking for a cofounder?

Blank

Founder bios, how long you have known each other, and impressive things you have built before

Blank Write these yourselves. A YC partner can check them, and a polished invention here would sink the interview. The true technical story you can point at is a live six-town desk on a daily catalog, with saves, itineraries, and a host price, built as a product rather than a scrape dumped on a page.

How far along are you?

The consumer desk is public. On 2 October 2026 it showed 3,036 curated listings, 61 listings that day, and 6 live towns: Park City 1,695, Heber Valley 691, Jackson Hole 513, Elkhart Lake 84, Green Lake 53, Midway 0. People can search, filter, save Interested and Going, build a named itinerary, and download a calendar file. Signed-in saves go to the account. There is a submit form that stores a pending listing, and a host order form at $0.99 and $9.99 a day that stores an order and a total. A card is not charged. View counts are started, not yet a report a host would trust. Midway is on the homepage with an empty catalog. Retention is not measured. Revenue is not claimed because there is none recorded here.

How long have each of you been working on this? How much of that has been full-time?

Blank The 2026 frontend work visible in the project history is concentrated from September 2026. How long the listing engine has existed before that, and who was full-time, should be answered by the people who did it.

Are people using your product?

The catalog is being published and the app is on the public internet. We do not have a number for accounts, return visits, itineraries created, or hosts who came back. We will not put a user count in this answer until that instrumentation exists. The honest use we can demonstrate in an interview is the desk itself: pick a town, filter to today, open a listing, mark Going, name a list.

Do you have revenue?

No revenue is recorded. Host prices are in the product. Orders can be stored. Charging a card is the next build, not a result.

If you have an online demo, what’s the url?

https://yoocal-2026.pages.dev/new-home-1

Why did you pick this idea? Do you have domain expertise?

Because the calendars in these towns are already public and still fail the person standing on Main Street at 4pm. The expertise we can show is operational: a daily gather, a rule against invented prices, town desks with different visitors and locals, and a homepage that changes with the season. Personal history with these towns is Blank unless a founder has it and writes it.

What’s new about what you’re making?

The new thing is a full town desk that treats visitors and locals as two jobs, keeps the ticket with the host, and uses a gathered public calendar so the town is dense before anyone pays. Placement is a daily price a supper club can try for a weekend. The plan, the share link, and the season are the habit. New towns are a copy of a desk that already retained, not a thin national launch.

What do you understand about your business that other companies in it just don’t get?

They treat “events” as tickets in big cities. In a resort town the valuable object is the decision on a specific day, and a lot of the best rows are free. A ticket fee misses the library and still does not tell a family what to do at 2pm. A tourism calendar misses the local. A Facebook group cannot be sent to a guest as a plan. The company that wins this town is the one that is full on day one, honest in a quiet week, and paid for placement rather than for checkout.

How do or will you make money? How much could you make?

Free basic listing. Featured at $0.99 a day. Partner Sponsor at $9.99 a day with a monthly reach report. Guests do not pay.

Plan Six towns, if 25 hosts buy 40 featured days and 8 hosts buy 90 partner days: about $49,000 in a year. That is the proof. Forty dense destination towns, at 12 partner hosts for 100 days plus a smaller featured tail: about $515,000. Assumptions are on the model page. We do not describe that as a forecast of what will happen. It is the shape of the business if the habit is real. A booking referral can come later, only after hosts renew placement.

Who are your competitors? What do you understand that they don’t?

Tourism bureau calendars, Facebook events, Google, Eventbrite, Dice, Fever, Bandsintown, hotel concierges, and activity marketplaces such as Airbnb Experiences. The specific contrast is on the model page. The short version: each of them owns a slice. None of them is the mixed day in a small seasonal town, with locals and visitors on one desk and the host paying for attention instead of for the ticket.

How will you get users?

First, be the page that answers “what is on in Park City this weekend,” because the inventory is already there. Second, the share link: one person builds a Saturday and the group opens it. Third, hosts point guests at their own listing once placement is something they paid for. Fourth, the corridor: Park City, Heber, and Midway are one trip, so a second town is distribution. We do not buy a national audience before a town retains.

How are you meeting users or customers?

Blank if you have conversations, name them. The product surface for hosts is the submit form and the businesses page. A count of conversations is not in the repo.

Category

Travel, local marketplace, consumer. The payer is the host. The habit is the guest and the local.

Have you formed any legal entity yet?

Blank

Have you taken any investment yet? Are you currently fundraising?

Blank

What convinced you to apply to Y Combinator?

The desk for one town is a local craft. The company is the machine that copies a dense desk into the next town without going thin. That is the point where a batch helps: host payments, the retention number, and the discipline to add Salt Lake only after Park City comes back. We are applying with a live product and a small honest plan, not with a user chart.

Who is the user?

Three people, one screen. The visitor planning a weekend, the local on an ordinary week, and the host who wants Saturday. The visitor and the local are the habit. The host is the payer.

How do you know anyone wants this?

We know the calendars are split, because we gather them, and we know a town can be dense: Park City alone has 1,695 listings. We do not yet know that people return. That is the next measurement, and we should say it that way.

Why won’t Google or Eventbrite just do this?

Google answers a name you already have. Eventbrite sells a ticket. Our row is often free, our unit is the day in a small town, and our payer is paying for placement. A ticket company is pushed to ignore the free library hour. That hour is why a local opens the desk.

Why is $49,000 a company?

It isn’t. It is the proof that hosts in six towns will pay. The company is forty towns with a season, at partner prices, which is about half a million dollars under the assumptions on the model page, and then a referral only if placement renews. If we cannot get the six-town proof, we should not add the forty.

What is the most impressive thing you have built?

A public desk that stays honest: real day counts, a price rule, six different towns, and a plan you can send. Point at the homepage. Then say Midway is empty and that is the thing we do not hide.

What is the hardest part?

Retention in one town, and a host report that is true. Gathering listings was the cold start, and a lot of it is done. The hard part is a person opening it next Thursday, and a restaurant buying the next weekend because the count was real.

Why these towns and not New York?

New York already has dense event products. Park City’s calendar is split, seasonal, and full of both visitors and locals. The registry includes New York and we are holding it. Launching it now would be a thin page with a famous name.

Are you a marketplace?

Yes, with a sequenced cold start. Supply is gathered, so the desk is useful before the first host types. Demand is the plan. Money is placement, not a take rate. That is a marketplace that does not need both sides to sign up before the first visit.

What will you do in the batch?

Charge cards for Featured and Partner. Fill Midway. Separate the lake winter from the ski winter. Count Park City repeat opens, Goings, and shared itineraries. Talk to the hosts who already have rows on the desk. Add no new live town unless Park City retains.

What do you want from YC?

Pressure on the scoreboard, introductions to people who have built local habit products, and help not mistaking a full catalog for fit. The batch is for the machine that copies a town, after one town is true.