Extraordinary Founders Dinner: Andrew Yeung's SF Gathering

A dinner application asks a founder to make a different kind of case: why would a conversation with this person be worth continuing? Extraordinary Founders Dinner, hosted by Andrew Yeung, brings that question to San Francisco on October 15, 2026. The gathering is designed for 16 people, with an invitation that explicitly welcomes immigrant founders, category builders and people who have built through difficult circumstances.

The event runs from 6:30 to 9:00 PM PDT in a private dining room, with a three-course meal provided by the partners. Applications require host approval, and the exact address is available through registration. For founders evaluating the evening, its potential value lies in having enough conversational time to explain an operating problem and hear how another builder approached something comparable.

What the Extraordinary Founders Dinner is offering

Andrew Yeung's invitation centers on founders with unusual or demanding paths into company building. That framing can give strangers a useful starting point: the part of a founder's story that disappears when an introduction becomes a company name, a title and a funding stage. A shared willingness to talk about the difficult work can matter more than a polished account of the result.

The planned experience is dinner and peer conversation. No speaker program or moderator is publicly announced, and the organizer has not published the guest roster. Readers should evaluate the invitation on the format that is actually described, rather than imagining a stage, a pitch competition or a particular investor waiting at the table.

The application process also changes the decision for someone considering attendance. A founder can explain the business being built, the obstacle that shaped it and the kind of exchange that would be useful. Host approval gives the organizer discretion over the room, while leaving the quality of the eventual conversation dependent on the people who arrive and the attention they give each other.

Sixteen places is a small enough format to make conversational continuity plausible. It also limits how many people any attendee can meet. The useful preparation is to decide which question deserves a considered response, rather than plan an evening around collecting the largest possible number of introductions.

The operating problems behind the partner mix

Attio and Whop are named in the opening invitation. The organizer's hosts-and-sponsors section also includes Winner AI and Jack & Jill. Those are listed relationships; the public page does not identify company representatives who will attend or specify sponsorship tiers.

The companies provide a useful operating lens for the gathering. Attio's current product centers on CRM, customer context and revenue workflows. Whop offers infrastructure for building and running businesses, including commerce and payments. Jack & Jill describes separate AI agents for careers and hiring. Customer relationships, transactions and team formation are recognizable founder problems, even when two businesses sell very different products.

That mix gives the conversation somewhere concrete to go. A founder might ask how another team recognized a serious buyer, kept customer context usable as the business grew or decided which work justified an early hire. These are editorial examples of questions participants could bring, rather than an announced discussion agenda or a promise of advice from the partner companies.

Automation adds another layer to those choices. Software can help organize information and execute workflows, while the founder still has to judge whether the customer, candidate or relationship fits the business. A peer can supply the missing context behind a decision: the constraint, the mistaken assumption or the tradeoff that a product description rarely captures.

Andrew Yeung's role in shaping the room

Andrew Yeung's current biography lists him as the founder of Fibe, co-founder of The Shortlist and a partner at Next Wave NYC. The combination connects event building with company formation and early investing. His role at this dinner is verified as host; the investment affiliation does not establish that the fund is sponsoring the gathering or offering capital to attendees.

For a dinner organized around founders who have crossed borders or built through unusual obstacles, the host's framing carries particular weight. An invitation can make room for a fuller account of how a business came together. It can also help an applicant articulate what they could contribute to a conversation beyond the company they are promoting.

The public invitation's emphasis on immigrants and building in a new country is meaningful as an intended audience. It should not be read as a demographic description of every approved guest. The roster remains private, and no claim about its eventual composition is necessary to understand why that starting point may appeal to a founder.

Someone building outside an established local network can use a focused peer conversation to find a point of connection. The exchange becomes more useful when both people can name a specific challenge and explain the work behind it. That possibility is the dinner's editorial interest; the resulting relationships will depend on fit, mutual interest and follow-through.

Before applying for the San Francisco dinner

The official Luma record lists October 15, 2026, with the evening scheduled from 6:30 to 9:00 PM in San Francisco's local time zone. Its General Admission offer currently lists a price of $0, alongside the requirement for host approval. Applicants should use the organizer's registration process for the current admission details and private location, rather than treat a public listing as confirmation of a seat.

A useful application can be brief and specific. Describe the company, the path that makes the invitation relevant and a problem another founder could meaningfully discuss. Avoid making the evening carry an entire fundraising, hiring or sales plan before anyone has agreed to meet.

For founders comparing this dinner with other formats in DevCuration's event coverage, the central choice is how they want to spend their attention. A small meal creates room for a conversation to develop; a technical program serves a different purpose. Selecting the format around the actual problem makes the calendar decision more useful.

The work after dinner deserves some preparation too. A relevant follow-up can remember the question someone was trying to answer and offer something concrete in return. If a conversation at Andrew Yeung's table opens a useful door, the founder still has to carry the context through it and give the next exchange a reason to happen.