About

Built for the person who rebuilds the rota every month.

ChapelHQ is one place for your people, rotas, children’s check-in, attendance and giving records — built in Malaysia, for churches of up to 1,500 people. Thirty days free, then RM 29 to RM 99 a month for the whole church, and we set it up with you.

How it gets this way, and what changes

It starts with one file, and it is immaculate, because one person made all of it and knows what every column means. Then youth ministry needs its own, because half those names are not members yet. Somebody takes the rota off the pastor and builds it the way they build things. A children’s worker keeps allergies in a notebook, because a notebook is what is on the desk when a parent tells you something at the door. And the treasurer’s giving record has never been on the same machine as any of it — which is correct. It should not be.

Not one of those is somebody doing it wrong. Every file exists because a person stepped in and took something on, and the cost of that never arrives while it is being built — it arrives later, all at once, on the Saturday night when the sound desk is still empty and nobody can remember who said yes; on the Sunday an adult nobody recognises comes to collect a child; in the fortnight after the person who knew everything moves away.

ChapelHQ is one place to put all of it. Your people and households, the serving rotas, children’s check-in, attendance, groups, events, room bookings, and a record of the giving the church has already received — one database instead of six files, with a name against who wrote what. Check-in prints a tag with a six-digit code, and the code is checked against the authorised pickup list when the child is collected.

In your month, it means this. Next month’s rota starts from last month’s instead of a blank sheet, and auto-fill skips anyone who has already said they cannot make that Sunday. You publish once; every person on it gets their own dates by email, opens them on their phone with no password and nothing to install, and taps confirm or decline. The slots nobody has taken show as a count on Tuesday rather than a discovery on Sunday morning. Tell the WhatsApp group as well, as you always have — what changes is that the answer no longer lives only in the group, or only in your head.

We grew up in churches here. The Saturday-night rota scramble and the WhatsApp thread nobody answers are not a market we researched — they are what we watched our own churches live with, for years, and what we got tired of watching.

So this is a small independent team in Malaysia, funded by the churches that use ChapelHQ rather than by investors with a growth target. That is why churches are taken on one at a time and set up by hand, and why the person who replies to your email is one of the people who writes the software.

You may not be the person who decides this. If it has to go to a pastor or an elder board, the case is short: RM 29 to RM 99 a month for the whole church depending on size, thirty days free before any invoice, no card form at any point, and everything exports to CSV from inside the app if the church ever decides to leave. What is otherwise on offer is a spreadsheet, or a British or American system priced for a congregation three times the size and built for a country with different assumptions about how Sunday runs. Send them this page, or send us the questions they will ask and we will answer them in writing.

THE FACTS, PLAINLY

  • One place. People, rotas, children’s check-in, attendance and giving records in one database, not six files.
  • Set up with you. Your existing records moved across, your first rotas built alongside your team. One church at a time, by hand.
  • RM 29 to RM 99 a month for the whole church, by congregation size — not by how many people log in. Paid for by the churches that use it, not by investors.
  • Thirty days free, then an invoice. No card form at any point.
  • Your data, under Malaysian law. Full CSV export from inside the app, whenever you want it.

What this software believes

Sent to 0 people · 1 had no email on file

Kids Church · Sun 16 Aug · nobody was notified.

WHAT CHAPELHQ REPORTS AFTER A SEND

Report what actually happened

Publish a rota and ChapelHQ reports exactly what left the building: how many people were notified, and who could not be reached. Most software shows “Sent” and moves on. An office needs the real number, because the member who was never told is the member who does not turn up.

The same standard runs through the product: counts you can act on, records that name who did what, and limits published rather than buried.

Who it’s for

Churches of up to 1,500 people, in Malaysia, running Sunday services with member teams — often more than one service, often in more than one language, usually with a children’s programme, and usually one administrator holding it together: part-time, or a member who started helping and never stopped.

The clearest sign it is time is not the size of the church. It is how many people have to be asked before anyone knows who is on sound this Sunday.

If a spreadsheet is genuinely working for you, we will say so. If you are a multi-site network wanting consolidated reporting across churches, that does not exist here.

Where it is right now

We are taking churches on one at a time. Each one gets its existing records imported, its first rotas built alongside its team, and a direct line to the people who write the software. That is slower than signing up on a form, and it is the reason none of the moving-across lands on you to work out alone.

We don’t publish our churches’ names or solicit quotes from them. Judge the software instead: the full feature list is public, and a screen share takes half an hour — come on your own first, if you would rather see it before you have to explain it to anyone.

Tell us about your Sundays.

How many people, how many services, and which part of the admin takes the most time. A person reads every enquiry, and replies within three working days.

Start your thirty days free