The event was full of interesting people. You had several good conversations. A week later, you cannot remember which person offered to review the prototype, which one needed a resource, or whether anyone actually agreed to a follow-up.
That is an operating problem, not a reason to dismiss founder events. A useful room can help you understand a market, meet a collaborator or improve a decision. The value depends on how you choose the room, participate and carry the conversation forward.
This is a practical guide for attending events. It does not claim that attendance produces customers, investors or partnerships, and it is not a retrospective account of a Foundshore event.
Give the event one primary job
Before registering, write what you hope to learn or move forward. Possible jobs include understanding a purchasing process, meeting people interested in a shared project, hearing how operators solved a particular problem, or reconnecting with an existing community.
Avoid an objective such as “network with everyone.” It produces no basis for choosing sessions or deciding which conversation deserves more time.
A more useful objective might be: “Find out who owns deployment approval for this kind of hardware.” You can make progress even if nobody becomes a sales lead. A relevant answer can improve research, product planning and the next set of introductions.
Keep a secondary objective, such as meeting peers, but do not require every social interaction to justify itself commercially.
Choose the room by its working format
Look beyond speaker names. Examine the stated audience, agenda, discussion format, expected preparation and opportunities for actual conversation. A large conference, a technical workshop and a small founder roundtable can all be worthwhile, but they serve different tasks.
Check whether attendees are primarily buyers, builders, investors, students, service providers or a mixture. Public event descriptions are imperfect evidence, so treat uncertain audience fit as a question rather than a fact.
Consider the full cost: travel, time away from the company, preparation and follow-through. A nearby focused session may fit an immediate research need better than an impressive event that consumes several working days. That is a task-specific judgment, not a ranking of event brands.
Prepare a question and a contribution
Prepare a short explanation of what you are working on. Include the customer and problem before the technical detail. The goal is to make a conversation possible, not deliver an unsolicited pitch.
Also prepare something useful to contribute: a relevant observation, a resource you can share, a specific question or an introduction you are genuinely able to offer with consent. Contribution should not be a disguised obligation for the other person to hear your sales message.
Bring only the materials that fit the setting. A small demonstration or one-page problem brief may help. Opening a full deck in the middle of an informal conversation may not.
Listen for the actual relationship
Not every relevant person is a prospective buyer. They may be a peer, mentor, potential collaborator, supplier or someone who simply knows the context better than you do.
Ask about the work they actually do and the part of the problem they have seen. Do not equate title with authority or a friendly conversation with purchase intent.
When someone describes an issue your product may address, ask a clarifying question before switching to a pitch. The useful next step might be sharing a method, seeing a sample, arranging a separate discussion or doing nothing further.
Respect the event’s purpose. A discussion designed for candid peer learning should not become a place where every admission of difficulty triggers a sales approach.
End a worthwhile conversation with a precise agreement
A good follow-up is small, specific and mutual. “May I send the checklist we discussed?” is clearer than “Let’s connect.” “Would a short call next week help compare the two approaches?” is clearer than assuming that someone owes you a meeting.
Record what was agreed, the context and the preferred contact route. Do not add private observations or sensitive disclosures to a broadly shared CRM merely because the person spoke openly in the room.
When an introduction involves a third person, ask before sharing details or making the connection. You can offer to seek permission without implying that access is already available.
Respect the rules of the room
Some discussions allow attribution, some allow use of information without identifying speakers, and some are off the record. These are different conditions.
The Chatham House Rule permits participants to use information received while withholding the identity and affiliation of speakers and other participants. It is not the same as a blanket prohibition on using the information. Follow the organizer’s actual stated conditions rather than applying a familiar label loosely. 1
Ask permission before recording or using automated transcription. If you later write an article, confirm attribution and context with the relevant people. An event admission or badge does not authorize publication of someone’s confidential business situation.
Turn notes into a small follow-through queue
After the event, separate three kinds of notes: commitments you made, questions to investigate, and relationships to maintain. Do not classify every contact as an active opportunity.
Note | Appropriate next action |
|---|---|
You promised a resource | Send the specific material with the original context |
Someone agreed to examine a sample | Confirm the sample and a suitable review arrangement |
A market assumption was challenged | Add a research task and preserve the source’s limits |
A peer conversation was enjoyable | Stay in touch without manufacturing a sales reason |
No further contact was agreed | Do not automatically enroll the person in a sequence |
A short follow-up should make it easy for the recipient to remember the conversation. Avoid attaching unrelated material or turning one agreed exchange into a series of escalating requests.
Evaluate progress after the follow-through
Measure whether you completed the commitments, improved your understanding or advanced an agreed conversation. Contact count is an activity measure, not evidence of customer value.
A founder might leave with no demo bookings but discover that the intended buyer does not own the budget. That is useful research. Another might schedule several calls that never address a real decision. The visible activity is higher, but its meaning is different.
Use what you learned to choose the next event and prepare better questions. Do not conclude that an entire community is irrelevant because one room did not meet your expectations; inspect audience fit, preparation and participation separately.
The best next step may be another conversation, a changed product assumption or a decision to stop pursuing a weak direction. An event becomes valuable when its information and relationships continue into thoughtful work—not when the badge joins a collection on your desk.
Sources and research scope
[1] Chatham House Rule — Chatham House. Official discussion rule. Reviewed 2026-10-04. Non-attribution is not a blanket ban on using information. Consent and organizer rules still govern event documentation.
