Founder and hacker houses
A defined group living or building together for a fixed period.
For Communities
Turn the way your community already helps into a clear program.
Agree the rules and budget before the cohort begins, then give members one private place to ask for help.
A first conversation starts the design work. It does not activate member support.
Cohort program
IllustrativeSponsor view
The approved cohort roster defines who may receive program access.
Sponsor budgetFunded before invitation
Decision authorityAuthorized people
Illustrative only. Every program needs approved terms, funding, and responsible partners.
What you see as an operator
- Members invited and participating
- Approved budget and payment status
- Requests — counts, never health details
People already show up. They should not have to improvise.
Rushed fundraisers
When help starts in a group chat, the outcome depends on who sees the message and how fast people can respond.
Unclear terms
Members should know what the program covers, who decides, and what documents they may need.
Pressure on organizers
A defined process keeps community leaders from making sensitive decisions on the fly.
Why it matters
One private way
to ask for help.
- Clear from the startMembers know what support may be available and how to ask for it.
- Private by designHealth records stay out of group chats, public networks, and sponsor reports.
- Ready before it is neededThe process is agreed before the cohort begins.
The people behind each request
- 01Community operatorConfirms who belongs to the cohort and where members can get help.
- 02Care partnerHelps route care and collect the right documents.
- 03Authorized reviewerMakes the final decision under the written terms.
From design to closeout, one path.
Step 01
Design it
Agree the cohort, terms, roles, and budget.
Step 02
Fund and approve it
Complete funding, legal review, and partner checks.
Step 03
Invite members
Share the written terms and private access path.
Step 04
Support and report
Review requests privately, decide them as people, and report only safe totals.
The offer
Members read the full terms before they join.
The offer explains the support, limits, documents, decision process, and appeal path in plain language.
- Private requestsHealth records and reviewer notes stay away from public networks.
- Ready and fundedThe budget, terms, legal review, and partners are approved first.
- People decideSoftware prepares the request. An authorized person decides it.
Upcoming cohort · ProgramIllustrative
CohortDates and roster agreed
BudgetFunded before invitations
TermsApproved in plain language
RequestsPrivate by default
DecisionsMade by authorized people
Every program is designed for one cohort and its real-world needs.
A strong fit for defined cohorts with fixed dates.
The cohort needs a sponsor, an organizer, and a realistic budget.
Network communities
A recurring cohort with an organizer and sponsor.
Pop-up cities and local groups
A time-bound gathering with clear dates and responsibilities.
Campus and builder collectives
A known roster whose support can be planned before arrival.
Running a company team instead? Nakama for Teams
Operator questions
What community leaders ask first.
The sponsor sets aside the approved program budget before members are invited. The terms name the responsible organizations, limits, and payment process.
The design sprint names who owns the roster, budget, member communication, reviews, payments, and any local care relationships.
After the scope, budget, legal review, responsible partners, and member terms are complete. There is no universal launch timeline.
For communities
Plan the support before the cohort begins.
Start with the people, dates, current process, and budget. We’ll turn them into a program members can understand.
Approved terms before invitations • Private requests • Human decisions