The digital command centre for churches · in development

Know your people.
Connect your church.

Kora OS connects members, visitors, conversations, attendance, giving and follow-up in one calm workspace — so your team can answer one question every morning: who needs attention today?

No visitor forgotten. No conversation lost. No member left unnoticed.

Illustrative preview with sample data. Names and figures are invented.
The problem

Care gets lost between the cracks

Most churches run on goodwill and a patchwork of tools. Everyone works hard, yet people still slip through — not because nobody cares, but because nobody can see the whole picture.

Spreadsheets that drift

Member lists copied between files, each slightly different, none trusted.

WhatsApp on personal phones

Visitor questions land on one volunteer’s phone and leave with them.

Paper registers

Attendance is counted, but nobody can see who has quietly stopped coming.

Disconnected tools

Giving, messaging and follow-up live in separate places with separate logins.

Visitors wait for a call that never comes.

The follow-up was on someone’s list — just not anyone else’s.

Absences go unnoticed for weeks.

The register was filled in; nobody connected the dots.

Conversations disappear with people.

When a volunteer steps down, their chat history goes with them.

Signature feature

Needs Attention: your team’s daily work queue

One prioritised list of the people and tasks that need someone today — each with a clear reason, an owner and the next step.

  • Visitors awaiting follow-up

    No meaningful contact within 48 hours of a first visit.

  • Members with eligible attendance gaps

    Three missed services they’re expected at — cancelled and unfinalized services don’t count.

  • Overdue staff tasks

    Follow-ups past their due date, owned or unassigned.

  • Clear next actions

    Assign, open the conversation, view the person, schedule or resolve — as your role allows.

In development · first releaseTry it in the demo

Needs Attention

Sample

Overdue follow-up

Overdue

Daniel Kpodo

Follow-up call was due Saturday. Two attempts logged, no conversation yet.

Owner
Abena Sarpong
Due
2 days ago
Source
Task · Welcome call

Returning visitor

Good news

Nana Adomako

Second visit in two weeks — a good moment for a personal welcome.

One connected story

From first visit to real connection

Every step attaches to the same person, so the next person to help can see what already happened.

  1. Visitor

    A first-time guest fills in a visitor card and chooses how they’d like to be contacted.

    Esi visits on Sunday and leaves her WhatsApp number.

  2. Conversation

    Their WhatsApp messages arrive in a shared inbox, linked to their record.

    Monday: “Is there a midweek group near Osu?”

  3. Follow-up

    Someone owns the next step, with a due date and a recorded outcome.

    Abena is assigned and calls on Tuesday.

  4. Attendance

    Check-ins show who is returning — and who has gone quiet.

    Esi checks in again the next Sunday.

  5. Connection

    Over time a visitor becomes a member of a group, a team, a household of faith.

    She joins the Osu home group.

What’s inside

Built around the work churches actually do

Kora OS is being built in stages. We label every capability honestly so you know what exists today and what is coming.

Foundation builtbuilt and tested in the workspace foundationIn development · first releasebeing built nowPlanned · later phaseon the roadmap
In development · first release

People & households

One record for every member and visitor, with households, campus, status and history in one place.

  • Visitor-to-member journey on the same record
  • Shared family phones handled without unsafe merges
  • Safe spreadsheet import with preview
In development · first release

WhatsApp inbox

Your church’s WhatsApp conversations in a shared inbox instead of on personal phones.

  • Assignment, status and labels
  • Private internal notes that never reach the contact
  • Person context filtered by permission
In development · first release

Attendance

Service sessions with QR and manual check-in, and history you can trust.

  • Unrecorded is never treated as absent
  • Cancelled services excluded
  • Audited corrections
In development · first release

Follow-up

Every visitor gets an owner, a due date and a recorded outcome.

  • Board and list views
  • Contact outcomes, not just “message sent”
  • Overdue work surfaces in Needs Attention
In development · first release

Giving

Funds, verified contributions and receipts — with amounts and currencies kept exact.

  • Hosted checkout; no card data stored
  • Receipts only after verified payment
  • Visible only to finance-permitted roles
Foundation built

Multi-campus coordination

Church and campus structure with roles granted at exactly the right level.

  • Campuses inside one church workspace
  • Staff see only the campuses they’re granted
  • Cross-campus reporting planned for later

See every feature and its status

Who it’s for

Designed for churches that are growing

Growing churches

150 to 2,000 people

Big enough that nobody can keep everyone in their head; small enough that every person still matters by name.

Multi-campus churches

One church, many locations

Each campus team sees and acts on its own people, while church leaders keep the full picture.

Denominations · later

Many churches, one view

Consolidated reporting across churches is on the roadmap, built on the same permission model.

Planned · later phase

Ghana first, international by design

We’re shaping the first release with churches in Ghana: WhatsApp-first communication, mobile-money giving and Ghana cedi amounts. Language, time zone and currency are separate settings from day one, so the product can serve churches elsewhere.

We’re speaking with churches about joining a small design-partner group. Partner places and launch dates are not yet confirmed.

Trust

People’s stories deserve careful handling

Church records can include faith, family, health and giving. These are the principles Kora OS is built on — and how we describe their status honestly.

Each church separate

Every church’s data is isolated at the database level, and that isolation is tested.

Access by role and campus

Staff see only what their role allows, where it’s granted. Nobody can hand out more access than they hold.

Changes are recorded

Access changes and sensitive actions leave an audit trail your church can review.

Care stays confidential

Pastoral care and giving stay restricted — even church owners don’t get automatic access to counselling notes.

Read how security works, and what we don’t claim

See what your Monday morning could look like

Walk through a sample church workspace, or tell us about yours and how you care for people today.