How to Start an IT Community on connpass: A Kyoto Case That Grew from 2 People to 615 Members [2026]
![How to Start an IT Community on connpass: A Kyoto Case That Grew from 2 People to 615 Members [2026]](/blog/connpass-start.jpg)
Key points (30-second read)
- Conclusion: connpass is a standard platform for IT study groups where group creation, event publishing, and participant management are all free.
- There are six steps: create a group; begin with a co-working study session; secure a venue; write the announcement; recruit; and continue monthly.
- 3–5 people are enough for the first event. Kyoto's Miyako de IT started with two people and grew over 7 years and 165 events to 615 members.
- The three main failure patterns are starting too big, overdesigning the event, and carrying everything alone.
Many people have thought, “There is no community in my area where IT engineers can gather casually.”
Launching an IT community is not as grand an undertaking as it may sound. You do not need a large study group or a sponsored event from the outset. You can begin small, and connpass is a convenient service for doing so.
What is connpass?
connpass is a platform designed for IT study groups and events. It suits the early stage of a community for three reasons.
1. People already use it to find IT events.
2. It supports ongoing operation organized around a group.
3. It provides enough publishing capability for a new group.
STEP 1: Create a group
First, establish a visible fact: “this community, on this theme, exists in this region.” Choose a group name that communicates its purpose at a glance.
STEP 2: Start the first event with a co-working study session
No speaker is required, no presentation materials are required, and preparation is light. Whether in a regional area or a major city, what matters first is not extravagance but the ability to hold the second event.
STEP 3: Write an event page that explains why people should register
At minimum, state what the event is, who it is for, what to bring, whether late arrival is allowed, and whether beginners are welcome.
STEP 4: Choose a venue you can keep using
Prioritize access, Wi-Fi and power, whether the space works with a small group, and whether the organizer can continue renting it without strain.
STEP 5: Recruit reliably rather than broadly
Trying to attract a large crowd for the first event is a mistake. 3–5 people are enough.
STEP 6: Continuity creates a community
Holding one event does not create a community. Set a manageable rhythm of about once per month.
Common mistakes
- Trying to start too big
- Overdesigning the event
- Taking on everything alone
- Letting attendance numbers dictate every decision
Conclusion
connpass makes the act of launching an IT community straightforward. Start small and continue; the community forms afterward.
Related links
Related articles
15 Active IT Engineer Communities to Join in 2026
A 2026 catalog of 15 communities for IT engineers—nine nationwide and six regional. Based on 7 years and 165 events of community operations in Kyoto, it covers choosing by learning, networking, speaking, or region; four steps to a first visit; and common questions. The order is not a ranking, and each community's 2025–2026 activity was checked against primary sources such as official sites and connpass.
How Corporate Sponsorship Supports IT Communities: Benefits and Process
More companies are sponsoring IT communities for recruiting branding and technical communications. Based on operating a Kyoto community of 615 members for 7 years and 165 events, this guide covers benefits, partnership options, process, and failure patterns.
A Practical Guide to the TEMPLE Model: From Launching an Internal Community to Sustaining It
The TEMPLE model was systematized through 7 years, 165 events, and 615 community members in Kyoto. This definitive guide brings its six pillars—Theme, Environment, Members, Persistence, Local, and Evolution—together with five steps for launching an internal community and practical knowledge for venue design, turning participants into supporters, continuity, external collaboration, and evolution.
Source data
The figures cited in this article are based on primary data in the Miyako de IT annual statistics report. It publishes yearly event counts, venue distribution, and event-format data.
Written by
Tomohiro Iida