Your First 90 Days As An AI Tinkerers Organizer

Status: Canonical public guide for launching and establishing an AI Tinkerers chapter.

Your first goal is simple: run one useful event each month for three months.

Do not start by trying to build the largest meetup in your city. Start by building a room that serious AI builders want to return to: live work, short demonstrations, honest implementation detail, and people who contribute more than a business card.

What You Are Building

AI Tinkerers is not a general networking group. It is a selective, capacity-limited community for leading innovators who are actively pushing AI forward through real projects, experiments, research, tools, and systems.

Your job is editorial as much as operational. You choose the work that goes onstage, curate the mix of people in the room, and protect a format where builders can share unfinished work, useful failures, hard problems, and what they learned.

Selection is meritocratic. Look for evidence of active work, relevance to the program, and likely contribution. A famous title does not guarantee entry. An unfamiliar builder with a real experiment may be exactly who the room needs.

The Operating Rhythm

For the first three months:

• put one event on the calendar each month;
• use one room and one program track;
• recruit three or four strong live demos;
• keep talks short enough for technical questions and discussion;
• review registrations before accepting people; and
• publish the event through the AI Tinkerers platform.

A consistent monthly heartbeat matters more than a complicated launch. Three consecutive events give local builders a reason to trust that the chapter will still exist next month.

Event One: Establish The Standard

Set the date three to five weeks out. Secure a room that fits a focused, conversational event. Publish the page as soon as the date and venue are real enough to share.

Recruit the demonstrations directly. Ask people you respect:

What are you building right now that you could show live for five to ten minutes—including what broke or surprised you?

Choose work with technical substance. A rough system that exposes an important problem is often more useful than a polished product pitch.

A practical two-hour shape is:

1. Welcome and format reminder.
2. Three or four short live demos with technical questions.
3. One room-wide discussion around the hardest shared problem.
4. Time for builders to continue the technical conversations.

The first event succeeds when people understand the standard and at least a few strong builders want to demo or help with the next one.

Event Two: Build Continuity

Announce the second date before the first event ends, or as soon afterward as possible. Follow up with the builders who contributed the most useful questions, demos, or introductions.

For event two:

• invite one or two people from event one to take a larger role;
• recruit at least one demo from outside your immediate circle;
• preserve the live-demo and implementation-detail standard; and
• note which topics are becoming locally distinctive.

Do not solve a weak program by accepting more people. Improve the work onstage and the mix in the room.

Event Three: Make The Chapter Repeatable

By event three, the chapter should no longer depend on one organizer doing everything.

Identify people who reliably:

• find or give strong demos;
• welcome builders without turning the event into generic networking;
• handle details and follow through;
• ask technically useful questions; and
• put the work and the room ahead of being the main character.

Give those people concrete roles: speaker outreach, venue, check-in, photography, recap, or the next event page. A good co-organizer is a builder-host with taste and reliability, not simply the loudest person in the room.

How To Review Registrations

Organizer review is an intentional part of the event, even when a room is not full. Consider:

• what the person is actively building, researching, or testing;
• how closely that work fits the event;
• what they may contribute through a demo, question, review, or collaboration;
• whether the room already has too much of one perspective; and
• actual venue capacity.

Platform scores and research can provide context. They are advisory, private organizer inputs—not automatic admission decisions. Review the evidence and make the call yourself.

Be honest about capacity. AI Tinkerers is exclusive in practice because the format needs a focused room and resources are limited. Explain the purpose and selection criteria; do not manufacture scarcity or confuse professional status with merit.

Sponsors In The First 90 Days

A sponsor can help with venue, food, tools, credits, infrastructure, or technical expertise. The strongest sponsor is useful to builders and respects organizer control of the program.

Because sponsors support the community, it is reasonable to give them more format latitude than an ordinary presenter. The best sponsor segment is usually a technical person showing something genuinely interesting the team built, where the sponsor’s product is naturally part of the story. It should teach or inspire an audience of builders rather than explain value props, product differentiation or high-level non-technical content. If the sponsor only needs a brand moment, use a quick elevator pitch rather than a presentation and allow an optional QR code for credits, a giveaway, or another opt-in offer.

If the sponsor contact sends a colleague to speak, brief the actual presenter directly and agree on the format before the event. Do not expect the sponsor liaison to enforce an outsider’s unfamiliar format rule inside their own company. Cash still does not buy attendee data, acceptance decisions, or private participant access. Do not promise pricing, deliverables, promotion, or access on behalf of HQ.

For the approved local coaching path, use Funding Your First Meetup: Sponsor Coaching for New City Organizers. For hackathon sponsor boundaries, use the AI Tinkerers Hackathons — Sponsor Overview.

Use The Platform For The Repeatable Work

The platform supports event pages, registration review, organizer communication, speaker promotion, and other repeatable workflows. You remain responsible for the date, room, program, curation, speaker quality, and in-person experience.

Use the Quick Start Tools page for direct links to banners, speaker cards, sponsor materials, Luma, check-in, name tags, stickers, recording gear, media upload, and post-event tools.

Use only the features that are currently available to your chapter. If a workflow or permission is unclear, ask through the organizer support channel rather than promising a capability to a speaker, venue, or sponsor.

Your 90-Day Scorecard

At the end of three months, ask:

• Did we run three useful events on a roughly monthly cadence?
• Did each event feature real demos or technical work rather than pitches?
• Are strong builders returning, contributing, and proposing future demos?
• Is registration review based on work, fit, contribution, and capacity?
• Have we found at least one reliable co-organizer or operating partner?
• Do we already have the next date, room, and first speaker leads?

Attendance is context, not the sole measure. A smaller room with excellent work and repeat contributors is a stronger foundation than a large room built around passive networking.

The Minimum Viable Next Event

If the chapter feels stuck, return to five things:

1. A date.
2. A room.
3. A public event page.
4. Three or four live demos.
5. An organizer who protects the standard.

Run that event. Then do it again next month.