Community collaboration
Co-hosting, venue provision, speaking, education, regional programs, employer or technical communication, and early user feedback are designed around value for participants.
COLLABORATION
Work with Kyoto’s IT community
Miyako de IT creates recurring contact among engineers, companies, universities, public organizations, venues, and other communities. Its 615 connpass registrations are not actual attendance or a pool of available recruits, and no hiring, reach, or proof-of-concept result is guaranteed.
Choose the right relationship
Software, AI, Web3, and digital-transformation work
Netsujo handles commercial implementation, proof-of-concept design, software development, and organizational digital-transformation work under a separate business engagement.
Challenges this relationship can address
Create contact with engineers in Kyoto and Kansai
Use recurring, opt-in events rather than unsolicited access to participant records.
Communicate engineering work and culture
Give technical staff a useful speaking, workshop, or co-hosting role.
Connect research, students, and working engineers
Create an early contact point before a formal industry–academia program.
Ground public-sector digital work in practitioner context
Connect a local government or support organization with people working in technology.
Collect early product feedback
Test comprehension, needs, and intent before committing to a larger proof of concept.
Hold a technology event in a distinctly Kyoto setting
Use a temple, machiya townhouse, university, or another place-specific venue for both outreach and the event experience.
Organizations that are likely to fit
Mid-sized companies seeking technical contact in Kyoto and Kansai
Organizations with a base in Kyoto, Shiga, or Nara that want local opportunities for engineering recruitment or technical exchange.
Universities and research organizations in Kyoto Prefecture
Faculties and laboratories seeking student career contact, an entry point for industry–academia work, or access to practitioners in data science and AI.
Local-government digital-transformation teams
Kyoto Prefecture or municipal teams seeking early practitioner feedback on resident services and regional challenges.
Business teams testing early reactions to new technology or products
New-business teams seeking early user feedback from a Kyoto IT community before proceeding to a proof of concept or development.
Human-resources and communications teams pursuing place-based employer communication
Teams considering expansion from Tokyo-centered recruiting toward Kyoto and Kansai.
When collaboration is not a fit
- The only objective is high-volume hiring in the short term.
- The only objective is direct sales to participants.
- The proposal provides no return to technology, learning, or the region.
- The expected result must be immediate after a single event.
- The community is treated only as advertising inventory.
Eight collaboration formats
Co-hosted event
Jointly design a study group or networking event around a technical or recruiting theme, with planning, outreach, and event-day support. Examples include Kyoto Chiesangyo-sozonomori, XRPL JAPAN, and CRAFT BANK.
Venue provision
Hold an event at an office or facility, creating recognition and direct, opt-in contact with IT practitioners. Examples include Butsugenji, Taisho University Kyoto Academia, Kokando, and Daikoji.
Talk or lightning talk
Create an external speaking opportunity for an engineer, supporting technical communication and personal professional visibility.
Hands-on workshop
Co-host a practical session using a product or technology so recognition and understanding grow through direct use, including Claude Code and WordPress sessions.
Educational collaboration
Connect a university or vocational school with students, internship contact, working engineers, and an entry point for industry–academia work.
Regional exchange program
Design events around regional revitalization, tourism technology, traditional industry and IT, temples and technology, or new activity in Fushimi Ward.
Employer contact
Use an optional company-introduction slot, public Discord job posts, and natural referral contact without direct access to participant records.
Early user feedback
Gather initial reactions around needs, comprehension, and likely use for Web3, AI, or another new product before a larger build or proof of concept.
Participant profile and limits
The public connpass group has 615 registered members. Roles represented in the source include frontend and backend web engineers, infrastructure and SRE practitioners, data scientists and machine-learning practitioners, startup founders and CTOs, freelancers and independent developers, university researchers, and students. Registration is not attendance, consent to sales contact, or evidence that any individual is available for work.
In the fixed registration analysis as of July 17, 2026, the first-registration share is 33.9% and the share registering at least twice is 37.9%. These are registration measures, not event-day attendance.
Experience ranges from under one year to more than 20 years. Participants come principally from Kyoto, with people also traveling from Osaka, Shiga, and Nara, and work with React, TypeScript, Python, AWS, GCP, Web3, AI, and other technologies.
Any direct follow-up requires the person’s explicit agreement. Reporting can cover registrations, non-identifying survey results, and public communication within the agreed scope.
Documented examples
Industry-support organization / co-host
Kyoto Chiesangyo-sozonomori
Co-hosted the recurring IT Engineer Networking Event in Kyoto series at KOIN, including legal and industry–academia sessions.
Direct contact between a prefectural industry-support organization and the local IT community.
Community / joint event organizer
Digital Nomad Kyoto
Jointly designed recurring co-working study sessions at Butsugenji with international and local participants.
International technical exchange in a Kyoto cultural setting.
University / venue and educational collaboration
Taisho University Kyoto Academia
Provided a recurring setting for co-working study sessions, generative-AI study groups, and craft-beer events.
Routine contact among students and working engineers.
Local government / policy relationship
Kyoto Prefecture
Miyako de IT participated in an IT-industry working group and connected operational community knowledge with regional policy discussion.
Practitioner context for public-sector technology programs.
Company / co-host
CRAFT BANK
Co-hosted Brew & Build, combining hands-on development with Kyoto craft-beer culture.
A new event experience connecting technology and local culture.
How a collaboration proceeds
1. Inquiry and initial context
Share the objective, intended audience, timing, and known budget range.
2. Initial conversation, 30–60 minutes
Meet online or in Kyoto, align the purpose and participant fit, and execute a nondisclosure agreement first when necessary.
3. Proposal and estimate
Receive options around one week after the conversation, from a one-off event through a three-year program, with support for internal approval material when appropriate.
4. Agreement, preparation, publication, and delivery
After the collaboration agreement, the teams jointly handle event planning, venue arrangements, announcement copy, connpass registration, outreach, and event-day operations.
5. Event and review
Run the program, publish any agreed report, and review evidence and improvements. A simple event can sometimes launch in two weeks; a full program generally needs three to four months.
Plans and indicative pricing
Three representative plans cover a trial one-off collaboration through a six- to twelve-month relationship. Final scope and pricing are agreed after an initial conversation.
Light co-hosting
JPY 100,000–200,000 / per event
Included
- Event co-hosting
- Announcement support
- Introduction on the day
- Concise report
Not included
- ×Workshop design
- ×Detailed report
A good fit for
A company testing technical or employer communication with the community
Standard co-creation
JPY 300,000–500,000 / per event
Included
- Theme design
- Talk or workshop
- connpass outreach
- Event operations
- Survey design
- Post-event report
Not included
- ×Long-term community operations
A good fit for
SaaS, AI, or Web3 companies, universities, and research organizations
Recommended
Continuing collaboration
JPY 100,000–300,000 / per month for six to twelve months
Included
- Multiple programs
- Discord coordination
- Continuing hiring, proof-of-concept, or education support
- Quarterly review
Not included
- ×Custom software development
- ×Dedicated recruiting agency work
A good fit for
Local governments, universities, mid-sized companies, and regional support organizations
Prices are indicative. Actual scope and pricing are adjusted and proposed individually after an initial conversation.
Products and programs that tend to fit
Developer products and SaaS
Tools, APIs, cloud services, libraries, and frameworks that engineers can use directly in a practical workshop.
Companies recruiting technical staff
Teams prepared to communicate real engineering work and culture without assuming access to participant records or guaranteed hiring.
New technology and early products
Teams that need initial reactions around comprehension, needs, and use intent before a larger proof of concept.
University and education programs
Research, student careers, practical workshops, and early industry–academia contact.
Regional and local-government digital work
Programs that need practitioner context, community outreach, or a separately contracted pilot.
Common questions
How much does a collaboration cost?
It depends on the scope. Venue provision can range from no fee to actual expenses; indicative prices are JPY 100,000–200,000 for light co-hosting, JPY 300,000–500,000 for standard co-creation, and JPY 100,000–300,000 per month for a continuing relationship. A specific amount is proposed individually after consultation.
Can a company outside Kyoto collaborate?
Yes. The source records collaboration with remote-friendly companies and organizations in Osaka and the wider Kansai region. Online co-hosted events are also possible.
What turnout can we expect?
Attendance depends on the format and topic. Historical results are about 10–20 people for co-working study sessions and 20–50 people for networking events. Announcements can reach the connpass group’s 615 registered members, but registration does not guarantee announcement views, reach, applications, or attendance.
How does a collaboration proceed?
The source process is: collaboration inquiry; an initial conversation of about 30 minutes; planning and an estimate; agreement and preparation; then the event and review. A simple event can sometimes be held in as little as two weeks.
Can you organize an event for students?
Yes. The source records collaboration with Taisho University Kyoto Academia. A program can include student participation places and event design that creates internship contact.
What should we prepare before the first conversation?
Preparation is smoother when you can outline the intended outcome, such as employer contact, recognition, or early user feedback; the expected schedule, such as a short campaign or continuing relationship; and the approximate budget approach, such as an unpaid collaboration, paid sponsorship, or joint program. If these points are not settled, the first conversation can organize them.
Who joins the execution team after a collaboration is agreed?
Tomohiro Iida leads planning and operations. When needed, the execution team includes Netsujo Inc. members, contacts at collaborating venues such as Butsugenji and Taisho University Kyoto Academia, and the organization’s own staff. Support covers progress management through Slack or Discord, monthly review meetings, and event-day operations.
How are confidentiality and contracts handled?
A nondisclosure agreement (NDA) can be signed when necessary, including for information shared during planning. A separate collaboration contract can also be used for a long-term relationship. Netsujo Inc. can act as the corporate contracting party and support internal approval and contract processing.
Which collaboration pattern has not worked well?
A relationship that ends with one event sponsorship tends to produce shallow learning and weak continuity for both sides. The source lesson is to design a relationship over six months to three years rather than only one event, and to discuss that longer view from the initial consultation.
📦
LM-1 FREE RESOURCE
Complete IT Community Sponsorship Guide
A practical sponsorship model based on Miyako de IT's operating record
For: Recruitment, communications, and developer-relations teams
Discuss a collaboration
An early conversation can start before the purpose is fully fixed. If possible, note the desired outcome, likely timing, and whether you are considering an unpaid contribution, paid sponsorship, or a separately scoped proof of concept.