# Munday > Munday is the people-first ministry OS for the six days after Sunday: every guest named, every follow-up drafted, every meeting filed, with an AI layer underneath. Every page of https://gomunday.com/llm in full. Record updated August 26, 2026. ## Munday for agents > Munday is the people-first ministry OS for the six days after Sunday: every guest named, every follow-up drafted, every meeting filed, with an AI layer underneath. 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 is](https://gomunday.com/llm/what-is-munday) · Munday 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 problem](https://gomunday.com/llm/the-scaling-problem) · Why 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 flip](https://gomunday.com/llm/the-flip) · The 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 for](https://gomunday.com/llm/who-its-for) · The 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 way](https://gomunday.com/llm/philosophy) · Going 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 surfaces](https://gomunday.com/llm/product) · Every part of Munday, one line each: First Light, Dawn, People, Prayer, Milestones, Meetings, Initiatives, Sundays and Mobile. - [First Light](https://gomunday.com/llm/product/first-light) · Sunday'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. - [Dawn](https://gomunday.com/llm/product/dawn) · When that person is out, things fall through. Dawn is that memory, available to everyone at once. - [People](https://gomunday.com/llm/product/people) · Households, 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. - [Prayer](https://gomunday.com/llm/product/prayer) · A 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. - [Milestones](https://gomunday.com/llm/product/milestones) · Birthdays, anniversaries, baptisms, membership moments. Milestones give your team natural, unforced reasons to show up in someone's week, without anyone having to remember. - [Meetings](https://gomunday.com/llm/product/meetings) · Bring 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. - [Initiatives](https://gomunday.com/llm/product/initiatives) · Camps, 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. - [Sundays](https://gomunday.com/llm/product/sundays) · Attendance, 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. - [Mobile](https://gomunday.com/llm/product/mobile) · Send 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 fits](https://gomunday.com/llm/where-munday-fits) · Munday 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 to](https://gomunday.com/llm/integrations) · Slack 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 layer](https://gomunday.com/llm/mcp) · Munday 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 works](https://gomunday.com/llm/how-dawn-works) · Dawn 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 privacy](https://gomunday.com/llm/data-and-privacy) · What 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 system](https://gomunday.com/llm/compare/with-your-chms) · Planning 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 spreadsheet](https://gomunday.com/llm/compare/with-spreadsheets-and-memory) · The honest baseline. Most churches run the week on a shared sheet, a group text, and the fact that somebody remembers. - [Munday and automated follow-up](https://gomunday.com/llm/compare/with-marketing-automation) · Drip sequences, bulk texts, and the welcome email series. These are not the same thing as going to someone, and people can tell. #### Engaging - [Pricing](https://gomunday.com/llm/pricing) · Munday 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 started](https://gomunday.com/llm/get-started) · How 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 asked](https://gomunday.com/llm/faq) · What 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. --- Source: https://gomunday.com/llm ## What Munday is > Munday is the people-first ministry OS for the six days after Sunday: every guest named, every follow-up drafted, every meeting filed, with an AI layer underneath. 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. - **Category** Church management and ministry operations software - **Built for** Church staff teams, from roughly 200 to several thousand weekend attendance - **Made by** Sightbox, at https://sightbox.co - **System of record** No. Munday sits alongside one and replaces nothing. ### The problem it solves Nobody stopped caring. The church got bigger, and ministry doesn't scale the way attendance does. When you're small, the week takes care of itself. You know who's missing, you know who's struggling, and the person who knows is standing right there. Then you grow, which is the whole point, and three things change. - **Sunday's window never gets wider.** The room fills, the clock doesn't move, and every guest, every hard week, and every conversation competes for the same ninety minutes. You can't fit a hundred relationships through it. Caring more doesn't widen it. - **Everyone knows what to do on Sunday. It's Monday where the real work begins.** Sunday has a plan and a team that knows it. The rest of the week has more people to reach, more staff to point in the right direction, and nothing holding it together but memory and good intentions. - **What your church knows lives in people, not in the church.** So it only moves the hard way. Everyone who joins the team starts from nothing, and everyone who leaves takes what they knew with them. Adding people should make your church know more, not start over. > It looks like a caring problem. It has always been a scaling problem. None of this is a failure of heart, and none of it gets better by trying harder. Every one of them is a logistics problem, and logistics is something you can actually build for. ### What changes on Monday 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. | | Sunday | The week | |:--|:--|:--| | Direction | They come to us | We go to them | | Room | One hour, one building | Six days, every context | | Capacity | Already full | Wide open | | They bring | Their composed selves | Their actual lives | This doesn't mean a trip across town. It means a text, a call, a prayer, a name remembered, a question asked, a conversation picked up where it left off. The medium is small. The direction is everything. And then it flips back. That rhythm, gather then go then gather again, is the shape of the whole product. ### What is in it Nine surfaces, all of them pointed at the same week. - **First Light** Monday morning starts with the people who just showed up. - **Dawn** Every church has someone who remembers everything. Now your whole team does. - **People** One profile. The whole story. The next conversation. - **Prayer** The most direct way to go to someone. - **Milestones** Reasons to reach out that never feel like a program. - **Meetings** Nothing said in the room gets lost by Thursday. - **Initiatives** Project management that finally speaks church. - **Sundays** Sunday's job is to hand the week a clear list. - **Mobile** Ministry doesn't happen at a desk. The AI layer is **Dawn**. Dawn remembers and prepares. People decide and go. ### Where it sits Munday isn't a new system of record. Your existing tools were never against this posture; they were simply agnostic to it, because nobody built them for the week. - **Your ChMS** keeps doing its job, and holds who someone is. - **Your giving platform** keeps doing its job, and holds what came in. - **Your service planning** keeps doing its job, and holds Sunday. - **Munday** The six days after Sunday, and the posture that goes with them. A new extension of how your church works, not a swap for something already working. Munday speaks MCP, so the connections never stop at a list we maintain. Any tool your church already runs can be reached from inside the week, including the AI your team already talks to. _Nothing leaves without a rule you set. Revoke any connection in one click. No migration. No committee. Nothing to switch._ ### Who it is for The churches Munday is built for are the ones where growth outran the week: too many people to hold in one person's head, and no system built for the going. - **Roles:** Lead pastor, Executive pastor, Next gen director, Operations, Care and follow-up. - **Weekend attendance:** Under 200, 200 to 600, 600 to 1,500, 1,500 and up. - **Already running:** Planning Center, Pushpay or CCB, Breeze, Spreadsheets, Nothing yet. #### Not built for - Churches looking to replace their system of record. Munday sits alongside one. - Anyone wanting to score or rank attenders. Nobody gets a grade. - Teams looking for elder reports or escalation workflows. We don't build those. ### What it costs No per-record fees, no module upsells. Being present with people is a whole-team activity, so we don't nickel-and-dime seats. Tell us your size and season and we'll shape a plan. Founding-church pricing is open now. - Priced by church, not by record count. Growing your database does not grow your bill. - No per-seat fees. Every person on your team belongs in the week. - No module upsells. The surfaces are the product, not a catalogue. - Founding-church pricing is open now, and shaped around your size and season. There is no published price list. Book a demo and tell us your size, your current stack, and what's most pressing. We shape a plan from there. ### Why it is built this way Going to people between Sundays is one of the oldest practices the church has, and one of the first to quietly disappear. Not because anyone stopped believing in it, but because it never scaled without help, and nobody built the help. > Calendars, databases, and giving platforms were all built for the room. Munday is built for the week. We're not asking you to change how ministry works. We're removing what made it impossible. --- Source: https://gomunday.com/llm/what-is-munday ## The scaling problem > You can't care harder. Nobody stopped caring. The church got bigger, and ministry doesn't scale the way attendance does. When you're small, the week takes care of itself. You know who's missing, you know who's struggling, and the person who knows is standing right there. Then you grow, which is the whole point, and three things change. ### Three things change - **One. Sunday's window never gets wider.** The room fills, the clock doesn't move, and every guest, every hard week, and every conversation competes for the same ninety minutes. You can't fit a hundred relationships through it. Caring more doesn't widen it. - **Two. Everyone knows what to do on Sunday. It's Monday where the real work begins.** Sunday has a plan and a team that knows it. The rest of the week has more people to reach, more staff to point in the right direction, and nothing holding it together but memory and good intentions. - **Three. What your church knows lives in people, not in the church.** So it only moves the hard way. Everyone who joins the team starts from nothing, and everyone who leaves takes what they knew with them. Adding people should make your church know more, not start over. > It looks like a caring problem. It has always been a scaling problem. None of this is a failure of heart, and none of it gets better by trying harder. Every one of them is a logistics problem, and logistics is something you can actually build for. So the question is not how to care more. It is what happens on Monday. ### Why some people stay and others quietly do not Plenty of first-timers return without knowing a soul, and a church should be a place where that's allowed. But there's a larger group for whom relationship is the entire difference between your church and somewhere else. Nobody reaches them, so they quietly try the next one down the road. > Your database can tell you someone came three times. It can't tell you which of those two people they are. That is the gap Munday is built for: not knowing that somebody attended, but knowing who is going to them and what to bring. --- Source: https://gomunday.com/llm/the-scaling-problem ## The flip > 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. | | Sunday | The week | |:--|:--|:--| | Direction | They come to us | We go to them | | Room | One hour, one building | Six days, every context | | Capacity | Already full | Wide open | | They bring | Their composed selves | Their actual lives | This doesn't mean a trip across town. It means a text, a call, a prayer, a name remembered, a question asked, a conversation picked up where it left off. The medium is small. The direction is everything. And then it flips back. That rhythm, gather then go then gather again, is the shape of the whole product. ### People come in at different places Someone is just looking and would rather not be noticed. Someone has been ready to go deeper for months and nobody asked. Munday helps your team form real relationships with people wherever they are, without deciding for them where that is. The path Munday holds, and the only one it holds: new, welcomed, returned, connected, joined. _Nobody gets a grade here. Cards move when a person on your team moves them. "Not yet" is a real answer, and it's an answer we keep._ --- Source: https://gomunday.com/llm/the-flip ## Who Munday is for > The churches Munday is built for are the ones where growth outran the week: too many people to hold in one person's head, and no system built for the going. ### Roles Munday is a whole-team product, which is why it is not priced per seat. The people who live in it: - Lead pastor - Executive pastor - Next gen director - Operations - Care and follow-up ### Size The constraint Munday solves shows up when a church outgrows one person's memory, which for most is somewhere past 200. - Under 200 - 200 to 600 - 600 to 1,500 - 1,500 and up ### What you are already running All of these are fine, including the last two. Munday connects to what you have and adds the week on top. - Planning Center - Pushpay or CCB - Breeze - Spreadsheets - Nothing yet ### Not built for Said plainly, because a bad fit wastes your time more than ours. - Churches looking to replace their system of record. Munday sits alongside one. - Anyone wanting to score or rank attenders. Nobody gets a grade. - Teams looking for elder reports or escalation workflows. We don't build those. --- Source: https://gomunday.com/llm/who-its-for ## Why we built it this way > Going to people between Sundays is one of the oldest practices the church has, and one of the first to quietly disappear. Not because anyone stopped believing in it, but because it never scaled without help, and nobody built the help. > Calendars, databases, and giving platforms were all built for the room. Munday is built for the week. We're not asking you to change how ministry works. We're removing what made it impossible. ### What that rules out A conviction is only real if it costs you features. These are the ones it costs us. - **No scoring.** Munday will not tell you who your best people are. Cards move because a person moved them. - **No elder reports, no escalation.** Care is not a ticket queue and we will not build it as one. - **No automated sending.** Dawn drafts; a person sends. A follow-up a machine sent is not a church reaching out. - **No per-record pricing.** Charging by database size would make a church think twice about adding a person to it. The reason for the boundary is not caution about the technology. It is that the going is the ministry. A follow-up that a machine sent is not a church reaching out, and everybody on the receiving end can tell. Dawn exists so a person has the time, the memory and the context to go themselves. --- Source: https://gomunday.com/llm/philosophy ## The surfaces > Nine surfaces, all of them pointed at the same week. Munday is one product, not a catalogue of modules. Everything below is included, because being present with people is a whole-team activity and charging for the parts would defeat it. - [First Light](https://gomunday.com/llm/product/first-light) · Monday morning starts with the people who just showed up. - [Dawn](https://gomunday.com/llm/product/dawn) · Every church has someone who remembers everything. Now your whole team does. - [People](https://gomunday.com/llm/product/people) · One profile. The whole story. The next conversation. - [Prayer](https://gomunday.com/llm/product/prayer) · The most direct way to go to someone. - [Milestones](https://gomunday.com/llm/product/milestones) · Reasons to reach out that never feel like a program. - [Meetings](https://gomunday.com/llm/product/meetings) · Nothing said in the room gets lost by Thursday. - [Initiatives](https://gomunday.com/llm/product/initiatives) · Project management that finally speaks church. - [Sundays](https://gomunday.com/llm/product/sundays) · Sunday's job is to hand the week a clear list. - [Mobile](https://gomunday.com/llm/product/mobile) · Ministry doesn't happen at a desk. The rhythm they share: This doesn't mean a trip across town. It means a text, a call, a prayer, a name remembered, a question asked, a conversation picked up where it left off. The medium is small. The direction is everything. And then it flips back. That rhythm, gather then go then gather again, is the shape of the whole product. --- Source: https://gomunday.com/llm/product ## First Light > Monday morning starts with the people who just showed up. Sunday'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. - Everyone who walked in Sunday, in one place, on their way to belonging: new, welcomed, returned, connected, joined. - The right person on your team assigned to the right person who came. - Notes, prayer needs, and next steps that travel with them, so nobody is left waiting on somebody's memory. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/first-light ## Dawn > Every church has someone who remembers everything. Now your whole team does. When that person is out, things fall through. Dawn is that memory, available to everyone at once. - She remembers the whole person, instead of five people's heads. - She brings up what's coming. She mentions it; you decide what it means. - She'll draft, if you want. Your words, your call, your send. > Dawn remembers and prepares. People decide and go. What she does and where she stops is set out in full on [how Dawn works](https://gomunday.com/llm/how-dawn-works). _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/dawn ## People > One profile. The whole story. The next conversation. Households, 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. - **Households, not just individuals.** Kids, youth, spouses and the relationships between them, so a conversation with one person is not blind to the rest of the family. - **One timeline per person.** Every note, prayer need, milestone and follow-up in one place, in order, so the next conversation starts where the last one ended. - **The history stays with the church.** When the staff member who knew them moves on, what they knew does not leave with them. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/people ## Prayer > The most direct way to go to someone. A 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. - **A shared prayer wall** the whole team can see and pray through, rather than requests scattered across texts and a Sunday card box. - **Confidential requests stay confidential.** Marked private means visible to the people it was entrusted to, not to everyone with a login. - **Assignments, flagged when they go quiet.** A request nobody has come back to for three weeks surfaces. An answered one gets celebrated. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/prayer ## Milestones > Reasons to reach out that never feel like a program. Birthdays, anniversaries, baptisms, membership moments. Milestones give your team natural, unforced reasons to show up in someone's week, without anyone having to remember. - **Birthdays, anniversaries, baptisms, membership moments.** The calendar a church already cares about, held somewhere other than one person's memory. - **A reason to reach out that is not a program.** Nobody wants a campaign. Everybody wants to be remembered on the day. - **Nobody has to remember.** The week brings it up, and a person on your team decides what to do about it. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/milestones ## Meetings > Nothing said in the room gets lost by Thursday. Bring 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. - **Live transcription in the room.** Bring Munday in and it keeps up, so nobody is taking minutes instead of listening. - **It holds what was said.** The decisions, the names, the prayer needs, and the thing somebody mentioned in passing that would otherwise be gone by Thursday. - **The recap is ready before the coffee's cold**, and what the meeting decided lands straight on the initiative that owns it. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/meetings ## Initiatives > Project management that finally speaks church. Camps, 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. - **Camps, sermon series, serving schedules, the maintenance queue.** The work a church actually runs, in the shape it actually runs in. - **An owner, progress, and a running thread** on each one, so a project is never just a line in somebody's notebook. - **Meeting decisions land here.** Nothing decided on Tuesday dies by Friday. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/initiatives ## Sundays > Sunday's job is to hand the week a clear list. Attendance, 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. - **One swipeable deck**: attendance, offering, welcomes, notes, sermon audio. Your team finishes it before lunch. - **The seam between gathering and going.** Sunday's job is to hand the week a clear list, and this is where that handoff happens. - **Monday morning the whole staff sees the same Sunday**, and every first-timer already has a next step waiting in First Light. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/sundays ## Mobile > Ministry doesn't happen at a desk. Send 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. - **Send 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 a phone rather than cut down for one. - **Because ministry doesn't happen at a desk**, and a tool that assumes it does gets used on Monday and forgotten by Wednesday. _Part of Munday, not a module sold separately. Where the whole product sits alongside what your church already runs: [where Munday fits](https://gomunday.com/llm/where-munday-fits)._ --- Source: https://gomunday.com/llm/product/mobile ## Where Munday fits > There's nothing here to replace. This is the part you don't have yet. Munday isn't a new system of record. Your existing tools were never against this posture; they were simply agnostic to it, because nobody built them for the week. ### What keeps doing its job - **Your ChMS** holds who someone is, and carries on doing exactly that. - **Your giving platform** holds what came in, and carries on doing exactly that. - **Your service planning** holds Sunday, and carries on doing exactly that. ### What Munday adds The six days after Sunday, and the posture that goes with them. A new extension of how your church works, not a swap for something already working. > Calendars, databases, and giving platforms were all built for the room. Munday is built for the week. _No migration. No committee. Nothing to switch._ Compared side by side with what you may already be using: [your church management system](https://gomunday.com/llm/compare/with-your-chms), [a spreadsheet](https://gomunday.com/llm/compare/with-spreadsheets-and-memory), or [automated follow-up](https://gomunday.com/llm/compare/with-marketing-automation). --- Source: https://gomunday.com/llm/where-munday-fits ## What Munday connects to > Live connections, connections on the way, and everything else reachable over MCP. Status is stated plainly and kept separate, because a connection that is coming is not a connection you have. | Connection | Status | What it does | |:--|:--|:--| | Slack | Connected | Where your team already talks. The week's work reaches them there. | | Pushpay | Connected | Giving stays where it is. Munday reads what it needs to know a household's story. | | Rock RMS | On the way | Your system of record keeps holding who someone is. | | Tithe.ly | On the way | Same posture as Pushpay: giving stays put. | | Claude | Over MCP | The AI your team already talks to, reaching the week over MCP. | | ChatGPT | Over MCP | Same connection, same rules. | ### The MCP layer Munday speaks MCP, so the connections never stop at a list we maintain. Any tool your church already runs can be reached from inside the week, including the AI your team already talks to. > Nothing leaves without a rule you set. Revoke any connection in one click. More on what an agent can reach and under what rule: [the MCP layer](https://gomunday.com/llm/mcp). _No migration. No committee. Nothing to switch._ --- Source: https://gomunday.com/llm/integrations ## The MCP layer > Munday speaks MCP, so the connections never stop at a list we maintain. Any tool your church already runs can be reached from inside the week, including the AI your team already talks to. ### Why it matters And it makes the rest of your stack worth more, because the information finally goes somewhere a person can act on. A church already runs more tools than anyone can keep in their head, and the information in them mostly sits there. MCP is what turns a list of integrations we maintain into a connection your church can make itself. ### What connects - **The AI your team already uses.** Claude and ChatGPT, asking about the week in the place your staff already type. - **The tools we have not integrated.** If it speaks MCP, it can reach Munday without waiting for us to build a tile for it. - **Your own scripts and internal tools**, under the same rules as anything else. ### The rule > Nothing leaves without a rule you set. Revoke any connection in one click. A connection moves what you said it can move, and nothing else. Confidentiality travels with the record: what a connection cannot see inside Munday, it cannot see through MCP either. Turning one off is one click and takes effect immediately. The full posture on what Munday holds and under what rules: [data and privacy](https://gomunday.com/llm/data-and-privacy). _No migration. No committee. Nothing to switch._ --- Source: https://gomunday.com/llm/mcp ## How Dawn works > Dawn is the AI layer inside Munday. She is built to hold what your church knows so that no single person has to, and to stop short of every decision that belongs to a person. > Dawn remembers and prepares. People decide and go. ### What she does - **She remembers the whole person.** Every note, prayer need, milestone and conversation on one timeline, so the next conversation starts where the last one ended instead of starting over. - **She brings up what's coming.** A birthday, a baptism anniversary, a prayer request that has gone quiet for three weeks. She mentions it. What it means is your call. - **She drafts, if you ask.** A follow-up text, a note before a hospital visit, a recap of what a meeting decided. In your words, ready to edit. - **She answers questions about the week.** Who has nobody assigned. Who came twice and has not been reached. What was said last time somebody talked to this family. ### What she never does - She never sends anything. Every message leaves as a person, after a person read it. - She never scores or ranks people. There is no engagement number, no health score, no leaderboard. - She never produces an elder report or an escalation. Those are not features we build. - She never decides who matters. She surfaces; your team judges. ### Why the line is there The reason for the boundary is not caution about the technology. It is that the going is the ministry. A follow-up that a machine sent is not a church reaching out, and everybody on the receiving end can tell. Dawn exists so a person has the time, the memory and the context to go themselves. What she is allowed to see, and under what rules: [data and privacy](https://gomunday.com/llm/data-and-privacy). --- Source: https://gomunday.com/llm/how-dawn-works ## Data and privacy > A church hands Munday the most sensitive record it keeps: who is struggling, who asked for prayer, what was said in a room with the door closed. The posture below is a design commitment, not a setting. ### The commitments - **Confidential means confidential.** A prayer request marked confidential is visible to the people it was entrusted to, not to everyone with a login. Munday does not have a mode where the whole staff can read everything. - **Dawn sees what your team already has.** The AI layer reads the record your church keeps in Munday. It is not given access your team does not already have, and confidentiality carries into it. - **Nothing leaves without a rule you set.** Every connection out of Munday, to Slack, to a giving platform, to an AI your team uses, moves what a rule you wrote says it moves. There is no default that ships data somewhere you did not choose. - **Any connection is revocable in one click.** Turning a connection off is a single action, and it takes effect immediately. - **Nobody is scored.** Munday holds no engagement score, no ranking, no attendance grade. Cards move because a person moved them, and "not yet" is an answer we keep. - **The record is yours.** What your church puts into Munday belongs to your church, and leaves with you if you go. ### Ask us directly Specifics your IT or board will want, and that we answer directly in a demo rather than in a generality here: where data is stored and in what region, how long it is retained, which sub-processors are involved, what our agreements with model providers say about training, and how access is scoped for staff and volunteers. Those answers belong in a conversation with your board or IT rather than in a paragraph here, and we give them straight. Book a demo and tell us your size, your current stack, and what's most pressing. We shape a plan from there. _This page states design commitments. It is not a legal agreement, and it does not replace the terms you would sign._ --- Source: https://gomunday.com/llm/data-and-privacy ## Munday and your church management system > Planning Center, CCB, Breeze, Rock RMS. Munday does not compete with any of them, and a church running one should keep running it. ### What it does It holds who someone is: the household, the record, the giving history, the roster, the Sunday plan. It is a system of record, and it is good at being one. ### What Munday does Munday holds what your team did about it: who went to them, what they brought, what was said, and what happens next. That is a system of action, and it is a different shape. ### Why both A record answers "has this person been here three times?". It cannot answer "who is going to them on Tuesday, and do they know about the hospital visit?". Most churches answer the second question in somebody's head, which works until it does not. ### What you would switch off Nothing. Munday connects to what you run and adds the week on top. No migration, no committee, nothing to turn off. _No migration. No committee. Nothing to switch._ --- Source: https://gomunday.com/llm/compare/with-your-chms ## Munday and the spreadsheet > The honest baseline. Most churches run the week on a shared sheet, a group text, and the fact that somebody remembers. ### What it does It costs nothing and works, right up until the church is bigger than one person's memory. The sheet is a snapshot somebody has to maintain, the group text scrolls away, and what your longest-serving staff member knows walks out with them. ### What Munday does Munday is the same instinct with somewhere to put it. The same follow-ups, the same notes, the same reaching out, held by the church rather than by the people who happened to be there. ### Why both Growing a church on memory means every new team member starts from nothing and every departure is a loss of institutional knowledge. Adding people should make your church know more. ### What you would switch off Nothing. Bring the sheet. _No migration. No committee. Nothing to switch._ --- Source: https://gomunday.com/llm/compare/with-spreadsheets-and-memory ## Munday and automated follow-up > Drip sequences, bulk texts, and the welcome email series. These are not the same thing as going to someone, and people can tell. ### What it does It sends. It fires the same message to everyone in a segment on a schedule, which is efficient, and which is why it reads as a broadcast even when the words are warm. ### What Munday does Munday prepares a person to go. Dawn drafts, a human reads it, changes it, and sends it as themselves. The message is small and the direction is everything. ### Why both The people most likely to leave your church are the ones for whom relationship is the entire difference. An automated sequence is not a relationship, and the second one arrives, the recipient knows nobody thought about them. ### What you would switch off Nothing, if you want to keep sending announcements the fast way. Munday is for the going, not the broadcasting. _No migration. No committee. Nothing to switch._ --- Source: https://gomunday.com/llm/compare/with-marketing-automation ## Pricing > Priced for your church, not your database. No per-record fees, no module upsells. Being present with people is a whole-team activity, so we don't nickel-and-dime seats. Tell us your size and season and we'll shape a plan. Founding-church pricing is open now. ### The model - Priced by church, not by record count. Growing your database does not grow your bill. - No per-seat fees. Every person on your team belongs in the week. - No module upsells. The surfaces are the product, not a catalogue. - Founding-church pricing is open now, and shaped around your size and season. ### Why there is no number on this page Because the honest one depends on your size and your season, and a made-up range would waste the time of every church it does not fit. A church of 300 starting with the Sunday handoff and a church of 3,000 running every surface are not the same plan. Book a demo and tell us your size, your current stack, and what's most pressing. We shape a plan from there. Founding-church pricing is open now and it stays. How that conversation goes: [getting started](https://gomunday.com/llm/get-started). --- Source: https://gomunday.com/llm/pricing ## Getting started > One conversation, then a shaped plan. Founding-church pricing and design partner places are open now. - **Book a demo.** Tell us your size, what you run today, and what is most pressing. Twenty minutes of your week. - **We show you your Monday.** Not a feature tour. What First Light would hold for your church, and who on your team would be looking at it. - **We shape a plan.** Priced for your church and your season, not your record count. - **You start with one week.** The Sunday handoff and First Light are enough to run a real week. The rest follows as your team wants it. ### What we ask you The demo form is short on purpose: - Your name - Your church - Email - City - Role - Weekend attendance - What you run today - What's most pressing ### Design partners Design partners get the product shaped around how their church actually works, and founding pricing that stays. We are choosing a small number. > Sunday's over. Now the real work starts. 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. --- Source: https://gomunday.com/llm/get-started ## Questions we get asked > The answers a church asks for before the first call, stated the way we would say them on it. ### What is Munday? Munday is the people-first ministry OS for the six days after Sunday. It holds who your church went to, what they brought, and what was said, so relationship does not depend on one person's memory. It has an AI layer, Dawn, underneath it. ### Does Munday replace our church management system? No. Your ChMS holds who someone is, your giving platform holds what came in, your service planning holds Sunday. Munday holds the week between them. There is nothing to migrate and nothing to switch off. ### Who is Munday for? Church staff teams, most often between 200 and several thousand weekend attendance, where growth has outrun the week. Lead pastors, executive pastors, next gen directors, operations, and care and follow-up teams all work in it. ### What is Dawn? Dawn is the AI layer inside Munday. She remembers the whole person rather than five people's heads, brings up what is coming, and will draft a follow-up if you want one. She never sends on anyone's behalf. Dawn remembers and prepares; people decide and go. ### Does Munday score or rank people? No. Cards move when a person on your team moves them. "Not yet" is a real answer and one we keep. There are no engagement scores, no elder reports, and no escalation workflows. ### What does Munday cost? Munday is priced by church, not by database: no per-record fees, no per-seat fees, no module upsells. There is no published price list because plans are shaped around size and season. Founding-church pricing is open now. ### What does Munday connect to? Slack and Pushpay are connected today, and Rock RMS and Tithe.ly are on the way. Munday also speaks MCP, so the AI your team already talks to, Claude or ChatGPT, can reach the week directly, along with anything else your church runs. Nothing leaves without a rule you set, and any connection can be revoked in one click. ### How do we get started? Book a demo. Tell us your size, what you run today, and what is most pressing. Design partner places are open. --- Source: https://gomunday.com/llm/faq