On this page
Choose one purpose for each event, prepare a short introduction and follow up on the conversations that were genuinely useful.
Choose a format that fits the goal
An informal meetup suits peer conversations and a first introduction to a community. A workshop is more useful when you want to practise a specific skill. A conference can combine talks and many planned meetings, but requires more preparation and a larger time commitment.
Do not choose only by audience size. If you need feedback from five product managers, a small relevant gathering can be a better experiment than a large general event. Ask who the format is designed for and whether you can realistically meet them.
Where to look
Our Community Events page lists Estonian Startup Community meetups and workshops, including individual event pages with venue information and registration links. Past events remain available as an archive; their dates are not invitations to register again.
Latitude59 is an organiser to follow for its Tallinn event. Tehnopol publishes its own activities and programmes. For an event outside Tallinn, sTARTUp Day is associated with Tartu, so check travel as well as tickets. These organisations are independent; use their own sites for current schedules.
Sources: Latitude59; Tehnopol; sTARTUp Day
Prepare before arriving
Write a two-sentence introduction covering what you are building and the problem you want to discuss. Have a simple product link or short demo available, but do not assume every conversation should become a pitch.
Check the location, local start time, entry conditions and registration status. For any discount or venue perk, use the conditions on the particular event page rather than assuming it applies to all community gatherings.
- One objective and a realistic number of conversations.
- A short introduction without unexplained jargon.
- Two questions you would genuinely like answered.
- Confirmed registration where required.
Make conversations specific
A useful opener could be: 'We are testing onboarding for small accounting teams. Have you seen where that process usually breaks?' It gives the other person a clear way to help or say they are not the right contact.
Ask before launching a demo, requesting an introduction or adding someone to a mailing list. Exchange details with permission and note the agreed next step. Listening for a concrete problem usually produces more useful information than repeating a memorised deck.
Follow up with context
Mention where you met, the topic and the action you agreed. Send the relevant item rather than a large collection of links. A suggested message is: 'Good to meet you at the meetup. Here is the onboarding example we discussed. Would next week work for the short feedback call?'
This is an example, not a script to send to everyone. If there was no agreed next step, avoid repeated requests. Respect a lack of response and keep community interactions useful rather than transactional.
Review the outcome
Measure useful follow-ups, customer insight and completed next steps rather than business cards collected. After a few events, compare formats and adjust your time investment.
For our next gathering, open the live events listing and select the event page. Join the community chat for discussion between meetups. An event registration does not imply investor access, a funding commitment or membership in another organisation.
Sources and review
Official sources checked on 16 September 2026. Programme terms and schedules can change. Check the provider's website before acting. Worked examples are illustrative, not client results.


