Events create proximity. MeetWho helps people understand why they may want to meet, choose whether to connect, and carry useful context forward after the event.
People, not attendee lists.
The number of people in a room says little about whether anyone found the context, confidence or next step to begin a useful professional relationship.
Event software has become very good at the logistics: pages, registrations, reminders, tickets and check-in. Professional networks have become very good at showing us more people. CRMs have become very good at turning relationships into records.
Yet the moment that matters is still often left to chance: Who might be worth meeting? Why? Would both people welcome the introduction? What happens after the room closes?
MeetWho is built for that gap.
What those numbers miss
The standard we are building toward
A useful reason to begin matters more than another directory of faces.
Visibility, introductions and contact sharing should remain separate, reversible decisions.
The relationship should keep its context when the room, call or webinar ends.
These principles guide what we build, what we measure and what we refuse to trade away.
What we believe
Registrations can tell an organizer who arrived. They do not tell an attendee where a valuable conversation could begin. We believe the value of a professional gathering should include the relationships it helps make possible.
What this means in MeetWho
MeetWho focuses the networking experience on a smaller set of potentially relevant people and the reasons a conversation may be useful.
What we believe
A recommendation should show the context behind it. It should never become a verdict on two people. A model may suggest; people decide what happens next.
What this means in MeetWho
MeetWho shows a plain-language “Why”, lets people dismiss a suggestion, and does not send an introduction in their name without an explicit action.
What we believe
Identity, workplace and attendance are different signals. Each can confirm something specific; none proves character, compatibility or intent.
What this means in MeetWho
MeetWho names the source and scope of each trust signal. A LinkedIn sign-in is shown as a connected account — not as identity or workplace verification.
What we believe
Registering for an event should not automatically grant strangers access to a person. Discoverability, introduction requests, contact sharing and calendar availability are different choices.
What this means in MeetWho
MeetWho treats event networking as a separate, event-scoped decision. A useful introduction is mutual by design, and block or report controls remain available.
What we believe
Relationship memory should help you show up with care: where you met, why the conversation mattered and what you said you would do next. It should not reduce another person to inventory in a pipeline.
What this means in MeetWho
Private relationship notes are not shared with other attendees or organizers. Organizer reporting is designed around aggregate event outcomes — not access to private memory, messages or individual declines.
What we believe
Events create proximity. Lasting value comes from a thoughtful follow-up, a shared next step and context people can return to. Continuity should be easier without manufacturing urgency.
What this means in MeetWho
MeetWho connects mutual relationships to private context, follow-up and a next step such as a message or a scheduled meeting — subject to each person's choices.
Here is how context, choice and continuity show up today.
See the event-specific context behind a suggestion before deciding what to do.
Product preview
Maya Chen
Product lead · Demo profile
Why you may want to meet
You both listed onboarding research as this event's focus, and Maya is speaking in the session you saved.
An introduction can move forward only through the choices and visibility rules that apply to both people.
Product preview
Introduction request
Waiting for both people to agree before contact details are shared.
Email and phone stay hidden until both people choose to share them.
Keep the context you need for a thoughtful next step without exposing private relationship memory to the room or its organizer.
Product preview
Private note
Met at the design track. Wants a walkthrough of our activation flow in September.
Not shared with other attendees or organizers. Organizers see aggregate event outcomes only.
Every product rewards something. We choose mutual, understandable and useful interaction over volume for its own sake.
We will not rank human worth.
We will explain why a conversation may be relevant.
We will not automate consent.
People decide whether an introduction moves forward.
We will not trade access to private people.
Payment should improve preparation and follow-through.
We will not expose private relationship memory.
Organizers should see aggregate outcomes, not personal context.
We will not present authentication as verification.
Every trust signal should say exactly what it confirms.
Our pricing principle follows from the same rule: pay for better context and follow-through — not access to people.
Attendees
You should understand why a recommendation appeared, control whether you are discoverable, decide whether to connect, and keep private relationship context out of the event's reporting layer.
Attendee controlsOrganizers
You should be able to understand whether an event created useful networking outcomes — without reading private notes, private messages or individual decline reasons.
Organizer outcomesMeetWho
We should make the rules visible, keep important choices reversible, and design the system so that revenue cannot quietly override consent.
See how recommendations work, what choices people keep, and how we protect the context they carry forward.
Our standard is simple: give people useful context, preserve their choice and make the next step easier. We will keep measuring MeetWho against that standard.
Yağız Gürbüz
Founder, MeetWho
Version 1.0 · Last reviewed August 2, 2026
