Builder co-working sessions: the 'no talks, just building' format
· buildtolaunch
This guide is for a student, club lead or community organizer who wants to run a builder co-working session where nobody gives a talk. You get the format, a minute-by-minute schedule, a one-page set of host rules and the mistakes that turn a work session into a meetup. For the wider picture, see the full guide to build days and builder communities.
Short answer
A "no talks, just building" co-working session is a three to five hour event where everyone works on their own project in the same room and shares what they made at the end. The loop is build, iterate, distribute. The host needs a room, Wi-Fi, power sockets, a timer and a clear goal for the room, such as "everyone leaves with a link to share."
Where the format comes from
The format is BuildStuff, a co-working session for builders started by Kỳ Nam. The idea, told in the essay BuildStuff: no talks, just building, is that most builder events spend their hours on speakers and networking while the actual building happens somewhere else. A BuildStuff session reverses this: the room exists so that people can work. buildtolaunch members have hosted sessions. For what a session looks like from an attendee's side, read BuildStuff: builder co-working sessions in Saigon.
This page is the host's version: how to run one yourself, in any city, with no budget.
The three-part loop
Every session repeats three activities. Put them on the wall so people know what each hour is for.
- Build. Each person works on their own project: an app, a landing page, a tool, a post series. Nobody assigns topics.
- Iterate. People show what they have to a neighbour, get one reaction, and fix the biggest problem. Quick feedback is the main reason to work in a room instead of at home.
- Distribute. People put the result in front of real users: send the link to the ten people who have the problem, post it, or submit it to a launch board. This is the step most builders skip when alone, so schedule it.
When to choose a co-working session
| Choose this if | Choose something else if |
|---|---|
| You have never hosted an event | You want a prize and a competition (try a hackathon) |
| You want the same people to return weekly | Your group has never built anything and needs a guided first app (try a vibe-a-thon) |
| You have no budget, no speakers and no sponsor | You want to show finished work to an audience (try a demo day) |
| Members have different skills and projects | Everyone must build the same thing |
Five people who come every week beat fifty who come once.
Plan the session
Pick the goal for the room
One sentence, said out loud at the start. Good examples:
- "Everyone leaves with a link someone else can open."
- "Everyone posts one launch before we finish."
- "Everyone sends their project to three people who have the problem."
A goal for the room is different from each person's own goal. Both matter. Ask each person to say theirs in one sentence when they arrive.
Choose a room
You need Wi-Fi that survives 20 laptops, one power strip per table, and chairs people can sit on for four hours. A cafe, a co-working space, a classroom or a company's spare meeting room all work. Ask the venue about quiet hours, closing time and whether you must order food or drinks. Do not assume; ask in writing.
Open registration
Use a free tool such as Luma. According to Luma's help center, a host can turn on approval for each registration, set a capacity limit and let people join a waitlist after capacity is reached. For a co-working session, capacity and a waitlist matter more than approval: match the number of seats to the room, and let the waitlist fill no-shows. Add one registration question: "What will you work on?" It tells you who is a builder and gives you a starting list for the show-and-tell.
A schedule you can copy
This runs for four hours. Shorten the build block for a three-hour session.
| Time | What happens | Who talks |
|---|---|---|
| 0:00 to 0:10 | Welcome, goal for the room, three rules | Host |
| 0:10 to 0:20 | Each person says what they will finish today, in one sentence | Everyone, 10 seconds each |
| 0:20 to 2:20 | Heads-down build, with a short break halfway | Nobody, unless asking for help |
| 2:20 to 3:10 | Iterate: swap laptops with a neighbour, give one reaction | Pairs |
| 3:10 to 3:40 | Distribute: share, post, send | Nobody |
| 3:40 to 4:00 | Show-and-tell: one minute each, a link or a screenshot is enough | Volunteers |
Notice what is missing: a keynote, a panel, a sponsor pitch. If a partner wants a mention, give them thirty seconds in the welcome.
Rules the host reads out
Keep these to three, and say them aloud:
- Be kind. Feedback is about the work, not the person.
- Show your work. Rough is fine. A half-finished link beats a perfect idea.
- Help the person next to you. If you know the answer, answer. If you do not, say so.
For anything longer, such as how to handle harassment, write a short code of conduct before the first session and share it on the registration page.
The host's job during the session
The host builds too, but keeps an eye on three things:
- People stuck for more than 15 minutes. Introduce them to a neighbour who has solved something similar.
- People who have not spoken to anyone. Pair them for the iterate block.
- The clock. Call each block aloud. Without a timer, the distribute step is the first thing to disappear.
What to do afterwards
Most sessions lose their value the next morning. Within 48 hours:
- Post who built what, with links.
- Announce the date of the next session. Better, announce it at the end of this one.
- Ask each person to post one line in the group chat on what they will do this week.
If members want a weekly deadline between sessions, buildtolaunch's Launch League is a public board where members post launches, and it resets every Monday. Members can also keep working in project Spaces with an AI teammate. Both are free.
Common mistakes
- Adding "one short talk." It never stays short, and it tells people the room is for listening.
- No distribute block. People finish the session with work on a laptop and no users.
- Making it a one-off. A single session is an event. A weekly one is a community.
- Hosting alone every time. Rotate hosts so the format outlives any one person.
Where buildtolaunch can help
buildtolaunch is a free community for university students, open to any major, with no coding needed to start. Your attendees can learn from 70+ free courses before the session, build in project Spaces with an AI teammate and post to the weekly Launch League. Upcoming events are listed on the Events page. If you want to turn sessions into a student club, read how to start a tech or builder club at your university. Members can sign up here.
Read the full guide: build days and builder communities.
FAQ
What is a "no talks, just building" session?
It is a co-working event where everyone works on their own project in one room and shares results at the end, with no keynotes or panels. The format comes from BuildStuff, which was started by Kỳ Nam. The loop is build, iterate, distribute.
How long should a co-working session be?
Three to five hours works for most groups. Under three hours, people spend most of the time settling in. Over five, energy drops. Keep at least 90 minutes of uninterrupted build time and a fixed slot for sharing.
How many people should I invite?
Match the number to the room: one seat, one power outlet and enough Wi-Fi for each person. Fifteen to thirty is a manageable size for a first-time host. Set a capacity and a waitlist when you register people, so empty seats get filled.
Do attendees need to code?
No. Attendees only need a project or a small problem to work on. AI and vibe coding tools now write most of the code for small products, so people from marketing, law, design and other majors can build too.
What if nobody wants to share at the end?
Make sharing small and normal: one minute, and a link or a screenshot is enough. Ask for volunteers first, then ask each table to nominate one person. The host going first with something unfinished also helps.
Can a co-working session replace a hackathon?
Not exactly. A hackathon adds a deadline, teams and a prize, which suit people who want a challenge. A co-working session builds a weekly habit and suits mixed skill levels. Many communities run sessions every week and a hackathon or build day once a term.