Church App — Product Vision

A mobile-first, member-focused platform for church movements and denominations. For most churches, this is all you need. No separate church management tool. No spreadsheets. A place where church life happens on your phone — with a backend that handles the rest.

Core Philosophy

The member is the user, not the admin. Existing tools like ChurchTools optimize for the back-office — volunteer rosters, resource booking, accounting. This app optimizes for the person sitting in the pew, joining a small group on Wednesday, or giving during the livestream on Sunday. Admin features exist, but they serve the member experience, not the other way around.

For most churches, the app IS enough. The dirty secret of church management tools is that most churches don’t need them. A 150-person church doesn’t need a volunteer rostering engine — they need a group chat and a shared calendar. A 300-person church doesn’t need resource booking software — they need one person with a key and a phone. The app, combined with its backend admin platform, covers what 80% of churches actually need day-to-day. The remaining 20% of admin complexity is either unnecessary or solvable through API integrations.

Three tiers, one platform:

The key insight: the backend admin platform is not an afterthought — it’s a first-class product. It’s the desktop/web companion where church admins manage people, create events, publish news, configure groups, review giving reports, and moderate content. It’s lightweight, focused, and doesn’t try to be an ERP. It’s the admin UI that serves the member app.

One app per movement, not per church. ICF Zürich, ICF Basel, ICF München — one app, one identity, shared infrastructure. Events, news, and content can live at the denomination level, the church level, or the group level. This is fundamentally different from Communiapp or Donkey Mobile, where each church gets an isolated app.

Groups and events are the backbone, not a feature. Everything in church life connects through groups and events. A Sunday service is an event. A small group is a group. A volunteering team is a group. A creative night is an event belonging to a group, containing sub-events (workshops) linked to sub-groups (video team, photo team). The data model must reflect this reality natively.

Feature Categories

1. Communication & News

The central nervous system of church life. News flows at multiple levels — not just top-down from “the church” but from every group, every event, every context the member is part of.

Core capabilities:

• Multi-level news feed — denomination → church/location → group → event. A member sees a unified, prioritized feed of everything relevant to them.
• Push notifications — configurable per level (denomination, church, group). Members choose what they get notified about. Churches can send targeted pushes.
• Official announcements — distinguished from regular posts. Pinnable, timestamped, with read receipts optional.
• Rich content — text, images, video embeds, links, polls, file attachments.
• Scheduled publishing — draft and schedule posts ahead of time.
• Notification settings — granular per group, per type (announcements only, all posts, muted).

USP vs. competitors:

• Communiapp has a flat feed per church. No hierarchy, no denomination layer.
• Donkey Mobile has a personalized timeline but no multi-level architecture.
• ChurchTools has no real news/feed concept at all.
• This app: True multi-level communication. A member of ICF Zürich sees ICF movement news, ICF Zürich church news, their small group posts, and their volunteer team updates — all in one contextual feed, with clear hierarchy and filtering.

2. Pinboard / Blackboard

A community marketplace — the digital equivalent of the notice board in the church foyer.

Core capabilities:

• Categories — offers, requests, recommendations, prayer requests, lost & found, housing, jobs, etc. Customizable per church.
• Scoped visibility — church-wide or group-specific pinboards.
• Expiring posts — auto-archive after configurable period (e.g. 30 days).
• Contact via chat — respond to a pinboard post through in-app chat, no phone number exchange needed.
• Moderation — admins can approve, flag, or remove posts.

USP vs. competitors:

• Communiapp has a pinboard feature — it’s their strongest asset.
• Donkey Mobile and ChurchTools have nothing comparable.
• This app: Pinboard exists at multiple levels (denomination, church, group) and integrates with chat. A member can post “looking for a ride to the retreat” in their small group pinboard or “offering free piano lessons” on the church-wide board.

3. Giving

Digital giving that works for Switzerland and Europe — not just NL/DE payment rails.

Core capabilities:

• In-app giving — one-time and recurring donations.
• Multiple funds — general tithe, building fund, missions, specific campaigns. Configurable per church.
• Swiss payment methods — TWINT, Swiss QR-Bill, PostFinance, credit cards.
• European payment methods — SEPA direct debit, iDEAL, Bancontact, PayPal, credit cards.
• QR code giving — scan during service for quick in-moment giving.
• Guest giving — web fallback for visitors without the app.
• Giving history — personal dashboard with tax-relevant annual summaries.
• Campaign progress — visual goal tracking for fundraising campaigns.
• Zero or minimal platform fee — the church receives what was given.

USP vs. competitors:

• Donkey Mobile has strong giving but only NL/BE payment methods (iDEAL, Bancontact, expanding to PayPal/CC). No Swiss rails.
• Communiapp has no giving at all.
• ChurchTools has no giving at all.
• This app: First church app with native TWINT and Swiss QR-Bill support. Multi-currency, multi-method, designed for the Swiss and broader European market from day one.

4. Sunday (Service Experience)

The Sunday service is the heartbeat of every church. The app should make Sunday better, not replace it.

Core capabilities:

• Livestream integration — embedded YouTube/Vimeo streams, or native streaming.
• Live interaction layer:
  • Bible verse references (tap to read in-app)
  • Sermon slides / presentation sync
  • Links to external tools (Kahoot, Slido, Mentimeter) or native live polls/votes
  • Live prayer wall — submit prayer requests during the service
  • Real-time reactions (subtle, not distracting — think faith/hope/love, not emoji spam)
• Personal sermon notes — take notes during the sermon, linked to the specific service/date/speaker.
• Sermon archive — browse past services by date, speaker, topic, series.
• Series & topics — organize sermons into teaching series with artwork and descriptions.
• Podcast feed — auto-generated from sermon recordings, subscribable in Apple Podcasts / Spotify.
• Speaker profiles — who preached, their bio, other sermons by them.

Data model: A Sunday service is a special event type. It belongs to a church (location) and optionally to a series. It has a preacher (person), a topic, media (video/audio), and can have live interaction elements attached.

USP vs. competitors:

• Donkey Mobile has basic video embedding and devotional content. No live interaction.
• Communiapp has video embedding. No sermon archive, no notes, no live features.
• ChurchTools has service planning (for the worship team), not service experience (for the member).
• This app: The only platform where a member can watch the livestream, follow along with slides, take personal notes, respond to a live poll, and submit a prayer request — all without leaving the app. And after Sunday, the sermon is automatically in the archive with their notes attached.

5. Events

Events are everywhere in church life — services, retreats, workshops, conferences, outreach activities.

Core capabilities:

• Event views — “My events” (registered/attending), “Recommended” (based on group memberships), “All events” (discovery).
• Event types — customizable per church. Examples: Sunday service, small group meeting, workshop, retreat, conference, community night, outreach, prayer meeting.
• Event ↔ Group relationship — an event can belong to a group (or multiple groups). A creative night is an event of the creative community group. Sub-events (workshops) belong to sub-groups (video team, photo team).
• Event hierarchy — parent events with child events. The creative night contains workshops. A conference contains sessions.
• Registration & RSVP — with capacity limits, waitlists, and forms.
• Ticketing / paid events — for retreats, conferences, camps (integrates with payment).
• Calendar integration — export to personal calendar (iCal/Google Calendar).
• Event-scoped communication — posts and updates within an event context.
• Recurring events — weekly small group meetings, monthly community nights.
• Location — physical address with map, or “online” with link.

USP vs. competitors:

• All competitors have basic event calendars. None model the event ↔ group ↔ sub-event relationship.
• This app: If you’re in the video team (a sub-group of the creative community), you see the video workshop (sub-event of creative night) in your “My Events.” But you also see the creative night itself, because your group is part of it. The hierarchy is automatic and contextual, not manually curated.

6. Groups

The most complex and most important entity in the data model. Everything flows through groups.

Core capabilities:

• Group views — “My groups” (member of), “Recommended” (based on interests, location, or church suggestions), “All groups” (browsable directory).
• Group types — customizable per church. Examples: small group, community, volunteer team, ministry team, leadership team, interest group, course/class.
• Group hierarchy — a group can have sub-groups. The creative community has sub-groups: video team, photo team, visuals team, etc. A campus can be a group containing all its ministry groups.
• Group ↔ group relations — parent/child, but also “related” (e.g., two small groups that occasionally meet together).
• Group-scoped features:
  • News feed (group-level communication)
  • Events (group calendar)
  • Chat (group messaging)
  • Pinboard (group-specific)
  • Member list with roles
  • Files / shared documents
• Roles within groups — leader, co-leader, member, guest. Permissions configurable per type.
• Open vs. closed groups — open (anyone can join), request-to-join (approval needed), invite-only (private).
• Group discovery — browse, search, filter by type/location/availability. “Find a small group near you.”

USP vs. competitors:

• Communiapp has flat groups with chat. No hierarchy, no types, no relations.
• Donkey Mobile has smart groups for content personalization. No hierarchy.
• ChurchTools has groups with detailed admin features but poor member-facing experience.
• This app: Hierarchical group model that mirrors real church org charts. The creative community → video team → creative night → video workshop chain is natively modeled, not hacked together.

7. Chat

Messaging for church context — not replacing WhatsApp, but complementing it where WhatsApp fails.

Core capabilities:

• Group chat — every group has an optional chat channel. Especially useful for volunteer teams where coordination happens in real-time.
• 1:1 chat — direct messaging between any two members (with privacy settings to control discoverability).
• Event chat — temporary or persistent chat for event participants.
• Read receipts — optional, configurable.
• Media sharing — images, files, voice messages.
• Mentions — @person, @everyone, @leaders.
• Threads — reply to specific messages to keep conversations organized.

Design decision: Chat is intentionally not the centerpiece. Small groups already live in WhatsApp — forcing them into a new chat tool creates friction. But volunteer teams coordinating Sunday setup, or event participants asking logistics questions — that’s where in-app chat shines. The app should be smart about when to suggest chat vs. when to link out to existing tools.

USP vs. competitors:

• Communiapp has full chat as a core feature — it’s essentially their product.
• ChurchTools has basic chat (bolted onto the admin tool).
• Donkey Mobile has no real chat.
• This app: Chat is contextual — it lives inside groups and events, not as a standalone messenger. This reduces noise and increases relevance.

8. People (Member Directory)

Finding and connecting with people in your church community.

Core capabilities:

• Directory — searchable member list with profile photos, roles, groups.
• Privacy-first — members control what’s visible (name only, phone, email, address). Default: minimal.
• Roles & tags — visible church roles (pastor, elder, deacon, group leader).
• Profile — personal info, groups, events, giving history (private), notification preferences.
• Onboarding flow — new member welcome journey with suggested groups, events, and connections.

9. Platform & Technical

The invisible backbone that makes everything possible — and extensible.

9a. Backend Admin Platform

The desktop/web companion to the mobile app. This is where church staff and leaders manage day-to-day operations — and for most churches, it’s all the “church management” they’ll ever need.

Core capabilities:

• People management — member list, contact details, tags, roles, group memberships, giving history. Import/export via CSV. Not a full CRM — a clean, focused people directory with the data churches actually use.
• Group management — create/edit groups, assign leaders, configure types and hierarchy, manage membership requests.
• Event management — create/edit events, link to groups, manage registrations, configure event types and recurring schedules.
• News & communication — compose posts, schedule publishing, send push notifications, manage announcements. Rich text editor with media uploads.
• Giving administration — view giving reports, manage funds/campaigns, export tax-relevant summaries, configure payment methods.
• Sunday / service management — create service entries, upload recordings, manage sermon series, configure live interaction elements.
• Pinboard moderation — review, approve, flag, or remove community posts.
• Settings & configuration — group types, event types, branding, roles & permissions, notification defaults, language settings, privacy policies.
• Basic reporting — member growth, event attendance trends, giving summaries, group engagement. Not BI-level analytics — the numbers a pastor needs for an elder meeting.

Design principles for the backend:

• Not an ERP. No resource booking, no room calendars, no accounting ledgers, no volunteer shift planning. If a church needs those, they integrate a ChMS via adapters or API.
• 80/20 rule. Covers 80% of what 80% of churches need. The remaining edge cases are handled by API integrations, not by bloating the platform.
• Same data, different view. The backend operates on the exact same entities as the app. A group created in the backend appears in the app instantly. A member who joins via the app appears in the backend. One source of truth.
• Responsive web app. Works on desktop for office use, but also on tablet for a pastor on the go.

9b. ChMS Adapters (for larger churches)

For churches that already have a ChMS investment, pre-built adapters provide bidirectional sync — not a rip-and-replace.

Available adapters (phased rollout):

• ChurchTools — sync people, groups, events. Most important adapter for the DACH market.
• Elvanto — popular in evangelical/free church circles.
• Planning Center — dominant in English-speaking churches, relevant for international movements.
• Salesforce (Nonprofit Cloud) — for denominations using Salesforce as their central system.
• Custom via API/webhooks — any system can integrate. When a new member is added in the external ChMS, a webhook fires and the app invites them. When someone registers for an event in the app, the ChMS is updated.

Key principle: Adapters are optional add-ons, not a core dependency. A church of 2,000 members may find the backend platform sufficient. The adapter exists for churches that want to keep their existing system, not because they have to.

9c. API & Developer Platform

• API-first architecture — every entity (person, group, event, news, giving, etc.) available via REST and/or GraphQL API. Documented, versioned, authenticated.
• Webhooks — real-time notifications for all entity changes. Churches can integrate with their own systems, websites, custom dashboards, or automation tools.
• Multi-tenant architecture — one deployment serves an entire denomination. Data isolation per church, shared features at denomination level.
• User roles & permissions — denomination admin, church admin, group leader, member, guest. Fine-grained, inheritable.
• GDPR compliance — data residency in EU/CH, right to deletion, data export, consent management, processing agreements.
• Privacy settings — per-member control over profile visibility, discoverability, notification preferences.
• Content filters — age-appropriate content, language filters, moderation tools.
• Multi-language — a church can operate in multiple languages. Content can be tagged by language. UI fully localized.
• Notification preferences — per-channel (push, email, in-app), per-level (denomination, church, group), per-type (announcements, events, chat).

USP vs. competitors:

• ChurchTools has 800+ API endpoints but is not API-first (the API serves the web UI, not the other way around). No webhooks. It’s a powerful admin tool but members don’t love it.
• Communiapp has no documented API. No extensibility. No backend admin beyond their own dashboard.
• Donkey Mobile has no documented API. Backend management via “Stable” portal but no extensibility.
• This app: Three products in one — a member-facing app, an admin backend that eliminates the need for a separate ChMS for most churches, and an API platform for those who need more. Nobody else offers this spectrum.

10. Design & Branding

Fresh, modern, minimal — but with room for denominational identity.

Core capabilities:

• One app per denomination — “ICF App”, “FEG App”, “Viva Church App” in the stores.
• Customizable branding — primary color, logo, accent color, background. Not full theme customization — guardrails ensure the app always looks good.
• Consistent design language — clean, minimal, modern. Works for charismatic ICF and traditional EMK alike. The content and structure make it feel different, not the UI chrome.
• Dark mode — of course.
• Accessibility — WCAG compliant, screen reader support, scalable text.

Unique Selling Propositions (vs. Competitors)

Proposed Additional Ideas

These are features not mentioned in the original vision that could significantly differentiate the product.

🎫 Registration, Ticketing & Camp Sign-Up (High Priority)

This is a massive pain point with no good solution in the church/nonprofit space. Enterprise ticketing (Eventbrite, Ticketmaster) is too expensive and too generic. Church-specific tools like cvents.ch are cheap and have good support but are too basic — no self-service APIs, no integration, no modern UX. The result: churches use Google Forms + manual payment tracking + spreadsheet chaos.

The opportunity: A registration and ticketing module that plugs into any event — whether it’s a tenant-level conference, a group-level workshop, or a camp tenant. One module, many shapes.

Four registration levels (same module, progressive configuration):

LEVEL 1: INTEREST ("I'll be there")
├── Just a button. No form. No commitment.
├── Purpose: community effect — see who's coming
├── "Lisa, Marco, and 12 others are going"
├── No capacity limit. No waitlist. No data collection.
└── Use case: weekly small group, community hangout, prayer night

LEVEL 2: REGISTRATION (profile-based)
├── One-tap sign-up using existing profile data (name, email already known)
├── Capacity limit + waitlist
├── Confirmation sent via push/email
├── Organizer gets attendee list
└── Use case: workshop with limited seats, volunteer sign-up, alpha course

LEVEL 3: REGISTRATION + CUSTOM FIELDS
├── Profile data + additional form fields per event
├── T-shirt size, dietary needs, emergency contact, travel info, etc.
├── Consent screen for cross-tenant events (camp model)
├── Instalment payments for expensive camps
├── Group registration (parent signs up 3 kids)
└── Use case: camp, retreat, multi-day conference, youth event

LEVEL 4: TICKETING (paid + scanning)
├── Everything from Level 3 + payment + ticket generation
├── Ticket types (early-bird, regular, VIP, group discount)
├── QR code ticket in the app (or PDF for email)
├── Scan at door with any smartphone
├── Seat selection for venues with assigned seating (Phase 3+)
├── Platform fee: 1-1.5% on paid tickets
└── Use case: concert, conference, gala dinner, large event with entry control

Each event simply selects its level. The admin toggles: “Interest only” / “Registration required” / “Custom fields” / “Paid tickets.” The module handles the rest. Start with Level 1-2 at MVP. Level 3-4 follow.

Core capabilities:

• Event Registration — RSVP with capacity limits, waitlist, custom form fields. The basics. Available on any event at any level. Free to include in all paid tiers.
• Ticketing — generate tickets (QR code) for events. Free or paid. Scan at the door with any smartphone (camera → validate against API). Ticket types (early-bird, regular, VIP, group discount). Seat selection for venues with assigned seating (Phase 3).
• Payment integration — paid tickets flow through the same Stripe Connect infrastructure as giving. Church receives funds directly. “Cover the fees” option for ticket buyers. Platform can take a small cut (1-2%) on paid ticket transactions — this is accepted in ticketing (unlike giving where 0% is expected).
• Camp registration — extended forms: T-shirt size, dietary requirements, emergency contacts, medical info, travel arrangements, room preferences. Consent-based data sharing for cross-tenant camps (see domain model). Instalment payments for expensive camps. Group registration (parent signs up 3 kids).
• Check-in — scan QR code at arrival. Real-time attendance tracking. Works offline (cache attendee list on device, sync when online). Badge printing integration (Phase 3).
• Ticket scanning — any smartphone with the admin app or a simple web scanner. No special hardware needed. Validates ticket → shows attendee name + ticket type → marks as scanned. Prevents duplicate entry.
• Waitlist management — automatic: when someone cancels, next on waitlist gets notified and has X hours to confirm. No manual work.
• Multi-session selection — for conferences: “Choose 3 workshops from 12 available.” Capacity per session. Conflict detection (overlapping times). Schedule builder.

Why this is a huge differentiator:

• cvents.ch — cheap, good support, but basic. No APIs, no self-service, no modern UX, no integration with a church app. You have to manage events in cvents AND in your church app separately.
• Eventbrite — powerful but expensive (6.5% + CHF 1.59 per paid ticket). Designed for public events, not church communities. No integration with groups, news, or member data.
• Google Forms + spreadsheets — the current reality for most churches. No payments, no tickets, no scanning, no waitlists. Manual chaos.
• This platform: Registration and ticketing is a module that plugs into any event that already exists in the app. The member is already logged in. Their name, email, and church membership are already known. Signing up for a conference is: tap event → select sessions → pay → receive ticket in the app. No new account. No separate platform. No data re-entry. The ticket IS in the app they already use.

Revenue opportunity:

• Registration module: included in paid tiers (it’s a core feature for adoption)
• Ticketing (with payments): 1-2% platform fee on paid tickets — this is industry-standard and accepted (unlike giving where 0% is expected). A CHF 25 conference ticket × 2% = CHF 0.50 platform fee. At 5,000 paid tickets/year across all tenants = CHF 2,500/year. Grows with adoption.
• Camp/conference tenant creation: CHF 29/event add-on (already defined in pricing)
• Advanced features (seat selection, badge printing, multi-session optimizer): premium add-on for large conferences

Implementation phasing:

• Phase 1 (MVP): Free RSVP with capacity + waitlist + custom form fields. This replaces Google Forms immediately.
• Phase 2: Paid tickets via Stripe Connect. QR code generation. Basic scanning. This replaces cvents.ch and simple Eventbrite usage.
• Phase 3: Camp registration with consent flows (cross-tenant). Check-in system. Multi-session selection. This is the full-featured replacement for enterprise event management.
• Phase 4 / huulo.io successor: Seat selection, badge printing, event analytics, sponsor management. At this point, you have an event platform that competes with Eventbrite for the nonprofit/church segment.

🤖 AI-Powered Features

• Sermon transcription & summarization — automatically transcribe sermons, generate summaries, extract key Bible references. Members who missed Sunday can catch up in 2 minutes.
• Smart translation — auto-translate news posts and announcements for multilingual churches. An ICF Zürich post in German is instantly available in English, French, Portuguese.
• Engagement insights — AI surfaces patterns to church leaders. “Attendance in the young adults group dropped 30% over 3 months.” “These 12 members haven’t engaged in 60 days.” Not creepy surveillance — pastoral care signals.
• Content suggestions — suggest relevant groups, events, or sermon series to members based on their interests and engagement patterns.
• Prayer request clustering — anonymously surface trending prayer themes to leadership. “This month, 40% of prayer requests relate to financial stress.”

🔄 ChMS Adapter Marketplace

• For churches that already have a ChMS — not a rip-and-replace pitch. Pre-built adapters for ChurchTools, Elvanto, Planning Center, Salesforce sync data bidirectionally.
• The pitch to a ChurchTools church: “Keep ChurchTools for what it’s great at. Give your members an app they’ll actually love. We sync everything.”
• The pitch to a church without a ChMS: “You don’t need one. Our backend does what you need. If you ever outgrow it, the API and adapters are there.”
• Revenue opportunity — adapters could be a premium tier feature, creating a natural upsell for larger churches.

📊 Member Engagement Dashboard

• For group leaders — see who’s attending, who’s drifting, who’s new. Not Big Brother — pastoral care tooling.
• For members — “Your year in review” — groups joined, events attended, giving summary, sermon notes count. Positive, affirming, not gamified.

🗺️ Church Finder

• Denomination-level feature — “Find an ICF church near you” with map, service times, and one-tap to join that location in the app.
• Visitor mode — someone visiting another city can open the app and find the nearest church in their movement, see what’s happening this Sunday, and even pre-register.

📅 Personal Spiritual Journey

• Reading plans — Bible reading plans, devotionals, Advent calendars. Optionally shared with a small group for accountability.
• Milestones — baptism date, membership anniversary, courses completed. Celebrated within the app.
• Notes & journal — private space for spiritual reflections, linked to sermons or Bible passages.

🎯 Onboarding Journey

• New member flow — when someone downloads the app and joins a church: welcome message → suggest groups based on interests → show upcoming events → explain giving → connect with a buddy/mentor.
• “Next steps” concept — churches define a pathway (e.g., Welcome lunch → Alpha course → Small group → Volunteering). The app guides members through it.

🔔 Smart Notifications

• Digest mode — instead of 15 push notifications, get a morning digest: “3 new posts in your groups, 1 event reminder, 1 announcement from ICF.”
• Priority detection — urgent announcements break through digest mode. Routine posts don’t.
• Quiet hours — automatic Do Not Disturb during services and nighttime.

🌍 Open Ecosystem / Marketplace

• Plugin API — third parties can build extensions. A worship lyrics provider, a check-in tool, a volunteer scheduling addon.
• Widget system — churches can add custom “cards” to their app homepage. A link to their website, a giving thermometer, a countdown to their next conference.

What This App Is NOT

• Not a full church management system (ChMS) — no resource booking, no room calendars, no accounting ledgers, no volunteer shift planning. The backend covers people, groups, events, giving, and communication — the 80% that matters. For the other 20%, integrate a ChMS via adapters or API.
• Not trying to replace ChurchTools — for churches that already use it, the adapter syncs everything. For churches that don’t, the backend is enough. No enemy, only opportunity.
• Not a website builder — the app is the app. Churches still need websites (but the API can feed them).
• Not a social media platform — no public profiles, no follower counts, no algorithmic feed. This is a private community space.
• Not a WhatsApp replacement — chat is contextual and complementary, not a full messenger.
• Not a one-size-fits-all — the group type system and event type system let each church configure their structure without custom development.

Target Market

Tier 1 — Denomination movements (the flagship customers): Swiss and DACH church movements with 10-100+ locations — ICF Movement, Chrischona/Viva, FEG, EMK, Heilsarmee. They get one branded app, denomination-level features, and a backend that each location uses. Some locations may use ChMS adapters, most won’t need to.

Tier 2 — Individual churches (the volume play): Medium-sized churches (100-1000 members) that currently use ChurchTools + WhatsApp + a giving tool + a website. They replace three tools with one app + backend. No denomination layer needed — just a single-church setup.

Tier 3 — International expansion: European church movements outside DACH as the platform matures. The multi-language, multi-currency architecture is built for this from day one.

Working Name Ideas

(just for brainstorming — to be validated)

• Ekklesia — Greek for “assembly/church”, signals heritage + modernity
• Gather — simple, warm, action-oriented
• Vine — “I am the vine, you are the branches” — connection metaphor
• Flock — community, belonging, movement
• Parish — traditional but could be recontextualized
• Union — togetherness, federation concept built into the name

Last updated: March 2026 Status: Product Vision — Pre-MVP