Munday for agents

Munday is church software for the week rather than the service. Where a church management system records who someone is and a service planner runs Sunday, Munday runs the days in between: who your team goes to, what they bring, and what was said last time. It is not a system of record and it replaces nothing you already run.

The short version. You can't care harder. Nobody stopped caring. The church got bigger, and ministry doesn't scale the way attendance does. On Sunday, people come to you. Monday morning, Munday turns your team the other way: toward the people who came, the people carrying something heavy, and the people nobody has thought about in a month.

Calendars, databases, and giving platforms were all built for the room. Munday is built for the week.

The pages

Start here

• What Munday isMunday is the people-first ministry OS for the six days after Sunday. What it is, what it does, where it sits alongside your existing tools, and what it costs.
• The scaling problemWhy ministry stops reaching everybody as a church grows, in three constraints. It looks like a caring problem and it has always been a scaling problem.
• The flipThe argument Munday turns on. Sunday is the gathering; the six days after it run the other direction, and that is the room nobody built for.
• Who Munday is forThe churches and the roles Munday is built for, the sizes it fits, and the three kinds of church it is explicitly not for.
• Why we built it this wayGoing to people between Sundays is one of the oldest practices the church has, and one of the first to quietly disappear. Munday is the missing infrastructure, not a new idea.

The product

• The surfacesEvery part of Munday, one line each: First Light, Dawn, People, Prayer, Milestones, Meetings, Initiatives, Sundays and Mobile.
• First LightSunday's new faces land in First Light with a face on every card and a next step already drafted. This is the moment the direction reverses: they came to you, and here's who you go to first, and why.
• DawnWhen that person is out, things fall through. Dawn is that memory, available to everyone at once.
• PeopleHouseholds, kids, youth, relationships, and the history that makes showing up personal instead of procedural. Every note lands on one timeline, so the next conversation starts where the last one ended.
• PrayerA shared prayer wall, confidential requests, and prayer assignments, flagged when they go quiet and celebrated when they're answered. For many new people, this is the first real relationship they have in your church.
• MilestonesBirthdays, anniversaries, baptisms, membership moments. Milestones give your team natural, unforced reasons to show up in someone's week, without anyone having to remember.
• MeetingsBring Munday into the room and it transcribes live and holds onto what was said: the decisions, the names, the prayer needs, the thing someone mentioned in passing. Your team decides who goes; the recap is ready before the coffee's cold.
• InitiativesCamps, sermon series, serving schedules, the maintenance queue: every project with an owner, progress, and a running thread. What a meeting decides lands straight on them, so nothing decided on Tuesday dies by Friday.
• SundaysAttendance, offering, welcomes, notes, sermon audio: one swipeable deck your team finishes before lunch. It's the seam between gathering and going. Monday morning the whole staff sees the same Sunday, and every first-timer already has a next step.
• MobileSend the note from the coffee line. Pray from the parking lot. Pull up a family before you walk into the hospital room. The same Home, People, Prayer, and Sundays, sized for the places ministry actually happens.

Where it fits

• Where Munday fitsMunday is not a system of record and replaces nothing. What your ChMS, your giving platform and your service planning keep doing, and what Munday adds on top.
• What Munday connects toSlack and Pushpay are connected. Rock RMS and Tithe.ly are on the way. Claude, ChatGPT and anything else your church runs reach the week over MCP.
• The MCP layerMunday speaks MCP, so the AI your team already talks to can reach the week directly. What it can reach, the rule it moves under, and how to revoke it.

Trust

• How Dawn worksDawn is the AI layer inside Munday. What she does, what she will never do, and why the boundary is the point rather than a caution.
• Data and privacyWhat Munday holds and the rules it holds it under: confidentiality, what Dawn is given, what leaves over a connection, and what your church keeps.

Compared with

• Munday and your church management systemPlanning Center, CCB, Breeze, Rock RMS. Munday does not compete with any of them, and a church running one should keep running it.
• Munday and the spreadsheetThe honest baseline. Most churches run the week on a shared sheet, a group text, and the fact that somebody remembers.
• Munday and automated follow-upDrip sequences, bulk texts, and the welcome email series. These are not the same thing as going to someone, and people can tell.

Engaging

• PricingMunday is priced by church, not by database: no per-record fees, no per-seat fees, no module upsells. There is no published price list, and this is why.
• Getting startedHow a church starts with Munday: one conversation, then a plan shaped to your size and season. Founding pricing and design partner places are open.
• Questions we get askedWhat Munday is, whether it replaces your ChMS, who it is for, what Dawn is, whether anyone is scored, what it costs, what it connects to, and how to start.

Reading this as an agent

• Every page here is served as markdown at the same path with .md on the end, or by sending Accept: text/markdown.
• /llms.txt is the index with a one-line summary per page. /llms-full.txt is every page in full.
• Schema.org JSON-LD for the product, the organisation and the FAQ is emitted on every page.
• Munday speaks MCP, so an agent can reach the week itself rather than only reading about it.

Getting a person

Munday helps your team go to the people who came, so the ones who needed someone to reach them aren't the ones who quietly disappear. Your church can keep growing without anyone becoming a stranger.

Book a demo and tell us your size, your current stack, and what's most pressing. We shape a plan from there. The demo form asks for: your name, your church, email, city, role, weekend attendance, what you run today, what's most pressing.