Why groups come apart
Groups rarely break up. They quietly stop meeting.
Almost nobody decides to end a small group. The week gets away from whoever is leading it, the meeting never gets set, two people never hear about it, and a few months later there is nothing left to come back to. What holds a group together is not enthusiasm. It is somebody deciding on purpose what happens this week, and everybody being able to see it. The tools these groups already have are not built for that.
-
Church and member management suites
Planning Center, Breeze and their peers are built to run an entire organization. They are not built to help one volunteer look after a dozen people, and the person leading that group pays for the difference in setup they never asked for.
-
The group chat
A thread is where a group talks. It is not what keeps a group together, which is why the same questions get asked again every week and nothing is findable when it matters.
The people in it
Somebody belongs. Somebody leads. Somebody holds it all together.
-
Shows up and belongs
Member
Opens the app and sees where the group is meeting, what it is working through, and what is on them. RSVPs in one tap, reads the agenda, talks to the group, browses what the group is reading. Joining is tapping an invite and confirming your name.
Cannot publish, invite, or see anything belonging to a leader or an admin.
-
Leads and teaches
Leader
Decides what the group works through, meeting by meeting: the agenda, the resources, who is hosting. Sees who is coming and who came. Invites members and co-leaders, and can hand the group on, because a group should outlast the person who started it.
Leaders set up their own groups. The admin does not do it for them.
-
Holds it all together
Admin
Creates the organization and invites the leaders. Sees every group, whether it is genuinely still meeting, and the alerts derived from that. Moderates anything a member reports, so a leader is not left to handle it alone.
Cannot create a group on a leader's behalf, and is not a participant in group chat.
Roles are enforced at the data layer, not hidden in the interface. What a member is not allowed to read, the database refuses to return.
The rhythm
A week somebody decided, instead of a week that just happened.
-
The leader decides the week
What the group is working through, where it meets, who is hosting. Built from a template, so it is minutes rather than an evening. The bar we build against is under five minutes, repeatedly, without it feeling like admin work, because a leader who dreads the preparation eventually stops doing it.
-
Everyone knows where to be and what is on them
One screen answers the only two questions a member has: what is happening this week, and what am I responsible for. RSVP is a single tap. Nobody has to scroll a thread to find an address, and nobody has a reason not to know.
-
The group carries on between meetings
Group chat attached to the group, and a shared library of what the group is reading or working through. The hour a week is not what makes people close. The six days around it are, and they should not be scattered across three apps.
-
Somebody notices when a group starts slipping
An admin responsible for twenty groups gets attendance and engagement per group instead of a feeling. A group that has quietly stopped meeting is something you want to find in week three, not in month six once people have already drifted off.
The logistics
The small stuff, handled, so the group can be about the people.
None of this is the point. It is what stops the point getting lost. All of it is running today, on iOS and the web.
Meetings and agendas
The group knows what it is working through before it arrives. Drafts stay leader only.
One tap RSVP
A leader knows who is coming without chasing anybody.
Host and snack rotation
The load is shared and visible, instead of landing on the same person every week.
Attendance
Notice early when someone stops coming. Opt in per group, and never the landing action.
Group chat
Realtime, kept with the group, with report and block built in.
Resource library
What the group is reading, kept where the group is. Links and a recommended item, not a CMS.
Calendar subscription
The meeting turns up in the calendar people already check.
Account and data control
Export your data, delete your account, in app.
Not built yet, and switched off rather than half shipped: push notifications and the weekly digest email. Both are designed and both stay dark until real groups tell us they want them. We would rather ship eight things that work than twelve with four of them pretending.
Where we actually are
Weekfold is not open yet.
The app is built and it runs. It is not taking public signups. Accounts are created by invitation while we run the first sessions with real groups, and we would rather say that plainly than put a button here that goes nowhere.
There is one question we have not answered, and it is the only one that matters: will somebody leading a group adopt a dedicated app when their organization already has a church app and a group chat. Nobody settles that with a landing page. It gets settled by a handful of leaders running their actual group on it for a few weeks and telling us the truth.
Who we are looking for
A church, club, nonprofit or professional network running several recurring groups, and one leader willing to put their real group on Weekfold for a few weeks and be blunt about it.
Early access
If you lead a group, we want to hear from you.
Tell us what kind of group, how many of them, and what is hardest about keeping people showing up. That is enough to start a conversation.
That button opens your mail app with a short note already written. There is no form on this page, no mailing list and no automated follow up, because we have not built any of that yet and a box that quietly swallows your address would be worse than none.