A congregation seated in pews during a Sunday service, seen from the balcony

Church software for small congregations · $19 flat

People should not disappear between Sundays.

Notice who is new, who needs follow-up, and who quietly stopped showing up.

SundayBridge keeps your congregation, groups, attendance, giving, serving, and follow-up in one calm place — so the guest from Sunday is still remembered on Wednesday, and the quiet regular who stopped coming gets noticed before they're gone.

The demo is a fully populated sample church — no login, no card, no sales call. Subscribing is one flat $19 a month, month to month, cancel anytime.

Use TRY25 at checkout for 25% off every renewal while you stay subscribed.

See how we compare:BreezePlanning CenterChurchTracfull table

Household · MarshGroup · Tuesday Women'sFirst visit · Jul 5Absent 3 SundaysFollow-up owed 9d

Sunday is loud. It's the week after that decides who stays.

A first-time household visits. A greeter means to call. A member slips out the back for a month. None of it is anyone's fault — it just lives in memory, and memory is the first thing a busy week takes. SundayBridge is a place to set the people work down, so it stops depending on someone remembering.

One place

Everything a small church actually runs on, in one home instead of five tools.

Not a bloated platform — the modules a congregation of ninety or two hundred uses every week, kept together so a person's whole story sits on one page.

People standing together with hands on one another's shoulders during a church service

Follow-up

A family visited three Sundays ago. Someone said they'd call. Nobody knows whether anyone did.

A guest becomes a next step with an owner and a date on it — on a board that shows you what nobody has picked up.

A congregation seated in wooden pews beside tall windows during a service

People & households

A name in the directory, a row in the attendance sheet, and a note on somebody's phone are three fragments of one person.

Individuals gathered into the households they actually live in, each with one profile: groups, serving, giving, care, and a readable engagement timeline.

Empty wooden church pews with red cushions in warm afternoon light

Attendance

The board asks whether attendance is down. You have a feeling, and a feeling is not an answer.

Record a named roster or a simple headcount, then chart attendance against its own history.

Two people's hands clasped together in a gesture of comfort

Giving records (optional)

If your church keeps contribution records here, they should stay organized without taking over the rest of church operations.

An optional manual contribution ledger with trends, a goal to track against, and printable year-end statements.

A circle of church volunteers praying together with hands on shoulders

Serving teams

The same four people serve every week. Someone who has never been asked would say yes if anyone asked.

Roles, assignments, and who is actually carrying the load — so serving is scheduled instead of assumed.

A woman holding a coffee cup at a table with an open Bible

Pastoral care

You promised a widow you would visit. It is now three weeks later and it lives only in your memory.

Care cases with comments and history, kept discreetly alongside the rest of a person's record — so the visit that was promised actually happens.

This is what the week looks like

Set it up on a Monday. Use it by Wednesday.

These are the actual screens, and the demo behind them is a real church's week already loaded — people, households, groups, a serving schedule, attendance history, giving, and live follow-up.

app.sundaybridge.com/follow-up

This week's follow-up

4 open

  • The Alvarez family

    First-time guest — call to welcome

    Dana

    Due Tue

  • Marcus Bell

    Back after 4 weeks away — check in

    Pastor Reyes

    Due Wed

  • Priya Nair

    Asked about baptism — follow up

    Dana

    Due Fri

  • The Okafor family

    New — invite to Tuesday group

    Sam

    Next week

01

Notice who needs a person

The dashboard opens on the week: who's new, what's open, and what nobody has picked up yet. Not a database — a short list of people.

app.sundaybridge.com/attendance

Weekly attendance

4-week average, last 12 Sundays

88

+9% vs. last year

02

Read the room honestly

Attendance is charted against its own history. One good Sunday isn't a trend; one bad one isn't a crisis. A quiet regular's absence shows up long before it hits the average.

app.sundaybridge.com/giving

Giving this year

By month, with giver count

$280k

142 givers

03

Keep the quiet books

Contributions per giver, with giving trends over time — the numbers you need for planning and statements, without turning generosity into a leaderboard.

Ask AI · included in the plan

Ask your own records a question.

“Which regulars have quietly stopped coming?” “How did giving do this quarter against last year?” Ask in plain English and the assistant reads the records you already keep — attendance, giving, follow-up, groups, and care — then answers in a sentence. No report to build first, no spreadsheet, no export.

  • It sees your church and no other. Your data is scoped at the database, not asked nicely in a prompt. No tool the assistant can call even has a field for naming a church — so another congregation's records cannot be requested, because they cannot be addressed. Underneath, the query runs as a read-only Postgres role that returns zero rows if the church isn't set. Your question and the selected summaries needed to answer it are sent to our AI provider to generate the response; they are not used to train its models.
  • It never makes a number up. The assistant is forbidden from doing arithmetic. Every figure comes from the same code that draws your dashboard, and for the insight panels any number the model writes that isn't in the allow-list of real figures is thrown away and replaced with a plain template. A wrong number can't reach the page.
  • It says when it doesn't know. If your records don't contain the answer, it tells you which tab would show it rather than guessing. If a report is empty, it says the record is empty. It will not speculate about a family's giving or a person's absence.

10 questions a month are included in the one $19 plan — there is no AI upsell. Ask AI is switched off in the public demo, because the demo church's records aren't yours to ask about.

app.sundaybridge.com/ask

Which regulars have quietly stopped coming?

Four people who attended at least twice a month have missed the last three Sundays: Marcus Bell, Priya Nair, and the two adults of the Okafor household. None of them has an open follow-up.

Read attendance trend, congregation summary.

How did giving do this quarter against last year?

Giving this quarter is $71,480 across 138 givers, up 6% on the same quarter last year ($67,410). The giver count is essentially flat — the increase is in average gift, not in more people giving.

Read giving summary.

Is the Alvarez family planning to become members?

Your records don't say. I can see the Alvarez family first visited on July 5 and has attended twice since, but membership intent isn't something SundayBridge stores. The Follow-up tab is where a conversation about it would be recorded.

No tool returned an answer.

7 of 10 questions left this month · answers come from your records, not the open internet

Light through a stained glass window falling in colour across a stone wall

Insights · on every page

The paragraph you would have written, if you'd had the time to read the numbers.

At the top of 12 pages, SundayBridge writes a short, plain-language read of what actually changed — the follow-up that has sat a week, the four-week attendance stretch, the volunteer serving every Sunday. You don't ask for it. It's there when you open the tab.

Ordinary code, not a model, decides what is worth pointing at. The model only writes the sentence — and if it writes a number that isn't one of your real figures, that sentence is thrown away and a plain template runs instead. It is architecturally unable to make a number up.

Detect → scrub → narrate → checkNo PII leaves the databaseEstimates, not advice
app.sundaybridge.com/dashboard

What changed this week

Attendance averaged 88 over the last four Sundays, the highest four-week stretch this year. Three follow-ups have been open more than a week, and one of them — a first-time guest from July 5 — still has nobody's name against it. Two volunteers served every Sunday this month.

AI-generated · estimates, not advice

  • 01

    Detected. Deterministic code finds what's unusual — no model involved.

  • 02

    Scrubbed. Emails, phone numbers, and birthdates are stripped before it's sent.

  • 03

    Narrated. The model writes prose. It is not allowed to calculate.

  • 04

    Checked. Any number it wrote that isn't a real figure is thrown out.

Why the record matters

The questions your Sunday leaves behind.

SundayBridge is new and we won't invent testimonials — open the demo and judge it yourself. Here is what a guest notices, what a pastor asks on Tuesday, and what a board asks in the spring, and where SundayBridge already has the answer.

What a guest notices

  • Somebody remembered my name on Wednesday.
  • The person who said they'd call, called.
  • I got invited into a group, not just a service.

What a pastor asks

  • Who visited us in the last month, and who followed up?
  • Which regulars have quietly missed three Sundays?
  • Who is carrying too much serving, and who has never been asked?

What a board asks

  • Is attendance actually trending down, or was that one week?
  • What did giving do this quarter against last year?
  • How many guests became members, and how long did it take?

Follow-up

The welcome that was meant, actually reaching someone.

Every church means to follow up. Almost none of them can say, on a Tuesday, who visited last Sunday and whether anyone called. That gap isn't a character flaw — it's a missing record.

  • A guest becomes a follow-up with an owner and a date, not a name on a card in a drawer
  • The board shows what's open, what's done, and what nobody has picked up
  • A member's absence shows on their profile before it shows in the average
Follow-up owed 9dAbsent 3 Sundays

A step nobody owns doesn't quietly disappear — it stays on the board with its age on it until a person picks it up. That is the whole difference between a database and a church that keeps people.

A family seated together in a church pew during a service

Reports

Twelve reports, because the elders want numbers by Thursday.

Every module reports. Chart it, pivot it, group it, and export the pivot or the raw rows to CSV — all built from records you were already keeping, so nobody spends Thursday assembling a spreadsheet.

Congregation makeup

Congregation

New people over time

Congregation

Households

Congregation

Group membership

Congregation

Attendance

Gatherings

Event registrations

Gatherings

Sunday school enrollment

Gatherings

Serving assignments

Serving

Follow-up

Care

Pastoral care cases

Care

Giving

Giving

Givers

Giving

One record per person

The one thing a stack of spreadsheets can't do: keep the whole person together.

A name in the directory, a row in the attendance sheet, an envelope in the giving log, and a note on somebody's phone are four fragments of one person. SundayBridge keeps them as one profile — household, groups, serving, giving, care, and an engagement timeline you can read in a glance before you knock on the door.

Households

People gathered the way they actually live — not isolated rows.

Engagement timeline

Attendance, serving, groups and care in one chronology.

Pastoral care

Cases with comments and history, kept discreet.

Follow-up board

Owned next steps, aged, so nothing goes quiet.

All of it visible in the demo, with a sample church already in it.

Plainly

What SundayBridge is

  • One home for your congregation, groups, attendance, gatherings, giving, serving, and follow-up.
  • A person's whole story on one profile — household, groups, serving, engagement.
  • Follow-up with real owners, so nobody slips through the cracks.
  • An AI assistant that reads your records, cannot see another church's, and won't invent a number.
  • Twelve reports across every module — charted, and exportable to CSV.
  • Bring your directory in from a CSV — a two-step preview before anything is written.
  • One flat price, and a public demo that is the trial.

On purpose, and honestly

What it isn't — yet

  • No multi-user staff roles or permissions — it's a single login per church for now.
  • No built-in email or text messaging. It won't send for you.
  • No online giving or payment processing. It records giving; it doesn't take it.
  • No child check-in kiosk. The front door is still people and paper.
  • Sunday school and reports are read-only. Attendance supports named rosters or a headcount, but there is no Sunday-morning kiosk or label printing.

We'd rather tell you now than sell you a checkmark. See what's shipped and what's planned →

Software should help you love people, not manage a database.

The whole point of SundayBridge

Pricing

One flat price. 7 days free, then $19/mo.

Every module and the AI assistant for $19 a month — no per-member pricing, no add-ons, no AI upsell, no tier to outgrow. A card starts the 7-day trial with $0 due today; the separate public demo, a fully populated church, needs no account or card at all.

Month to month · no setup fee · cancel anytime

The demo

$0

The whole app, a sample church. No login, no card.

Your church

$19/mo

Every module, AI included. Cancel anytime.

See everything included, and what isn't →

Field notes

Practical guides for running a small church.

Empty church pews lit by warm evening light, with a wooden cross beyond

Judge it yourself, with a church already in it.

Walk the live demo — no login, no card, no sales call — or start your church on SundayBridge for $19 a month.

Month to month · cancel anytime · your data is never mixed with the demo