# Pastoral care visits and follow-ups for churches

Pastoral care visits and follow-ups for churches is a SaaS idea for pastoral teams at churches and faith groups with 100 to 1,000 members, priced to test at $19 a month per congregation. Needs are passed on after a service or in a corridor chat, then forgotten. With it, churches and faith groups keep a private list of people who need a visit, assign volunteers, and see who’s been missed.

_Published 19 Oct 2026. A starting point we wrote, not market research: run the 7-day test before you build._

## What problem does it solve?

Needs are passed on after a service or in a corridor chat, then forgotten. Some people get several visits in a week and others none, and private notes sit in personal notebooks.

**Why now:** Pastoral work leans more and more on volunteers, and they need one shared list rather than the minister’s memory.

## What do they use today?

Pastoral teams often rely on a shared group chat, a minister’s diary and the memory of a few long-serving volunteers. Anything private is kept in somebody’s own notes, which no one else can check.

## How does it work?

The pastoral lead adds a person who needs a visit to the care list, notes the need and assigns a volunteer. After the visit, the volunteer jots a quick note, sets a follow-up date, and gets a reminder when it falls due. Private notes are seen only by the lead, and a weekly email tells the minister who has been visited and who has been missed.

## What goes in the first version?

- A care list with each person’s need and assigned visitor
- Quick visit and call notes after each contact
- Follow-up dates, with reminders to the visitor
- Private notes only the pastoral lead can see
- A weekly summary email for the minister

## Who pays, and how much?

- **Who pays:** Pastoral teams at churches and faith groups with 100 to 1,000 members
- **Price to test:** $19 a month per congregation

A congregation is one community with one budget, so a flat monthly price per congregation is simple for a treasurer to approve. Volunteer visitors change often, so there is no seat count to keep updating.

## How to test it in 7 days

1. Ask five ministers or pastoral leads how they keep track of who needs a visit.
2. Ask one pastoral team to use a shared mock-up for a week and note what they skip.
3. Check what church management systems offer for pastoral care and where small churches find them too much.

## Where to find the first customers

- Church administrator groups on Facebook
- Regional denominational offices that advise local churches
- Training courses for pastoral care volunteers

## What are the risks?

- Notes about health and grief are sensitive, so privacy and access control come first.
- Church management suites include pastoral modules, so stay simpler and cheaper.

## How to build it on shipanysaas

4 of the parts it needs are already in the kit. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.

**Already in the kit:** Teams and roles, Billing, Emails, In-app notifications

**You build:**

- Care list with assignments and follow-ups
- Visit notes with private access levels
- Weekly summary email

[Get the kit](https://www.shipanysaas.com/pricing)

### The starting prompt

```text
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase. Help me build the first version of Pastoral care visits and follow-ups for churches.

Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it.

## The product
- What it does: Churches and faith groups keep a private list of people who need a visit, assign volunteers, and see who’s been missed.
- Who pays: Pastoral teams at churches and faith groups with 100 to 1,000 members
- Their problem: Needs are passed on after a service or in a corridor chat, then forgotten. Some people get several visits in a week and others none, and private notes sit in personal notebooks.
- Price to test: $19 a month per congregation (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. A care list with each person’s need and assigned visitor
2. Quick visit and call notes after each contact
3. Follow-up dates, with reminders to the visitor
4. Private notes only the pastoral lead can see
5. A weekly summary email for the minister

## Already in the kit: reuse it, never rebuild it
- Teams and roles: team accounts with members, roles and invitations
- Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments
- Emails: transactional email through Resend or Nodemailer
- In-app notifications: a notifications bell in the web app

## New code it needs
- Care list with assignments and follow-ups
- Visit notes with private access levels
- Weekly summary email

## How to work
1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK.
2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files.
3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next.

## Rules
- Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel.
- Leave the parts of the kit this product doesn't use as they are.

Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
```

### Guides for the parts it uses

- [Multi-tenant SaaS architecture: teams, roles and invitations done right](https://www.shipanysaas.com/blog/multi-tenant-saas-teams-roles-invitations)
- [How to add in-app notifications to a Next.js + Supabase app](https://www.shipanysaas.com/blog/nextjs-supabase-in-app-notifications)
- [How to add Resend email to a Next.js + Supabase app](https://www.shipanysaas.com/blog/nextjs-supabase-resend-email)

## More ideas: Nonprofits

- [Weekend pitch allocation for grassroots sports clubs](https://www.shipanysaas.com/saas-ideas/grassroots-pitch-allocation): Fixture secretaries assign pitches, kick-off times and referees for every team’s weekend games, and coaches get their slot by email.
- [Expense claims and receipts for volunteer-run groups](https://www.shipanysaas.com/saas-ideas/volunteer-expense-claims): Volunteers snap a receipt and claim the money back, the treasurer approves it, and spending is tracked against each grant.
- [Outcome tracking and funder reports for small charities](https://www.shipanysaas.com/saas-ideas/charity-outcome-reports): Staff and volunteers record sessions, attendance and before-and-after answers, and each funder’s report comes from the same records.

- [All SaaS ideas](https://www.shipanysaas.com/saas-ideas)
- [Try the free generator](https://www.shipanysaas.com/saas-ideas#generator)