Every piece of software a community uses was built for something else.
Group chat was built for friends. Project tools were built for teams shipping deliverables. Social groups were built to sell advertising. Spreadsheets were built for accountants. Each is good at its original job, and community organizers have spent two decades assembling them into something that almost works.
That's the gap we kept running into, and eventually decided to build for.
The pattern we kept noticing
Talk to anyone who runs a club, an association, a choir or a neighbourhood group and the same conversation happens. They aren't short of tools. They're short of a system.
The specifics vary and the shape never does. Attendance lives in a chat thread. The member list is a spreadsheet one person maintains. Documents are in a folder shared by whoever set it up. Nothing knows about anything else, so a volunteer spends their evenings as the integration layer between five apps.
Nobody asks for a community platform. What they ask is "does anyone know how many people are coming on Saturday", every single week, forever.
Three decisions we made early
Most of what Joyn is follows from three choices we made before writing much of it.
Groups are first-class, not tags. Real communities are made of smaller communities: the youth team, the committee, the Thursday walkers, the trip to Berlin. Most tools flatten those into one feed with labels. We gave each one its own channels, events, files and admins, because the structure is the thing that makes a large community feel small enough to belong to.
Members join free, with a link. Not a growth tactic. If joining costs the organization money per person, someone has to decide which volunteers are worth a seat, and we didn't want to build a tool that forces that conversation.
No algorithmic feed. When someone posts that training is cancelled, everyone in that group should see it. Ranking that against a funnier post is a business model, not a feature.
What we deliberately did not build
We think it's more useful to be clear about this than to claim we do everything.
Joyn doesn't do kanban boards, client access, time tracking or deliverable management. If your organization ships client work, a project tool is the correct choice for that side of things, and we'll happily say so. We wrote an honest comparison with Basecamp that includes where Basecamp is simply better.
We'd rather be the obvious choice for one kind of organization than a mediocre fit for every kind.
Where we are
Joyn is built in Odense, Denmark, by a small team, for communities that mostly don't have a budget for software. That shapes the decisions: free to get started, no seat counting, native apps as well as the web, and a strong bias toward removing an organizer's evening admin rather than adding one more dashboard.
There's a lot still to do. We'd rather ship the unglamorous things, like fewer manual steps and less duplicate typing, than the impressive-looking ones.
If you run a community and something here sounds like your Tuesday evening, we'd genuinely like to hear about it. Tell us what you're wrestling with - the awkward, specific, boring problems are the useful ones.