Industry solution

Religious & Community Organizations

Families, giving, volunteers and the hall calendar, working as one congregation

Household records that keep up with families, gifts kept to their funds, full rosters, one hall calendar and a building serviced in time.

Products
8
Challenges
6
Concepts
16
Talk to us about Faith & CommunityAsk a question
Volunteers serving a community meal to families in a bright community hall
ComradeCircle(opens ComradeCircle in a new tab)Subscriber Bot(opens Subscriber Bot in a new tab)FluidGrids(opens FluidGrids in a new tab)EventfullyManaged(opens EventfullyManaged in a new tab)CrewFoundry(opens CrewFoundry in a new tab)BuildMyIQ(opens BuildMyIQ in a new tab)AssetHandler(opens AssetHandler in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

Why running a congregation is harder than it looks

Temples, churches, mosques and gurdwaras run on volunteers, paper registers and group chats, so family records, designated gifts, rosters, room bookings and upkeep drift apart until a busy day exposes the gap.

A temple, church, mosque or gurdwara is at once a place of worship, a charity, an employer, a school, a caterer and a landlord, usually run by a small paid staff and a much larger circle of volunteers. The household register, the giving records, the volunteer roster, the hall diary and the maintenance file each live with a different person, often in a spreadsheet or a group chat that leaves with them when their term on the committee ends.

The pressure comes in waves the calendar sets: Christmas and Easter, Diwali and Navratri, Ramadan and Eid, Vaisakhi and the Gurpurabs, the High Holy Days. Attendance can multiply in a week, the community kitchen may feed hundreds a night, and a funeral can arrive with a day's notice, because some traditions ask for burial or cremation within a day or two. Every one of these draws on the same rooms, the same volunteers and the same few people in the office.

Trust is what holds it together. Families expect their congregation to know when a child is born or a parent dies, and to handle that news with care. Donors expect a gift made for the building, the poor or the community meal to be spent on exactly that. Parents expect to know who is teaching their children and who may collect them. When records drift apart, it is these moments that people remember.

Who this is for

  • Congregation administrators and office managers

    One place for households, bookings and rosters, so the week runs from records rather than a front-desk diary and three group chats.

  • Treasurers and finance committees

    Every gift kept to the fund it was given for, failed monthly gifts caught early and giving statements that agree with the books.

  • Trustees and management committee members

    Membership standing nobody disputes before elections, building risks in view and one picture of funds, pledges and upkeep for the board.

  • Volunteer and seva coordinators

    Full rosters for services, community meals and parking, with certified leads and the work spread fairly across the congregation.

  • Religious school principals and youth leaders

    Accurate attendance, teachers and helpers whose checks and training are current, and a clear list of who may collect each child.

  • Buildings and grounds committees

    Air conditioning, plumbing, fire systems and service contracts kept current, so nothing fails on the busiest day of the year.

A day in the life

The story behind the solution

The last week of Ramadan at Willowmere Islamic Center

As the only full-time operations manager at Willowmere Islamic Center, Hana Qureshi answers to the trustees for the prayer halls, the community hall and the weekend school. About 700 households are members, several hundred more families attend without joining, and nearly everything outside Friday prayer runs on volunteers. It is the last week of Ramadan: the community iftar feeds about 350 people every evening, the fundraising dinner is on Thursday, and Eid will fall on Monday or Tuesday, depending on the moon.

  1. Monday, 9:10 a.m.

    A voter list, a new baby and a letter to a man who has died

    The general body meeting after Eid will elect four trustees, and Hana must publish the voter list by Wednesday. Eligibility depends on household membership paid by the cut-off, but the register is a spreadsheet three secretaries have kept in turn. She learns from a thank-you card that the Demir family moved and had a baby this winter. Then Yunus Patel calls: last week's renewal reminder was addressed to his father, Haji Ismail Patel, who died in February, and the family wants to know why the center did not know.

    How this is solved: Household records that keep up with families' lives

  2. Tuesday, 10:30 p.m.

    Four piles of gifts and a shoebox of pledge cards

    After night prayers, Bilal Chaudhry, the treasurer, sits with the counting team over the donation boxes. He still has the lobby card kiosk, online gifts and bank transfers to match, and zakat, zakat al-fitr, the iftar fund and the building fund must stay separate. A batch of online gifts arrived with no fund chosen, and twenty-three monthly gifts failed on expired cards. Thursday's dinner will bring a new round of pledges, while last year's roof pledges sit on cards in a shoebox.

    How this is solved: Designated gifts, pledges and giving statements that add up

  3. Wednesday, 4:30 p.m.

    Four volunteers short, three hours before sunset

    Fatima Diallo, who coordinates volunteers, learns that four of tonight's eighteen iftar volunteers cannot come, including the kitchen lead, the only person on tonight's list with a current food-handler certificate. The women's dining hall has no servers after eight, and the parking team for night prayers is two short. Sign-ups live in two group chats and a shared sheet, so she starts messaging people one by one without knowing who has already served four nights this week.

    How this is solved: Season-long volunteer rosters for the community kitchen and prayers

  4. Thursday, 7:40 a.m.

    A funeral request in the middle of Eid planning

    The Farah family calls: Abdullahi Farah died overnight, and they hope for the funeral prayer after Friday's midday prayer, with burial that afternoon. The washing room needs two trained volunteers, the community hall is booked for the Eid bazaar setup, a nikah is booked in the small hall on Saturday and the imam has a hospital visit on Friday morning. Meanwhile the Eid prayers need the main hall on a day the moon will decide, and every booking lives in a paper diary and on a trustee's phone.

    How this is solved: One booking desk for funerals, weddings, rentals and festival days

  5. Friday, 11:15 a.m.

    The air conditioning fails before the last Friday prayer of Ramadan

    Two hours before the last Friday prayer of Ramadan, the air conditioning in the main prayer hall trips and will not restart. Omar Haddad, who chairs the buildings committee, finds the contractor's number on a sticker and learns the service agreement lapsed in January because the renewal letter went to a former trustee. A faucet in the wudu area, where worshippers wash before prayer, has leaked for two weeks, and the fire alarm inspection is due next month.

    How this is solved: Building upkeep, inspections and service contracts

  6. Saturday, 12:50 p.m.

    A man at the school door who is not on the list

    It is the last weekend school day before the Eid break. Mariam Siddiqui, the principal, has 210 children in 14 classes taught by 26 volunteer teachers and 15 helpers, with attendance on paper registers in a tray. That morning a substitute arrived whose child-safety training had lapsed, and a father asked whether his son had been coming at all. Now, ten minutes before pickup, a man says he is seven-year-old Yasmin's uncle, and the volunteer on the door has no list to check him against.

    How this is solved: Weekend school classes, cleared adults and safe pickup

None of this is unusual; every congregation has its own version of this week, at Christmas, Diwali, Vaisakhi or the High Holy Days. The solution below shows how the same week could run with family news recorded once and handled with care, gifts kept to their funds, rosters filled before sunset, one calendar for every room, a building serviced ahead of the crowds and a school door with a clear list of who may take each child home.

Challenges and how they are solved

6 problems, several products, one connected answer

Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.

Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.

Challenge 1 of 6

Household records that keep up with families' lives

ComradeCircle(opens ComradeCircle in a new tab)Subscriber Bot(opens Subscriber Bot in a new tab)

The problem

The general body meeting after Eid will elect four trustees, and eligibility depends on household membership paid by the cut-off date. The register is a spreadsheet three secretaries have kept in turn. The Demir family moved and had a baby this winter, and the office heard about it from a thank-you card. The Mansour family joined on a paper form that never reached the office. And last week a renewal reminder went to Haji Ismail Patel, who died in February; his son called to ask, quietly, why his own congregation did not know.

What it costs

Families feel unknown by their own congregation, reminders reach the bereaved, and a voter list nobody can verify can turn a routine election into a long dispute.

How the products work together

New families are designed to join online through a New Families group in ComradeCircle, so no paper form goes missing. However news arrives, staff record it once in Subscriber Bot, which keeps track of each household's membership and renewal date, stops reminders to anyone who has died and lists who may vote under the trust's own rules. News is shared only if the family agrees.

How it works — technical detail

Technical detail

New families request to join the New Families circle in ComradeCircle, where the office approves each household online instead of waiting for a paper form and places its members in circles such as Youth, Sisters or Seniors. Each approved household is designed to pass to Subscriber Bot, which holds its membership as a recurring relationship with plan, payment method and renewal date. News reaches the office in many ways, by phone, at the desk or in a circle, and staff record it once on that household record, so reminders to a member who has died are designed to stop there. ComradeCircle is designed to announce a birth or a bereavement only after the family agrees. For elections, Subscriber Bot is designed to list households in good standing on the cut-off date under the trust's own eligibility rules, with the reason shown beside any that are not.

The outcome it is designed for

The household record is designed to change once, when the office hears the news, reminders stop reaching the bereaved, and the voter list rests on payment records the elections committee can check.

The concepts behind it

Challenge 2 of 6

Designated gifts, pledges and giving statements that add up

FluidGrids(opens FluidGrids in a new tab)EventfullyManaged(opens EventfullyManaged in a new tab)Subscriber Bot(opens Subscriber Bot in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

After night prayers on Tuesday, the treasurer sits with the counting team over the donation boxes, then turns to the lobby card kiosk, online gifts and bank transfers. Zakat, zakat al-fitr, the iftar fund and the building fund must be kept apart, yet a batch of online gifts arrived with no fund chosen. Twenty-three monthly gifts failed on expired cards. Last year's roof pledges are on cards in a shoebox, nobody can say who is behind, Thursday's fundraising dinner will add more, and three families have already asked for a statement of this year's gifts.

What it costs

Gifts made for one purpose risk being spent on another, donors lose confidence when statements disagree with their bank records, and the treasurer's evenings go to reconciling instead of stewardship.

How the products work together

Online gifts and bank transfers are designed to be brought in by FluidGrids and matched to households, with unclear ones set aside. EventfullyManaged records each dinner pledge with its fund. Subscriber Bot keeps every household's gifts and pledges by fund, catches failed payments and lists each household's gifts for the treasurer to check and send. BigConsole shows the finance committee every fund. Your accounting system stays in place.

How it works — technical detail

Technical detail

Gifts and payment statuses from the online giving provider and bank transfers are designed to arrive through FluidGrids workflows, matched to households where the reference allows, with unmatched items going to the same queue as undesignated gifts. EventfullyManaged is designed to record each pledge at the fundraising dinner against the guest and the fund, and pass it on as a pledge schedule. Subscriber Bot is designed to extend its recurring-relationship record with a fund on each gift: its giving and pledge desk holds every household's gifts and pledges by fund, flags failed payments and expiring cards, and lists each household's gifts by fund for the treasurer to check against the books and send. FluidGrids workflows are designed to load the desk's records, with the counting team's cash and kiosk totals, into BigConsole data sinks behind a fund-balances console, whose Explain panel is designed to cite the records behind each change. The accounting system stays the book of record.

The outcome it is designed for

Every gift is designed to carry its fund from the moment it is recorded, failed monthly gifts are caught before they lapse, and each household's gift list agrees with what the finance committee sees.

The concepts behind it

Subscriber Bot

Congregation Giving and Pledge Desk

Designed to hold each household's recurring gifts and pledges by fund, catch failed payments and gifts with no fund or household, and list each household's gifts for the treasurer to check.

Works with FluidGrids, EventfullyManaged, BigConsole

Concept pagefor Congregation Giving and Pledge Desk on the Subscriber Bot website (opens in a new tab)

Challenge 3 of 6

Season-long volunteer rosters for the community kitchen and prayers

CrewFoundry(opens CrewFoundry in a new tab)BuildMyIQ(opens BuildMyIQ in a new tab)ComradeCircle(opens ComradeCircle in a new tab)

The problem

Every congregation has a kitchen that runs on a roster: thirty nights of iftar, a weekly langar, a Sunday fellowship lunch. The roster starts the season full and thins by the third week. Sign-ups sit in group chats and a shared sheet, so the coordinator cannot see who has served eleven nights and who has never been asked, whether a sixteen-year-old helper has an adult on the same shift, or whether the one volunteer with a current food-handler certificate is the one who just cancelled. At one gurdwara, the Sunday langar sewa list is rebuilt every week from memory by whoever arrives first to light the stoves.

What it costs

The same few volunteers burn out, gaps appear with hundreds waiting to eat, young helpers end up on shifts without an adult, and nobody can say whether the kitchen lead is certified.

How the products work together

CrewFoundry is designed to keep one roster for the whole season, from the kitchen to parking, showing how many nights each volunteer has served so the load is shared, and flagging young helpers without an adult on the shift. It checks the food-safety certificates recorded in BuildMyIQ. Unfilled shifts are designed to go to the volunteers' group in ComradeCircle, where people accept on their phones.

How it works — technical detail

Technical detail

CrewFoundry, which holds people and skills with shift rosters on its roadmap, is designed to run a season roster: every night or week of the season against every role, from kitchen lead, servers and clean-up to ushers, parking marshals and the livestream desk. Volunteers sign up for themselves or for their household, and the roster is designed to show nights served this season beside each name, so the coordinator asks those who have served least, and to flag a youth volunteer without an adult on the same shift. BuildMyIQ is designed to record each volunteer's food-handler certificate from the approved provider, with its expiry date, and it issues the congregation's own kitchen refresher and child-safety course certificates; the roster is designed to read both before placing a lead. When a gap stays open, CrewFoundry is designed to post a cover request to the Volunteers circle in ComradeCircle, and whoever accepts is placed back on the roster.

The outcome it is designed for

Each night of the season is designed to have a named, qualified lead before the doors open, the load is spread across more households, and the coordinator stops rebuilding the roster in group chats.

The concepts behind it

Challenge 4 of 6

One booking desk for funerals, weddings, rentals and festival days

EventfullyManaged(opens EventfullyManaged in a new tab)CrewFoundry(opens CrewFoundry in a new tab)AssetHandler(opens AssetHandler in a new tab)ComradeCircle(opens ComradeCircle in a new tab)

The problem

In most congregations the room diary is a paper book at the front desk, a trustee's phone and the clergy's own calendar. At one parish, a funeral requested for Thursday morning lands on top of a tutoring club's rental of the parish hall, the wedding rehearsal needs the church the evening before, and nobody can say whether the rental's deposit was paid. Traditions that bury within a day or two turn every such clash into a same-day negotiation: the family waits while staff work out which room is free, whether the priest or imam can be there, who will prepare the body and which booking must move. Festival days add prayers or services on dates that may not be fixed until the night before.

What it costs

Grieving families wait while staff untangle clashing bookings, renters and couples hear of a change at the last minute, and deposits go unrecorded.

How the products work together

EventfullyManaged is designed to put every room and booking, from funerals and weddings to classes and rentals, on one calendar that records deposits, flags clashes, checks the imam or priest is free and puts a funeral first. Each booking is designed to tell CrewFoundry which volunteers it needs and AssetHandler what to set up, and the family decides when the funeral is announced.

How it works — technical detail

Technical detail

EventfullyManaged holds every room as a venue with its capacity: the prayer halls, the community hall, the small hall, the washing room, the kitchen and the classrooms. A congregation hall and ceremony calendar is designed to keep typed bookings, such as funerals, weddings, naming ceremonies, classes and community rentals, each with a family contact, the clergy member involved, expected numbers and any deposit, and to flag clashes as a booking is made, including a clergy member already committed elsewhere. A funeral is designed to be placed first, with the moves it needs proposed to the bookings it displaces. Each confirmed booking is designed to hand its open shifts, such as washing volunteers and ushers, to CrewFoundry and its setup to AssetHandler as a work order, and the funeral time to go out on ComradeCircle's announcements channel only once the family agrees. Festival prayers sit on the same calendar; festival-day crowd planning is covered on the Culture, Heritage & Faith page.

The outcome it is designed for

A grieving family is designed to get a confirmed time and place quickly, from one calendar, and every displaced booking, deposit and setup job is handled in the open instead of by phone.

The concepts behind it

EventfullyManaged

Congregation Hall and Ceremony Calendar

Designed to put every room's funerals, weddings, rentals and classes on one grid with clergy and deposits, flag clashes, place a funeral first and pass each booking's staffing and setup on.

Works with CrewFoundry, AssetHandler, ComradeCircle

Concept pagefor Congregation Hall and Ceremony Calendar on the EventfullyManaged website (opens in a new tab)

Challenge 5 of 6

Building upkeep, inspections and service contracts

AssetHandler(opens AssetHandler in a new tab)Subscriber Bot(opens Subscriber Bot in a new tab)

The problem

Most places of worship keep their equipment history in a folder and a caretaker's memory. Service agreements renew by letter to whoever signed them years ago, so a lapsed contract is discovered on the day a call-out is refused. Failures cluster on the busiest days, when equipment runs hardest: at one church the boiler cut out on the Sunday before Christmas, and the only record of its last service was a handwritten tag on the pipe. Small leaks run for weeks because nobody owns the job, inspection dates are remembered only when a notice arrives, and when the insurer asks when a unit was last serviced, nobody can answer from a record.

What it costs

Hot halls and leaking washrooms land on the busiest days, lapsed contracts turn routine service into emergency call-outs, and trustees cannot show insurers or inspectors what was done.

How the products work together

AssetHandler is designed to keep a record of the building's equipment, from air conditioning and boilers to plumbing and the fire alarm, with servicing scheduled weeks before busy seasons and inspection certificates tracked to their expiry. Subscriber Bot keeps every service agreement and insurance policy with its renewal and notice dates, and warns the buildings committee before one lapses or goes up in price.

How it works — technical detail

Technical detail

AssetHandler holds the building as assets: the rooftop air-conditioning units, boilers, wudu area plumbing, kitchen equipment, the fire alarm panel and the sound system, each with a preventive maintenance schedule and its work order history. Servicing before a festival or a busy month is designed to sit on the maintenance calendar weeks ahead, and the inspection register is designed to show fire alarm, extinguisher and boiler certificates with expiry dates and the work order booked to renew each. Subscriber Bot holds the recurring contracts the building depends on, from the air-conditioning service agreement and fire alarm monitoring to pest control, waste collection and insurance, each with its owner, payment method, next charge and notice date, and is designed to warn the buildings committee before one lapses or renews at a higher price. A lapsed agreement is designed to show on the affected asset in AssetHandler, so the committee knows before calling whether a visit is covered.

The outcome it is designed for

Servicing is designed to happen before the crowds arrive, contracts are flagged before they lapse, and the committee can show an insurer or inspector the service history from one record.

The concepts behind it

Challenge 6 of 6

Weekend school classes, cleared adults and safe pickup

BuildMyIQ(opens BuildMyIQ in a new tab)EventfullyManaged(opens EventfullyManaged in a new tab)ComradeCircle(opens ComradeCircle in a new tab)

The problem

Weekend and evening schools, whether Sunday school, Hebrew school, Punjabi or Gujarati classes, or Quran and Arabic, are run by volunteers with registers on paper. When a parent asks whether a child has been attending, the principal leafs through a tray of sheets. Safeguarding rests on background checks and training that expire at different times and are tracked, if at all, in a coordinator's spreadsheet, and on rules such as two adults in every classroom that nobody can see being kept on a given morning. At one parish Sunday school, a helper's background check lapsed over the summer and nobody noticed until October. And at pickup, the volunteer on the door rarely has a list of who each family has authorized to collect a child.

What it costs

Parents lose confidence when attendance is guesswork, and any doubt about who may teach or collect a child is a gap no congregation, of any tradition, can leave open.

How the products work together

BuildMyIQ is designed to keep the weekend school's classes, attendance and each child's pickup list, and to show whether every adult has a recorded background check and current child-safety training, with two adults in each class. At the door, EventfullyManaged is designed to flag a check-out for anyone not on the list, so the volunteer calls a guardian. Notices reach parents through their ComradeCircle group.

How it works — technical detail

Technical detail

BuildMyIQ runs the weekend school as classes: each one a cohort with its teacher, helpers, room and term dates, and a register the teacher is designed to mark on a phone. Each child's record holds guardians and the adults the family has authorized to collect them. The register is designed to count an adult as cleared only when the office has recorded a background check with its renewal date and the adult's child-safety course certificate, issued in BuildMyIQ, is current; Burdenoff does not run the checks. It is designed to flag a class when someone is not cleared or fewer than two adults are present. At the door, EventfullyManaged's QR check-in kiosk is designed to read the authorized list from BuildMyIQ and flag a check-out for anyone not on it, so the door volunteer follows the school's pickup policy and calls a guardian. Term notices, the Eid break date and end-of-term reports are designed to be posted from BuildMyIQ to the Parents circle in ComradeCircle.

The outcome it is designed for

Every class is designed to start with cleared adults and two in the room, parents can see attendance, and a check-out by anyone the family has not authorized is flagged so the door volunteer calls a guardian.

The concepts behind it

BuildMyIQ

Weekend Faith School Register and Pickup

Designed to keep classes, attendance, each adult's recorded check and training, two adults per class and each child's authorized pickup adults on one register for a volunteer-run school.

Works with EventfullyManaged, ComradeCircle

Concept pagefor Weekend Faith School Register and Pickup on the BuildMyIQ website (opens in a new tab)

How it fits together

From a family's news to the trustees' console, handed on step by step

Follow a household and a busy week through the products. One path keeps families, membership and giving in order; the other turns bookings into staffed, prepared rooms. Each step is one product doing one job and handing a record to the next, and both paths meet in the trustees' console.

  1. To Subscriber Bot: New families and family news, designed to keep membership correct

  2. To FluidGrids: Fund totals and pledges, designed to be collected each night

  3. To CrewFoundry: Who holds a current certificate, designed to be checked first

  4. To CrewFoundry: Volunteers needed and setup jobs, designed to be passed on

  5. To AssetHandler: Named volunteers, designed to be added to each setup job

  6. To FluidGrids: Open repairs, upkeep costs and inspection dates, designed to be collected

  7. To BigConsole: Funds, pledges, volunteer cover and upkeep, refreshed each night

Step 1 of 8: Welcome the family

How each hand-off works — technical detail

Technical detail

  1. 1. ComradeCircle — Welcome the family: New families request to join the New Families circle online, members are placed in circles such as Youth, Parents and Volunteers, and news is announced only when the family agrees.Hands to Subscriber Bot: Each approved household, and the family news the office records, designed to update the household's membership record.
  2. 2. Subscriber Bot — Keep giving to its fund: Holds each household's membership, monthly gifts and pledges by fund, flags failed payments and undesignated gifts, and lists each household's gifts for the treasurer.Hands to FluidGrids: Gift, pledge and membership records by fund, designed to be picked up by FluidGrids workflows each night.
  3. 3. BuildMyIQ — Clear the volunteers: Issues the congregation's own course certificates, is designed to record outside food-handler certificates with expiry dates, and runs the weekend school register.Hands to CrewFoundry: Certificate status and expiry for every volunteer, which the roster is designed to read before placing anyone.
  4. 4. EventfullyManaged — Book the rooms: Keeps the hall and ceremony calendar with clergy, deposits and clashes, places a funeral first, and checks families in and out at the school door.Hands to CrewFoundry: Each confirmed booking's open shifts, designed to arrive in CrewFoundry, and its setup, designed to reach AssetHandler as a work order.
  5. 5. CrewFoundry — Fill the roster: Places qualified volunteers across the season, favoring those who have served least, keeps youth with an adult, and sends unfilled shifts to the Volunteers circle.Hands to AssetHandler: The named setup volunteers, designed to be added to each booking's AssetHandler work order.
  6. 6. AssetHandler — Ready the building: Turns each booking's setup into a work order and keeps air conditioning, plumbing and fire systems serviced and inspected ahead of the busy days.Hands to FluidGrids: Open work orders, upkeep spend and inspection due dates, designed to be picked up by FluidGrids workflows.
  7. 7. FluidGrids — Carry the records: Is designed to bring gifts from the giving provider and bank into Subscriber Bot, and loads giving, volunteer cover and upkeep into BigConsole data sinks on a schedule.Hands to BigConsole: Keyed data sinks for funds, pledges, membership standing, volunteer cover and upkeep, refreshed on a schedule.
  8. 8. BigConsole — Show the trustees: Shows funds, pledges, membership standing, volunteer cover and upkeep on one console for the finance committee and trustees, designed to add cited notes on what changed.

Products in this solution

What each product brings

  • ComradeCircle

    Circles, announcements and member roles

    Gives the congregation its groups, such as new families, youth, parents and volunteers, each with announcements and events, and is designed to carry requests for help and school notices to the right people.

    Technical detail

    Technical detail

    Runs circles with join requests, announcement channels, events and member roles, and is designed to host a congregation's New Families, Youth, Parents and Volunteers circles and to receive cover requests and school notices from the other products.

    Visit ComradeCircleAll concepts

  • Subscriber Bot

    Membership, recurring giving and service contracts

    Keeps track of each household's membership and renewal date, and is designed to keep gifts and pledges by fund and catch failed payments. It also tracks the building's service contracts and insurance so none lapse by surprise.

    Technical detail

    Technical detail

    Models each household membership, monthly gift and pledge as a recurring relationship with plan, payment method and renewal date, is designed to add a fund to each gift, and tracks the building's service agreements and policies.

    Visit Subscriber BotAll concepts

  • FluidGrids

    Carrying gifts and records between products

    Is designed to bring gifts from the online giving provider and the bank into Subscriber Bot each night, and to gather giving, volunteer and building figures for the trustees' view in BigConsole.

    Technical detail

    Technical detail

    Runs scheduled and webhook-started workflows with payment and service connectors and a BigConsole DataSink node, and is designed to bring gifts from the giving provider into Subscriber Bot and fill the trustees' console.

    Visit FluidGridsAll concepts

  • EventfullyManaged

    Hall calendar, bookings and door check-in

    Is designed to put every room and booking on one calendar that flags clashes and puts a funeral first, and it runs fundraising dinners and checks families in and out at the school door.

    Technical detail

    Technical detail

    Models rooms with capacities, conflict checks for rooms and speakers, fundraising pledges and QR check-in, and is designed to add a congregation hall and ceremony calendar and school-door check-in.

    Visit EventfullyManagedAll concepts

  • CrewFoundry

    Season volunteer rosters and cover

    Is designed to keep one roster for every volunteer job across a season, show the gaps, check certificates and suggest who could step in, favoring people who have served least.

    Technical detail

    Technical detail

    Holds people and skills, with shift rosters on its roadmap, and is designed to run a congregation's season volunteer roster with nights served, youth-with-adult checks, certified leads and cover requests.

    Visit CrewFoundryAll concepts

  • BuildMyIQ

    Weekend school and volunteer training

    Is designed to run the weekend school's classes, attendance and pickup lists, show whether each adult is cleared, and issue the congregation's own training certificates that the volunteer roster checks.

    Technical detail

    Technical detail

    Runs classes as cohorts and issues course certificates with expiry dates, and is designed to record outside food-handler certificates and add a weekend school register with attendance, clearance and each child's authorized pickup adults.

    Visit BuildMyIQAll concepts

  • AssetHandler

    Building maintenance and inspections

    Keeps a record of the building's equipment, schedules servicing before busy seasons and tracks inspection certificates, and is designed to turn each booking's setup into a job with a named person.

    Technical detail

    Technical detail

    Keeps the building's equipment as assets with preventive maintenance schedules, work orders and an inspection register, and is designed to take setup work orders from the hall calendar.

    Visit AssetHandlerAll concepts

  • BigConsole

    Finance committee and trustee console

    Is designed to give the treasurer, finance committee and trustees one view of funds, pledges, membership, volunteers and upkeep, open only to the people allowed to see it, with plain notes on what changed.

    Technical detail

    Technical detail

    Builds governed consoles from data sinks that FluidGrids workflows fill, and is designed to add cited Explain notes and to show fund balances, pledges, membership standing, volunteer cover and upkeep for the finance committee and trustees.

    Visit BigConsoleAll concepts

One platform underneath: Burdenoff Workspaces

Every product here runs on Burdenoff Workspaces, so staff, trustees and volunteers sign in once, each sees only what their role allows, every change lands in one audit trail, and the congregation receives one bill across whichever products it uses.

Concept gallery

Every concept in this solution

16 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.

Pitch kit

The Faith & Community solution in one minute

Congregations run on trust, volunteers and a handful of staff, with records scattered across spreadsheets, paper diaries and group chats. Burdenoff brings membership and giving, volunteer rosters, the hall calendar, the weekend school and building upkeep onto one workspace, with products designed to hand records to each other. It is designed so the office records family news once, every gift stays with its fund, rosters fill in time, and trustees see funds and risks in one place.

  • New families join online, with news such as a birth or a bereavement designed to be recorded once and announced only with the family's agreement
  • Monthly gifts and pledges kept by fund, whether building, relief or zakat, with failed payments caught and gifts listed by fund for the treasurer
  • One season roster for kitchens, ushers and parking, with certified leads and cover requests designed to go to the volunteers circle
  • One hall calendar designed to put a funeral first, record deposits and check that clergy are free before a booking is confirmed
  • A school register with recorded checks, two adults per class and pickup checks, and a building serviced before the busy days
Email it

Questions

Frequently asked

Does this work for churches, temples, gurdwaras and synagogues, not only mosques?

Yes. The story follows an Islamic center, but each congregation sets its own funds, volunteer roles, rooms and ceremony types, so a parish, temple, gurdwara or synagogue can work the same way. Setup is done by configuring the products, not by building anything custom.

Technical detail

Technical detail

Yes. The illustrative story follows an Islamic center, but nothing in the products is tied to one tradition. Each congregation configures its own funds, volunteer roles, rooms and ceremony types: a parish can track a stewardship campaign and a fellowship lunch roster, a temple its festival sponsorships and prasadam kitchen, a gurdwara its langar sewa and Gurpurab programs. The products are offered under their own names and are configured, not customized.

Does Burdenoff replace our accounting system or our online giving provider?

No. Your bookkeeping and giving providers stay in place. Subscriber Bot keeps each household's gifts and pledges by fund, and BigConsole gives the finance committee a view to check against the books. Rules on how funds may be used stay with your trustees and advisers.

Technical detail

Technical detail

No. Burdenoff is not fund-accounting software or a payment processor. Your bookkeeping system remains the book of record, and your card, bank and online giving providers keep processing gifts. Subscriber Bot is designed to hold each household's gifts, pledges and membership by fund, and BigConsole is designed to give the finance committee a shared view to check against the books. The products do not give tax, legal or religious guidance on how funds may be used; those rules stay with your trustees and advisers.

How is family and member information kept private?

The office keeps household records, and each person sees only what their role allows, so a volunteer coordinator sees the roster, not giving. Members control their own profile, and news such as a death is shared only with the family's agreement.

Technical detail

Technical detail

Household records are held by the congregation's office, and Burdenoff Workspaces gives each person access by role, so a volunteer coordinator sees the roster but not giving records, and every change is recorded in one audit trail. Members control their own ComradeCircle profile and whether others can find them. Sensitive news such as a death is designed to be announced only with the family's agreement, and background checks are run by the congregation's chosen provider, with the school register designed to hold only the result and its renewal date.

Do we need all eight products to get started?

No. Start where it hurts most: giving and pledges (Subscriber Bot with BigConsole), the volunteer roster (CrewFoundry with ComradeCircle) or the hall calendar (EventfullyManaged). Everything shares one sign-in and one set of roles, so adding a product later means no new logins.

Technical detail

Technical detail

No. Most congregations start where the pain is sharpest: giving and pledges (Subscriber Bot with FluidGrids and BigConsole), the volunteer roster (CrewFoundry with ComradeCircle), or the hall calendar (EventfullyManaged). Because every product shares one Burdenoff Workspaces sign-in, set of roles and audit trail, adding another later does not mean new logins or new staff accounts, and it is designed to pick up households through the same hand-offs shown above.

Can volunteers, teachers and families use it on their phones?

Yes. Volunteers are designed to pick their nights and accept cover on a phone, teachers to mark the register on a phone, and members to follow announcements on mobile. The check-in kiosk at the school door runs on a tablet.

Technical detail

Technical detail

Yes, that is the design intent. Volunteers are designed to pick their nights and accept cover requests on a phone, teachers to mark the class register on a phone, and members to join circles and follow their announcements on mobile. The check-in kiosk at the school door runs on a tablet.

Is this available today?

Not yet. The products are pre-launch, and this page shows how they are designed to work together. Some connections between products are planned rather than finished. We can walk you through what exists today and what is coming.

Technical detail

Technical detail

Not yet. Burdenoff's products are pre-launch, and this page describes a solution concept: how they are designed to work together for congregations and community trusts. Several hand-offs between products shown here are design intent rather than finished connections. We are glad to walk through what exists today and what is on the roadmap.

Related domains

Where these products also work together

All domains

Want to explore this for your organization?

Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.

Talk to usBrowse every domain

This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.